Bug#932598: Upgrade to buster fails with start-stop-daemon error
Package: sendmail Version: 8.15.2-12 Severity: grave Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On upgrade to buster, sendmail upgrade failed with this message: > start-stop-daemon: matching only on non-root pidfile > /var/run/sendmail/mta/sendmail.pid is insecure Some work with Google found Debian bug #922395, which, although not for sendmail, pointed the way to the solution. The following patch for /etc/init.d/sendmail should fix the problem: - - CUT HERE -- *** sendmail.orig 2019-07-20 23:35:49.360737086 -0400 - --- sendmail 2019-07-20 22:40:04.782571907 -0400 *** *** 149,163 - --- 149,166 --start"; STOP_MTAL_CMD="start-stop-daemon \ --pidfile $MTAL_PIDFILE \ + --exec $MTA_DAEMON \ --name sendmail-mta \ --stop"; SIGNAL_MTAL_CMD="start-stop-daemon \ --pidfile $MTAL_PIDFILE \ + --exec $MTA_DAEMON \ --name sendmail-mta \ --stop"; START_MTAQ_CMD="start-stop-daemon \ --pidfile $MTAQ_PIDFILE \ --make-pidfile \ + --exec $MTA_DAEMON \ --startas $MTA_COMMAND \ --start"; STOP_MTAQ_CMD="start-stop-daemon \ *** *** 165,170 - --- 168,174 --stop"; SIGNAL_MTAQ_CMD="start-stop-daemon \ --pidfile $MTAQ_PIDFILE \ + --exec $MTA_DAEMON \ --name sendmail-mta \ --stop"; START_MSP_CMD="start-stop-daemon \ - - CUT HERE -- It may also be necessary to delete /var/run/sendmail/mta/sendmail.pid as well. Note: Although probably not a sendmail problem (start-stop daemon?), it might be advisable to re-word the error message. "matching only on non-root pidfile xxx.pid is insecure" is rather cryptic, and does not point the way to fixing the problem. .Ron Murray - -- Package-specific info: Output of /usr/share/bug/sendmail/script: ls -alR /etc/mail: /etc/mail: total 568 drwxr-sr-x 8 smmta smmsp 4096 Jul 20 22:42 . drwxr-xr-x 260 root root 16384 Jul 20 23:16 .. - -rwxr-xr-- 1 root smmsp 12904 Jul 20 22:42 Makefile - -rw--- 1 root smmsp 5526 Jul 20 22:42 access - -rw-r- 1 smmta smmsp 12288 Jul 20 22:42 access.db - -rw-r--r-- 1 root smmsp 5432 Jul 2 2018 access.old - -rw--- 1 root root 2084 Nov 4 2014 access.orig - -rw-r--r-- 1 root root281 Sep 5 2004 address.resolve lrwxrwxrwx 1 root smmsp10 Mar 28 2015 aliases -> ../aliases - -rw-r- 1 smmta smmsp 12288 Jul 21 2017 aliases.db - -rw-r--r-- 1 root root 1040 Nov 25 2007 aliases.orig drwx--S--- 2 root smmsp45 Jun 18 2017 auth - -rw-r--r-- 1 root root 3722 Jul 20 22:42 databases - -rw-r--r-- 1 root root 3720 Oct 22 2014 databases.orig - -rw-r- 1 smmta smmsp42 Apr 7 2004 default-auth-info - -rw-r--r-- 1 smmta smmsp 0 Oct 1 2000 domaintable - -rw-r--r-- 1 root root 5659 Dec 8 2016 helpfile - -rw-r--r-- 1 smmta smmsp21 Apr 7 2004 local-host-names drwxr-sr-x 2 smmta smmsp81 Jul 20 20:54 m4 - -rw-r--r-- 1 smmta smmsp15 Sep 25 2008 mailertable - -rw-r- 1 root smmsp 12288 Jun 18 2017 mailertable.db - -rw-r--r-- 1 smmta smmsp 12973 Jun 4 2015 mimedefang-filter - -rw-r--r-- 1 smmta smmsp 12973 Jun 4 2015 mimedefang-filter.spamassassin - -rw-r--r-- 1 smmta smmsp 4108 Aug 18 2006 mimedefang.conf.12596 - -rw-r--r-- 1 smmta smmsp 4108 Dec 28 2006 mimedefang.conf.13657 - -rw-r--r-- 1 smmta smmsp 4108 Jan 30 2007 mimedefang.conf.15047 - -rw-r--r-- 1 smmta smmsp 4108 Mar 16 2007 mimedefang.conf.25782 - -rw-r--r-- 1 smmta smmsp 4108 Apr 26 2005 mimedefang.conf.5937 - -rw-r--r-- 1 smmta smmsp 4108 Nov 21 2006 mimedefang.conf.6382 - -rw-r--r-- 1 smmta smmsp 4108 Mar 27 2006 mimedefang.conf.7263 - -rw-r--r-- 1 root root276 Feb 11 2005 mimedefang.pl.conf drwxr-xr-x 2 root root 21 Jul 20 20:51 peers - -rw-r--r-- 1 smmta smmsp 0 Jan 30 2002 relay-domains - -rw-r--r-- 1 root root 4297 May 14 2018 sa-mimedefang.cf drwxr-xr-x 2 smmta smmsp 132 May 24 2015 sasl - -rw-r--r-- 1 smmta smmsp54 Apr 4 2015 sendmail.cN - -rw-r--r-- 1 root smmsp 75517 Jul 20 22:42 sendmail.cf - -rw-r--r-- 1 root root 75514 Jul 20 22:42 sendmail.cf.old - -rw-r--r-- 1 root root 12235 Jul 20 22:42 sendmail.conf - -rw-r--r-- 1 root root 1 Oct 22 2014 sendmail.conf.orig - -rw-r--r-- 1 smmta smmsp15 Apr 3 2015 sendmail.ct - -rw-r--r-- 1 smmta smmsp 209 Mar 2 2008 sendmail.cw - -rw-r--r-- 1 root smmsp 8600 Jul 20 22:42 sendmail.mc - -rw-r--r-- 1 root root148 Sep 15 2018 service.switch - -rw-r--r-- 1 root root179 Sep 15 2018 service.switch-nodns drwxr-sr-x 2 smmta smmsp53 Nov 7 2014 smrsh lrwxrwxrwx 1 root root 15
Bug#928631: firmware-amd-graphics: Removing vega20 firmware files corrects the problem on my system
Package: firmware-amd-graphics Version: 20190502-1 Followup-For: Bug #928631 Dear Maintainer, Updating to any version of the firmware-amd-graphics with the vega20 firmware causes my system to hang during boot after grub. Removing all the vega20 firmware files and causing initrd to rebuild corrects the problem and system boots normally. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/32 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.133 -- no debconf information
Bug#932592: [Pkg-giraffe-maintainers] Bug#932592: kopano-webapp: autopkgtest regression
Hello Jelle, it would be great if you on upstream could have a look at this! Looking at the history in ci.d.n it's visible this problem is alive since the Chromium version 76.0.3809.62-1, the previous version works fine. Maybe some kid of lovely API change ... https://ci.debian.net/packages/k/kopano-webapp/testing/amd64/ Am 21.07.19 um 02:27 schrieb Michael Gilbert: > package: src:kopano-webapp > severity: serious > version: 3.5.6+dfsg1-1 > > kopano-webapp currently has a failing autopkgtest [0]. This currently > blocks migration of chromium since it is listed as an autopkgtest > dependency for this package. > > == > ERROR: test_login (test_webapp.TestWebApp) > -- > Traceback (most recent call last): > File > "/tmp/autopkgtest-lxc.720_qx5v/downtmp/build.vfl/src/debian/tests/test_webapp.py", > line 70, in test_login > elem.click() > File > "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webelement.py", > line 80, in click > self._execute(Command.CLICK_ELEMENT) > File > "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webelement.py", > line 633, in _execute > return self._parent.execute(command, params) > File > "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", > line 321, in execute > self.error_handler.check_response(response) > File > "/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", > line 242, in check_response > raise exception_class(message, screen, stacktrace) > selenium.common.exceptions.JavascriptException: Message: javascript > error: circular reference > (Session info: headless chrome=76.0.3809.62) > > It looks like a selenium issue, but I haven't debugged further than > reading this log. If it has to do with chromium-driver, please create > a chromium bug with more information. > > Best wishes, > Mike > > [0] https://ci.debian.net/packages/k/kopano-webapp/testing/amd64/ -- Regards Carsten Schoenert
Bug#932592: kopano-webapp: autopkgtest regression
package: src:kopano-webapp severity: serious version: 3.5.6+dfsg1-1 kopano-webapp currently has a failing autopkgtest [0]. This currently blocks migration of chromium since it is listed as an autopkgtest dependency for this package. == ERROR: test_login (test_webapp.TestWebApp) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.720_qx5v/downtmp/build.vfl/src/debian/tests/test_webapp.py", line 70, in test_login elem.click() File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webelement.py", line 80, in click self._execute(Command.CLICK_ELEMENT) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webelement.py", line 633, in _execute return self._parent.execute(command, params) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute self.error_handler.check_response(response) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.JavascriptException: Message: javascript error: circular reference (Session info: headless chrome=76.0.3809.62) It looks like a selenium issue, but I haven't debugged further than reading this log. If it has to do with chromium-driver, please create a chromium bug with more information. Best wishes, Mike [0] https://ci.debian.net/packages/k/kopano-webapp/testing/amd64/
Bug#932591: librust-exa+git-dev: depends on old version of librust-cargo-dev
Package: librust-exa+git-dev Version: 2.2.10-1 Severity: serious Tags: sid User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan Hi Ximin, The librust-exa+git-dev package is uninstallable in unstable because it depends on older ABIs of librust-git2-dev: $ sudo apt install librust-exa+git-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: librust-exa+git-dev : Depends: librust-git2-0.7-dev E: Unable to correct problems, you have held broken packages. $ Please update this package. -- 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
Processed (with 2 errors): Connect bugs related to epydoc and pychecker
Processing commands for cont...@bugs.debian.org: > # Removal of pychecker is blocked by spe, a reverse dependency > severity 930398 serious Bug #930398 [spe] spe: Pychecker will be removed after buster Severity set to 'serious' from 'normal' > block 932575 by 930398 Bug #932575 [ftp.debian.org] RM: pychecker -- ROM; Obsolete (Python 2) and Unmaintained 932575 was not blocked by any bugs. 932575 was not blocking any bugs. Added blocking bug(s) of 932575: 930398 > # Removal of pychecker is blocked by python-mode, a reverse dependency > severity 930399 serious Bug #930399 [python-mode] python-mode: Pychecker will be removed after buster Severity set to 'serious' from 'normal' > block 932575 by 930399 Bug #932575 [ftp.debian.org] RM: pychecker -- ROM; Obsolete (Python 2) and Unmaintained 932575 was blocked by: 930398 932575 was not blocking any bugs. Added blocking bug(s) of 932575: 930399 > # Removal of pychecker is blocked by boa-constructor, a reverse dependency > severity 930400 serious Bug #930400 [boa-constructor] boa-constructor: Pychecker will be removed after buster Severity set to 'serious' from 'normal' > block 932575 by 930400 Bug #932575 [ftp.debian.org] RM: pychecker -- ROM; Obsolete (Python 2) and Unmaintained 932575 was blocked by: 930399 930398 932575 was not blocking any bugs. Added blocking bug(s) of 932575: 930400 > # Removal of epydoc is blocked by pydoctor, a reverse dependency > block 932584 by 881550 Bug #932584 [python-pydoctor] python-pydoctor: Epydoc will be removed 932584 was not blocked by any bugs. 932584 was not blocking any bugs. Added blocking bug(s) of 932584: 881550 > block 932574 by 932584 Bug #932574 [ftp.debian.org] RM: epydoc -- ROM; Obsolete (Python 2) and Unmaintained 932574 was not blocked by any bugs. 932574 was not blocking any bugs. Added blocking bug(s) of 932574: 932584 > # Removal of epydoc is blocked by pywbem, a reverse dependency > block 932585 by 881560 Bug #932585 [python-pywbem] python-pywbem: Eypdoc will be removed 932585 was not blocked by any bugs. 932585 was not blocking any bugs. Added blocking bug(s) of 932585: 881560 > block 932574 by 932585 Bug #932574 [ftp.debian.org] RM: epydoc -- ROM; Obsolete (Python 2) and Unmaintained 932574 was blocked by: 932584 932574 was not blocking any bugs. Added blocking bug(s) of 932574: 932585 > # Removal of epydoc is related to these bugs against reverse build > dependencies Unknown command or malformed arguments to command. > affects 932574 + 881546 881547 881548 881551 881552 881553 881555 881556 Bug #932574 [ftp.debian.org] RM: epydoc -- ROM; Obsolete (Python 2) and Unmaintained Added indication that 932574 affects 881546, 881547, 881548, 881551, 881552, 881553, 881555, and 881556 > 881557 881558 881561 881563 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 930398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930398 930399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930399 930400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930400 932574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932574 932575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932575 932584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932584 932585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: autopkgtest failures are now RC; raising severity for *existing* bugs
Processing commands for cont...@bugs.debian.org: > # The release team has announced that autopkgtest failure is now RC > # https://lists.debian.org/debian-devel-announce/2019/07/msg2.html > severity 901779 serious Bug #901779 [src:debirf] debirf: autopkgtest fails because script is not executable Severity set to 'serious' from 'normal' > reassign 909276 qbzr 0.23.2-4 Bug #909276 [src:xorg-server, src:qbzr] xorg-server breaks qbzr autopkgtest: AssertionError: Timeout! Bug reassigned from package 'src:xorg-server, src:qbzr' to 'qbzr'. No longer marked as found in versions qbzr/0.23.2-4 and xorg-server/2:1.20.1-3. Ignoring request to alter fixed versions of bug #909276 to the same values previously set Bug #909276 [qbzr] xorg-server breaks qbzr autopkgtest: AssertionError: Timeout! Marked as found in versions qbzr/0.23.2-4. > found 909276 0.23.2-6 Bug #909276 [qbzr] xorg-server breaks qbzr autopkgtest: AssertionError: Timeout! Marked as found in versions qbzr/0.23.2-6. > severity 909276 serious Bug #909276 [qbzr] xorg-server breaks qbzr autopkgtest: AssertionError: Timeout! Severity set to 'serious' from 'normal' > # boost1.62 isn't in testing anymore anyways > reassign 914043 boost1.62 Bug #914043 [src:boost-defaults, src:boost1.62] boost-defaults breaks boost1.62 autopkgtest Bug reassigned from package 'src:boost-defaults, src:boost1.62' to 'boost1.62'. No longer marked as found in versions boost1.62/1.62.0+dfsg-10 and boost-defaults/1.67.0.1. Ignoring request to alter fixed versions of bug #914043 to the same values previously set > severity 914043 serious Bug #914043 [boost1.62] boost-defaults breaks boost1.62 autopkgtest Severity set to 'serious' from 'normal' > reassign 920545 python-intervaltree-bio 1.0.1-2 Bug #920545 [src:python-intervaltree, src:python-intervaltree-bio] python-intervaltree breaks python-intervaltree-bio autopkgtest Bug reassigned from package 'src:python-intervaltree, src:python-intervaltree-bio' to 'python-intervaltree-bio'. No longer marked as found in versions python-intervaltree/3.0.2-1 and python-intervaltree-bio/1.0.1-2. Ignoring request to alter fixed versions of bug #920545 to the same values previously set Bug #920545 [python-intervaltree-bio] python-intervaltree breaks python-intervaltree-bio autopkgtest Marked as found in versions python-intervaltree-bio/1.0.1-2. > severity 920545 serious Bug #920545 [python-intervaltree-bio] python-intervaltree breaks python-intervaltree-bio autopkgtest Severity set to 'serious' from 'important' > reassign 921384 node-xmpp 0.3.2-4 Bug #921384 [src:node-stringprep, src:node-xmpp] node-stringprep breaks node-xmpp autopkgtest Bug reassigned from package 'src:node-stringprep, src:node-xmpp' to 'node-xmpp'. No longer marked as found in versions node-stringprep/0.8.0-5 and node-xmpp/0.3.2-4. Ignoring request to alter fixed versions of bug #921384 to the same values previously set Bug #921384 [node-xmpp] node-stringprep breaks node-xmpp autopkgtest There is no source info for the package 'node-xmpp' at version '0.3.2-4' with architecture '' Unable to make a source version for version '0.3.2-4' Marked as found in versions 0.3.2-4. > severity 921384 serious Bug #921384 [node-xmpp] node-stringprep breaks node-xmpp autopkgtest Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 901779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901779 909276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909276 914043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914043 920545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920545 921384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932585: python-pywbem: Eypdoc will be removed
Package: python-pywbem Severity: serious Justification: Policy 5.9.2 Hi, This is one of several packages in the archive that still depend on Epydoc. I have filed a bug with ftp.debian.org to have epydoc removed from unstable. Besides its lack of support for Python 3, epydoc has been completely unsupported upstream for close to a decade. It really should have been removed from the archive years ago. Thanks, KEN
Bug#932584: python-pydoctor: Epydoc will be removed
Package: python-pydoctor Severity: serious Justification: Policy 5.9.2 Hi, This is one of several packages in the archive that still depend on Epydoc. I have filed a bug with ftp.debian.org to have epydoc removed from unstable. Besides its lack of support for Python 3, epydoc has been completely unsupported upstream for close to a decade. It really should have been removed from the archive years ago. Thanks, KEN
Bug#902828: marked as done (pgpdump: autopkgtest regression: sh: 0: Can't open debian/test)
Your message dated Sat, 20 Jul 2019 21:09:50 + with message-id and subject line Bug#902828: fixed in pgpdump 0.33-2 has caused the Debian Bug report #902828, regarding pgpdump: autopkgtest regression: sh: 0: Can't open debian/test to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 902828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgpdump Version: 0.33-1 User: debian...@lists.debian.org Usertags: regression Dear maintainers, Since the upload of 0.33-1, your package fails its autopkgtest in both unstable and testing, with the error copied below. It seems you dropped the file you wanted to test somewhere during packaging. This regression is causing your package to have to wait 13 extra days to migrate to testing. Thanks for consideration. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/p/pgpdump/533316/log.gz autopkgtest [19:13:36]: test command1: [--- sh: 0: Can't open debian/test autopkgtest [19:13:36]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pgpdump Source-Version: 0.33-2 We believe that the bug you reported is fixed in the latest version of pgpdump, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 902...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated pgpdump package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Jul 2019 12:33:15 +0200 Source: pgpdump Binary: pgpdump Architecture: source Version: 0.33-2 Distribution: unstable Urgency: medium Maintainer: Debian GnuPG Maintainers Changed-By: Gianfranco Costamagna Description: pgpdump- PGP packet visualizer Closes: 902828 Changes: pgpdump (0.33-2) unstable; urgency=medium . [ Gianfranco Costamagna ] * Fix testsuite, force UTC as timestamp * Team upload. . [ Steve Langasek ] * Restore dropped debian/test. Closes: #902828. Checksums-Sha1: 73c5d0fc40b374ee833c05deeacfd5bf77904301 2005 pgpdump_0.33-2.dsc f3a35460e15b2fcb3f30b77eb7af2d9d3c80fe62 5152 pgpdump_0.33-2.debian.tar.xz 8a4cba8feace91dc3dbf82cfe06b629238b8df37 7091 pgpdump_0.33-2_source.buildinfo Checksums-Sha256: 6e905f4fed7953098e971a6d668fe6eceab29dc1fe0da21213d8e6722b631839 2005 pgpdump_0.33-2.dsc be51c729f200636da706f80c847aee1872116a9e0673192832403324874133f2 5152 pgpdump_0.33-2.debian.tar.xz 98f5e5d2ecca7dd13b3e4e1288911108991f76f7c46ffd8abdb21c567bfc6bc3 7091 pgpdump_0.33-2_source.buildinfo Files: a6557706112445e6313f27cf423ffe71 2005 utils optional pgpdump_0.33-2.dsc 35b6a64ae630f05e8578c691ad521c18 5152 utils optional pgpdump_0.33-2.debian.tar.xz 78e87f150e3d8f6dc4039b4104bc85e9 7091 utils optional pgpdump_0.33-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl0qQHcACgkQ808JdE6f XdnwQg/+JxKDw1MP548h4NEiGEKnYdWcQaQFvbqLPOZk/1YTOP2LalR0fgnd6qVm +m1nOj5alSLTLkEKFGdfqCx3gTg2qujmqdOQT5mbPis9YW7+30Xm3KL5hBk53c1L 1oBuFrxh0Va545L/JVhyibuE1ASPGQ6zN1xvz17mSoGKYLO3HY0B/QMRibW2lBbB vKvkd4LOzWzkUhssR/+viAFb7mNDokxW6+ya2WGIQsSoKjnDugWbMd1YoI0xjTg8 8GZD5viL+POD6UmQrLEcoNZc+St/sDwL2yZcPZ/RZCBc07i+BBdv1OvnAMyedMPD x7os5+AdfBR0VfDKSWesLP/8SmRa7FBGRv+svZMW1cNJYtbmQBLP+mc3BkWQzZPF TCwJ1j+xL1zWC5QTOaCM+BHQBEVhAjXq8mp80PZSwmULiWSLasAvemu6N/qvX7ay a9nrEsZwDAsXhyR273Dco0hpCTu3rlerN6VH5hvl68jAJAn54+P9sWLdBhV0WQEF B0CjhMWcBNaK+uRVxzxmPhu7P2qa/BJ9C8O9AMooeid+WW3IwLn5PvI2nOCouHBw a4kSQrs5HNxiITQYhl1JCzHYsfbj0HTp54fnvXvqmSyH6Hf4GpLiCB+dk5O7LyqD CcqRTbEi761SEr+8T2ae/HC8i23rO+QLTLT83AcFTxrFpCXTgyA= =p2V5 -END PGP SIGNATURE End Message ---
Bug#932582: anbox: ignores mouse input
Package: anbox Version: 0.0~git20190124-1 Severity: grave Justification: renders package unusable I am able to launch the android apps from the desktop menu, but cannot interact other than moving the window around and fullscreening. I thought this was reported upstream as [#780], but the fix was merged in [bbf05d8f3] on 2019-01-06 and so included in the debian version. [#780]: https://github.com/anbox/anbox/issues/780 [bbf05d8f3]: https://github.com/anbox/anbox/commit/bbf05d8f3267ef5fb102525c372183aaa83df830 -- Phil Morrell (emorrp1) -- System Information: Debian Release: 10.0 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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 anbox depends on: ii iptables1.8.2-4 ii libboost-atomic1.67.0 1.67.0-13 ii libboost-chrono1.67.0 1.67.0-13 ii libboost-date-time1.67.01.67.0-13 ii libboost-filesystem1.67.0 1.67.0-13 ii libboost-iostreams1.67.01.67.0-13 ii libboost-log1.67.0 1.67.0-13 ii libboost-program-options1.67.0 1.67.0-13 ii libboost-regex1.67.01.67.0-13 ii libboost-serialization1.67.01.67.0-13 ii libboost-system1.67.0 1.67.0-13 ii libboost-thread1.67.0 1.67.0-13 ii libc6 2.28-10 ii libegl1 1.1.0-1 ii libgcc1 1:8.3.0-6 ii libgles21.1.0-1 ii liblxc1 1:3.1.0+really3.0.3-8 ii libprotobuf-lite17 3.6.1.3-2 ii libsdl2-2.0-0 2.0.9+dfsg1-1 ii libsdl2-image-2.0-0 2.0.4+dfsg1-1 ii libstdc++6 8.3.0-6 ii libsystemd0 241-5 ii lxc 1:3.1.0+really3.0.3-8 Versions of packages anbox recommends: ii dbus-user-session 1.12.16-1 anbox suggests no packages. -- no debconf information To: Debian Bug Tracking System Subject: anbox: ignores mouse input X-Debbugs-Cc: deb...@emorrp1.name Package: anbox Version: 0.0~git20190124-1 Severity: grave Justification: renders package unusable I am able to launch the android apps from the desktop menu, but cannot interact other than moving the window around and fullscreening. I thought this was reported upstream as [#780], but the fix was merged in [bbf05d8f3] on 2019-01-06 and so included in the debian version. [#780]: https://github.com/anbox/anbox/issues/780 [bbf05d8f3]: https://github.com/anbox/anbox/commit/bbf05d8f3267ef5fb102525c372183aaa83df830 -- Phil Morrell (emorrp1) -- System Information: Debian Release: 10.0 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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 anbox depends on: ii iptables1.8.2-4 ii libboost-atomic1.67.0 1.67.0-13 ii libboost-chrono1.67.0 1.67.0-13 ii libboost-date-time1.67.01.67.0-13 ii libboost-filesystem1.67.0 1.67.0-13 ii libboost-iostreams1.67.01.67.0-13 ii libboost-log1.67.0 1.67.0-13 ii libboost-program-options1.67.0 1.67.0-13 ii libboost-regex1.67.01.67.0-13 ii libboost-serialization1.67.01.67.0-13 ii libboost-system1.67.0 1.67.0-13 ii libboost-thread1.67.0 1.67.0-13 ii libc6 2.28-10 ii libegl1 1.1.0-1 ii libgcc1 1:8.3.0-6 ii libgles21.1.0-1 ii liblxc1 1:3.1.0+really3.0.3-8 ii libprotobuf-lite17 3.6.1.3-2 ii libsdl2-2.0-0 2.0.9+dfsg1-1 ii libsdl2-image-2.0-0 2.0.4+dfsg1-1 ii libstdc++6 8.3.0-6 ii libsystemd0 241-5 ii lxc 1:3.1.0+really3.0.3-8 Versions of packages anbox recommends: ii dbus-user-session 1.12.16-1 anbox suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#928893: gnome-disk-utility: disk content permamently lost when changing LUKS password
On Sat, 20 Jul 2019 at 06:01:35 -0300, Guilhem Moulin wrote: > LUKS2_get_volume_key_size() fails because the key size is specified in > the ‘keyslots’ object of LUKSv2's JSON header [0], and that object is > the empty array at that point. Forgot to add another data point which supports my claim: with a LUKSv2 device with two active key slots (#0 unlocked by passphrase “test” and #1 unlocked by a random passphrase), LUKS2_get_volume_key_size() succeeds and so does crypt_keyslot_add_by_volume_key(). $ cryptsetup luksFormat --pbkdf-force-iterations 4 --pbkdf-memory 32 \ --type luks2 -q /tmp/disk.img <
Bug#932578: Cinnamon Settings fail to start
Package: cinnamon Version: 3.8.8-1 Severity: grave Dear Maintainer, after dist-upgrading a current sid system cinnamon-settings fail to start. If started from terminal the following backtrace comes up: /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:220: DeprecationWarning: Gtk.Widget.set_margin_right is deprecated self.stack_switcher.set_margin_right(n) /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:233: DeprecationWarning: Gtk.Window.set_has_resize_grip is deprecated self.window.set_has_resize_grip(False) Traceback (most recent call last): File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 608, in window = MainWindow() File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 244, in __init__ for module in modules: File "/usr/share/cinnamon/cinnamon-settings/modules/cs_backgrounds.py", line 5, in import imtools File "/usr/share/cinnamon/cinnamon-settings/bin/imtools.py", line 623, in if Image.VERSION == '1.1.7': AttributeError: module 'PIL.Image' has no attribute 'VERSION' Reason is the uncoordinated upload of pillow in ver. 6.1.0-1. Downgrading python3-pil "solve" the problem for now. Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.1.18-towo.1-siduction-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cinnamon depends on: ii cinnamon-common 3.8.8-1 ii cinnamon-control-center 3.8.1-1 ii cinnamon-desktop-data3.8.1-2 ii cinnamon-screensaver 3.8.2-1 ii cinnamon-session 3.8.2-1 ii cinnamon-settings-daemon 3.8.4-2 ii cjs 3.8.0-5 ii cups-pk-helper 0.2.6-1+b1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-caribou-1.0 0.4.21-7 ii gir1.2-clutter-1.0 1.26.2+dfsg-10 ii gir1.2-cmenu-3.0 3.8.2-1 ii gir1.2-cogl-1.0 1.22.2-6 ii gir1.2-cvc-1.0 3.8.1-2 ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 ii gir1.2-gkbd-3.0 3.26.1-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gnomedesktop-3.0 3.30.2.1-2 ii gir1.2-gtk-3.0 3.24.10-1 ii gir1.2-gtkclutter-1.01.8.4-4 ii gir1.2-keybinder-3.0 0.3.2-1 ii gir1.2-meta-muffin-0.0 3.8.2-1 ii gir1.2-nm-1.01.18.0-3 ii gir1.2-nma-1.0 1.8.22-2 ii gir1.2-notify-0.70.7.7-4 ii gir1.2-pango-1.0 1.42.4-6 ii gir1.2-polkit-1.00.105-25 ii gir1.2-soup-2.4 2.64.2-2 ii gir1.2-upowerglib-1.00.99.10-1 ii gir1.2-xapp-1.0 1.2.2-1 ii gkbd-capplet 3.26.1-1 ii gnome-backgrounds3.30.0-1 ii gnome-themes-extra 3.28-1 ii gsettings-desktop-schemas3.28.1-1 ii iso-flags-png-320x2401.0.2-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libcinnamon-desktop4 3.8.1-2 ii libcinnamon-menu-3-0 3.8.2-1 ii libcjs0 3.8.0-5 ii libclutter-1.0-0 1.26.2+dfsg-10 ii libcogl-pango20 1.22.2-6 ii libcogl-path20 1.22.2-6 ii libcogl201.22.2-6 ii libcroco30.6.12-3 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgirepository-1.0-11.58.3-2 ii libgl1 1.1.0-1 ii libglib2.0-0 2.60.5-1 ii libglib2.0-bin 2.60.5-1 ii libgstreamer1.0-01.16.0-2 ii libgtk-3-0 3.24.10-1 ii libmuffin0 3.8.2-1 ii libpango-1.0-0 1.42.4-6 ii
Processed: Re: Bug#932509: pyresample: FTBFS in bullseye due to missing python-xarray
Processing commands for cont...@bugs.debian.org: > notfound 932509 pyresample/1.12.3-2 Bug #932509 [src:pyresample] pyresample: FTBFS in bullseye due to missing python-xarray No longer marked as found in versions pyresample/1.12.3-2. > severity 932509 normal Bug #932509 [src:pyresample] pyresample: FTBFS in bullseye due to missing python-xarray Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 932509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932543: Please switch to Python 3
Control: tags -1 upstream Control: forwarded -1 https://github.com/PacificBiosciences/pbcommand/issues/189 On Sat, Jul 20, 2019 at 03:28:41PM +0200, Thomas Goirand wrote: > Your package is Python 2 only, please switch it to Python 3 (only), as I'm > removing Python 2 support in python-xmlbuilder which is a reverse build > dependency. I'll file according bugs for pbcommand and its rdepends to upstream. Thanks for pushing Andreas. -- http://fam-tille.de
Processed: Re: Bug#932543: Please switch to Python 3
Processing control commands: > tags -1 upstream Bug #932543 [python-pbcommand] Please switch to Python 3 Added tag(s) upstream. > forwarded -1 https://github.com/PacificBiosciences/pbcommand/issues/189 Bug #932543 [python-pbcommand] Please switch to Python 3 Set Bug forwarded-to-address to 'https://github.com/PacificBiosciences/pbcommand/issues/189'. -- 932543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919665: marked as done (uwsgi: Change build dependency to libglusterfs-dev)
Your message dated Sat, 20 Jul 2019 18:34:22 + with message-id and subject line Bug#919665: fixed in uwsgi 2.0.18-3 has caused the Debian Bug report #919665, regarding uwsgi: Change build dependency to libglusterfs-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:uwsgi Version: 2.0.17.1-11 Severity: normal Hello, with glusterfs 5.3-1 in unstable the libraries have been split out of the glusterfs-common package, there is also now a libglusterfs-dev package. Please build depend on libglusterfs-dev instead of glusterfs-common. Until all packages have been migrated, glusterfs-common will depend on libglusterfs-dev, but I try to remove this for the buster release. Also have a look here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919643 -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ --- End Message --- --- Begin Message --- Source: uwsgi Source-Version: 2.0.18-3 We believe that the bug you reported is fixed in the latest version of uwsgi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated uwsgi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jul 2019 19:30:26 +0200 Source: uwsgi Architecture: source Version: 2.0.18-3 Distribution: unstable Urgency: medium Maintainer: uWSGI packaging team Changed-By: Thomas Goirand Closes: 919665 Changes: uwsgi (2.0.18-3) unstable; urgency=medium . * debian/control build-depends: Replaced glusterfs-common by libglusterfs-dev (Closes: #919665). Checksums-Sha1: 3dee6a738bcc1159915c01538cc1d8e9031b744c 8288 uwsgi_2.0.18-3.dsc 11a0893ffc476d45b30972161fae111887764799 56508 uwsgi_2.0.18-3.debian.tar.xz 3f5b9593b5d4f73416ab9a9dca2f3f3b0ba09279 40123 uwsgi_2.0.18-3_amd64.buildinfo Checksums-Sha256: 6bb9192b9a982ffbe3752f31d8989f29ca916f55a090c4bee24776490685b56d 8288 uwsgi_2.0.18-3.dsc 89dd26d276995484cc08509eb5f526e79c3b088930a5e417a0b0ff02688fa141 56508 uwsgi_2.0.18-3.debian.tar.xz 949fbb9c8788c89b958e8f1d1867db541dc98da463062f847937e3f21ed0ba10 40123 uwsgi_2.0.18-3_amd64.buildinfo Files: 0e4a2d9969d340d61f9da4f2d43e45d3 8288 httpd optional uwsgi_2.0.18-3.dsc bd157d7bfeda11a30afe47d306cd0308 56508 httpd optional uwsgi_2.0.18-3.debian.tar.xz aa8eb9805f8437c5d3322d86b8cff6d2 40123 httpd optional uwsgi_2.0.18-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl0zV4kACgkQ1BatFaxr Q/49axAAibCGvmt4a2BoF6Q2HGscBia5wdo6CAwA3+gtAg6yxbUXrRXjCaA6lV0T 9mVvrFKEoAbWC0MrwkuAXb5ylzxmL2WaOun994NuLBr7iLMDlBfbv7hjqKpBO2Bb XYihujcqoQ5VAQ49wYormoBJgRYTuRAtdfSd9b6H1YFUN1MwLDThPUeoAWeRMfBY tnjr6qOMUywVerYAqZDaQzXmUD7ojdQihHaG+2lwdNxsHf+FJ99EQpLz5Fga5nSM OaI358G1jhoGq4M8VZfQyRbPzuZcPxcB9o7kLqSn/XK5yxRPXVF7h/IB/JjXdkCq K3ZZldo5TIKYQGOuJmTf/H2A1GVmE1Z4MyLViJhsjEASspfCcluB6OL1zz6zx6LD mHY5f94HnJO28IB1kQnmQNLayJ6LPDNiGc+DPV60K+RO/t/64Y4yMzDmXpU1tbUC BYgGrZUBXalZoDlUBGMTTsKbZs6DaGajEfbpLFsb5SEpqEheUnewbOQDhV0QdF8X dYyFo6kVY3HFsnRp4MC6wRfkieGukIaw4GPMeeAL2AuIEFKU2Nzuk8N85jutNqe2 1/GTdsL7k5aixL3Trqh3+1Zux0l/YAQw4deDLI9ko2RhdQZOSzVEMQcz3KQHZwyk xzzMw2sPewKVMWG/SC0sSsBqGifHiqvPBk7bDgRh4bFHpf5cfcs= =5i1/ -END PGP SIGNATURE End Message ---
Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream
Le 20/07/19 à 16:45, Graham Inggs a écrit : Hi Laurent Hello Graham, On Sat, 20 Jul 2019 at 14:42, Laurent Bigonville wrote: If nobody has any plans to work on this, I'll request to remove the package from the archive then? Any objections about this? Last I read, upstream is still working on this. Ah good to know, because I don't see any activity on the sourceforge page. Does not removing the package now cause any problems? No, that can still wait a bit
Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream
Hi Laurent On Sat, 20 Jul 2019 at 14:42, Laurent Bigonville wrote: > If nobody has any plans to work on this, I'll request to remove the > package from the archive then? Any objections about this? Last I read, upstream is still working on this. Does not removing the package now cause any problems? If the Linsmith / Watch item disappears from my DDPO page, I might not notice when a new upstream is released. Notifications from SourceForge are a bit hit and miss for me; sometimes they get sent weeks late, and sometimes not at all. Regards Graham
Bug#932544: s3ql build-depends on cruft package
Package: s3ql Version: 3.2+dfsg-1 Severity: serious Tags: patch s3ql build-depends on the obsolete transitional package texlive-generic-extra , please build-depend on texlive-plain-generic instead. I have succesfully built a package for raspbian bullseye with this change. A debdiff should show up soon at https://debdiffs.raspbian.org/main/s/s3ql
Bug#932543: Please switch to Python 3
Package: python-pbcommand Version: 1.1.1-1 Severity: serious Hi, Your package is Python 2 only, please switch it to Python 3 (only), as I'm removing Python 2 support in python-xmlbuilder which is a reverse build dependency. Cheers, Thomas Goirand (zigo)
Bug#932542: Please switch to Python 3
Source: nipype Severity: serious Hi, Please make nipype use Python 3, as it wont have python-xvfbwrapper support for Python 2 in a few minutes (I'll be uploading in a few minutes a version of python-xvfbwrapper that removes Python 2 support). Cheers, Thomas Goirand
Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream
On Sat, 12 Jan 2019 23:46:01 +0200 Yavor Doganov wrote: > On Wed, 09 Jan 2019 07:24:00 +0200, > Jeremy Bicha wrote: > > We'd like to remove those libraries soon, but I am willing to wait a > > bit longer for someone to port linsmith to gtk3. > > JFTR, I don't intend to work on this package. I don't have time at > the moment, but more importantly I don't have the motivation, knowing > in advance that this is already fixed upstream. If nobody has any plans to work on this, I'll request to remove the package from the archive then? Any objections about this?
Processed: qbittorrent: CVE-2019-13640
Processing control commands: > found -1 4.1.5-1 Bug #932539 [src:qbittorrent] qbittorrent: CVE-2019-13640 Marked as found in versions qbittorrent/4.1.5-1. -- 932539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932539: qbittorrent: CVE-2019-13640
Source: qbittorrent Version: 4.1.6-1 Severity: grave Tags: security upstream Forwarded: https://github.com/qbittorrent/qBittorrent/issues/10925 Control: found -1 4.1.5-1 Hi, The following vulnerability was published for qbittorrent. CVE-2019-13640[0]: | In qBittorrent before 4.1.7, the function | Application::runExternalProgram() located in app/application.cpp | allows command injection via shell metacharacters in the torrent name | parameter or current tracker parameter, as demonstrated by remote | command execution via a crafted name within an RSS feed. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-13640 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13640 [1] https://github.com/qbittorrent/qBittorrent/issues/10925 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#932452: marked as done (adacontrol: FTBFS on i386 mips because of tests)
Your message dated Sat, 20 Jul 2019 12:19:10 + with message-id and subject line Bug#932452: fixed in adacontrol 1.21r3-3 has caused the Debian Bug report #932452, regarding adacontrol: FTBFS on i386 mips because of tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adacontrol Version: 1.21r3-2 Severity: serious Justification: fails to build from scratch on i386 mips Here are the relevant lines from build logs. On i386 mips hppa powerpc: => t_type_usage.txtFAILED<= ... -- Passed= 85, Failed= 1 -- --- Total run time: 1mn 20s. make[1]: *** [debian/rules:58: override_dh_auto_test-arch] Error 1 On sparc64: => tfw_stress.txt FAILED - Passed= 85, Failed= 1 -- On s390x: -- Passed= 86, Failed= 0 -- --- make[1]: *** [debian/rules:58: override_dh_auto_test-arch] Error 1 --- End Message --- --- Begin Message --- Source: adacontrol Source-Version: 1.21r3-3 We believe that the bug you reported is fixed in the latest version of adacontrol, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated adacontrol package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jul 2019 13:46:19 +0200 Source: adacontrol Architecture: source Version: 1.21r3-3 Distribution: unstable Urgency: medium Maintainer: Ludovic Brenta Changed-By: Nicolas Boulenguez Closes: 932452 Changes: adacontrol (1.21r3-3) unstable; urgency=medium . * Disable a crashing test. Closes: #932452. Checksums-Sha1: 239a223f1ba29cc9bc86efe85a1c3dbf9c45bdd2 2249 adacontrol_1.21r3-3.dsc b4ad2145c10b7605438c8816078b915cbb50ae22 12604 adacontrol_1.21r3-3.debian.tar.xz Checksums-Sha256: d3389c2416fe8f4c7339cb514b972c9ef74bb378bbced7d94454e33ae64a492d 2249 adacontrol_1.21r3-3.dsc 8921cd381f907291160e8c7bdb3d6b1d425001a9861eda5b2584ac1ed56c2002 12604 adacontrol_1.21r3-3.debian.tar.xz Files: a8847a8d40681166f68862ee7a591eb4 2249 devel optional adacontrol_1.21r3-3.dsc 57b926139a5a43c615bd086fe176707e 12604 devel optional adacontrol_1.21r3-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl0zAtYTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jSpuD/968S8c0P5YPv1dmWsQWzQSc2PqTfHJ /TbV3KdgwFKRVWo8Jba3FcgsaiYhnuzf0AOxpATUz0t1HFcGsdntscxUHPQvVDhj HF2vAl0bh5Zwj+Dzl9V3YWIT0IrY8LYBqzckHgDk29+8TIp9F9FgIehm0WnQNTOg T2G4V3c7mkTsOY+h4WOeaw9UUzJE4hhod36CuB9hU6O74UsOYYe6ch8zGexsXjfU 7pcGeq+OdE/7r7kjoOf6GW9GMGTiN0+uYU1hZ+L60wsxQ6DXpWpub/xcOWA2QwEB DB8aZaMNDtgugIRzkO0ULdMOsJ1StKEa0sYY/SHz3/9Us4YqAszr9gIKWzyWE0sh Utsc1/sN9UGXlvj75OJKpic9U7cMYYRqbROedELVDDtcHP0zgwFzj7DXhaYcYWV1 iLgGcD6VINNNJbwwsfs+eIrcbKJZq/00DGrq9onEVnrBMAyHbI5PloKw6BsQB5+j Xn9n/MI+zOIQrVZ3llKnZPzXj6iHwScYe3Y7Wpx43tBt8+p34/m4hPILzIa6pBac t439ofM1aKGceN7aNOVp7p9ThrXfZOkTaf5OGdDKglE1GDE/4oDVSPRB7b+XPbpB 1JDjemPL0OWD0Sx2MrrzNEPkfhE/zfAsyxaV6J0/8fS4cYoUcT9QI0Yg9n0p5jFO /KB3TagqD2fWqA== =QMG4 -END PGP SIGNATURE End Message ---
Processed: buster-pu: package yubikey-personalization/1.19.3-3
Processing control commands:
> block 931081 by -1
Bug #931081 {Done: Nicolas Braud-Santoni } [libyubikey-udev]
libyubikey-udev: missing Breaks+Replaces: libykpers-1-1 (<< 1.19.3)
931081 was not blocked by any bugs.
931081 was not blocking any bugs.
Added blocking bug(s) of 931081: 932518
--
931081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931081
932518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921688: Updates
Hello everyone, This bug has been open and the electrum package has been unusable for almost 6 months now. Tristan, are you planning on packaging a new version at some point, or is the package no longer maintained? Thanks for your work on this! Best regards, -- Antoine Amarilli On Sun, Jun 02, 2019 at 06:55:48PM +0200, Antoine Amarilli wrote: > Hi, > > Are there any updates on packaging a new version of electrum in Debian? > > Many thanks for your work on this! > > Best, > > -- > Antoine Amarilli > signature.asc Description: PGP signature
Bug#908662: marked as done (r-cran-etm: autopkgtest regression: saved results mismatch)
Your message dated Sat, 20 Jul 2019 09:49:16 + with message-id and subject line Bug#908662: fixed in r-cran-etm 1.0.5-2 has caused the Debian Bug report #908662, regarding r-cran-etm: autopkgtest regression: saved results mismatch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 908662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-etm Version: 1.0.4-2 User: debian...@lists.debian.org Usertags: regression Hi R Package Team Now that #903672 has been resolved, we can see that r-cran-etm fails its autopkgtest [1] with the following errors: --- tests.etm.Rout.save_2018-09-10 10:04:21.100595425 + +++ tests.etm.Rout_ 2018-09-10 10:04:21.104595447 + @@ -246,7 +246,7 @@ 116 0.9990 116.0 4.764e-07 0.99767 1. 1 0 124 0.9990 124.0 4.764e-07 0.99767 1. 2 0 164 0.9990 164.0 4.764e-07 0.99767 1. 0 0 -183 1. 183.0 1.337e-19 1.0 1. 1 1 +183 1. 183.0 1.032e-19 1.0 1. 1 1 > > ## gonna play a bit with the state names > dd <- sir.cont @@ -694,7 +694,7 @@ 0.90344 35 1.193e-04 0.88204 0.92484 54 4 0.96816 54 4.374e-05 0.95520 0.98113 15 2 0.98894 77 1.668e-05 0.98094 0.99695 5 0 - 1.0 460 1.016e-20 1.0 1.0 1 1 + 1.0 460 2.253e-19 1.0 1.0 1 1 Transition 1 1 P time var lower upper n.risk n.event autopkgtest [10:04:21]: test run-unit-test: ---] autopkgtest [10:04:21]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1 Regards Graham [1] https://ci.debian.net/packages/r/r-cran-etm/unstable/amd64/ --- End Message --- --- Begin Message --- Source: r-cran-etm Source-Version: 1.0.5-2 We believe that the bug you reported is fixed in the latest version of r-cran-etm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated r-cran-etm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Jul 2019 09:21:21 + Source: r-cran-etm Architecture: source Version: 1.0.5-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Graham Inggs Closes: 908662 Changes: r-cran-etm (1.0.5-2) unstable; urgency=medium . * Team upload * Drop fix_test_results.patch * Filter out test output where exact floating point values are compared in order to fix autopkgtest on all architectures Closes: 908662 Checksums-Sha1: 392aa8635d71186b11e9b2b5b47a1adbc0240f8d 2099 r-cran-etm_1.0.5-2.dsc 6b330a95d3bdf0b37bf38eef250845f8ede3c860 3364 r-cran-etm_1.0.5-2.debian.tar.xz Checksums-Sha256: d94ff870a3f12feac574f374ecb94c2546e2800f6b6de9723e730c7f251f1d5a 2099 r-cran-etm_1.0.5-2.dsc 4d046d2f0fc78a77acbc3afe1224e7c1848c3bff0eba62fbd0ecbbc8ddcc96aa 3364 r-cran-etm_1.0.5-2.debian.tar.xz Files: 3b42d59646708c2b18e22db379b5c7c3 2099 gnu-r optional r-cran-etm_1.0.5-2.dsc bfcae9d430383e66aa02fef1c41fa91b 3364 gnu-r optional r-cran-etm_1.0.5-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl0y3yAACgkQr8/sjmac 4cL89RAAtAdWv/kZRI3L7SYo6w/cXDItdCIAVzZAew6QXvl1lJ+EohRN/7PtmvaO Tx7CZazfY38aGncedvz/MzEhRVOYEE/niFIaFq9xztrmbJ+MVzKGtPy2EjYDgW0I LkArSC9bAnLkZCwEws2swz7Zg2VzJqa5IlJqy8++krRf4PdM3IiFhjBM6JML5G6i yODsPFGkWMkEBcw9cO+gGoJKJMb4wDayeAeb/I/97o2oHFhADMMvPWy88Fxtpz/v z9PnLXK9wNP38xPGwdmUhkWEVa4IH9hnd8KaAPcHFBPx5yu1WbYjHWb8ig+N/Njp ud3wLWyoxTbcI/Zi+to+axwlHKDsqJ6Jh9O0ux1UqAsEX/8VKdGezHWHPv7scTU7 zdEcaaItnh2rHgZvcxklC3buupHeYFpXfyknE57/VoSvYwo897iAs0T8GareBUa0 ASRZQ/dTNzAoDyWngTuITU3dP/HynJHUBAM8TGmkCBScVs+RezMtZGAQbnyD+2P3 djQlAW9yoYnOUK2wxo45Ijdqo+sQLIR/smUXhhobqRkKC0z2oSKCliQHAYhwQZJJ gJ50a7J6J7/oOIPEphQ54FE5LkDoB+Ac790WY+5TKvjhrn5LBu7TaCoukfRbOthT kzbF9vjjodb7/zf5B0cN13nE92MlAn2K/KjKTE+duoUXHIgRJI4= =/DFr -END PGP SIGNATURE End Message ---
Bug#908662: r-cran-etm: autopkgtest regression: saved results mismatch
Sure I'll agree - just do whatever you consider sensible. Thanks, Andreas. On Sat, Jul 20, 2019 at 10:11:51AM +0200, Graham Inggs wrote: > Control: reopen -1 > Control: tags -1 + patch > > Hi Andreas > > Your patch fixed the autopkgtest on amd64 and armhf, but now it fails > on i386, arm64, ppc64el and s390x. > > Instead of a patch, how about simply filtering the offending line from > the saved results, as below? > > If you agree, I'll upload with this change. > > --- a/debian/tests/run-unit-test > +++ b/debian/tests/run-unit-test > @@ -11,6 +11,7 @@ > -e '^ISBN 3' \ > -e '^Loading required package: lattice' \ > -e '^Loading required package: splines' \ > +-e '^183 1\. 183\.0 [0-9.e-]* 1\.0 1\. 1 1' \ > $1 | \ > sed -e '/^> *proc\.time()$/,$d' \ > -e '/^ Natural language support but running in an English > locale/,+1d' > > Regards > Graham > > ___ > R-pkg-team mailing list > r-pkg-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team -- http://fam-tille.de
Bug#928893: gnome-disk-utility: disk content permamently lost when changing LUKS password
Hi there, On Fri, 19 Jul 2019 at 22:14:49 -0300, intrigeri wrote: > it turns out this is caused by a bug in libblockdev, which is fixed in > sid already (although it seems like upstream applied the fix for > unrelated reasons and it's not clear whether they realized this bug > was a possibility). AFAICT there were two bugs in src/plugins/crypto.c:bd_crypto_luks_change_key_blob() https://sources.debian.org/src/libblockdev/2.20-7/src/plugins/crypto.c/#L1359 The API calls to libcryptsetup roughly goes as follows: keyslot = crypt_volume_key_get(cd, …, volume_key, old_passphrase); crypt_keyslot_destroy(cd, keyslot); crypt_keyslot_add_by_volume_key(cd, 0, volume_key, new_passphrase); The first call uses the old passphrase to unlock a keyslot and set the volume key. (In LUKS2 the volume key of open devices isn't accessible to userspace, but of course it's no problem here since the passphrase is used to unlock a keyslot, which yields the volume key.) The second call removes the keyslot used to get the volume key in the first call. The third call adds a new key slot with the new passphrase. There are IMHO two issues with these calls (regardless of the LUKS format version): 1. It only adds the new slot *after* deleting the old one, so there is moment where the LUKS header might have no active key slot left. Worse, if crypt_keyslot_add_by_volume_key() fails for whichever reason, then the header is left in a broken state; if the user doesn't notice and closes the mapped device (or simply reboots) then the entire content of the device is lost. 2. The second argument of crypt_keyslot_add_by_volume_key() is always 0, while the user might want to change another key slot. I'm unfortunately not familiar with libblockdev, but the attached program, to be linked against libcryptsetup, shows these problems AFAICT. Format a device as LUKSv1 (although the same happens with v2), with a random passphrase for key slot 0, and passphrase “test” for key slot 1. (The extra PBKDF argument are there just so the test doesn't take too long.) $ dd if=/dev/zero of=/tmp/disk.img bs=1M count=64 $ head -c 32 /dev/urandom >/tmp/keyslot0 $ cryptsetup luksFormat --pbkdf-force-iterations 1000 --type luks1 \ -q --key-file=/tmp/keyslot0 /tmp/disk.img $ cryptsetup luksAddKey --pbkdf-force-iterations 1000 \ --key-file=/tmp/keyslot0 -q /tmp/disk.img <
Bug#932509: pyresample: FTBFS in bullseye due to missing python-xarray
Source: pyresample Version: 1.12.3-2 Severity: serious Tags: bullseye Hi Maintainer As can be seen on reproducible builders [1], pyresample FTBFS in bullseye because it Build-Depends on python-xarray which is no longer available. Unfortunately, britney does not take into consideration Build-Depends for arch:all packages (#145257) and allowed python-xarrray 0.12.1-1, which dropped Python 2 support, to migrate. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/pyresample.html
Processed: r-cran-etm: autopkgtest regression: saved results mismatch
Processing control commands:
> reopen -1
Bug #908662 {Done: Andreas Tille } [src:r-cran-etm]
r-cran-etm: autopkgtest regression: saved results mismatch
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions r-cran-etm/1.0.5-1.
> tags -1 + patch
Bug #908662 [src:r-cran-etm] r-cran-etm: autopkgtest regression: saved results
mismatch
Added tag(s) patch.
--
908662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#908662: r-cran-etm: autopkgtest regression: saved results mismatch
Control: reopen -1 Control: tags -1 + patch Hi Andreas Your patch fixed the autopkgtest on amd64 and armhf, but now it fails on i386, arm64, ppc64el and s390x. Instead of a patch, how about simply filtering the offending line from the saved results, as below? If you agree, I'll upload with this change. --- a/debian/tests/run-unit-test +++ b/debian/tests/run-unit-test @@ -11,6 +11,7 @@ -e '^ISBN 3' \ -e '^Loading required package: lattice' \ -e '^Loading required package: splines' \ +-e '^183 1\. 183\.0 [0-9.e-]* 1\.0 1\. 1 1' \ $1 | \ sed -e '/^> *proc\.time()$/,$d' \ -e '/^ Natural language support but running in an English locale/,+1d' Regards Graham
Bug#932507: python-crontab (build-)depends on cruft package.
package: python-crontab severity: serious version: 1.9.3-2 tags: bullseye,sid python-crontab (build-)depends on the python-croniter binary package which is no longer built by the python-croniter source package. It's probablly time to drop python 2 support from your package.
Bug#932506: elastalert: (build-)depends on cruft packages.
Package: elastalert Version: 0.1.29-1 Severity: serious Tags: bullseye, sid elastalert (build-)depends on the python-croniter binary package which is no longer built by the python-croniter binary package. If you want to keep your package in Debian you will probablly need to migrate to python 3.
Bug#932505: kombu: (build-)depends on cruft package.
package: kombu severity: serious tags: bullseye , sid python-kombu depends on and kombu build-depends on the python-aqmp binary package which is no longer built by the python-aqmp source package.
