Bug#919170: [Piuparts-devel] Bug#919170: Please update dependency to python3-debianbts

[Holger Levsen]

On Fri, Aug 23, 2019 at 09:36:12PM -0400, Sandro Tosi wrote:
> Hey Holger,
> 
> On Sun, 13 Jan 2019 14:02:53 + Holger Levsen  
> wrote:
> > piuparts has a python2 codebase. Help porting it to python3 would be
> > much appreciated.
> 
> i see there's been some activities in the repo about porting piuparts
> to py3k, f.e. 
> https://salsa.debian.org/debian/piuparts/commit/336d7650927f883db6abe2a6783bd88ed953acc9
> -- any idea if there's an upload expected soon? that would help
> dropping python-debianbts (piuparts is its only rdep) which would then
> free python-pysimplesoap.

someone needs to test the master branch and confirm it still works on
buster *and* sid. once that has happened, I'll upload to sid.

the master branch should be ready for python3 thanks to zigo's work.

i'll try to get this done ASAP, which likely will translate to september.
as usual, help is very welcome.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#930993: blhc: false positives with Python setuptools compile_catalog

[Simon Ruderich]

On Mon, Jun 24, 2019 at 09:53:37AM +0100, Simon McVittie wrote:
>> 487:NONVERBOSE BUILD: compiling catalog tap/locale/ja/LC_MESSAGES/tappy.po 
>> to tap/locale/ja/LC_MESSAGES/tappy.mo
>> 488:NONVERBOSE BUILD: compiling catalog tap/locale/nl/LC_MESSAGES/tappy.po 
>> to tap/locale/nl/LC_MESSAGES/tappy.mo
> (etc.)
>
> I think this should be treated as a false positive: this is not a C
> compiler or similar.

Hello Simon,

sorry for the late reply. Should be fixed in 0798b6d ("Fix false
positive in non-verbose check for python setuptools", 2019-08-24)
[1].

Regards
Simon

[1]: 
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=0798b6d8fc65dd5fe2a975789dea153a96dcac89
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#931659: transition: rm python2

[Matthias Klose]

On 21.08.19 21:40, Matthias Klose wrote:
> On 09.07.19 17:50, Matthias Klose wrote:
>> On 09.07.19 00:31, Scott Kitterman wrote:
> 
> could somebody fix the py2-removal tracker again? replacing the terminating \b
> chars with \s (4 times)?  currently it matches all python-* (python-gi-dev,
> python-*-doc, ...) I think we are better with a smaller set

that was too much, now not matching a package name followed by a comma.
attaching the two lines, and using [\s,] for the delimiter.

> this removes around 2000 matches, and obviously is missing some dependencies,
> but the current tracker has too many false positives.  Or we create another
> tracker with this change.
> 
> Interesting thing found: python-gi-dev depends on both python2 and 3 packages 
> ...


is_affected = .depends ~ 
/\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)[\s,]/
 | .build-depends ~ 
/\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)[\s,]/;
is_bad = .depends ~ 
/\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)[\s,]/
 | .build-depends ~ 
/\s(python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|python2|python2-minimal|python2-dev|libpython2-dev|libpython2-stdlib|python2-doc|python2-dbg|libpython2-dbg|python2.7|libpython2.7-stdlib|python2.7-minimal|libpython2.7-minimal|libpython2.7|python2.7-examples|python2.7-dev|libpython2.7-dev|libpython2.7-testsuite|idle-python2.7|python2.7-doc|python2.7-dbg|libpython2.7-dbg)[\s,]/;

Bug#935582: dahdi: dahdi_genconf fail with .../spantype: No such file or directory

[Petter Reinholdtsen]

[Tzafrir Cohen]
> I believe that this is https://bugs.debian.org/cgi-bin/916577 .
>
> Could you please test this with the Bullseye package (I believe you
> should be able to install it as-is on the Buster system)?

I tested with dahdi_3.0.0-1_amd64.deb, and the 'cat' error is gone, but
I still do not get any valid configuration:

# dahdi_hardware 
pci::01:05.0 wctdm+   e159:0001 Wildcard TDM400P REV I
# dahdi_genconf -
Default parameters from /etc/dahdi/genconf_parameters
Empty configuration -- no spans
Generating /etc/dahdi/assigned-spans.conf
Empty configuration -- no spans
Generating /etc/dahdi/system.conf
Empty configuration -- no spans
Generating /etc/asterisk/dahdi-channels.conf
#

-- 
Happy hacking
Petter Reinholdtsen

Bug#935630: devscripts: documentation for --rebuild is incorrect

[David Bremner]

Package: devscripts
Version: 2.19.6
Severity: minor

User: devscri...@packages.debian.org
Usertags: debchange

The doc claims it will add a "buildXX" suffix, but that seems to be
only enabled in Ubuntu

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBUILD_DPKG_BUILDPACKAGE_OPTS="-i"
DEBUILD_SET_ENVVAR_DH_ALWAYS_EXCLUDE="CVS:.svn"
DEBCHANGE_RELEASE_HEURISTIC=changelog

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages devscripts depends on:
ii  dpkg-dev   1.19.7
ii  fakeroot   1.23-1
ii  file   1:5.37-5
ii  gnupg  2.2.17-3
ii  gnupg2 2.2.17-3
ii  gpgv   2.2.17-3
ii  libc6  2.28-10
ii  libfile-homedir-perl   1.004-1
ii  libfile-which-perl 1.23-1
ii  libipc-run-perl20180523.0-1
ii  libmoo-perl2.003004-2
ii  libstring-shellquote-perl  1.04-1
ii  libwww-perl6.39-1
ii  patchutils 0.3.4-2+b1
ii  perl   5.28.1-6
ii  python33.7.3-1
ii  sensible-utils 0.0.12
ii  wdiff  1.2.2-2+b1

Versions of packages devscripts recommends:
ii  apt 1.9.1
ii  at  3.1.23-1+b1
ii  curl7.65.3-1
ii  dctrl-tools 2.24-3+b1
ii  debian-keyring  2019.07.26
ii  dput-ng [dput]  1.28
ii  equivs  2.2.0
ii  libdistro-info-perl 0.21
ii  libdpkg-perl1.19.7
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.048-1
ii  libgitlab-api-v4-perl   0.20-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.07-2
ii  libsoap-lite-perl   1.27-1
ii  libtry-tiny-perl0.30-1
ii  liburi-perl 1.76-1
ii  licensecheck3.0.31-3
ii  lintian 2.18.0
ii  man-db  2.8.6.1-1
ii  patch   2.7.6-6
ii  python3-apt 1.9.0
ii  python3-debian  0.1.35
ii  python3-magic   2:0.4.15-2
ii  python3-requests2.21.0-1
ii  python3-unidiff 0.5.5-2
ii  python3-xdg 0.25-5
ii  strace  4.26-0.2
ii  unzip   6.0-25
ii  wget1.20.3-1+b1
ii  xz-utils5.2.4-1

Versions of packages devscripts suggests:
ii  adequate  0.15.2
ii  autopkgtest   5.10
pn  bls-standalone
ii  bsd-mailx [mailx] 8.1.2-0.20180807cvs-1+b1
ii  build-essential   12.6
pn  check-all-the-things  
pn  cvs-buildpackage  
ii  debhelper 12.5.3
pn  devscripts-el 
pn  diffoscope
pn  disorderfs
ii  dose-extra5.0.1-14
pn  duck  
pn  faketime  
ii  gnuplot-qt [gnuplot]  5.2.6+dfsg1-2
pn  how-can-i-help
ii  libauthen-sasl-perl   2.1600-1
ii  libdbd-pg-perl3.9.1-1
ii  libfile-desktopentry-perl 0.22-1
pn  libnet-smtps-perl 
pn  libterm-size-perl 
ii  libtimedate-perl  2.3000-2
pn  libyaml-syck-perl 
ii  mailutils [mailx] 1:3.5-3
pn  mozilla-devscripts
ii  mutt  1.10.1-2.1+b1
ii  openssh-client [ssh-client]   1:8.0p1-4
ii  piuparts  1.0.1
ii  postgresql-client-11 [postgresql-client]  11.5-1
ii  quilt 0.65-3
pn  ratt  
pn  reprotest 
pn  svn-buildpackage  
pn  w3m   

-- no debconf information

Bug#935632: libreoffice-l10n-in should recommend libreoffice-l10n-kn and libreoffice-l10n-ne

[Jonas Smedegaard]

Package: libreoffice-l10n-in
Version: 1:6.3.0-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binary package libreoffice-l10n-in is missing these packages for
languages spoken in India:

libreoffice-l10n-kn

libreoffice-l10n-ne


Kind regards,

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl1hd28ACgkQLHwxRsGg
ASHTkw/7B5hXRoqMrZ3XzMVP/I9N9PhzDltF2qVTQZY9XdeS+TBDA0SuAiGwS4rl
dM8kAU8tON0jrawfYfdAIVwquABsna5aqx29YshZumgHBENuL+bf5UVhgLZeK+YB
Q26B7WGOHKjy4R3Mr1DsI1gn2W38ItE35QieH/4gCIQhRmWP4ZUg7RvbampS6SQN
Q6Mf4KX/OqxjDiRwwzJOggSQPJXEBe3MtPGkfiOMxBaX1uUDczpYgMlf+SeaJPbw
L8lFUMBvnWuTLf+eL6hTbK9SkpQjeJaeBYApmluV/PwIvDpKQszBPS335AnCxxYz
5M02R9dY8jyrc0GS7DbIdwY4DEmknRDNj9nVroWq8DUL8dy+5L9V7kmYMPoZCuDZ
PVCckUGaMikogLaeDkYvkbKxkoNQvRYddxEMpQgK74tqa6ZgjX9C68EeBXDSc+Wd
rbANQpyfIgwI0tLyUsldMzqohfSjyMSuzA3Ar4D377C0NBTmDUEu622nNqBsGooR
hUG5DnOVzYTpGLpCQxPBpNnxbKHA5nFy916m2PzwnXxcT1UvSXQQeltdeHAc4qC9
wW1is2xOKQSl49H58tyhziNDEHsnAAe4lWhB0VitXUpQ7NPo1OfTEBGkw6Kgc3xs
QpYjuTnyI4pT94Y/KZuxmeAOsF7UaVVv6/j3DIN2ly56lGEOBu0=
=kqT+
-END PGP SIGNATURE-

Bug#935639: Abandoned upstream

[David Prévot]

Package: phpunit-dbunit
Version: 4.0.0-2
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

Since this PHPUnit extension is abandoned upstream and nothing depends
on it in Debian, there is a priori little point to keep this package in
the next stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 
'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phpunit-dbunit depends on:
ii  php-common2:69
ii  php-symfony-yaml  4.3.3+dfsg-3
ii  php-xml   2:7.3+69
ii  php7.3-xml [php-xml]  7.3.8-1
ii  phpunit   8.2.4-1

phpunit-dbunit recommends no packages.

phpunit-dbunit suggests no packages.


signature.asc
Description: PGP signature

Bug#935641: ITP: lazydocker -- The lazier way to manage everything docker

[Dawid Dziurla]

Package: wnpp
Severity: wishlist
Owner: Dawid Dziurla 

* Package name: lazydocker
  Version : 0.7-1
  Upstream Author : Jesse Duffield
* URL : https://github.com/jesseduffield/lazydocker
* License : Expat
  Programming Lang: Go
  Description : The lazier way to manage everything docker

 A simple terminal UI for both docker and docker-compose, written
 in Go with the gocui (https://github.com/jroimartin/gocui) library.
 .
 Memorising docker commands is hard. Memorising aliases is slightly
 less hard. Keeping track of your containers across multiple terminal
 windows is near impossible. What if you had all the information
 you needed in one terminal window with every common command
 living one keypress away (and the ability to add custom commands
 as well). Lazydocker's goal is to make that dream a reality.

Project is relatively new, but has developed rapidly in recent months
and I think it would be nice to have this program packaged in Debian.

Bug#935004: cups-filters: print test page problem solved by upgrading to github version (1.25.1)

[frederik]

I'm so sorry I will try to get around to that today

On Sat, Aug 24, 2019 at 08:21:21PM +0100, Brian Potkin wrote:

tags 935004 moreinfo
thanks


On Sun 18 Aug 2019 at 17:27:29 +0200, Didier 'OdyX' Raboud wrote:


I have just uploaded 1.25.2 to Debian unstable; could you try this version,
from the Debian repos?


Any news?

Cheers,

Brian.

Bug#875208: [tora] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Aug 24, 2019 at 10:12:34PM +0200, Michael Meskes wrote:
> > > It's now the last one, so if I don't hear back soon that someone
> > > intends to 
> > > upgrade this to Qt5, I'll file for the rm.
> > 
> > Adding the primary uploader to CC.
> 
> I'm not using the tool anymore, nor do I have time to take care of it.
> The only reason why I didn't orphan it, is that somebody inb the group
> might be willing to, but apparently not. So in short, go ahead.

Ack, I've just filed a removal bug.

Cheers,
Moritz

Bug#935658: RM: tora -- RoQA; Depends on qt4, unmaintained

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove tora. While it's ported to Qt5 upstream, the current
maintainer doesn't use it any longer and the current version in the
archive still relies on Qt4, which is scheduled for removal.

Cheers,
Moritz

Bug#935598: mpirun has detected an attempt to run as root. (Was: Bug#935598: phyml: autopkgtest regression: gzip: *.gz: No such file or directory)

[Andreas Tille]

Hi,

the issue with gzip is fixed in Git.  However I'm running into a
new issue

-- 
http://fam-tille.de

Bug#700870: building eapol_test

[Terry Burton]

Hi,

With eapol_test missing from Debian it is irksome to extend the
autopkgtests for the freeradius package to include testing of EAP
methods, and there are some good reasons to include such tests.

I have refreshed Matthew Newton's earlier patch against the latest
packaging source for wpa, and attached...

I've experienced no issues with building eapol_test from the upstream
repository over the last few years and this utility has been included
in the wpa_supplicant package of most RPM-based distributions for some
time. The utility is frequently used by those implementing AAA systems
and the upstream author is very responsive so I think that concerns
about the build quality of the tool are no longer founded.

Please could you review the decision to accept this patch to build an
eapol_test package (or roll it into the wpa_supplicant package)?


Many thanks,

Terry
diff --git a/debian/config/wpasupplicant/kfreebsd b/debian/config/wpasupplicant/kfreebsd
index 9bfc129..51834ad 100644
--- a/debian/config/wpasupplicant/kfreebsd
+++ b/debian/config/wpasupplicant/kfreebsd
@@ -191,7 +191,7 @@ CONFIG_HT_OVERRIDES=y
 CONFIG_VHT_OVERRIDES=y
 
 # Development testing
-#CONFIG_EAPOL_TEST=y
+CONFIG_EAPOL_TEST=y
 
 # Select control interface backend for external programs, e.g, wpa_cli:
 # unix = UNIX domain sockets (default for Linux/*BSD)
diff --git a/debian/config/wpasupplicant/linux b/debian/config/wpasupplicant/linux
index c12c17e..8be0243 100644
--- a/debian/config/wpasupplicant/linux
+++ b/debian/config/wpasupplicant/linux
@@ -191,7 +191,7 @@ CONFIG_HT_OVERRIDES=y
 CONFIG_VHT_OVERRIDES=y
 
 # Development testing
-#CONFIG_EAPOL_TEST=y
+CONFIG_EAPOL_TEST=y
 
 # Select control interface backend for external programs, e.g, wpa_cli:
 # unix = UNIX domain sockets (default for Linux/*BSD)
diff --git a/debian/control b/debian/control
index fa5e3d8..b43a30b 100644
--- a/debian/control
+++ b/debian/control
@@ -97,3 +97,13 @@ Description: Client support for WPA and WPA2 (IEEE 802.11i)
  association with IEEE 802.11i networks.
  .
  This is a udeb of wpasupplicant for use by the debian-installer.
+
+Package: eapoltest
+Architecture: any
+Depends: ${shlibs:Depends},
+ ${misc:Depends}
+Description: EAPoL testing utility
+ eapol_test allows testing EAP authentication methods without using
+ a full 802.1X connection. It is frequently used to test the EAP
+ configuration of RADIUS systems. It is an administrator tool and not
+ required for standard 802.1X authentication.
diff --git a/debian/eapoltest.install b/debian/eapoltest.install
new file mode 100644
index 000..d3fe2c3
--- /dev/null
+++ b/debian/eapoltest.install
@@ -0,0 +1 @@
+wpa_supplicant/eapol_test usr/bin/
diff --git a/debian/eapoltest.lintian-overrides b/debian/eapoltest.lintian-overrides
new file mode 100644
index 000..45ffdbc
--- /dev/null
+++ b/debian/eapoltest.lintian-overrides
@@ -0,0 +1,6 @@
+# We distribute the package under the terms of the BSD license due to the
+# openssl issue, tell lintian to not complain:
+eapoltest: possible-gpl-code-linked-with-openssl
+
+# These are numerous and unlikely to be fixed anytime soon, filter them out.
+eapoltest: hyphen-used-as-minus-sign
diff --git a/debian/eapoltest.manpages b/debian/eapoltest.manpages
new file mode 100644
index 000..1c02297
--- /dev/null
+++ b/debian/eapoltest.manpages
@@ -0,0 +1 @@
+wpa_supplicant/doc/docbook/eapol_test.8
diff --git a/debian/rules b/debian/rules
index 9f68be3..8b15405 100755
--- a/debian/rules
+++ b/debian/rules
@@ -56,6 +56,9 @@ override_dh_auto_build:
 	dh_auto_build --sourcedirectory=hostapd \
 	  --buildsystem=makefile
 	dh_auto_clean --sourcedirectory=src --buildsystem=makefile
+	# build eapol_test
+	dh_auto_build --sourcedirectory=wpa_supplicant \
+	  --buildsystem=makefile -- eapol_test
 
 override_dh_auto_clean:
 	dh_auto_clean --sourcedirectory=wpa_supplicant/doc/docbook \
@@ -91,6 +94,7 @@ override_dh_installchangelogs:
 	dh_installchangelogs --package=hostapd hostapd/ChangeLog
 	dh_installchangelogs --package=wpasupplicant wpa_supplicant/ChangeLog
 	dh_installchangelogs --package=wpagui wpa_supplicant/ChangeLog
+	dh_installchangelogs --package=eapoltest wpa_supplicant/ChangeLog
 ### end dh overrides
 
 %:

Bug#935666: RM: kde4libs -- RoQA; Obsolete libs (Qt4)

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Everything that builds againt kde4libs either has been removed or has a
pending rm bug, so it's time for kde4libs.

Scott K

Bug#935665: RM: kde-l10n -- RoQA; Obsolete libs (Qt4)

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

All kde4libs rdepends have either been removed or have pending rm
requests, so it is time for kde-l10n to go as well.

Scott K

Bug#935004: cups-filters: print test page problem solved by upgrading to github version (1.25.1)

[frederik]

Sorry for the delay, I just ran 'sudo apt-get update' and 'sudo apt-get remove 
cups-filters' and 'sudo apt-get install cups cups-filters hplip 
printer-driver-gutenprint printer-driver-hpcups' and I saw that it is trying to 
install the same version of cups-filters as I had reported the bug in. Can you 
explain how I should install the version you uploaded to Debian Unstable? I 
don't often use Debian so I am not familiar with this process.

Also, is there a reason why you think the new version would fix the problem? 
Perhaps since my time is limited and no one else has reported this bug, we 
should regard it as a potential misconfiguration, or an issue that may have 
arisen from my trying to install and then uninstall the Github cups-filters 
package as I explained in my original report.

Thanks!

On Sun, Aug 18, 2019 at 05:27:29PM +0200, Didier 'OdyX' Raboud wrote:

Le dimanche, 18 août 2019, 01.13:46 h CEST frede...@ofb.net a écrit :

Package: cups-filters
Version: 1.21.6-5
Severity: normal

(resending due to email problems on Pi)

Dear Maintainer,

I get the following error when trying to print a test page on my inkjet (via
the web interface):

Print Test Page
Print Test Page HP_Photosmart_Plus_B210_series Error

Unable to print test page:

Unsupported format "text/plain".

I will try to attach the PPD.

The software works fine when I install the latest version of cups-filters
from GitHub. Here is something from error log


I have just uploaded 1.25.2 to Debian unstable; could you try this version,
from the Debian repos?

Cheers,
   OdyX

Bug#935667: RM: pyside-tools -- RoQA; Obsolete libs (Qt4/Python2), unmaintained, replaced for pyside2

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Blocking the removal of pyside, which will shortly be the last blocker
for removal of qtwebkit.

Scott K

Bug#935670: gamemode: Unable to set the 'CPU govenor' and 'GPU Optimisations'

[Robert]

Package: gamemode
Version: 1.5~git20190722.4ecac89-1
Severity: normal
Tags: upstream

Dear Maintainer,

gamemode is not able to set the 'CPU govenor' and 'GPU Optimisations'.


Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Adding game: 4836
[/usr/bin/env]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Entering Game Mode...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: governor was initially set
to [powersave]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Requesting update of
governor policy to performance
Aug 25 05:29:21  gamemoded[4352]: Error accessing
/usr/libexec/cpugovctl: No such file or directory
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: External process failed
with exit code 127
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Output was:
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Failed to update cpu
governor policy
Aug 25 05:29:21  /usr/bin/gamemoded[4838]: Failed to execute external
process: /usr/libexec/gpuclockctl No such file or directory
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: External process failed
with exit code 1
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Output was:
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Failed to call
gpuclockctl, could not get values!
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Requesting GPU
optimisations on device:1
Aug 25 05:29:21  gamemoded[4352]: Error accessing
/usr/libexec/gpuclockctl: No such file or directory
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: External process failed
with exit code 127
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Output was:
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Failed to call
gpuclockctl, could not apply optimisations!
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Addition requested for
already known client 4836 [/usr/bin/env].
-- This may happen due
to using exec or shell wrappers. You may want to
-- blacklist this
client so GameMode can see its final name here.
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Adding game: 4842
[/usr/bin/xargs]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4842,4842]: ioprio was (0) but we expected (4)
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Adding game: 4843
[/bin/readlink]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4843,4843]: ioprio was (0) but we expected (4)
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Removing game: 4843
[/bin/readlink]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Removing game: 4842
[/usr/bin/xargs]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Adding game: 4844
[/usr/bin/dirname]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4844,4844]: ioprio was (0) but we expected (4)
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Removing game: 4844
[/usr/bin/dirname]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Adding game: 4845
[/bin/chmod]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4845,4845]: ioprio was (0) but we expected (4)
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Removing game: 4845
[/bin/chmod]
Aug 25 05:29:21  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Adding game: 4846
[/mnt/M4-CT256M4SSD2/spiele/steamapps/common/Tropico
6/Tropico6/Binaries/Linux/Tropico6-Linux-Shipping]
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4846,4846]: ioprio was (0) but we expected (4)
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Adding game: 4861
[/bin/dash]
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4861,4861]: ioprio was (0) but we expected (4)
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Adding game: 4862
[/bin/dash]
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:22  /usr/bin/gamemoded[4352]: Skipping ioprio on client
[4862,4862]: ioprio was (0) but we expected (4)
Aug 25 05:29:26  /usr/bin/gamemoded[4352]: Removing expired game
[4862]...
Aug 25 05:29:26  /usr/bin/gamemoded[4352]: Removing game: 4862
[/bin/dash]
Aug 25 05:29:26  /usr/bin/gamemoded[4352]: Setting ioprio value...
Aug 25 05:29:26  /usr/bin/gamemoded[4352]: Could not inspect tasks
for client [4862]! Skipping ioprio optimisation.
Aug 25 05:29:26  /usr/bin/gamemoded[4352]: Removing expired game
[4861]...
Aug 25 05:29:26  /usr/bin/gamemoded[4352]: Removing game: 4861

Bug#935672: librust-backtrace+addr2line-dev/amd64 unsatisfiable Depends: librust-addr2line-0.9+std-dev

[Steve Langasek]

Source: rust-backtrace
Version: 0.3.34-1
Severity: serious
Affects: src:rust-addr2line
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

The rust-backtrace package depends on a newer rust-addr2line than is
available in the Debian archive.

librust-backtrace+addr2line-dev/amd64 unsatisfiable Depends: 
librust-addr2line-0.9+std-dev

Only rust-addr2line 0.7 is currently available.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#694077: Package review

[Lisandro Damián Nicanor Pérez Meyer]

please release it (dch -r), push it and I'll upload.

On Tue, 20 Aug 2019 at 09:07, Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> Hi!
>
> El mar., 20 ago. 2019 05:35, Jérôme Lebleu  escribió:
>>
>> Hi Lisandro,
>>
>> I am happy to read from you!
>>
>> Le 19/08/2019 à 21:42, Lisandro Damián Nicanor Pérez Meyer a écrit :
>> > I'm afraid it's failing to build from source:
>> >
>> > x86_64-linux-gnu/qt5 -isystem 
>> > /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
>> > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
>> > /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
>> > /usr/include/x86_64-linux-gnu/qt5/QtScript -isystem 
>> > /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm 
>> > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o qlcfixturedefcache.o 
>> > qlcfixturedefcache.cpp
>> > qlcfixturedef.cpp: In member function ‘QLCPhysical 
>> > QLCFixtureDef::physical() const’:
>> > qlcfixturedef.cpp:342:12: error: implicitly-declared 
>> > ‘QLCPhysical::QLCPhysical(const QLCPhysical&)’ is deprecated 
>> > [-Werror=deprecated-copy]
>> >   342 | return m_physical;
>> >   |^~
>> > In file included from qlcfixturedef.h:28,
>> >  from qlcfixturemode.h:29,
>> >  from qlcfixturedef.cpp:28:
>> > qlcphysical.h:78:18: note: because ‘QLCPhysical’ has user-provided 
>> > ‘QLCPhysical& QLCPhysical::operator=(const QLCPhysical&)’
>> >78 | QLCPhysical& operator=(const QLCPhysical& physical);
>> >   |  ^~~~
>> > cc1plus: all warnings being treated as errors
>> > make[3]: *** [Makefile:1206: qlcfixturedef.o] Error 1
>> > make[3]: *** Waiting for unfinished jobs
>> > make[3]: Leaving directory '/<>/engine/src'
>> > make[2]: *** [Makefile:90: sub-src-make_first-ordered] Error 2
>> > make[2]: Leaving directory '/<>/engine'
>> > make[1]: *** [Makefile:96: sub-engine-make_first-ordered] Error 2
>> > make[1]: Leaving directory '/<>'
>> > dh_auto_build: make -j2 returned exit code 2
>> > make: *** [debian/rules:14: build] Error 255
>> > dpkg-buildpackage: error: debian/rules build subprocess returned exit 
>> > status 2
>> > 
>> > Build finished at 2019-08-19T19:38:24Z
>> >
>> >
>> > Could it be the switch to gcc-9?
>>
>> Thanks for your report, I have just discovered that yesterday too. Yes
>> it should be the switch to gcc-9 as there were no errors before... I
>> have added -Wno-error=deprecated-copy for the moment to makes this
>> warnings not be errors. I will take the time as soon as possible to
>> report it upstream, if it is not meanwhile fixed. Is it also okay for a
>> first upload too?
>
>
> I think it is.



-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#935652: RM: appmenu-qt -- ROM; Obsolete libs (Qt4), dead upstream, Qt5 port dead too

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Time for this to go as part of Qt4 removal.

Scott K

Bug#935655: stretch-pu: package liquidsoap/1.3.3-2+deb10u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to update liquidsoap in buster to smoothen some upgrade paths
from stretch. liquidsoap/buster Breaks+Replaces about 35 plugin packages
from stretch, but on some upgrade paths apt prefers to keep some old
packages including liquidsoap installed (noticed in piuparts). Adding
Conflicts: liquidsoap-plugin-ogg "improves" the scores given by apt to
ensure more cruft gets removed and no upgradable package is kept at an
old version (verified in piuparts).

There is no point in applying this HACK in sid, since direct
stretch->bullseye/sid upgrades skipping buster are not supported.


Andreas
diff -Nru liquidsoap-1.3.3/debian/changelog liquidsoap-1.3.3/debian/changelog
--- liquidsoap-1.3.3/debian/changelog   2018-09-04 20:35:40.0 +0200
+++ liquidsoap-1.3.3/debian/changelog   2019-08-24 20:36:44.0 +0200
@@ -1,3 +1,12 @@
+liquidsoap (1.3.3-2+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Conflicts: liquidsoap-plugin-ogg (<< 1.3) in addition to the existing
+Breaks to ensure removal of the obsolete plugin packages on more upgrade
+paths from stretch.
+
+ -- Andreas Beckmann   Sat, 24 Aug 2019 20:36:44 +0200
+
 liquidsoap (1.3.3-2) unstable; urgency=medium
 
   * Fix build errors on armel and mips*
diff -Nru liquidsoap-1.3.3/debian/control liquidsoap-1.3.3/debian/control
--- liquidsoap-1.3.3/debian/control 2018-09-04 20:35:40.0 +0200
+++ liquidsoap-1.3.3/debian/control 2019-08-24 20:36:12.0 +0200
@@ -155,6 +155,10 @@
  liquidsoap-plugin-voaacenc,
  liquidsoap-plugin-vorbis,
  liquidsoap-plugin-xmlplaylist
+Conflicts:
+# use Conflicts in addition to Breaks to slightly push apt's scores towards
+# removal of the obsolete ogg plugin package which has many rdepends
+ liquidsoap-plugin-ogg (<< 1.3),
 Description: audio streaming language
  Liquidsoap is a powerful tool for building complex audio streaming systems,
  typically targeting internet radios (e.g. icecast streams).

Bug#875149: [qtcurve] Future Qt4 removal from Buster

[Scott Kitterman]

On Sat, 9 Sep 2017 23:07:54 +0200 Lisandro =?iso-8859-1?Q?
Dami=E1n_Nicanor_P=E9rez?= Meyer  wrote:
> Source: qtcurve
> Version: 1.8.18+git20160320-3d8622c-5
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 

Please go ahead and drop the Qt4 parts of this package.  Almost all KDE4 apps 
have been removed and removal of kde4libs is imminent.

Scott K

Bug#935668: RM: qtwebkit -- RoQA; Obsolete libs (Qt4), unmaintained, security nightmare

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

All rdepends have either been removed or have pending rm bugs.  We can
finally remove this.

Scott K

Bug#935675: RM: criu -- RoQA; Obsolete libs (Python2)

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Note that this package is currently maintained in experimental, so
unstable rm is ack'ed by the maintainer.  It will come back to unstable
later (with python3 support).

Scott K

Bug#927132: src:hash-slinger: Please port to python3

[Scott Kitterman]

On Mon, 15 Apr 2019 08:45:59 -0400 Scott Kitterman  
wrote:
> Package: src:hash-slinger
> Version: 2.7-1
> Severity: important
> 
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle.  It is not safe to assume it will be included in the
> next release, so if you want to be sure hash-slinger can stay in Debian,
> please port it to python3.  I see upstream suddendly did a new release
> after three years, so maybe an upstream port will appear.
> 
> Personally, I want to remove some packages I maintain, particularly python-
> ipaddr, which hash-slinger depends on during the Bullseye cycle, regardless 
of
> what happens to python2.7, so please update (python3 includes the ipaddress
> module, which was developed from ipaddr, in the standard library).

Bumping to serious now that python-ipaddr has been requested for removal.

Please let me know if you have lost interest in the package.  If so, I will 
ask for it to be removed.

Scott K

Bug#721197: RFP: minetest-mod-technic -- Minetest mod - Technic

[Phil Morrell]

I mainly want to note that this package is still desired and provide
information from the new ContentDB:

https://content.minetest.net/packages/RealBadAngel/technic/

#1 most popular mod by downloads

Required Dependencies
✓ basic_materials
✓ default (minetest-data)
✓ pipeworks

Optional Dependencies
✓ intllib
✓ mesecons
✓ moreblocks
✓ moreores
✓ unified_inventory
✓ unifieddyes
* bucket
* digiline_remote
* digilines
* mesecons_mvp
* mg
* screwdriver
* vector_extras

All required dependencies are packaged, which means the zip file from
ContentDB can be used as-is in the mod directory.


signature.asc
Description: PGP signature

Bug#934960: closed by Ondřej Nový (Bug#934960: fixed in pytest-mock 1.10.4-1)

[Paul Gevers]

Hi Ondřej,

On 24-08-2019 19:27, Debian Bug Tracking System wrote:
>  pytest-mock (1.10.4-1) unstable; urgency=medium
>  .
>* Team upload.
>* New upstream release (Closes: #904304).

Was this bug only an issue in the autopkgtest, or was it causing an
issue in pytest-mock? In the former case, a *versioned* test dependency
would have helped the system to pick the right combination for testing.
In the latter case, a *versioned* normal dependency is missing. If it's
a test issue only, you can either fix it with a new upload (preferred),
or tell me and I'm willing to help the system test the combination.

>* d/control: Remove ancient X-Python3-Version field
>* Use debhelper-compat instead of debian/compat.
>* Fix compatibility with newer Python, python-mock and pytest
>  (Closes: #934960).
>* Bump standards version to 4.4.0 (no changes).
>* Bump debhelper compat level to 12.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#935642: ITP: golang-github-acarl005-stripansi -- A little Go package for removing ANSI color escape codes from strings

[iuri]

Gentleman, please unsubscribe me for now. Best regards.

Em sáb, 24 de ago de 2019 17:27, Dawid Dziurla 
escreveu:

> Package: wnpp
> Severity: wishlist
> Owner: Dawid Dziurla 
>
> * Package name: golang-github-acarl005-stripansi
>   Version : 0.0~git20180116.5a71ef0-1
>   Upstream Author : Andy
> * URL : https://github.com/acarl005/stripansi
> * License : Expat
>   Programming Lang: Go
>   Description : A little Go package for removing ANSI color escape
> codes from strings
>
>  This Go package removes ANSI escape codes from strings.
>  .
>  Ideally, we would prevent these from appearing in any text we want to
>  process. However, sometimes this can't be helped, and we need to be able
>  to deal with that noise. This will use a regexp to remove those unwanted
>  escape codes.
>
> This package is in the dependency tree of "lazydocker" (#935641)
>
>

Bug#874825: [Pkg-kde-extras] Bug#874825: [appmenu-qt] Future Qt4 removal from Buster

[Scott Kitterman]

On Saturday, August 24, 2019 1:12:04 PM EDT Reiner Herrmann wrote:
> There is a Qt5 port available at: https://launchpad.net/appmenu-qt5

I checked and it's dead.  Not even in Ubuntu.

Scott K

Bug#935564: Typo

[Jean-Francois Pirus]

Opps, should have said:

With kenel 5.2.0-2-amd64,  TX is  4184/KB/sec 
With kenel 4.19.0-5-amd64, TX is 39678/KB/sec

Bug#935654: matrix-synapse: /etc/init.d/matrix-synapse stop doesn't work

[sergio]

Package: matrix-synapse
Version: 1.3.0-1~bpo10+1
Severity: normal

Dear Maintainer,

# /etc/init.d/matrix-synapse stop
doesn't work:

# lsof -i -n -sTCP:LISTEN | grep mat
python3 3831 matrix-synapse   10u  IPv6  51886  0t0  TCP [::1]:8448 (LISTEN)
python3 3831 matrix-synapse   11u  IPv4  51887  0t0  TCP *:8448 (LISTEN)
python3 3831 matrix-synapse   12u  IPv6  51888  0t0  TCP [::1]:8008 (LISTEN)
python3 3831 matrix-synapse   13u  IPv4  51889  0t0  TCP *:8008 (LISTEN)

Bug#935621: openstack-dashboard: incompatible with django 2.2

[Thomas Goirand]

Hi,

I'm very much aware of this issue, but can't find a way to fix it
myself. openstack_auth/views.py is using a login() function instead of
the now required LoginView class. I'm not skilled enough in Django to do
this myself, and upstream unfortunately doesn't feel it's urgent. Until
this is fixed, it's useless to work on anything else regarding Horizon
(I do believe I could fix the rest of the Django 2.2 related issues).

Cheers,

Thomas Goirand (zigo)

Bug#935501: Issue resolved

[Peda Bone]

Upgraded to Kernel 4.19.0-6-amd64 from Buster-Backports and no longer 
have the issue.

Bug#910902: Please test again: my_print_defaults and Akonadi for a freash installation

[Andreas Beckmann]

On Sun, 4 Aug 2019 18:45:28 +0100 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
 wrote:
> For some strange reason page https://tracker.debian.org/pkg/mariadb-10.3
> still says "Updating mariadb-10.3 introduces new bugs: #910902".
> 
> Do you Sandro have any ideas why that is?

I think that was because the bug was assigned to the arch:all
metapackage, that has a "buggy" cruft version in sid.
Should have been fixed by reassigning to mariadb-server-core-10.3 (done
a few minutes ago).

mariadb-server | 1:10.3.13-1  | unstable | all
mariadb-server | 1:10.3.15-1  | stable   | all
mariadb-server | 1:10.3.15-1  | testing  | all
mariadb-server | 1:10.3.17-1  | unstable | all


Andreas

Bug#935659: RM: kopete -- RoQA; Obsolete libs - Qt4

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

The current unstable version is Qt4.  There is a Qt5 version in
experimental, but the maintainer has not yet concluded it's appropriate
to include in a future release.  Once the Qt5 version is ready, it can
be uploaded to unstable to re-introduce the package.  In the meantime,
it doesn't make sense to block further progress on removing Qt4.

Scott K

Bug#935662: RM: qt-at-spi -- RoQA; Obsolete libs (Qt4)

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

We are well along in the process of removing Qt4 from Unstable.  This is
one of only a handful of packages left that build-depend on kdelibs5-dev
(the kde4libs development package - oddly numbered for historical
reasons).  I plan to go ahead and remove this since there will very
shortly be no packages left requiring accessibility support.

Scott K

Bug#935568: sphinx-issuetracker: should this package be removed?

[Sandro Tosi]

On Sat, Aug 24, 2019 at 12:59 PM Dmitry Shachnev  wrote:
>
> Hi Sandro!
>
> On Fri, Aug 23, 2019 at 10:46:30PM -0400, Sandro Tosi wrote:
> > Hello,
> > sphinx-issuetracker is currently incompatible with python3.7:
> > [...]
> >
> > It has no reverse-dependencies and it's currently one of the few r-deps of
> > python-debianbts.
> >
> > Should we just remove this package from Debian?
>
> I support the removal.
>
> However, there is one reverse build-dependency: src:migrate.

i checked on dak and it reports no rdeps, either binary or source:

```
$ dak rm -Rn -b python-sphinxcontrib.issuetracker
Will remove the following packages from unstable:

python-sphinxcontrib.issuetracker | 0.11-2 | all

Maintainer: Debian Python Modules Team


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.
```

> But it looks like use of issuetracker is actually patched away:
> https://sources.debian.org/src/migrate/0.12.0-3/debian/patches/disable_issuetracker.patch/
>
> Dear migrate maintainers (Cc'ed), can you please check if that
> build-dependency is still needed?

it's possible `migrate` used to depend on
python-sphinxcontrib.issuetracker but that's no longer the case, i
think?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#935671: librust-rle-decode-fast+bench-dev/amd64 unsatisfiable Depends: librust-criterion-0.2+default-dev

[Steve Langasek]

Source: rust-rle-decode-fast
Version: 1.0.1-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

The rust-rle-decode-fast package generates two binary packages that appear
to depend on rust-criterion, but there is no rust-criterion package in the
archive (or in the new queue).

librust-rle-decode-fast+bench-dev/amd64 unsatisfiable Depends: 
librust-criterion-0.2+default-dev
librust-rle-decode-fast+criterion-dev/amd64 unsatisfiable Depends: 
librust-criterion-0.2+default-dev

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#927131: src:grr: Please port to python3

[Scott Kitterman]

On Mon, 15 Apr 2019 08:40:09 -0400 Scott Kitterman  
wrote:
> Package: src:grr
> Version: 3.1.0.2+dfsg-6
> Severity: important
> 
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle.  It is not safe to assume it will be included in the
> next release, so if you want to be sure grr can stay in Debian, please port
> it to python3 (I see there are upstream commits for a python3 port, but no
> release yet).
> 
> Personally, I want to remove some packages I maintain, particularly python-
> ipaddr, which grr depends on during the Bullseye cycle, regardless of what
> happens to python2.7, so please update (python3 includes the ipaddress 
module,
> which was developed from ipaddr, in the standard library).
> 
> I'm aware there are complications in updating to a newer release.  I figure
> early notice is better than late.

Bumping to serious now that python-ipaddr removal has been requested.  If you 
have lost interest in the package, please let me know and I'll ask to have it 
removed.

Scott K

Bug#935651: ITP: golang-github-jesseduffield-asciigraph -- Go package to make lightweight ASCII line graph without dependencies

[Dawid Dziurla]

Package: wnpp
Severity: wishlist
Owner: Dawid Dziurla 

* Package name: golang-github-jesseduffield-asciigraph
  Version : 0.4.1+git20190605.6d88e39-1
  Upstream Author : Jesse Duffield
* URL : https://github.com/jesseduffield/asciigraph
* License : BSD-3-clause
  Programming Lang: Go
  Description : Go package to make lightweight ASCII line graph without 
dependencies

 Go package to make lightweight ASCII line graphs.
 .
 This package is golang port of library
 asciichart (https://github.com/kroitor/asciichart).

This package is in the dependency tree of "lazydocker" (#935641)

Bug#695069: cmus: remaining time is wrong when using ALSA PulseAudio sink

[Ryan Kavanagh]

control: tags -1 + moreinfo unreproducible

Hi Dominik,

I tried using your proposed ~/.cmus/autosave and couldn't reproduce the
bug. Have you noticed it with a particular format of audio file? Is it
still an issue with a current version of cmus?

Best
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#875494: connectomeviewer: Qt4 removal form Buster

[Scott Kitterman]

On Mon, 11 Sep 2017 16:33:30 -0300 =?utf-8?q?
Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?=  wrote:
> Source: connectomeviewer
> Version: 2.1.0-1.1
> Severity: minor
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> Note: this bug is being filled because your package recommends python-
qscintilla2.
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as announced in:
> 
> [announced]
> 

This is now in progress.  Upstream for this package seems dead (no commits in 
upstream git in nearly two years).  It seems likely the right answer is 
probably to remove the package.

This is the last package left in the archive that needs python-qscintilla2.

If no one indicates they are going to upload this without the python-
qscintilla2 Recommends (I have no idea if that even makes sense), then I'll 
file an QoRA rm bug soon.

Scott K

Bug#935663: RM: kdepimlibs -- RoQA; Obsolete libs (Qt4)

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

As part of Qt4 removal, it's time for pimlibs to go.  There are other rm
requests already for the remainng rdepends.

Scott K

Bug#935664: RM: kde-runtime -- RoQA; Obsolete libs (Qt4)

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

KDE4 applications have either already been removed or have rm bugs
filed.  As part of Qt4 removal it's time to remove the core KDE4
packages.

Scott K

Bug#935673: rust-ring depends on out-of-date rust-untrusted

[Steve Langasek]

Source: rust-ring
Version: 0.14.6-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

The rust-ring package is uninstallable, because it depends on a version of
rust-untrusted that is older than what's in unstable:

 librust-ring-dev : Depends: librust-untrusted-0.6+default-dev (>= 0.6.2-~~) 
but it is not installable

rust-untrusted is at version 0.7.0.  So rust-ring needs to be updated.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#935650: netcat-openbsd: valid arguments disallowed

[astian]

Package: netcat-openbsd
Version: 1.203-1
Severity: normal
Control: tags -1 + patch

Dear Maintainer,

The debian-specific patch "use-flags-to-specify-listen-address.patch"
disallows the usage of "-s" in some valid cases.  For example, the
following should connect to the unix socket "target" and use "foo" as
its client socket:

  $ nc -U -s foo target
  usage: nc ...

Looking at the patch I don't trust this is the only behaviour change.  I
don't understand why this divergence from upstream was introduced and I
wish it was reverted altogether.  But if that's not possible below is a
patch that you can fold into the existing one.

By the way, when I was looking at netcat 2 weeks ago I found several
other issues.  I wrote to the upstream ML and was planning to report the
bugs to the Debian BTS afterwards but it seems upstream is not very
interested because there was no reply in 10+ days.  Anyway, in case you
want to fix any of these, of the upstream issues the ones that are most
relevant for the Debian "fork" are the following:
  - https://marc.info/?l=openbsd-bugs=156551733219405=2 (the
non-kernel part, obviously)
  - https://marc.info/?l=openbsd-bugs=156568806424551=2
  - https://marc.info/?l=openbsd-bugs=156551644519192=2
  - https://marc.info/?l=openbsd-bugs=156551645219193=2
  - https://marc.info/?l=openbsd-bugs=156551644219191=2

There's also this one, but here Debian unfortunately diverged so there's
less of a compelling reason to fix it:
  - https://marc.info/?l=openbsd-bugs=156551640819187=2

The remaining one is OpenBSD-specific.

In my Debian box I've been running a custom netcat package with all of
the above patched (some "provisionally", some with patches that differ
slightly for Linux), so feel free to ask if you want the patches.


Thanks.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages netcat-openbsd depends on:
ii  libbsd0  0.9.1-2
ii  libc62.28-10

netcat-openbsd recommends no packages.

netcat-openbsd suggests no packages.

-- no debconf information

--- a/netcat.c
+++ b/netcat.c
@@ -511,7 +511,7 @@ main(int argc, char *argv[])
if (argc == 0 && lflag) {
uport = 
host = sflag;
-   } else if (argc == 1 && !pflag && !sflag) {
+   } else if (argc == 1 && !pflag && (!sflag || family == AF_UNIX)) {
if (family == AF_UNIX) {
host = argv[0];
uport = NULL;

Bug#875208: [Pkg-kde-extras] Bug#875208: [tora] Future Qt4 removal from Buster

[Scott Kitterman]

On Saturday, August 24, 2019 4:12:34 PM EDT Michael Meskes wrote:
> > > It's now the last one, so if I don't hear back soon that someone
> > > intends to
> > > upgrade this to Qt5, I'll file for the rm.
> > 
> > Adding the primary uploader to CC.
> 
> I'm not using the tool anymore, nor do I have time to take care of it.
> The only reason why I didn't orphan it, is that somebody inb the group
> might be willing to, but apparently not. So in short, go ahead.

Thanks.  rm bug filed.

Scott K

Bug#934816: tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer

[Andreas Beckmann]

Control: severity -1 normal

On Sat, 24 Aug 2019 17:11:10 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= 
 wrote:
> Increasing severity to 'serious' since this is one of the 5 packages
> what still depend on libmariadbclient18, which will soon be removed
> from unstable and then render this package uninstallable. Please
> rebuild and upload, so that the package will automatically be built
> and depend on newest libraries (including libmariadb3 which has
> replaced libmariadbclient18).

This is an alternative dependency, the package will not be
affected by libmariadbclient18 removal:

Package: tcl8.6-tdbc-mysql
Version: 1.1.0-2+b1
Architecture: amd64
Depends: libc6 (>= 2.14), tcl8.6, tcl8.6-tdbc (>= 1.0.5), libmariadb3 | 
libmariadbclient18 | libmysqlclient18 | libmysqlclient20


> debian-sid$ apt-rdepends -r libmariadbclient18

Instead of rdepends you should rather check what happens upon removal:


anbe@coccia:~$ dak rm -Rn -b libmariadbclient18
Will remove the following packages from unstable:

libmariadbclient18 | 1:10.3.13-1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

Maintainer: Debian MySQL Maintainers 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
dballe: libdballe7
mosquitto-auth-plugin: mosquitto-auth-plugin
mysql++: libmysql++3v5
quickfix: libquickfix16 [i386]
stardict: stardict-tools

Dependency problem found.


Andreas

Bug#935243: Does not work with Thunderbird 6x (60+)

[martin f krafft]

Quoting "Mechtilde Stehmann", who wrote on 2019-08-24 at 20:21 Uhr +0200:
you find a new package version 2.3 in experimental. there is thunderbird 
(>=68), too.


Thank you so much! It's working again, though I now need to figure 
out a problem with Radicale.


--
.''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
 `-  Debian - when you have better things to do than fixing systems

a gourmet concerned about calories is like a punter eyeing the clock.


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#934989: openjdk-11-jre: Performance of JDK11/12 is 10%-15% worse than JDK8

[tony mancill]

On Sun, Aug 18, 2019 at 04:54:52PM +0200, Erich Schubert wrote:
> Hi,
> 
> To reproduce the experiments, get the (older than what I used) ELKI
> standalone jar here:
> 
> https://elki-project.github.io/releases/release0.7.5/elki-bundle-0.7.5.jar
>
> (snip)
>
> A suitable command line is:
> 
> taskset -c 0 $JAVA_HOME/bin/java \
> -jar elki-bundle-0.7.5.jar \
> cli -time -dbc.in aloi-hsb-2x2x2.csv.gz \
> -algorithm clustering.DBSCAN -dbscan.minpts 20 -dbscan.epsilon 0.01 \
> -evaluator NoAutomaticEvaluation -resulthandler DiscardResultHandler
> 
> the "cli" command runs this headless; the "-time" parameter enables a
> minimal output of statistics. The last two parameter disable the
> (unnecessary for this purpose) evaluation and result output. tasksets forces
> this to use only the first CPU (except for the garbage collection,
> everything is single-threaded in this call).

I have been able to reproduce the "Java 8 is faster than Java 11"
results initially reporting using the ALOI datasets from [1].  However,
I have also seen Java 11 outperform Java 8 (by 4-5%) using the same
command-line invocation of ELKI against a different dataset [2].  This
isn't intended to refute your findings but to suggest that there could
be other factors.  Perhaps the performance difference depends on
specific aspects of the workload - e.g., whether there is more pressure
on the memory subsystem than CPU (or something like that).

Each of these are run on Debian sid (3) times on an otherwise quiet
system; the results below are representative (for all runs, JDK 11 was
faster on my system with this dataset):

#
# Java 8 
# OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
#
elki taskset -c 0 /usr/lib/jvm/java-8-openjdk-amd64/bin/java \
-jar elki-bundle-0.7.5.jar \
cli -time -dbc.in data/Range-Queries-Aggregates.csv \ 
-algorithm clustering.DBSCAN -dbscan.minpts 20 -dbscan.epsilon 1 \
-evaluator NoAutomaticEvaluation -resulthandler DiscardResultHandler
de.lmu.ifi.dbs.elki.datasource.FileBasedDatabaseConnection.load: 829 ms
de.lmu.ifi.dbs.elki.algorithm.clustering.DBSCAN.average-neighbors: 1.0
There are very few neighbors found. Epsilon may be too small.
de.lmu.ifi.dbs.elki.algorithm.clustering.DBSCAN.runtime: 513229 ms

#
# Java 11
# OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Debian-1, mixed mode)
#
elki taskset -c 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java \
-jar elki-bundle-0.7.5.jar \
cli -time -dbc.in data/Range-Queries-Aggregates.csv \
-algorithm clustering.DBSCAN -dbscan.minpts 20 -dbscan.epsilon 1 \
-evaluator NoAutomaticEvaluation -resulthandler DiscardResultHandler
de.lmu.ifi.dbs.elki.datasource.FileBasedDatabaseConnection.load: 864 ms
de.lmu.ifi.dbs.elki.algorithm.clustering.DBSCAN.average-neighbors: 1.0
There are very few neighbors found. Epsilon may be too small.
de.lmu.ifi.dbs.elki.algorithm.clustering.DBSCAN.runtime: 490520 ms

So, this is to be continued...
In any event, thank you for bringing this benchmark to the list.

Cheers,
tony

[1] https://www.dbs.ifi.lmu.de/research/outlier-evaluation/input/ALOI.tar.gz
[2] http://archive.ics.uci.edu/ml/datasets/Query+Analytics+Workloads+Dataset


signature.asc
Description: PGP signature

Bug#927136: src:zabbix-cli: Please update to python3

[Scott Kitterman]

On Mon, 15 Apr 2019 08:56:40 -0400 Scott Kitterman  
wrote:
> Package: src:zabbix-cli
> Version: 1.7.0-1
> Severity: important
> 
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle.  It is not safe to assume it will be included in the
> next release, so if you want to be sure zabbix-cli can stay in Debian, 
please
> update it to the python3 version available from upstream..
> 
> Personally, I want to remove some packages I maintain, particularly python-
> ipaddr, which zabbix-cli depends on during the Bullseye cycle, regardless of
> what happens to python2.7, so please update (python3 includes the ipaddress
> module, which was developed from ipaddr, in the standard library).

Bumping to serious because python-ipaddr will be removed soon.  Upstream 
support python3.  Please update to a new version or ack that you've lost 
interest in the package and I'll ask to have it removed.

Scott K

Bug#935677: ganeti-2.16: Depends on to be removed packages (python2/python-ipaddr specifically)

[Scott Kitterman]

Package: ganeti-2.16
Version: 2.16.0-5
Severity: serious
Justification: Policy 2.5

As you may have heard, the plan is to remove python2 for the bullseye
release.  As part of that effort, the python teams are working on
removing as much of the python2 stack as early as we can.  As part of
that effort, I've asked to have my package python-ipaddr removed (since
it is python2 only).

This package depends on python-ipaddr and needs to be updated.

It doesn't appear to me that upstream supports python3 yet, so I don't
know what exactly to suggest for this release cycle.  For the short
term, you can probable switch to using python-ipaddress as the API is
almost identical.

Scott K

Bug#935676: ganeti-2.15: Depends on to be removed packages (python2/python-ipaddr specifically)

[Scott Kitterman]

Source: ganeti-2.15
Version: 2.15.2-15
Severity: serious
Justification: Policy 2.5

As you may have heard, the plan is to remove python2 for the bullseye
release.  As part of that effort, the python teams are working on
removing as much of the python2 stack as early as we can.  As part of
that effort, I've asked to have my package python-ipaddr removed (since
it is python2 only).

This package depends on python-ipaddr and needs to be updated.

It doesn't appear to me that upstream supports python3 yet, so I don't
know what exactly to suggest for this release cycle.  For the short
term, you can probable switch to using python-ipaddress as the API is
almost identical.

Scott K

Bug#935653: [unattended-upgrades] /usr/bin/unattended-upgrade hogging cpu

[Riccardo Magliocchetti]

Package: unattended-upgrades
Version: 1.14
Severity: normal

--- Please enter the report below this line. ---

Hello,

I have /usr/bin/python3 /usr/bin/unattended-upgrade using 100% of a core calling 
stat in a very tight loop for no apparent good reason. It does so by holding the 
/var/lib/dpkg/lock-frontend lock.


Even after a kill -9, a new process shows the same behaviour.

Stracing it looks like it's in a loop calling stat for files that does not 
exists:

sudo strace -c -p 6778
strace: Process 6778 attached
strace: [ Process PID=6778 runs in x32 mode. ]
strace: [ Process PID=6778 runs in 64 bit mode. ]
^Cstrace: Process 6778 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
100,000,147692   1 77789 57944 stat
-- --- --- - - 
100.000,147692 77789 57944 total

Excerpt on actual calls:

stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-en", 
{st_mode=S_IFREG|0644, st_size=208649, ...}) = 0
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.xz", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.bz2", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.lzma", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.gz", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.lz4", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.zst", 
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)

...


Thanks

--
Riccardo Magliocchetti
@rmistaken

http://menodizero.it

Bug#827196: Already fixed upstream

[Ernesto Domato]

Package: ocrfeeder
Version: 0.8.1-4
Followup-For: Bug #827196

Dear Maintainer,

This issue has been fixed upstream since Mar 18, 2018 [1]

Please consider packaging last version from the Git repository [2]

Thanks for all.
Ernesto

[1]
https://gitlab.gnome.org/GNOME/ocrfeeder/commit/f5f1b076993ec0ba94250f21051e049072c7e230
[2] https://gitlab.gnome.org/GNOME/ocrfeeder



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ocrfeeder depends on:
ii  ghostscript   9.28~~rc1~dfsg-1
ii  gir1.2-goocanvas-2.0  2.0.4-1
ii  gir1.2-gtk-3.03.24.10-1
ii  gir1.2-gtkspell3-3.0  3.0.9-3
ii  iso-codes 4.3-1
ii  python2.7.16-1
ii  python-enchant2.0.0-1
ii  python-gi 3.32.2-1
ii  python-lxml   4.4.1-1
ii  python-pil6.1.0-1
ii  python-reportlab  3.5.23-1
ii  python-sane   2.8.3-1+b2
ii  tesseract-ocr 4.1.0-1

Versions of packages ocrfeeder recommends:
pn  unpaper  
ii  yelp 3.31.90-1

ocrfeeder suggests no packages.

-- no debconf information

Bug#935657: Please port and switch this package to Python 3 or remove it from Debian

[Thomas Goirand]

Package: calendarserver
Version: 9.2+dfsg-1
Severity: serious

Hi,

We're trying to remove Python 2 from Bullseye. And I came across your package,
which is still py2 only.

Please switch it to Python 3. If that's not possible, then it's probably the
time for your package to get removed from Debian, unfortunately.

Cheers,

Thomas Goirand (zigo)

Bug#935656: RM: qwbfsmanager -- RoQA; unmaintained, depends on qt4

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove qwbfsmanager. The version currently in the archive is 
unmaintained (last
maintainer upload in 2011, now orphaned) and depends on Qt 4. There's a new 
upstream
release on Github which is actually ported to Qt5, but it also depends on a new 
Qt
extension library (fresh). If someone wants to revive qwbfsmanager in the 
future,
that library would need to be packaged/uploaded beforehand.

Cheers,
Moritz

Bug#935660: tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci

[Scott Kitterman]

Source: tortoisehg
Version: 4.8.1-0.1
Severity: serious
Justification: Policy 2.5

We are in the process of removing python2 from Debian during the
bullseye release cycle.  This package is the last remaining dependency
of python-pyqt5.qsci.  Please update to python3 (I have not checked if
your upstream supports it).

Based on the other open RC bug, this package appears unmaintained.  If
no one responds, I expect that we'll file an RoQA rm bug soonish.

Scott K

Bug#935661: wicd-gtk: Recommends obsolete kde-runtime

[Scott Kitterman]

Package: wicd-gtk
Version: 1.7.4+tb2-6
Severity: important

The kde-runtime package, which wicd-gtk recommends, is about to be
removed from Debian as part of Qt4 removal.  Please drop the recommends.

Note that the current invocation in set.py won't work anyway, so I don't
plan to wait on this package for removing kde-runtime.

Scott K

Bug#935579: cwltool: bad upstream test testing udocker, not cwltool

[Steve Langasek]

On Sat, Aug 24, 2019 at 11:48:58AM +0200, Michael Crusoe wrote:
> Hey Steve,

> I think this is fixed in my recent upload, let me know if it works for you.

There are no errors now about udocker on non-x86, but the autopkgtests are
now failing on all architectures in Debian and Ubuntu with this error:

 ERRORS 
__ ERROR collecting tests/test_trs.py __
ImportError while importing test module 
'/usr/lib/python3/dist-packages/cwltool/tests/test_trs.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/cwltool/tests/test_trs.py:3: in 
import mock
E   ModuleNotFoundError: No module named 'mock'

So it looks like a missing test dep.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#927135: src:rekall: Please update to python3 version

[Scott Kitterman]

On Mon, 15 Apr 2019 08:52:16 -0400 Scott Kitterman  
wrote:
> Package: src:rekall
> Version: 1.6.0+dfsg-2
> Severity: important
> 
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle.  It is not safe to assume it will be included in the
> next release, so if you want to be sure rekall can stay in Debian, please
> update it to the python3 version available from upstream..
> 
> Personally, I want to remove some packages I maintain, particularly python-
> ipaddr, which rekall depends on during the Bullseye cycle, regardless of 
what
> happens to python2.7, so please update (python3 includes the ipaddress 
module,
> which was developed from ipaddr, in the standard library).

Bumping to serious as python-ipaddr has been requested for removal.

If you have lost interest in the package, please let me know so I can ask to 
have it removed.

Scott K

Bug#935352: trimage: Qt4 removal from Bullseye

[Reiner Herrmann]

Control: tags -1 + fixed-upstream

The new upstream version 1.0.6 supports Qt5.


signature.asc
Description: PGP signature

Bug#787034: Further details: .wav files causing problems

[Ryan Kavanagh]

control: tags -1 + unreproducible moreinfo

Hi Tim,

On Thu, May 28, 2015 at 09:58:28AM -0500, Tim Chase wrote:
> RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono
> 44100 Hz

I am unable to reproduce this. I tried converted an mp3 file to WAV
using ffmpeg, and cmus was able to both add it to the library and play
it. Could you please let me know if this is still an issue with the
current version of cmus? In case I'm missing something, here are the
steps I took to generate the WAV file:

rak@zeta:/tmp$ ffmpeg -i test.mp3 test.wav
[...]
rak@zeta:/tmp$ file test.wav
test.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit,
stereo 44100 Hz
rak@zeta:/tmp$ xxd test.wav | head -3
: 5249 4646 c087 5102 5741 5645 666d 7420  RIFF..Q.WAVEfmt
0010: 1000  0100 0200 44ac  10b1 0200  D...
0020: 0400 1000 4c49 5354 b400  494e 464f  LISTINFO

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#935650: netcat-openbsd: valid arguments disallowed

[Guilhem Moulin]

Control: retitle -1 netcat-openbsd: Unable to specify client socket for 
UNIX-domain datagram sockets
Control: found -1 1.187-1
Control: found -1 1.195-2

Hi,

On Sat, 24 Aug 2019 at 20:25:00 +, astian wrote:
> Looking at the patch I don't trust this is the only behaviour change.  I
> don't understand why this divergence from upstream was introduced and I
> wish it was reverted altogether.

The patch was added to support the following calls for consistency with
netcat-traditional:

nc -l -s 127.0.0.1 -p 12345 ## listen on AF_INET socket 
INADDR_LOOPBACK:12345
nc -l -p 12345  ## listen on AF_INET socket ADDR_ANY:12345

It'd be a regression to stop supporting these forms, or any of the
others from https://bugs.debian.org/897020#17 .

> But if that's not possible below is a patch that you can fold into the
> existing one.
> […]
> - } else if (argc == 1 && !pflag && !sflag) {
> + } else if (argc == 1 && !pflag && (!sflag || family == AF_UNIX)) {

In combination with ‘-U’ the ‘-s’ option only makes sense for datagrams,
no?  AFAICT it's a no-op for stream sockets; might make sense to error
out unless ‘-u’ is set.

As for your other patches, I'm personally not keen to further diverge
with upstream (especially when it comes to adding new flags/options) —
but hopefully they'll eventually pick up your fixes or address your
concerns ;-)

Thanks for the reports and patches!
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#935622: libgnuradio-osmosdr0.1.4: Gnuradio 3.8 does not load osmo/rtl blocks

[A. Maitland Bottoms]

Andre Offringa  writes:

> Package: libgnuradio-osmosdr0.1.4
> Version: 0.1.4-14+b10
> Severity: important
>
> Dear Maintainer,
>
> After gnuradio was recently upgraded to 3.8, the blocks provided by
> libgnuradio-osmosdr0.1.4 are no longer available in gnuradio. The gnuradio-
> companion just doesn't show the blocks, and saved gnuradio schemes that 
> include
> an rtl or osmo-source, show a 'Missing Block' instead of the osmo/rtl block,
> and hence no longer work.
>
> The files like /usr/share/gnuradio/grc/blocks/rtlsdr_source.xml are present on
> my system, but for some reason are not loaded by gnuradio-companion. No errors
> are shown when I start gnuradio-companion.
>
> Regards,
> André Offringa

Indeed. Many changes in gnuradio 3.8 - Python3 instead of Python2,
blocks defined in yaml with .yml files instead of .xml files.

This will happen with most gr-* packages. binnmu is not enough.

Lucky for us, there are two people updating gr-osmosdr,
https://github.com/mvaenskae/gr-osmosdr
https://github.com/igorauad/gr-osmosdr
and I will upload new Debian source package soon. (I am awaiting for
some dependencies to get through NEW processing, due to the API/ABI
bumps.)

I hope I can get the various gr-* packages and gqrx-sdr back working
again in Debian testing in time for the gnuradio conference, GRCon, next
month.

For Debian Bullseye, the gnuradio 3.7.x.x are scheduled to be removed
because of the end of Python 2 support. So - 3.8 and progress!

Thank you for your interest in gnuradio and Debian,
-Maitland

Bug#935669: assaultcube-data: Outdated version makes assaultcube uninstallable

[Guillem Jover]

Package: assaultcube-data
Version: 1.1.0.4+repack1-2.1
Severity: serious

Hi!

The assaultcube package got updated to version 1.2.0.2.1-1, but the
matching assaultcube-data package has not been uploaded which makes
the former to be currently uninstallable in unstable.

Thanks,
Guillem

Bug#927104: criu: Please update to python3

[Scott Kitterman]

On Saturday, August 24, 2019 5:22:11 AM EDT Salvatore Bonaccorso wrote:
> Contorl: tags -1 + help
> 
> Hi
> 
> At the moment I'm somehow a bit time limited to work on src:criu, but
> not completely lost track. But if someone wants to help here and on
> the FTBFS bug then be my guest, will happily merge proposed changes.
> 
> In any case criu should not block the python2.7 removal, so feel free
> to request removal from unstable at any point it is needed for you.
> 
> I plan at the moment to keep it anyway updated in experimental, as it
> is still before uploading a new version to unstable at all.

I took a brief look at this.  I did not make progress on the FTBFS, so I'm 
unable to test anything, but I can make some suggestions on the Python bits.

At the very least, you'll need the following:

In debian/rules chang with python2 to python3

Add PYTHON="python3" to the install override

In debian control:

Build-depend on python3-all instead of python-all

Drop the depends on python-future and python-ipaddr
Change python-protobuf to python3-protobuf

More generally, there's a missing build-dep on pkg-config.

It looks like upstream supports python3, so that's at least a start.

Scott K

Bug#935640: running 'firehol restart' does not always reproduce ruleset

[Jerome BENOIT]

Hello Toni,

I guess that your issue is related to FireHOL issue #352:
https://github.com/firehol/firehol/issues/352

This issue seems to cause a lot of trouble.
It is related to the new iptable-{legacy,nft}.
FireHOL does not yet support iptable-nft.
In the last Debian package, FireHOL is forced to use the -legacy tools.
See the comment by FabioPedretti on Nov 8, 2018.

The issue seems to appear on at upgrade stage: on my own box, rebooting was 
sufficient.
I agree to say that the upgrade should be smoother.
Any idea on how to deal with this issue is welcome.

Cheers,
Jerome


-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#935674: librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends: librust-clippy-0.0.41+default-dev

[Steve Langasek]

Source: rust-blake2-rfc
Version: 0.2.18-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

The rust-blake2-rfc package generates a binary package that appears to
depend on rust-clippy, but there is no rust-clippy package in the archive
(or in the new queue).

librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends: 
librust-clippy-0.0.41+default-dev

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#935576: buster-pu: package z3/4.4.1-1~deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2019-08-24 at 08:39 +0200, Andreas Beckmann wrote:
> I'd like to rebuild z3 from sid for buster to fix the incorrect
> SONAME of libz3java.so (#842892)

Please go ahead.

Regards,

Adam

Bug#935581: stretch-pu: package z3/4.4.1-1~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2019-08-24 at 11:03 +0200, Andreas Beckmann wrote:
> Followup-For: Bug #935581
> 
> Now with diff ...
> 

Please go ahead.

Regards,

Adm

Bug#935551: osinfo-db: broken debian installer iso urls in buster version

[Guido Günther]

Hi,
On Sat, Aug 24, 2019 at 11:52:24AM +0200, Laurent Bigonville wrote:
> Hello,
> 
> I opened a bug before the release for this, but unfortunately it was not
> fixed in time (see: #919486)
> 
> Please find here a patch that fixes several issues with the version
> currently in buster:
> 
> osinfo-db (0.20181120-1.1) buster; urgency=medium
> 
>   * Non-maintainer upload.
>   * debian/patches/debian9-update.patch: Fix the URL's to download the iso
>     files and point to the latest point release (9.9.0)
>   * debian/patches/debian10-Add-info.patch: Add information about the debian
>     buster/10 release (Closes: #935551)
>   * d/p/debian-preseed-Fix-typo-in-config-s-name.patch: Fix the name of the
>     parameter used to set the fullname when generating a preseed file, the
>     documentation explicitly talks about "user-realname" but the profile was
>     using "user-fullname" (the debconf parameter name) by mistake
> 
>  -- Laurent Bigonville   Sat, 24 Aug 2019 10:06:02 +0200
> 
> Is that OK if I'm doing a NMU with this?

I was about to import newer snapshot but since you got this prepared
already just go ahead and NMU.
Thanks!
 -- Guido

> 
> Kind regards,
> 
> Laurent Bigonville
> 

> diff -Nru osinfo-db-0.20181120/debian/changelog 
> osinfo-db-0.20181120/debian/changelog
> --- osinfo-db-0.20181120/debian/changelog 2018-11-20 22:41:36.0 
> +0100
> +++ osinfo-db-0.20181120/debian/changelog 2019-08-24 10:06:02.0 
> +0200
> @@ -1,3 +1,17 @@
> +osinfo-db (0.20181120-1.1) buster; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/patches/debian9-update.patch: Fix the URL's to download the iso
> +files and point to the latest point release (9.9.0)
> +  * debian/patches/debian10-Add-info.patch: Add information about the debian
> +buster/10 release (Closes: #935551)
> +  * d/p/debian-preseed-Fix-typo-in-config-s-name.patch: Fix the name of the
> +parameter used to set the fullname when generating a preseed file, the
> +documentation explicitly talks about "user-realname" but the profile was
> +using "user-fullname" (the debconf parameter name) by mistake
> +
> + -- Laurent Bigonville   Sat, 24 Aug 2019 10:06:02 +0200
> +
>  osinfo-db (0.20181120-1) unstable; urgency=medium
>  
>* [aa777b6] New upstream version 0.20181120
> diff -Nru osinfo-db-0.20181120/debian/patches/debian10-Add-info.patch 
> osinfo-db-0.20181120/debian/patches/debian10-Add-info.patch
> --- osinfo-db-0.20181120/debian/patches/debian10-Add-info.patch   
> 1970-01-01 01:00:00.0 +0100
> +++ osinfo-db-0.20181120/debian/patches/debian10-Add-info.patch   
> 2019-08-24 09:45:19.0 +0200
> @@ -0,0 +1,223 @@
> +From 13e84168d359b4ab1170451716098b5e72ac15f9 Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= 
> +Date: Tue, 9 Jul 2019 08:55:30 +0200
> +Subject: [PATCH] debian10: Add info
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +Debian 10 has been released on July 6th, 2019.
> +
> +Signed-off-by: Fabiano Fidêncio 
> +Reviewed-by: Cole Robinson 
> +---
> + data/os/debian.org/debian-10.xml.in | 203 
> + 1 file changed, 203 insertions(+)
> + create mode 100644 data/os/debian.org/debian-10.xml.in
> +
> +--- /dev/null
>  b/data/os/debian.org/debian-10.xml.in
> +@@ -0,0 +1,203 @@
> ++
> ++
> ++  http://debian.org/debian/10;>
> ++debian10
> ++debianbuster
> ++<_name>Debian 10
> ++10
> ++<_vendor>Debian Project
> ++linux
> ++debian
> ++buster
> ++http://debian.org/debian/9"/>
> ++http://debian.org/debian/9"/>
> ++
> ++2019-07-06
> ++
> ++
> ++  
> ++10
> ++1
> ++1073741824
> ++10737418240
> ++  
> ++  
> ++10
> ++1073741824
> ++21474836480
> ++  
> ++
> ++
> ++
> ++  <_name>Debian 10
> ++
> ++
> ++  <_name>Debian 10
> ++
> ++
> ++
> ++
> ++  
> ++  
> http://cdimage.debian.org/cdimage/release/10.0.0/i386/iso-cd/debian-10.0.0-i386-netinst.iso
> ++  
> ++Debian 10.(\d)+.(\d)+ i386 n
> ++  
> ++  install.386/vmlinuz
> ++  install.386/initrd.gz
> ++
> ++
> ++  
> ++  
> http://cdimage.debian.org/cdimage/release/10.0.0/amd64/iso-cd/debian-10.0.0-amd64-netinst.iso
> ++  
> ++Debian 10.(\d)+.(\d)+ amd64 n
> ++  
> ++  install.amd/vmlinuz
> ++  install.amd/initrd.gz
> ++
> ++
> ++  
> ++  
> http://cdimage.debian.org/cdimage/release/10.0.0/arm64/iso-cd/debian-10.0.0-arm64-netinst.iso
> ++  
> ++Debian 10.(\d)+.(\d)+ arm64 n
> ++  
> ++  install.a64/vmlinuz
> ++  install.a64/initrd.gz
> ++
> ++
> ++  
> ++  
> http://cdimage.debian.org/cdimage/release/10.0.0/armhf/iso-cd/debian-10.0.0-armhf-netinst.iso
> ++  
> ++Debian 10.(\d)+.(\d)+ armhf n
> ++  
> ++  

Bug#923031: opusfile: updated package (new upstream, multiarch-capable, etc.)

[Simon McVittie]

On Sat, 23 Feb 2019 at 10:55:56 +0100, Jan Nordholz wrote:
> as libopusfile0 has now become a dependency of libsdl2-mixer-2.0-0, its
> missing multiarch support is hitting more people.

I'm aware that the maintainer of opusfile does not usually want to make
packaging changes without specific reasons, so I've opened #935590 to
represent the missing multiarch support and sent a more minimal patch
there, based on the earlier patch sent to #899138.

>   - new upstream

I've opened a separate wishlist bug report #935591 for this.

>   - recent debhelper level
>   - automatic -dbgsym package
>   - policy compliance
>   - open bug reports
>   - make lintian happy (this also meant removing the probably outdated
> Vcs-* fields)

If the maintainer would be willing to consider some subset of these
changes, or even all of them, I'd be happy to help with reviewing them,
and if necessary breaking them up into separate changes with specific
justifications for why they are desirable.

smcv

Bug#935593: RM: yubikey-val -- ROM; low popcon

[Simon Josefsson]

Package: ftp.debian.org
X-Debbugs-CC: pkg-auth-maintain...@lists.alioth.debian.org

Please remove "yubikey-val" from "unstable".

The package has low popcon, and the few people who would use the
package would likely not run it without local customizations since
upstream made no releases since 2016, and PHP code grows old quickly. 
Maintaining the package with its various hooks to Apache in
postinst/postrm and interaction with the init system (never ported to
systemd) is also not worth the effort for me.

/Simon



signature.asc
Description: This is a digitally signed message part

Bug#935596: RM: teeworlds/0.6.5+dfsg-1~deb9u1

[Moritz Muehlenhoff]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Please remove teeworlds in the 9.10 point release, it has open
security issues, but it's not really worth fixing as the package
from Stretch is now incompatible with current game servers.

Cheers,
Moritz

Bug#935609: lintian suggest to use php-net-ipv4 which isn't in the archive anymore available

[Carsten Schoenert]

Package: lintian
Version: 2.19.0
Severity: normal

Dear Maintainer,

while working on some random PHP package I've noticed that Lintian is
suggesting to use the package php-net-ipv4 [1] as possible replacement
which is only available for Stretch and that's currently old-stable. So
the suggstion from Lintian isn't a valuable and useful suggestion.

The package php-net-ipv4 was removed due PHP7.0 transition and no
further usage within the Debian releases.

It might be a good idea to check if more such suggestions are currently
inside Lintian.

[1] https://tracker.debian.org/pkg/php-net-ipv4

Regards
Carsten

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils 2.32.51.20190727-1
ii  bzip21.0.6-9.2
ii  diffstat 1.62-1+b1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.37-5
ii  gettext  0.19.8.1-9
ii  gpg  2.2.17-3
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b1
ii  libarchive-zip-perl  1.64-1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.44-1
ii  libclass-accessor-perl   0.51-1
ii  libclone-perl0.41-1+b1
pn  libdigest-sha-perl   
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.74-1
ii  libipc-run-perl  20180523.0-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b4
ii  libmoo-perl  2.003004-2
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3000-2
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.004004-1
ii  liburi-perl  1.76-1
ii  libxml-simple-perl   2.25-1
ii  libyaml-libyaml-perl 0.79+repack-2
ii  man-db   2.8.6.1-1
ii  patchutils   0.3.4-2+b1
ii  perl 5.28.1-6
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b5

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libhtml-parser-perl3.72-3+b3
ii  libtext-template-perl  1.55-1

-- no debconf information

Bug#935610: RM: openambit -- RoQA; dead upstream, depends on qjson/qt4

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove openambit, it's orphaned and depends on qjson, which
gets removed alongside with qt4.

Cheers,
Moritz

Bug#935611: liblablgtk3-ocaml-dev: missing Breaks+Replaces: liblablgtk3-ocaml (<< 3.0~beta6)

[Andreas Beckmann]

Package: liblablgtk3-ocaml-dev
Version: 3.0~beta6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../28-liblablgtk3-ocaml-dev_3.0~beta6-1_amd64.deb ...
  Unpacking liblablgtk3-ocaml-dev (3.0~beta6-1) over (3.0~beta3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-BYyNXz/28-liblablgtk3-ocaml-dev_3.0~beta6-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/ocaml/lablgtk3/META', which is also in package 
liblablgtk3-ocaml 3.0~beta3-1


cheers,

Andreas


liblablgtk3-ocaml-dev_3.0~beta6-1.log.gz
Description: application/gzip

Bug#935599: stretch-pu: package libxslt/1.1.29-2.1+deb9u1

[Salvatore Bonaccorso]

Hi Adam,

On Sat, Aug 24, 2019 at 03:01:13PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2019-08-24 at 14:30 +0200, Salvatore Bonaccorso wrote:
> > I preapred a NMU for libxslt incorporating fixes for three CVEs which
> > are no-dsa but would be good to have fixed as well in stretch
> > following the fixes for unstable and buster. The debdiff is attached.
> > 
> 
> Please go ahead; thanks.

Ack, uploaded actually at same time as submitting the bugreport.

Regards,
Salvatore

Bug#935623: dbconfig-common: [INTL:de] updated German debconf translation

[Helge Kreutzmann]

Package: dbconfig-common
Version: 2.0.12
Severity: wishlist
Tags: patch l10n

Please find the updated German debconf translation for dbconfig-common
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# Translation of dbconfig-common debconf templates to German
# Copyright (C) Andreas Tille , 2005.
# Copyright (C) Helge Kreutzmann , 2006, 2009, 2015, 
2016, 2019.
# This translation is distributed under the same terms as dbconfig-common
#
msgid ""
msgstr ""
"Project-Id-Version: dbconfig-common 2.0.12\n"
"Report-Msgid-Bugs-To: dbconfig-com...@packages.debian.org\n"
"POT-Creation-Date: 2019-08-18 20:35+0200\n"
"PO-Revision-Date: 2019-08-24 16:33+0200\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: de \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid "Will this server be used to access remote databases?"
msgstr ""
"Wird dieser Server zum Zugriff auf entfernte Datenbanken verwendet werden?"

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid ""
"For the database types that support it, dbconfig-common includes support for "
"configuring databases on remote systems. When installing a package's "
"database via dbconfig-common, the questions related to remote configuration "
"are asked with a priority such that they are skipped for most systems."
msgstr ""
"Für die Datenbanktypen, die dies unterstützen, enthält Dbconfig-common "
"Unterstützung für die Konfiguration von Datenbanken auf anderen Systemen. "
"Bei der Installation einer Datenbank eines Pakets mittels dbconfig-common "
"werden die Fragen bezüglich einer Datenbank auf einem anderen System mit "
"solch einer Priorität gestellt, dass sie auf den meisten Systemen "
"ausgelassen werden."

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid ""
"If you select this option, the default behavior will be to prompt you with "
"questions related to remote database configuration when you install new "
"packages."
msgstr ""
"Falls Sie diese Option wählen, werden Ihnen standardmäßig Fragen mit Bezug "
"auf die Konfiguration von Datenbanken auf anderen Systemen gestellt, wenn "
"Sie neue Pakete installieren."

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:2001
msgid "If you are unsure, you should not select this option."
msgstr ""
"Falls Sie sich unsicher sind, sollten Sie diese Option nicht auswählen."

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid "Remember database passwords permanently in debconf?"
msgstr "Datenbankpassworte dauerhaft in Debconf ablegen?"

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid ""
"When you configure, upgrade, or remove applications with dbconfig-common, "
"administrator-level database passwords are needed. By default, these "
"passwords are not stored, so you will be prompted for them each time."
msgstr ""
"Wenn Sie Anwendungen mit dbconfig-common konfigurieren, entfernen oder ein "
"Upgrade dieser Anwendungen damit durchführen, werden Datenbanken mit "
"Passwörten für administrative Tätigkeiten benötigt. Standardmäßig werden "
"diese Passwörter nicht gespeichert und daher werden Sie jedes Mal nach Ihnen "
"gefragt."

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid ""
"Alternatively the passwords can be permanently remembered in the debconf "
"database (which is protected by Unix file permissions), though this is less "
"secure and thus not the default setting."
msgstr ""
"Alternativ können die Passwörter dauerhaft in der Debconf-Datenbank (die von "
"Unix-Dateirechten geschützt wird) abgelegt werden. Dies ist allerdings nicht "
"so sicher und daher nicht die Standard-Einstellung."

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:3001
msgid ""
"If you would rather not be bothered for an administrative password every "
"time you upgrade a database application with dbconfig-common, you should "
"choose this option. Otherwise, you should refuse this option."
msgstr ""
"Falls das administrative Passwort nicht bei jedem Upgrade der Datenbank-"
"Anwendung mit dbconfig-common aktualisiert werden soll, so wählen Sie diese "
"Option. Andernfalls sollten Sie diese Option ablehnen."

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:4001
msgid "Configure database for ${pkg} with dbconfig-common?"
msgstr "Konfigurieren der Datenbank für ${pkg} mit dbconfig-common?"

#. Type: boolean
#. Description
#: ../dbconfig-common.templates:4001
msgid ""
"The ${pkg} package must have a database installed and configured before it "
"can be used. This can be optionally 

Bug#932009: buster-pu: package gcab/1.2-3

[Stephen Kitt]

On Sat, 24 Aug 2019 10:21:24 +0100, "Adam D. Barratt"
 wrote:
> Thanks. Please go ahead.

Uploaded, thanks!

Regards,

Stephen


pgp5lbCq9vyUu.pgp
Description: OpenPGP digital signature

Bug#935585: node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export

[Pirate Praveen]

Control: block -1 by 930920

On Sat, 24 Aug 2019 11:29:57 +0200 Paul Gevers  wrote:
> autopkgtest [18:11:04]: test require: [---
> /usr/lib/nodejs/d3/node_modules/d3-scale/index.js:1
> (function (exports, require, module, __filename, __dirname) { export {
>   ^^
> 
> SyntaxError: Unexpected token export
> at new Script (vm.js:79:7)
> at createScript (vm.js:251:10)
> at Object.runInThisContext (vm.js:303:10)
> at Module._compile (internal/modules/cjs/loader.js:657:28)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
> at Module.load (internal/modules/cjs/loader.js:599:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
> at Function.Module._load (internal/modules/cjs/loader.js:530:3)
> at Module.require (internal/modules/cjs/loader.js:637:17)
> at require (internal/modules/cjs/helpers.js:22:18)
> autopkgtest [18:11:05]: test require: ---]
> 

I think the root cause is broken d3-format.js in node_modules

/usr/share/nodejs/d3$ ls node_modules/d3-format/d3-format.js -l
lrwxrwxrwx 1 root root 51 Aug 23 08:32
node_modules/d3-format/d3-format.js ->
../../../../share/javascript/d3-format/d3-format.js

Root cause is #930920 which forces me to embed d3-format and d3-scale in
the first place by adding lots of hacks.

Bug#935626: RFA: numba

[Mo Zhou]

Package: wnpp

Bug#935629: dput-ng: Upload method SFTP fails where SSH succeeds

[Nicolas Braud-Santoni]

Package: dput-ng
Version: 1.28
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

I recently switched from dput to dput-ng (due to needing the `dcut dm` command).

- - dput-ng complained about the scp method being deprecated, which was
  selected due to dput's old config being present;
- - I apt-purged dput;
- - since then, dput-ng fails to upload,
  presumably due to using Paramiko instead of OpenSSH.

Opening a bug because this is likely not intended behaviour.

> $ dput /opt/deb/buildarea/pam-u2f_1.0.7-1+deb10u1_source.changes 
> Uploading pam-u2f using sftp to ssh-upload (host: ssh.upload.debian.org; 
> directory: /srv/upload.debian.org/UploadQueue/)
> running allowed-distribution: check whether a local profile permits uploads 
> to the target distribution
> running protected-distribution: warn before uploading to distributions where 
> a special policy applies
> running checksum: verify checksums before uploading
> running suite-mismatch: check the target distribution for common errors
> running gpg: check GnuPG signatures before the upload
> Logging into host ssh.upload.debian.org as nicoo
> /usr/lib/python3/dist-packages/paramiko/ecdsakey.py:164: 
> CryptographyDeprecationWarning: Support for unsafe construction of public 
> numbers from encoded data will be removed in a future version. Please use 
> EllipticCurvePublicKey.from_encoded_point
>   self.ecdsa_curve.curve_class(), pointinfo
> /usr/lib/python3/dist-packages/paramiko/kex_ecdh_nist.py:39: 
> CryptographyDeprecationWarning: encode_point has been deprecated on 
> EllipticCurvePublicNumbers and will be removed in a future version. Please 
> use EllipticCurvePublicKey.public_bytes to obtain both compressed and 
> uncompressed point encoding.
>   m.add_string(self.Q_C.public_numbers().encode_point())
> /usr/lib/python3/dist-packages/paramiko/kex_ecdh_nist.py:96: 
> CryptographyDeprecationWarning: Support for unsafe construction of public 
> numbers from encoded data will be removed in a future version. Please use 
> EllipticCurvePublicKey.from_encoded_point
>   self.curve, Q_S_bytes
> /usr/lib/python3/dist-packages/paramiko/kex_ecdh_nist.py:111: 
> CryptographyDeprecationWarning: encode_point has been deprecated on 
> EllipticCurvePublicNumbers and will be removed in a future version. Please 
> use EllipticCurvePublicKey.public_bytes to obtain both compressed and 
> uncompressed point encoding.
>   hm.add_string(self.Q_C.public_numbers().encode_point())
> please login: To accept ssh-ed25519 hostkey 
> b'5c90717e5b00364ec2130d9d7a46e4f7' for ssh.upload.debian.org type "yes": 
> [yes, no]: yes
> Exception: key cannot be used for signing
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/paramiko/transport.py", line 2036, in 
> run
> handler(self.auth_handler, m)
>   File "/usr/lib/python3/dist-packages/paramiko/auth_handler.py", line 298, 
> in _parse_service_accept
> sig = self.private_key.sign_ssh_data(blob)
>   File "/usr/lib/python3/dist-packages/paramiko/agent.py", line 418, in 
> sign_ssh_data
> raise SSHException("key cannot be used for signing")
> paramiko.ssh_exception.SSHException: key cannot be used for signing
> 
> SFTP error uploading to ssh.upload.debian.org: SSHException('No existing 
> session')
> 
> $ ssh -N ssh.upload.debian.org
> Linux usper 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64
> 
> This device is for authorized users only.  All traffic on this device
> is monitored and will be used as evidence for prosecutions.  By using
> this machine you agree to abide by the Debian Machines Usage Policies
> https://www.debian.org/devel/dmup>.
> 
> %%
> 
>  Francesco Usper (November 1st, 1561 - February 24th, 1641)
> 
>  Welcome to usper.debian.org, used for the following services:
> ftp.upload.debian.org - FTP upload queue
> ssh.upload.debian.org - SSH upload queue
> 
>  This virtual server runs on the cluster ganeti.csail.debian.org, which is
>  hosted at csail.
>  
> %%


Using a ~/.dput.cf snippet to revert to the SCP method (as opposed to SFTP)
works.


Best,

  nicoo


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dput-ng depends on:
ii  python3   3.7.3-1
ii  python3-dput  1.28

dput-ng recommends no 

Bug#935568: sphinx-issuetracker: should this package be removed?

[Dmitry Shachnev]

Hi Sandro!

On Fri, Aug 23, 2019 at 10:46:30PM -0400, Sandro Tosi wrote:
> Hello,
> sphinx-issuetracker is currently incompatible with python3.7:
> [...]
>
> It has no reverse-dependencies and it's currently one of the few r-deps of
> python-debianbts.
>
> Should we just remove this package from Debian?

I support the removal.

However, there is one reverse build-dependency: src:migrate.
But it looks like use of issuetracker is actually patched away:
https://sources.debian.org/src/migrate/0.12.0-3/debian/patches/disable_issuetracker.patch/

Dear migrate maintainers (Cc'ed), can you please check if that
build-dependency is still needed?

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#935634: RM: mosquitto-auth-plugin -- NBS; Upstream dead

[Adam Majer]

Package: ftp.debian.org
Severity: normal

Package fails to build from source with current dependencies.
Upstream closed upstream project for personal reasons

Bug#935636: ITP: crypto-policies - unify the crypto policies used by different applications and libraries

[Hideki Yamane]

Package: wnpp
Severity: wishlist

* Package name: crypto-policies
  Version : 20190816~git
  Upstream Author : Red Hat, Inc.
* URL : https://gitlab.com/redhat-crypto/fedora-crypto-policies/
* License : LGPL-2.1+
  Programming Lang: Python
  Description: unify the crypto policies used by different applications and 
libraries

 "crypto-policies" is a utility to unify the crypto policies used by different
 applications and libraries. The current implementations works by setting the
 desired policy in /etc/crypto-policies/config. After this file is changed
 the script 'update-crypto-policies' should be executed, and the new policies
 will activate.
 .
 The supported back ends are:
  - GnuTLS
  - OpenSSL
  - NSS
  - BIND9
  - libkrb5
  - OpenSSH
  - Java (OpenJDK)
  - libssh

Bug#874855: [codequery] Future Qt4 removal from Buster

[Reiner Herrmann]

Control: tags -1 + patch

Dear maintainer,

Qt5 is already supported and can be easily enabled with the attached
patch (which also fixes #886193).

Kind regards,
  Reiner
diff -Nru codequery-0.21.1+dfsg1/debian/control codequery-0.21.1+dfsg1/debian/control
--- codequery-0.21.1+dfsg1/debian/control	2018-10-31 07:51:35.0 +0100
+++ codequery-0.21.1+dfsg1/debian/control	2019-08-24 20:27:14.0 +0200
@@ -5,8 +5,10 @@
 Build-Depends: debhelper (>= 11),
asciidoc,
cmake,
-   libqscintilla2-dev,
+   libqscintilla2-qt5-dev,
libsqlite3-dev,
+   qtbase5-dev,
+   qttools5-dev,
xmlto,
 Standards-Version: 4.2.1
 Homepage: https://github.com/ruben2020/codequery
diff -Nru codequery-0.21.1+dfsg1/debian/rules codequery-0.21.1+dfsg1/debian/rules
--- codequery-0.21.1+dfsg1/debian/rules	2018-10-31 07:47:54.0 +0100
+++ codequery-0.21.1+dfsg1/debian/rules	2019-08-24 20:27:14.0 +0200
@@ -11,7 +11,7 @@
 override_dh_auto_configure:
 	cat debian/*manpages | sed 's/$$/.txt/p' | xargs -n 1 a2x --attribute=footer-style=none --doctype manpage --format manpage
 	perl -pi -e 's/build/obj-$(DEB_HOST_GNU_TYPE)/' gui/codequery.qrc
-	dh_auto_configure
+	dh_auto_configure -- -DBUILD_QT5=YES
 
 override_dh_clean:
 	dh_clean


signature.asc
Description: PGP signature

Bug#932009: buster-pu: package gcab/1.2-3

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Fri, 2019-08-23 at 21:34 +0200, Stephen Kitt wrote:
> On Fri, 26 Jul 2019 16:35:49 -0300, "Adam D. Barratt"
>  wrote:
> > On 2019-07-13 15:52, Stephen Kitt wrote:
[...]
> > > Would it be possible to consider a stable update to gcab 1.2-3
> > > (or its
> > > equivalent as a stable upload)? It fixes a data corruption bug,
> > > #913487; that’s the only change between 1.2-2, which is in
> > > Buster, and
> > > 1.2-3, which is in Bullseye. The debdiff is as follows:
> > > 
> > > diff -Nru gcab-1.2/debian/changelog gcab-1.2/debian/changelog
> > > --- gcab-1.2/debian/changelog 2018-12-22 12:37:31.0
> > > +0100
> > > +++ gcab-1.2/debian/changelog 2019-07-06 10:18:07.0
> > > +0200
> > > @@ -1,3 +1,10 @@
> > > +gcab (1.2-3) unstable; urgency=medium  
> > 
> > While this is probably fine, please could we have a debdiff
> > versioned as 
> > 1.2-2+deb10u1 (or 1.2-3~deb10u1 if you prefer and it is exactly the
> > same 
> > content as -3), using a changelog distribution of "buster" and
> > built / 
> > prepared on buster?
> 
> Here goes:

Thanks. Please go ahead.

Regards,

Adam

Bug#935583: buster-pu: package babeltrace/1.5.6-2+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2019-08-24 at 10:53 +0200, Andreas Beckmann wrote:
> babeltrace/buster ships a symbols file with insufficient versioning,
> allowing the stretch packages to satisfy the dependencies, even if
> they
> don't ship the sublibraries.
> This is a backport of the relevant changes from 1.5.7-1 in sid.
> 

Please go ahead.

Regards,

Adam

Bug#842892: java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model

[Andreas Beckmann]

Followup-For: Bug #842892

Hi,

I've just opened 2 PU requests to get this bug fixed in buster and
stretch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935576
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935581

Andreas

Bug#935588: nmu: rdepends of libbabeltrace1/buster

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: binnmu
Control: block -1 with 935583

As a followup to tightening the versions in the libbabeltrace1 symbols
file rebuild gdb to tighten the libbabeltrace1 dependency. (See #931147)

Actually all rdepends need to be rebuilt, since all have ldd report
  libbabeltrace-ctf.so.1 => not found
on some binary if libbabeltrace1 1.5.1-1 is installed.

Checking reverse dependencies...
# Broken Depends:
babeltrace: babeltrace
libbabeltrace-ctf1
libbabeltrace-dev
python3-babeltrace
ceph: ceph-common
gdb: gdb [amd64 armel armhf i386 mips mipsel s390x]
 gdb-multiarch [amd64 armel armhf i386 mips mipsel s390x]
gdb-mingw-w64: gdb-mingw-w64
linux: linux-perf-4.19
lttv: lttv

nmu gdb_8.2.1-2 . ANY . buster . -m "Rebuild against libbabeltrace1 
1.5.6-2+deb10u1"
dw gdb_8.2.1-2 . ANY . buster . -m "libbabeltrace1 (>= 1.5.6-2+deb10u1)"
nmu gdb-mingw-w64_10.8 . ANY . buster . -m "Rebuild against libbabeltrace1 
1.5.6-2+deb10u1"
dw gdb-mingw-w64_10.8 . ANY . buster . -m "libbabeltrace1 (>= 1.5.6-2+deb10u1)"
nmu ceph_12.2.11+dfsg1-2.1 . ANY . buster . -m "Rebuild against libbabeltrace1 
1.5.6-2+deb10u1"
dw ceph_12.2.11+dfsg1-2.1 . ANY . buster . -m "libbabeltrace1 (>= 
1.5.6-2+deb10u1)"
nmu lttv_1.5-3 . ANY . buster . -m "Rebuild against libbabeltrace1 
1.5.6-2+deb10u1"
dw lttv_1.5-3 . ANY . buster . -m "libbabeltrace1 (>= 1.5.6-2+deb10u1)"
nmu linux . ANY . buster . -m "Rebuild against libbabeltrace1 1.5.6-2+deb10u1"
dw linux . ANY . buster . -m "libbabeltrace1 (>= 1.5.6-2+deb10u1)"


Andreas

Bug#932611: Fixed in 1.1.0

[darkdragon]

The dependency was removed in version 1.1.0 (see
https://github.com/novnc/noVNC/issues/1075).

Bug#935454: pymca: autopkgtest regression: Segmentation fault

[Paul Gevers]

Control: block 935454 by 933056

On 22-08-2019 23:13, PICCA Frederic-Emmanuel wrote:
> This regression is due to a bug in python-numpy #933056, that I already 
> reported, whcih was solved upstream and will be available in the 0.17 version.

So, let's tell the BTS that as well.

Thanks for investigating well back.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#933118: libwww-search-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer

[gregor herrmann]

On Fri, 26 Jul 2019 16:39:11 -0300, intrig...@debian.org wrote:

> If libwww-search-perl is suitable for Bullseye, please either port
> libwww-search-perl away from pkg-components or consider taking over
> its maintenance upstream.

I have a local branch which doesn't use pkg-components any more but
the new component features of gbp and uscan, and some loops in
d/rules … following the nice docs at
https://wiki.debian.org/Javascript/GroupSourcesTutorial

What keeps me from uploading is that the version number, with the
"group"ing approach in d/watch, is
2.51.80+~2.154+~3.052+~1.14+~0.02+~1.02+~2.225+~0.14+~2.415-1
which is a bit ugly (and lintian also complains about long file names
which might cause issues somewhere, probably because of this).

If I'm understanding uscan(1) correctly, instead of "group" we could
also use "ignore" in d/watch, then we're back at 2.51.80-n but then
we probably never learn about updates of the components, and updating
a single component is probably also an issue?

/cc-ing yadd as the uscan expert :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Alanis Morisette: 21 Things I Want In A Lover


signature.asc
Description: Digital Signature

Bug#931801: [debian-mysql] Bug#931801: mariadb-server-core-10.3: mysqld segfaults when database `information_schema` is accessed

[Otto Kekäläinen]

Control: fixed -1 1:10.3.17-1

This is fixed in the version in Debian unstable and will be fixed for
Buster in next stable point release.

Bug#935607: lintian: classify "Starting $DESC" in init.d scripts

[Chris Lamb]

# marking as moreinfo simply for triage
tags 935607 + moreinfo
thanks

Hi Dmitry,

> some init.d script print description of service they are starting with
> following line:
> 
>   log_daemon_msg "Starting X display manager" "xdm"
> or
>   log_action_begin_msg "Starting $DESC"
> 
> The pattern is `"Starting '. Some (minority, I think) do the same, but
> only if $VERBOSE != no, like this:
> 
>   [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"

Can you describe what is wrong with this? (So we can add it to the
long description at the very least...)

Also, do we need to do this for "stop" or other actions too?

> Please add classification tag, that distinguish these cases. After that,
> minority behaviour could be marked with minor severity tag

Just FYI what we prefer to do here is to mark it as 'experimental' but
the idea is the same (ie. fix false-positives first).


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#934816: tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Control: severity -1 serious

Increasing severity to 'serious' since this is one of the 5 packages
what still depend on libmariadbclient18, which will soon be removed
from unstable and then render this package uninstallable. Please
rebuild and upload, so that the package will automatically be built
and depend on newest libraries (including libmariadb3 which has
replaced libmariadbclient18).

debian-sid$ apt-rdepends -r libmariadbclient18
libmariadbclient18
  Reverse Depends: libdballe7 (>= 7.21-1+b1)
  Reverse Depends: libmysql++3v5 (>= 3.2.2+pristine-2)
  Reverse Depends: mosquitto-auth-plugin (>= 0.1.2-1+b1)
  Reverse Depends: stardict-tools (>= 3.0.6-0.2)
  Reverse Depends: tcl8.6-tdbc-mysql (1.1.0-2+b1)

Bug#934814: libdballe7: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Control: severity -1 serious

Increasing severity to 'serious' since this is one of the 5 packages
what still depend on libmariadbclient18, which will soon be removed
from unstable and then render this package uninstallable. Please
rebuild and upload, so that the package will automatically be built
and depend on newest libraries (including libmariadb3 which has
replaced libmariadbclient18).

debian-sid$ apt-rdepends -r libmariadbclient18
libmariadbclient18
  Reverse Depends: libdballe7 (>= 7.21-1+b1)
  Reverse Depends: libmysql++3v5 (>= 3.2.2+pristine-2)
  Reverse Depends: mosquitto-auth-plugin (>= 0.1.2-1+b1)
  Reverse Depends: stardict-tools (>= 3.0.6-0.2)
  Reverse Depends: tcl8.6-tdbc-mysql (1.1.0-2+b1)