Processed: reassign 949703 to src:thunderbird, forcibly merging 949703 949695
Processing commands for cont...@bugs.debian.org:
> reassign 949703 src:thunderbird
Bug #949703 [src:thunderbird] thunderbird doesn' start on Sid
Ignoring request to reassign bug #949703 to the same package
> forcemerge 949703 949695
Bug #949703 [src:thunderbird] thunderbird doesn' start on Sid
Bug #949695 {Done: Patrick Matthäi } [src:thunderbird]
thunderbird does not start anymore
Severity set to 'normal' from 'serious'
Bug reopened
Ignoring request to alter fixed versions of bug #949695 to the same values
previously set
Bug #949703 [src:thunderbird] thunderbird doesn' start on Sid
The source thunderbird and version 1:68.4.1-1+b1 do not appear to match any
binary packages
Marked as found in versions thunderbird/1:68.4.1-1+b1.
Merged 949695 949703
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949695
949703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 949703 949695
Processing commands for cont...@bugs.debian.org: > forcemerge 949703 949695 Bug #949703 [thunderbird] thunderbird doesn' start on Sid Unable to merge bugs because: package of #949695 is 'src:thunderbird' not 'thunderbird' Failed to forcibly merge 949703: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 949695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949695 949703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938763: marked as done (utidylib: Python2 removal in sid/bullseye)
Your message dated Sat, 25 Jan 2020 05:50:04 + with message-id and subject line Bug#938763: fixed in utidylib 0.5-3 has caused the Debian Bug report #938763, regarding utidylib: Python2 removal in sid/bullseye 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.) -- 938763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:utidylib Version: 0.5-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:utidylib If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: utidylib Source-Version: 0.5-3 We believe that the bug you reported is fixed in the latest version of utidylib, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated utidylib 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, 25 Jan 2020 00:36:13 -0500 Source: utidylib Architecture: source Version: 0.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 938763 Changes: utidylib (0.5-3) unstable; urgency=medium . [ Michal Čihař ] * Cleanup debian/control, bump standards to 4.2.1. . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Debian Janitor ] * Use secure URI in debian/watch. * Bump debhelper from old 9 to 12. * Set upstream metadata fields: Bug-Database, Bug-Submit, Name, Repository, Repository-Browse. . [ Sandro Tosi ] * Drop python2 support; Closes: #938763 Checksums-Sha1: 2ef21b35e44ae955ac009cfe0de208279b61547e 2019 utidylib_0.5-3.dsc db46cc0ef7437b72b13fc4d4373eec579d7a79a3 3884 utidylib_0.5-3.debian.tar.xz f9a7937f54063eab304eb3ea4f589d7567af0b36 6386 utidylib_0.5-3_source.buildinfo Checksums-Sha256:
Processed: fix ftbfs/ftcbfs bug metadata
Processing commands for cont...@bugs.debian.org: > # reassign to source package > reassign 935527 src:scantool Bug #935527 [scantool] scantool: FTBFS due to undefined reference to symbol 'ceilf@@GLIBC_2.4' Bug reassigned from package 'scantool' to 'src:scantool'. No longer marked as found in versions scantool/2.0-1. Ignoring request to alter fixed versions of bug #935527 to the same values previously set > # restore found version > found 935527 2.0-1 Bug #935527 [src:scantool] scantool: FTBFS due to undefined reference to symbol 'ceilf@@GLIBC_2.4' Marked as found in versions scantool/2.0-1. > # reassign to source package > reassign 939594 src:vmtk Bug #939594 [vmtk] vmtk build-depends on cruft package Bug reassigned from package 'vmtk' to 'src:vmtk'. No longer marked as found in versions vmtk/1.3+dfsg-2.3. Ignoring request to alter fixed versions of bug #939594 to the same values previously set > # restore found version > found 939594 1.3+dfsg-2.3 Bug #939594 [src:vmtk] vmtk build-depends on cruft package Marked as found in versions vmtk/1.3+dfsg-2.3. > # fix typo in affects > affects 895991 src:gtkmathview Bug #895991 [libgdome2-dev] libgdome2-dev: move gdome2.pc to a multiarch location Added indication that 895991 affects src:gtkmathview > # more affects > affects 878612 + src:kodi Bug #878612 [samba-libs] please drop dependency on python-talloc from samba-libs Added indication that 878612 affects src:kodi > # reassign to binary package > reassign 946502 hyphen-ru Bug #946502 [src:hyphen-ru] mark hyphen-ru Multi-Arch: foreign Bug reassigned from package 'src:hyphen-ru' to 'hyphen-ru'. No longer marked as found in versions hyphen-ru/20030310-1. Ignoring request to alter fixed versions of bug #946502 to the same values previously set > # restore found version > found 946502 20030310-1 Bug #946502 [hyphen-ru] mark hyphen-ru Multi-Arch: foreign Marked as found in versions hyphen-ru/20030310-1. > # more affects > affects 948611 + src:gnome-2048 src:gnome-firmware src:grim src:libxkbcommon > src:minder src:pbseqlib src:scrcpy src:zimwriterfs Bug #948611 [meson] meson fails to cross build anything with the cross file from debcrossgen Added indication that 948611 affects src:gnome-2048, src:gnome-firmware, src:grim, src:libxkbcommon, src:minder, src:pbseqlib, src:scrcpy, and src:zimwriterfs > thanks Stopping processing here. Please contact me if you need assistance. -- 878612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878612 895991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895991 935527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935527 939594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939594 946502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946502 948611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938763: marked as pending in utidylib
Control: tag -1 pending Hello, Bug #938763 in utidylib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/utidylib/commit/3a469160d6fc46d610c2f87b4ec62bac2ba0afc0 Drop python2 support; Closes: #938763 (this message was generated automatically) -- Greetings https://bugs.debian.org/938763
Processed: Bug#938763 marked as pending in utidylib
Processing control commands: > tag -1 pending Bug #938763 [src:utidylib] utidylib: Python2 removal in sid/bullseye Added tag(s) pending. -- 938763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937271: marked as done (pep8: Python2 removal in sid/bullseye)
Your message dated Sat, 25 Jan 2020 04:49:28 + with message-id and subject line Bug#937271: fixed in pep8 1.7.1-9 has caused the Debian Bug report #937271, regarding pep8: Python2 removal in sid/bullseye 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.) -- 937271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pep8 Version: 1.7.1-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pep8 If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pep8 Source-Version: 1.7.1-9 We believe that the bug you reported is fixed in the latest version of pep8, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pep8 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, 24 Jan 2020 23:26:56 -0500 Source: pep8 Architecture: source Version: 1.7.1-9 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937271 940736 Changes: pep8 (1.7.1-9) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #937271 * Drop transitional pep8 package; Closes: #940736 Checksums-Sha1: 16b2d159a94af2cbbb3bed261faa90e587c755db 2034 pep8_1.7.1-9.dsc df9aa80933933f29a9348729d6e23dae3a94543c 4948 pep8_1.7.1-9.debian.tar.xz 01e2bca78ac89bdeed97b2ff32c8aef102d2f61b 6317 pep8_1.7.1-9_source.buildinfo Checksums-Sha256: b06e3176d64c0174ddfceed628773f7e5c22a719c8952e4951d49b7842b34be4 2034 pep8_1.7.1-9.dsc 742ffbb0ae0473e99d2d80d739b4b499709551e1635a937e7340e671b517dd4a 4948 pep8_1.7.1-9.debian.tar.xz c876d0f3dc20377b2ab74b41401696b03f4496161832341e14383a80bb4e9329 6317 pep8_1.7.1-9_source.buildinfo Files: cd3dbc7bbf5a252c6034d7e09f1f63e5 2034 python optional pep8_1.7.1-9.dsc
Bug#937271: marked as pending in pep8
Control: tag -1 pending Hello, Bug #937271 in pep8 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/pep8/commit/900d56456bfca56f04f6debde396dd7e79651d57 Drop python2 support; Closes: #937271 (this message was generated automatically) -- Greetings https://bugs.debian.org/937271
Processed: Bug#937271 marked as pending in pep8
Processing control commands: > tag -1 pending Bug #937271 [src:pep8] pep8: Python2 removal in sid/bullseye Added tag(s) pending. -- 937271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937717: marked as done (python-doubleratchet: Python2 removal in sid/bullseye)
Your message dated Sat, 25 Jan 2020 04:05:08 + with message-id and subject line Bug#937717: fixed in python-doubleratchet 0.6.0-2 has caused the Debian Bug report #937717, regarding python-doubleratchet: Python2 removal in sid/bullseye 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.) -- 937717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-doubleratchet Version: 0.6.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-doubleratchet If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-doubleratchet Source-Version: 0.6.0-2 We believe that the bug you reported is fixed in the latest version of python-doubleratchet, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-doubleratchet 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, 24 Jan 2020 22:40:51 -0500 Source: python-doubleratchet Architecture: source Version: 0.6.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 937717 Changes: python-doubleratchet (0.6.0-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Debian Janitor ] * Bump debhelper from old 11 to 12. * Set upstream metadata fields: Bug-Database. . [ Sandro Tosi ] * Drop python2 support; Closes: #937717 Checksums-Sha1: bac0665ea3cb27d49489b65dead0bfd932a28c33 2140 python-doubleratchet_0.6.0-2.dsc 02eddc100a8f151d2ad14cef7694a2a5510106f8 2052 python-doubleratchet_0.6.0-2.debian.tar.xz cace9533ce7e266e0e62951ef1960917df1a27dd 6525 python-doubleratchet_0.6.0-2_source.buildinfo Checksums-Sha256:
Processed: py2removal bugs severity updates - 2020-01-25 03:35:36.465577+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # mail threads for more details on this severity update > # python-utidylib is a module and has 0 external rdeps or not in testing > severity 938763 serious Bug #938763 [src:utidylib] utidylib: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pep8 is a module and has 0 external rdeps or not in testing > severity 937271 serious Bug #937271 [src:pep8] pep8: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-doubleratchet is a module and has 0 external rdeps or not in testing > severity 937717 serious Bug #937717 [src:python-doubleratchet] python-doubleratchet: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937271 937717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937717 938763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal blocks updates - 2020-01-25 03:35:36.382362+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # python-distutils-extra > block 939102 by 938885 Bug #939102 [src:python-distutils-extra] python-distutils-extra: Python2 removal in sid/bullseye 939102 was blocked by: 936641 939110 939107 939104 939113 939106 849087 939103 939114 939115 937114 939105 939109 939111 939112 939108 939102 was blocking: 937448 937695 937817 938168 943104 Added blocking bug(s) of 939102: 938885 > # pycryptodome > block 937412 by 936805 Bug #937412 [src:pycryptodome] pycryptodome: Python2 removal in sid/bullseye 937412 was blocked by: 935450 936730 938094 938663 937412 was blocking: 937695 938168 Added blocking bug(s) of 937412: 936805 > End of message, stopping processing here. Please contact me if you need assistance. -- 937412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937412 939102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: meep: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org:
> Severity 937003 serious
Bug #937003 {Done: Thorsten Alteholz } [src:meep] meep:
Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.
Please contact me if you need assistance.
--
937003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#949764: marked as done (ksh: ksh/2020.0.0-3 will not uninstall cleanly (piuparts error))
Your message dated Sat, 25 Jan 2020 02:42:11 + with message-id and subject line Bug#949764: fixed in ksh 2020.0.0-4 has caused the Debian Bug report #949764, regarding ksh: ksh/2020.0.0-3 will not uninstall cleanly (piuparts error) 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.) -- 949764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ksh Version: 2020.0.0-3 Severity: serious https://piuparts.debian.org/sid/fail/ksh_2020.0.0-3.log 0m14.4s DEBUG: Modified(user, group, mode, size, target): /etc/shells expected(root, root, - 100644, 73, None) != found(root, root, - 100644, 100, None) 0m14.4s ERROR: FAIL: After purging files have been modified: /etc/shellsnot owned 0m14.4s ERROR: FAIL: Installation and purging test. This often indicates that the handling of /etc/shells has bugs. Please take a look into it. -- Best, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: ksh Source-Version: 2020.0.0-4 We believe that the bug you reported is fixed in the latest version of ksh, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anuradha Weeraman (supplier of updated ksh 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: Fri, 24 Jan 2020 20:05:27 -0500 Source: ksh Architecture: source Version: 2020.0.0-4 Distribution: unstable Urgency: high Maintainer: Anuradha Weeraman Changed-By: Anuradha Weeraman Closes: 949764 Changes: ksh (2020.0.0-4) unstable; urgency=high . * Piuparts issue (Closes: #949764) * Separated shcomp to its own alternative * Updated man page to reflect new binary name Checksums-Sha1: 43e122f3a3c889496cc0a93ea02a291b9fab0d34 1919 ksh_2020.0.0-4.dsc af6c38d2d13ea8b91ddefaa47ff06ba2e6ec5ead 21300 ksh_2020.0.0-4.debian.tar.xz c179b46eb3dd35a46fd26f5e7c97acf1a8886795 6892 ksh_2020.0.0-4_amd64.buildinfo Checksums-Sha256: c31d47a91187aa2d5ce50cd3814f72965e1c959b61d4f0e634bdf4c54c0edc02 1919 ksh_2020.0.0-4.dsc 9329b709e2e4a43faadd17d3fc9ded989ba034fdc75aa1722271bc85136b83ca 21300 ksh_2020.0.0-4.debian.tar.xz 0df8dc8225a5f15187fb3fb835244409a2a3a85fd35adbcb30f7979591fb8dd2 6892 ksh_2020.0.0-4_amd64.buildinfo Files: 33459640904d6e7ad614300864325495 1919 shells optional ksh_2020.0.0-4.dsc 856e3dd05d14bd0010272898cbe344b2 21300 shells optional ksh_2020.0.0-4.debian.tar.xz 6684a339c4485e6b4e43f6c9fecdc303 6892 shells optional ksh_2020.0.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE9WuPFOAUze9dBH/BY221odkYYP0FAl4roF0ACgkQY221odkY YP0XEhAAw7K/NXF4Vn8ag/TTMj7xilV8bILv5KkkX9YOovvNZIKjudBrZXtn3Zl5 gGm/VlfLoZAnbdh1i1VQZLVIO/l7EPJC+onY8Qc7+lTKoKZPHMjZFsoErLF+MNkY M7RE+8ymKVzaesRMTv1kBN4xbCOmPsTh3MRu3zFYFdzyGcVo503sYiJ54PhyVSDL q9Rzt6OCipF3FM3qNQrF9HOHuDsevtVSygnfAJ3V4IkUpIj/JyBUlZ6dTwZwwh/m N2u4oh30lhToWGeB3xKTNHz9ZkJ7EA3kwdQu0ngo5j/lu+D5lV/ZJ4DwV4eMmC8p s5JF74vgXZHfgJNmsVkuS2F1r205uaW2xifvWJ9kSg6UTZGcoaoHVnXmazmIQaWb DL05IWvrxAmBcSdAwpLWP9j/xA2k+A9E08FEYEpDWHN1DhwDW/LSzZTKnVRQ/pkH anjsHpJlZkFBa20YwOkkaxh6w8sGBqZJkA+a78WhQAfmVY9Wq5GRWD6YIwP49qcf H7mRRU+J5xMb2VA8novA2si/m07Py7S6WUbfKcBeK1vAA8VM8NnZ15Pj7/KhmYL2 +gxb+a3jrWWzc4JM4Nn1LtBi5qwmDXHtB+voZ7K10sK01NWwkYHlT7HcjReioz/e 78FktiprtIdkiandVgfuilXSzXKXMZLWaEDV26SIKJWQ1DkPaxo= =2WSa -END PGP SIGNATURE End Message ---
Bug#937321: presage: Python2 removal in sid/bullseye
Hi Matteo, I don't know if you saw, but I sent you a merge request[1] to remove the Python subpackages in presage. They don't have any rdeps and have very low popcon so it seems reasonable to remove them now (and they can be added back later when Python 3 support is ready). Let me know if you are good with this change. Thanks, Scott [1] https://sourceforge.net/p/presage/presage-debian/merge-requests/1/ On Tue, 3 Dec 2019, Matteo Vescovi wrote: Hi Scott, Someone approached me and volunteered to port presage to Python 3 in late October, but I haven't heard back since them. Let me take a look at what kind of an effort it would be to port to python 3: that would be my preferred option if I can find the time to do. Else, the suggestion to remove the python pieces sound like the next best thing, if I can't find the time to port to python 3 now, we can then later reintroduce the python pieces. What are the planned timelines for the python 2 removal? Cheers, - Matteo On Tuesday, 3 December 2019, 05:02:48 CET, Scott Talbert wrote: On Mon, 2 Dec 2019, Scott Talbert wrote: >> Python2 becomes end-of-live upstream, and Debian aims to remove >> Python2 from the distribution, as discussed in >> https://lists.debian.org/debian-python/2019/07/msg00080.html >> >> Your package either build-depends, depends on Python2, or uses Python2 >> in the autopkg tests. Please stop using Python2, and fix this issue >> by one of the following actions. > > Hi Matteo, > > Do you plan to port presage to Python 3? If not, I'll probably convert this > to an RM request as the package seems to be mostly unmaintained and is > blocking the removal of Python 2. Alternatively, perhaps just the Python pieces of presage can be removed, as those don't seem to have any rdepends? Scott
Bug#925905: marked as done (knot: d/copyright is severely incomplete)
Your message dated Sat, 25 Jan 2020 01:34:38 + with message-id and subject line Bug#925905: fixed in knot 2.7.8-1 has caused the Debian Bug report #925905, regarding knot: d/copyright is severely incomplete 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.) -- 925905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: 2.8.0-1 Severity: serious Flagging as serious because it's a policy violation. autotools files, and install-sh, in various directories not accounted for in d/copyright. distro/deb presumably is GPL-3+ without the SSL exception. contrib/ does not have the OpenSSL exception either ... is that code compiled into the main executable, or not? src/contrib has all sorts of licensing, most of which which is not accounted for in d/copyright. Copyright years for `Files: *` stanza need updating. src/contrib/ucw/lists.c is listed as GPL-3+? The original copyright date is before that license had been published. tests-fuzz/main.c has a different license. Copyright holders and licensing for tests/tap is wrong. It's not just Russ, and some of the files are GPL. Thanks to Sean Whitton for pointing this out! --dkg signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: knot Source-Version: 2.7.8-1 We believe that the bug you reported is fixed in the latest version of knot, 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 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Edmonds (supplier of updated knot 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, 24 Jan 2020 19:48:01 -0500 Source: knot Architecture: source Version: 2.7.8-1 Distribution: unstable Urgency: medium Maintainer: knot packagers Changed-By: Robert Edmonds Closes: 925905 933285 933917 Changes: knot (2.7.8-1) unstable; urgency=medium . * New upstream version 2.7.8 . [ Daniel Salzman ] * Remove resolved lintian-overrides * Don't require libcap-ng-dev on kfreebsd-i386, kfreebsd-amd64, and hurd-i386 * Update copyright (Closes: #925905) * Fix typo in copyright * Don't include pdf to doc package * Fix unsafe usage of yaml.load() (Closes: #933917) . [ Diederik de Haas ] * Remove knslookup from description as it is not provided. . [ Santiago Ruano Rincón ] * Revert changes about excluding pdf files in distro/deb/rules, moving them to debian/rules (Closes: #933285) . [ Robert Edmonds ] * debian/gbp.conf: Set "upstream-branch = upstream/2.7" * debian/gbp.conf: [import-orig] Also filter config.guess, config.sub * debian/patches/0003-correct-kdig-documentation-about-no-crypto.patch: Remove, applied upstream * debian/control: Add myself to Uploaders * debian/control: Bump Standards-Version to 4.5.0 (no changes) * debian/copyright: Fix path to src/libdnssec/contrib/vpool/ files Checksums-Sha1: 18715b0ff6f766b057f9af2470bf5c17ff42400f 3096 knot_2.7.8-1.dsc 81500127e7c14b0426510be5ba94ce7d36c50273 1158284 knot_2.7.8.orig.tar.xz 3d8dd8208ce885a6b9060ba37b1e0e4d7baf 833 knot_2.7.8.orig.tar.xz.asc 40c0ca6a3fbf4479d70665ea7caa2c8c7473d277 33012 knot_2.7.8-1.debian.tar.xz 9b4fd7dadaa262612cf2efcbc4803b94263d8ebd 12101 knot_2.7.8-1_amd64.buildinfo Checksums-Sha256: 24a426ec3669bbcfffc6b1bddfb9150a4a38f3109b2237728e8cf06ed26a0fe1 3096 knot_2.7.8-1.dsc b641730278479d04e7c1ff202989ae74e0e7c1cf203b873853a79d3d130f4c15 1158284 knot_2.7.8.orig.tar.xz 4c892204611f974c62378607fd58732f85297d6c8a9dbf02809caf72d9de7d64 833 knot_2.7.8.orig.tar.xz.asc 4c4d4cb995342972fe63f72cabcbf442f7fcc4a6e27e2b72468a7e17c9d09855 33012 knot_2.7.8-1.debian.tar.xz 09ccc4e47ea4276522ae873612d0076b3c9567d8c49f3f946e7fc5148e04d8d1 12101 knot_2.7.8-1_amd64.buildinfo Files: 44ccfd78058d64e18dc338ffb7b096ba 3096 net optional knot_2.7.8-1.dsc f4b5110e23b08d1ffb5be650a54aba02 1158284 net optional knot_2.7.8.orig.tar.xz eccf526fc3c787288d82e2b6f39c5536 833 net optional knot_2.7.8.orig.tar.xz.asc 925ab12a6cb033d1e181103baa48836c 33012 net optional
Bug#933285: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Sat, 25 Jan 2020 01:34:38 + with message-id and subject line Bug#933285: fixed in knot 2.7.8-1 has caused the Debian Bug report #933285, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye 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.) -- 933285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breathe Version: 4.11.1-1 Severity: serious Tags: ftbfs sid bullseye Recently the texlive-base package has stopped building the transitional package texlive-generic-extra. This is an issue for your package as it build-depends on it. Please update the building of your package to use texlive-plain-generic instead. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-07-16. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: knot Source-Version: 2.7.8-1 We believe that the bug you reported is fixed in the latest version of knot, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Edmonds (supplier of updated knot 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, 24 Jan 2020 19:48:01 -0500 Source: knot Architecture: source Version: 2.7.8-1 Distribution: unstable Urgency: medium Maintainer: knot packagers Changed-By: Robert Edmonds Closes: 925905 933285 933917 Changes: knot (2.7.8-1) unstable; urgency=medium . * New upstream version 2.7.8 . [ Daniel Salzman ] * Remove resolved lintian-overrides * Don't require libcap-ng-dev on kfreebsd-i386, kfreebsd-amd64, and hurd-i386 * Update copyright (Closes: #925905) * Fix typo in copyright * Don't include pdf to doc package * Fix unsafe usage of yaml.load() (Closes: #933917) . [ Diederik de Haas ] * Remove knslookup from description as it is not provided. . [ Santiago Ruano Rincón ] * Revert changes about excluding pdf files in distro/deb/rules, moving them to debian/rules (Closes: #933285) . [ Robert Edmonds ] * debian/gbp.conf: Set "upstream-branch = upstream/2.7" * debian/gbp.conf: [import-orig] Also filter config.guess, config.sub * debian/patches/0003-correct-kdig-documentation-about-no-crypto.patch: Remove, applied upstream * debian/control: Add myself to Uploaders * debian/control: Bump Standards-Version to 4.5.0 (no changes) * debian/copyright: Fix path to src/libdnssec/contrib/vpool/ files Checksums-Sha1: 18715b0ff6f766b057f9af2470bf5c17ff42400f 3096 knot_2.7.8-1.dsc 81500127e7c14b0426510be5ba94ce7d36c50273 1158284 knot_2.7.8.orig.tar.xz 3d8dd8208ce885a6b9060ba37b1e0e4d7baf 833 knot_2.7.8.orig.tar.xz.asc 40c0ca6a3fbf4479d70665ea7caa2c8c7473d277 33012 knot_2.7.8-1.debian.tar.xz 9b4fd7dadaa262612cf2efcbc4803b94263d8ebd 12101 knot_2.7.8-1_amd64.buildinfo Checksums-Sha256: 24a426ec3669bbcfffc6b1bddfb9150a4a38f3109b2237728e8cf06ed26a0fe1 3096 knot_2.7.8-1.dsc b641730278479d04e7c1ff202989ae74e0e7c1cf203b873853a79d3d130f4c15 1158284 knot_2.7.8.orig.tar.xz 4c892204611f974c62378607fd58732f85297d6c8a9dbf02809caf72d9de7d64 833 knot_2.7.8.orig.tar.xz.asc 4c4d4cb995342972fe63f72cabcbf442f7fcc4a6e27e2b72468a7e17c9d09855 33012 knot_2.7.8-1.debian.tar.xz 09ccc4e47ea4276522ae873612d0076b3c9567d8c49f3f946e7fc5148e04d8d1 12101 knot_2.7.8-1_amd64.buildinfo Files: 44ccfd78058d64e18dc338ffb7b096ba 3096 net optional knot_2.7.8-1.dsc f4b5110e23b08d1ffb5be650a54aba02 1158284 net optional knot_2.7.8.orig.tar.xz eccf526fc3c787288d82e2b6f39c5536 833 net optional knot_2.7.8.orig.tar.xz.asc 925ab12a6cb033d1e181103baa48836c 33012 net optional knot_2.7.8-1.debian.tar.xz c7c09d5d9d6dd02bf7e6821a69f3cd46 12101 net optional knot_2.7.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE3z2W7rOCeCDzAmZcAYF6sKr2za4FAl4rlBwACgkQAYF6sKr2 za48sw//TIq2TEoxf1O2rSB3yr+vMBbxb9lpBwwYF0S756QsusYO+CSUeC32K9y0
Bug#933917: marked as done (src:knot: Unsafe use of yaml.load())
Your message dated Sat, 25 Jan 2020 01:34:38 + with message-id and subject line Bug#933917: fixed in knot 2.7.8-1 has caused the Debian Bug report #933917, regarding src:knot: Unsafe use of yaml.load() 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.) -- 933917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:knot Version: 2.7.6-2 Severity: grave Tags: security Justification: user security hole The new version of pyyaml no longer allows use of yaml.load() without a loader being specifed. This raises a deprecation warning which has caused and autopkgtest failure on this package. These are generally trivial to fix, see the upstream guidance [1]. Scott K [1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation --- End Message --- --- Begin Message --- Source: knot Source-Version: 2.7.8-1 We believe that the bug you reported is fixed in the latest version of knot, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Edmonds (supplier of updated knot 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, 24 Jan 2020 19:48:01 -0500 Source: knot Architecture: source Version: 2.7.8-1 Distribution: unstable Urgency: medium Maintainer: knot packagers Changed-By: Robert Edmonds Closes: 925905 933285 933917 Changes: knot (2.7.8-1) unstable; urgency=medium . * New upstream version 2.7.8 . [ Daniel Salzman ] * Remove resolved lintian-overrides * Don't require libcap-ng-dev on kfreebsd-i386, kfreebsd-amd64, and hurd-i386 * Update copyright (Closes: #925905) * Fix typo in copyright * Don't include pdf to doc package * Fix unsafe usage of yaml.load() (Closes: #933917) . [ Diederik de Haas ] * Remove knslookup from description as it is not provided. . [ Santiago Ruano Rincón ] * Revert changes about excluding pdf files in distro/deb/rules, moving them to debian/rules (Closes: #933285) . [ Robert Edmonds ] * debian/gbp.conf: Set "upstream-branch = upstream/2.7" * debian/gbp.conf: [import-orig] Also filter config.guess, config.sub * debian/patches/0003-correct-kdig-documentation-about-no-crypto.patch: Remove, applied upstream * debian/control: Add myself to Uploaders * debian/control: Bump Standards-Version to 4.5.0 (no changes) * debian/copyright: Fix path to src/libdnssec/contrib/vpool/ files Checksums-Sha1: 18715b0ff6f766b057f9af2470bf5c17ff42400f 3096 knot_2.7.8-1.dsc 81500127e7c14b0426510be5ba94ce7d36c50273 1158284 knot_2.7.8.orig.tar.xz 3d8dd8208ce885a6b9060ba37b1e0e4d7baf 833 knot_2.7.8.orig.tar.xz.asc 40c0ca6a3fbf4479d70665ea7caa2c8c7473d277 33012 knot_2.7.8-1.debian.tar.xz 9b4fd7dadaa262612cf2efcbc4803b94263d8ebd 12101 knot_2.7.8-1_amd64.buildinfo Checksums-Sha256: 24a426ec3669bbcfffc6b1bddfb9150a4a38f3109b2237728e8cf06ed26a0fe1 3096 knot_2.7.8-1.dsc b641730278479d04e7c1ff202989ae74e0e7c1cf203b873853a79d3d130f4c15 1158284 knot_2.7.8.orig.tar.xz 4c892204611f974c62378607fd58732f85297d6c8a9dbf02809caf72d9de7d64 833 knot_2.7.8.orig.tar.xz.asc 4c4d4cb995342972fe63f72cabcbf442f7fcc4a6e27e2b72468a7e17c9d09855 33012 knot_2.7.8-1.debian.tar.xz 09ccc4e47ea4276522ae873612d0076b3c9567d8c49f3f946e7fc5148e04d8d1 12101 knot_2.7.8-1_amd64.buildinfo Files: 44ccfd78058d64e18dc338ffb7b096ba 3096 net optional knot_2.7.8-1.dsc f4b5110e23b08d1ffb5be650a54aba02 1158284 net optional knot_2.7.8.orig.tar.xz eccf526fc3c787288d82e2b6f39c5536 833 net optional knot_2.7.8.orig.tar.xz.asc 925ab12a6cb033d1e181103baa48836c 33012 net optional knot_2.7.8-1.debian.tar.xz c7c09d5d9d6dd02bf7e6821a69f3cd46 12101 net optional knot_2.7.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE3z2W7rOCeCDzAmZcAYF6sKr2za4FAl4rlBwACgkQAYF6sKr2 za48sw//TIq2TEoxf1O2rSB3yr+vMBbxb9lpBwwYF0S756QsusYO+CSUeC32K9y0 AqeEeuImT1ped9J80zwF6lATbF+Ok87hVCPH5jTvXOxdUFfBH/g+OaWui0MGX8TL qqDlYhR+ZmZiHzFJD3ckm+8NzZ6DEH8SLsbuDPLnoEjJeSVP6yR9ZXI26Rc0rAou
Bug#949775: marked as done (libsimgrid-java: missing (unversioned) Breaks+Replaces: simgrid-java)
Your message dated Fri, 24 Jan 2020 22:24:09 + with message-id and subject line Bug#949775: fixed in simgrid 3.24+dfsg-6 has caused the Debian Bug report #949775, regarding libsimgrid-java: missing (unversioned) Breaks+Replaces: simgrid-java 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.) -- 949775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsimgrid-java Version: 3.24+dfsg-4 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 .../libsimgrid-java_3.24+dfsg-4_amd64.deb ... Unpacking libsimgrid-java (3.24+dfsg-4) ... dpkg: error processing archive /var/cache/apt/archives/libsimgrid-java_3.24+dfsg-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libsimgrid-java.so.3.24', which is also in package simgrid-java 3.24+dfsg-1.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsimgrid-java_3.24+dfsg-4_amd64.deb Since the simgrid-java package is gone from sid, the B+R should be unversioned. cheers, Andreas simgrid-java=3.24+dfsg-1.1_libsimgrid-java=3.24+dfsg-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: simgrid Source-Version: 3.24+dfsg-6 We believe that the bug you reported is fixed in the latest version of simgrid, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Quinson (supplier of updated simgrid 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, 24 Jan 2020 22:50:12 +0100 Source: simgrid Architecture: source Version: 3.24+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Martin Quinson Changed-By: Martin Quinson Closes: 949775 Changes: simgrid (3.24+dfsg-6) unstable; urgency=medium . * libsimgrid-java breaks+replace simgrid-java (Closes: #949775). * Disable java in cmake on non-official architectures, too. Checksums-Sha1: a8568657fde6906bb53ad8a37454c8ad8c1473c2 2456 simgrid_3.24+dfsg-6.dsc 198ae8a187ffca2b4d16f84512fb5e23d1e01584 16032 simgrid_3.24+dfsg-6.debian.tar.xz 984a84b58d013a6b9ad41ecbb7223f6574590d9c 12619 simgrid_3.24+dfsg-6_amd64.buildinfo Checksums-Sha256: de7e700dfc9cf4be9b26e428a7f877e95144fe36c321200258d39e00ce3e6dee 2456 simgrid_3.24+dfsg-6.dsc 7f88ea9e5674bf775be7fbb239288575aff5eac8be9707503220de8d800192da 16032 simgrid_3.24+dfsg-6.debian.tar.xz 9d460c09bcb9ce51b604b7bc96c779351a217e69372ed0590741ea43247e5311 12619 simgrid_3.24+dfsg-6_amd64.buildinfo Files: c191ab60ce6d3fd4c42e30e823980aeb 2456 science optional simgrid_3.24+dfsg-6.dsc 60818e99ecf55548e3c604c9c8e07435 16032 science optional simgrid_3.24+dfsg-6.debian.tar.xz 11b76dcec11e064d74c76cb9f9b8c103 12619 science optional simgrid_3.24+dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEET76cTupS7xPVQWYSmL2XJE9zvqcFAl4raNwUHG1xdWluc29u QGRlYmlhbi5vcmcACgkQmL2XJE9zvqfOPQ/+NRDGuqxzgaYS/VNRHerEpjph3lEj t3b5/CTh7vt9Cz/JqcvabPepSThmJwIiU6MOxBkXRClljhnmbTLf9TCm5TjtUqmI Sg0STNljzqHmDesmTsrO2vFhSvzpgdGYsjPoHNS4496S35y2/7rpwhaatPcNUB43 9tzn1w0/HDpyIJTBARIVfg7zE8lljoB6YRD9FeV9z4QPG8riBK4ETX8GRaw1sial SHZNCwB6OjINOJM5wzjiYb1WBcFOFOoqZSPDiB4NCjZHb8ghfRP3gumdyr+G2D1y GI2L1Wt/g2bP+3hGLE70OVwmkhHHLjBgnNNreeis3oxMi5Mjf+rgURFDyPTb4ZDw v1P0TIseV4u4WiebZFB/7l5iRs43xpCkMnHfIbTTl0c5UEho3OCKRTVR10ZO/fQ6 X+d/f6D1pSZ48ST6n8IRmX/o6xSgJ8ApO4HiEmKD11mhcq8/HDyKLjRZqNYUSGxU SbVyZfheK+NhyFtOI8SeJFQoB8L29qBIbeZQj61TNV65ZB+2Vi64hya6AC6GbSiR k7sFokbk8+A1d2Y4MxSpUivJ9V8Q4d2kdTmGgwBFExJhvbsYa8QTZxOR/AnjimkD
Processed: Bug#949066 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #949066 [src:lintian] lintian: testsuite failures on arm* Added tag(s) pending. -- 949066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949066: marked as pending in lintian
Control: tag -1 pending Hello, Bug #949066 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/lintian/lintian/commit/7975d71063bc1db65c42ef3f0448d129a5b791b5 For one i386-only test package, build only on i386. (Closes: #949066) Unfortunately, dpkg-buildpackage cannot tell when no build is needed. Source packages are nowadays permitted to build undeclared artifacts. That is why a build attempt for this test package will fail even though there is simply nothing to do. (this message was generated automatically) -- Greetings https://bugs.debian.org/949066
Bug#949780: maptool: Maptool segfaults
Package: maptool Version: 0.5.3+dfsg.1-2+b1 Severity: grave Justification: renders package unusable Trying to use maptool with a .pbf file gave a segfault almost immediately. Compiling my own maptool directly from the navit git gave a working version. This was encountered while looking at the issues with navit on wince: see https://github.com/navit-gps/navit/issues/953#issuecomment-578313710 Search down that page to see the problem with the Debian testing maptool: maptool --protobuf -i /ssdback1/ael/mapping/mkgmap/great-britain-latest.osm.pbf test.bin but that SEGFAULTED almost immediately after writing some empty *.tmp files. gdb shows Program terminated with signal SIGSEGV, Segmentation fault. #0 0x55c63a68cf30 in osmpbf.blob_header.init () Backtrace showed: (gdb) bt #0 0x55c63a68cf30 in osmpbf.blob_header.init () #1 0x55c63a6917da in protobuf_c_message_unpack () #2 0x55c63a68a7ec in ?? () #3 0x55c63a68abb8 in map_collect_data_osm_protobuf () #4 0x55c63a679e73 in main () I see that there is a new version in unstable but I have not tried that version as yet. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores) 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) Versions of packages maptool depends on: ii libc6 2.29-9 ii libglib2.0-0 2.62.4-1 ii zlib1g1:1.2.11.dfsg-1+b1 maptool recommends no packages. Versions of packages maptool suggests: pn navit -- no debconf information
Bug#949778: ruby-oembed: autopkgtest needs update for new version of gem2deb: missing skippable restriction
Source: ruby-oembed Version: 0.12.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, gem2...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gem2deb Dear maintainers, With a recent upload of gem2deb the autopkgtest of ruby-oembed fails in testing when that autopkgtest is run with the binary packages of gem2deb from unstable. It passes when run with only packages from testing. In tabular form: passfail gem2debfrom testing1.0.3 ruby-oembedfrom testing0.12.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The cause of this is that gem2deb started to exit with code 77 to indicate that there is no test to run. This is meant to be used in conjunction with the skippable restriction, to avoid giving the wrong information to the migration software. Please add the skippable restriction to your package, or better, add a real test. Currently this regression is blocking the migration of gem2deb to testing [1]. Of course, gem2deb shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in gem2deb was intended and your package needs to update to the new situation. If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gem2deb https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-oembed/4079292/log.gz autopkgtest [21:12:45]: test command1: gem2deb-test-runner --autopkgtest 2>&1 autopkgtest [21:12:45]: test command1: [--- ┌──┐ │ Run tests for ruby2.5: no test suite! │ └──┘ autopkgtest [21:12:45]: test command1: ---] autopkgtest [21:12:46]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 77 signature.asc Description: OpenPGP digital signature
Processed: ruby-oembed: autopkgtest needs update for new version of gem2deb: missing skippable restriction
Processing control commands: > affects -1 src:gem2deb Bug #949778 [src:ruby-oembed] ruby-oembed: autopkgtest needs update for new version of gem2deb: missing skippable restriction Added indication that 949778 affects src:gem2deb -- 949778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925665: marked as done (cycfx2prog: ftbfs with GCC-9)
Your message dated Fri, 24 Jan 2020 21:04:20 + with message-id and subject line Bug#925665: fixed in cycfx2prog 0.47-1.1 has caused the Debian Bug report #925665, regarding cycfx2prog: ftbfs with GCC-9 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.) -- 925665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cycfx2prog Version: 0.47-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/cycfx2prog_0.47-1_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] cycfx2dev.cc:393:16: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits] 393 | assert(nbytes>=0 && nbytes<256); | ~~^~~ gcc -pipe -lusb cycfx2prog.o cycfx2dev.o -o cycfx2prog /usr/bin/ld: cycfx2prog.o: in function `USBDumpBusses(_IO_FILE*)': cycfx2prog.cc:(.text+0x201): undefined reference to `usb_busses' /usr/bin/ld: cycfx2prog.o: in function `main': cycfx2prog.cc:(.text.startup+0x2a3): undefined reference to `usb_init' /usr/bin/ld: cycfx2prog.cc:(.text.startup+0x2a8): undefined reference to `usb_find_busses' /usr/bin/ld: cycfx2prog.cc:(.text.startup+0x2d2): undefined reference to `usb_find_devices' /usr/bin/ld: cycfx2dev.o: in function `USBFindDevice(char const*, char const*)': cycfx2dev.cc:(.text+0xd): undefined reference to `usb_busses' /usr/bin/ld: cycfx2dev.o: in function `USBFindDevice(int, int, int)': cycfx2dev.cc:(.text+0x93): undefined reference to `usb_busses' /usr/bin/ld: cycfx2dev.o: in function `CypressFX2Device::BlockRead(int, unsigned char*, unsigned long, char)': cycfx2dev.cc:(.text+0x157): undefined reference to `usb_claim_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x16b): undefined reference to `usb_set_altinterface' /usr/bin/ld: cycfx2dev.cc:(.text+0x1b5): undefined reference to `usb_bulk_read' /usr/bin/ld: cycfx2dev.cc:(.text+0x222): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x2a1): undefined reference to `usb_interrupt_read' /usr/bin/ld: cycfx2dev.cc:(.text+0x2be): undefined reference to `usb_strerror' /usr/bin/ld: cycfx2dev.cc:(.text+0x2ea): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x31c): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x361): undefined reference to `usb_strerror' /usr/bin/ld: cycfx2dev.cc:(.text+0x387): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x3a2): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x3ab): undefined reference to `usb_strerror' /usr/bin/ld: cycfx2dev.cc:(.text+0x43b): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.o: in function `CypressFX2Device::BlockWrite(int, unsigned char const*, unsigned long, char)': cycfx2dev.cc:(.text+0x4a2): undefined reference to `usb_claim_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x4b6): undefined reference to `usb_set_altinterface' /usr/bin/ld: cycfx2dev.cc:(.text+0x4fd): undefined reference to `usb_bulk_write' /usr/bin/ld: cycfx2dev.cc:(.text+0x54b): undefined reference to `usb_release_interface' /usr/bin/ld: cycfx2dev.cc:(.text+0x598): undefined reference to `usb_release_interface' /usr/bin/ld:
Processed: reassign 949674 to libsqlite3-0, forcibly merging 949644 949674
Processing commands for cont...@bugs.debian.org:
> reassign 949674 libsqlite3-0
Bug #949674 [firefox] firefox: Firefox 72.0.2-1 crash on launch.
Bug reassigned from package 'firefox' to 'libsqlite3-0'.
No longer marked as found in versions firefox/72.0.2-1.
Ignoring request to alter fixed versions of bug #949674 to the same values
previously set
> forcemerge 949644 949674
Bug #949644 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
Bug #949645 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins
has no effect.
Bug #949646 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
Bug #949647 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Unable to lounch
Bug #949648 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox-esr: New version crash immediately at start
Bug #949650 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Crash at startup
Bug #949657 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Crashes on startup
Bug #949668 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox-esr: does not start after upgrade
Bug #949683 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash)
Bug #949674 [libsqlite3-0] firefox: Firefox 72.0.2-1 crash on launch.
Set Bug forwarded-to-address to
'https://bugzilla.mozilla.org/show_bug.cgi?id=1607902'.
Marked Bug as done
Added indication that 949674 affects thunderbird,firefox-esr,firefox
Marked as fixed in versions sqlite3/3.31.0+really3.30.1+fossil191229-1.
Marked as found in versions sqlite3/3.31.0-1.
Added tag(s) upstream, confirmed, and patch.
Bug #949645 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins
has no effect.
Bug #949646 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
Bug #949647 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Unable to lounch
Bug #949648 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox-esr: New version crash immediately at start
Bug #949650 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Crash at startup
Bug #949657 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Crashes on startup
Bug #949668 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox-esr: does not start after upgrade
Bug #949683 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash)
Merged 949644 949645 949646 949647 949648 949650 949657 949668 949674 949683
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644
949645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949645
949646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949646
949647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949647
949648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949648
949650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949650
949657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949657
949668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949668
949674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949674
949683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: tesseract: uses -march=native
Processing commands for cont...@bugs.debian.org: > Severity 949638 normal Bug #949638 [tesseract] tesseract: uses -march=native Severity set to 'normal' from 'serious' > Thanks Stopping processing here. Please contact me if you need assistance. -- 949638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949638: tesseract: uses -march=native
Severity 949638 normal Thanks On 24/01/2020 19:16, Stefan Weil wrote: As far as I know all Linux distributions use the autoconf based build, Debian certainly does appear to be using the autoconf based build. The default autoconf build uses -march=native only if it is supported by the compiler Which, of course it is. and only for a single file, but not for the rest of the code. The code from that single file is not executed by default, but only if an advanced user runs Tesseract with a special command line option (-c dotproduct=native). Ok, that dramatically reduces the impact of this issue. Downgrading the bug to normal. I still don't think -march=native is appropriate for a binary distribution though. If you want to offer different versions of the code built with different CPU requirements, that is fine, but please don't let them depend on what CPU happens to be in the autobuilder.
Bug#949776: wiredtiger FTBFS
Source: wiredtiger Version: 3.2.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=wiredtiger https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/wiredtiger.html Seems there was a test failure, and now there is additionally a build failurre.
Bug#949775: libsimgrid-java: missing (unversioned) Breaks+Replaces: simgrid-java
Package: libsimgrid-java Version: 3.24+dfsg-4 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 .../libsimgrid-java_3.24+dfsg-4_amd64.deb ... Unpacking libsimgrid-java (3.24+dfsg-4) ... dpkg: error processing archive /var/cache/apt/archives/libsimgrid-java_3.24+dfsg-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libsimgrid-java.so.3.24', which is also in package simgrid-java 3.24+dfsg-1.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsimgrid-java_3.24+dfsg-4_amd64.deb Since the simgrid-java package is gone from sid, the B+R should be unversioned. cheers, Andreas simgrid-java=3.24+dfsg-1.1_libsimgrid-java=3.24+dfsg-4.log.gz Description: application/gzip
Bug#949085: marked as done (slirp: CVE-2020-7039)
Your message dated Fri, 24 Jan 2020 20:43:07 + with message-id and subject line Bug#949085: fixed in slirp 1:1.0.17-10 has caused the Debian Bug report #949085, regarding slirp: CVE-2020-7039 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.) -- 949085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libslirp Version: 4.1.0-1 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for libslirp. CVE-2020-7039[0]: | OOB buffer access while emulating tcp protocols in tcp_emu() 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-2020-7039 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7039 [1] https://www.openwall.com/lists/oss-security/2020/01/16/2 [2] https://gitlab.freedesktop.org/slirp/libslirp/commit/2655fffed7a9e765bcb4701dd876e9dab975f289 https://gitlab.freedesktop.org/slirp/libslirp/commit/ce131029d6d4a405cb7d3ac6716d03e58fb4a5d9 https://gitlab.freedesktop.org/slirp/libslirp/commit/82ebe9c370a0e2970fb5695aa19aa5214a6a1c80 Regards, Salvatore --- End Message --- --- Begin Message --- Source: slirp Source-Version: 1:1.0.17-10 We believe that the bug you reported is fixed in the latest version of slirp, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roberto Lumbreras (supplier of updated slirp 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, 24 Jan 2020 20:12:54 +0100 Source: slirp Architecture: source Version: 1:1.0.17-10 Distribution: unstable Urgency: high Maintainer: Roberto Lumbreras Changed-By: Roberto Lumbreras Closes: 949085 Changes: slirp (1:1.0.17-10) unstable; urgency=high . * Fix for CVE-2020-7039 (Closes: #949085) * Make it compile on GNU Hurd, really. Checksums-Sha1: 318e92945defe83b52dfb43ce2d7f82c65002b9f 1737 slirp_1.0.17-10.dsc 95b1ea5be5291a86d46a8948cb644d8db0acea04 16148 slirp_1.0.17-10.debian.tar.xz 4c080c25ce38d9ec169645231f9133456760ac43 6443 slirp_1.0.17-10_amd64.buildinfo Checksums-Sha256: 3d468c649b60472b3bbebffc97b880759a0dec6bcd48cf2686ef5f990d11914a 1737 slirp_1.0.17-10.dsc b48acd79fed656e67890318014ac9867b741c4927fe32be3bf4bcd7997046abc 16148 slirp_1.0.17-10.debian.tar.xz b8cfb2d6cfe25ea4f918327721ab6a7d2f17f217a478253428312018026c1ed7 6443 slirp_1.0.17-10_amd64.buildinfo Files: 4c898e71f5da127e1e72390fbdc4f293 1737 net optional slirp_1.0.17-10.dsc 61b1c842e6caa11544ae1ce4aa986cc8 16148 net optional slirp_1.0.17-10.debian.tar.xz 9f35d208b4a857047cd2e229e36b4f79 6443 net optional slirp_1.0.17-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE0P8TF3YtXzyApcdAtn7iEBIpC00FAl4rSxoRHHJvdmVyQGRl Ymlhbi5vcmcACgkQtn7iEBIpC01+WxAAizBsiaf4BEUD6/0kHscokfdWeuc8uuhQ 2H6Xoub8MURq5P0h17FIqFvuUFPJfNHFivXV/G0XkhY7l6IjcpV8xhuuF8r6v3Pw U9q+b6JyNsbl6Htmbp3JkYYGeRaVpe/D30vmjVonFInGwk0my6IpgtlBZXqkazo1 5LNXFEPFdig14nKZGy7cuws2LNX4lQSZwl12c//OnFKK9hLz7qqM/Aj/5J7xeUVm Z2gEa7n7fDkiJjGm/KDKx20r7fZQ73NvRF3Se06eP8xMyVkBIOUt9CHq61F/BkcI azVML3mk01ZIZ/WG+RwdTGcmRY7cXJnowENU3jeP8UXjHLhI/8ZhtbVKc1FMOC5q tSLJeZvNTCWJBtTMJiTOHvajYNp3dl4GliKErTjmcEmXgnvKUNM6u6jOi0aIuhtj R1RyFDsI5dDy/UIQ3YKDUaOic+oICwZu78pxGTbbdaJc/ZpCX0+lUPm+VoJ/xmJy BgtnnaiVuyIYq0Q21FJPmbPmsXkSz8uL+DtDYGJuX+uYuYHoCCmA1o6Y3o1I44Go a69KnIx1JDRQ0vmfbWkTVGTyO6vsFKakUy8pnyaarmaFCQnBbuszgkx3hxupDsPq 1hyaO9k/bKxzkcYaZrnuCfiRrJ2u1BZQeBdGXSpYPoZTD6cNOYE7IjPr+/Y9jyIq vEvMWcOwGc0= =bddE -END PGP SIGNATURE End Message ---
Processed (with 1 error): forcibly merging 949644 949674
Processing commands for cont...@bugs.debian.org:
> forcemerge 949644 949674
Bug #949644 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
Bug #949645 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins
has no effect.
Bug #949646 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
Bug #949647 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Unable to lounch
Bug #949648 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox-esr: New version crash immediately at start
Bug #949650 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Crash at startup
Bug #949657 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox: Crashes on startup
Bug #949668 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
firefox-esr: does not start after upgrade
Bug #949683 {Done: Laszlo Boszormenyi (GCS) } [libsqlite3-0]
libsqlite3-0: upgrade to 3.31.0-1 breaks iceweasel (makes it crash)
Unable to merge bugs because:
package of #949674 is 'firefox' not 'libsqlite3-0'
Failed to forcibly merge 949644: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644
949645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949645
949646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949646
949647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949647
949648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949648
949650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949650
949657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949657
949668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949668
949674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949674
949683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#949774: votca-tools: missing Breaks+Replaces: libvotca-tools-dev (<< 1.6~)
Package: votca-tools Version: 1.6~rc1-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 .../votca-tools_1.6~rc1-1_amd64.deb ... Unpacking votca-tools (1.6~rc1-1) ... dpkg: error processing archive /var/cache/apt/archives/votca-tools_1.6~rc1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/votca_property.1.gz', which is also in package libvotca-tools-dev 1.5.1-1 Errors were encountered while processing: /var/cache/apt/archives/votca-tools_1.6~rc1-1_amd64.deb cheers, Andreas libvotca-tools-dev=1.5.1-1_votca-tools=1.6~rc1-1.log.gz Description: application/gzip
Bug#948779: marked as done (waffle: FTBFS: glx dependency is missing: x11-xcb)
Your message dated Fri, 24 Jan 2020 12:29:47 -0800 with message-id <157989778689.441179.7095832585006105720@jljusten-skl> and subject line RE: waffle: FTBFS: glx dependency is missing: x11-xcb has caused the Debian Bug report #948779, regarding waffle: FTBFS: glx dependency is missing: x11-xcb 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.) -- 948779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: waffle Version: 1.6.0-2 Severity: serious Tags: ftbfs Dear maintainer, during a rebuild in a standard sid chroot, your package failed to build: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BINARY_DIR=/build/1st/waffle-1.6.0/debian/tmp -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release -Dwaffle_has_gbm=1 -Dwaffle_has_glx=1 -Dwaffle_has_surfaceless_egl=1 -Dwaffle_has_x11_egl=1 -Dwaffle_has_wayland=1 -Dwaffle_build_manpages=1 -Dwaffle_build_htmldocs=0 -Dwaffle_build_examples=0 .. -- The C compiler identification is GNU 9.2.1 -- The CXX compiler identification is GNU 9.2.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Checking for module 'egl' -- Found egl, version 1.5 -- Checking for module 'gl' -- Found gl, version 1.2 -- Checking for module 'wayland-client>=1' -- Found wayland-client, version 1.17.0 -- Checking for module 'wayland-egl>=9.1' -- Found wayland-egl, version 18.1.0 -- Checking for module 'x11-xcb' -- No package 'x11-xcb' found -- Checking for module 'gbm' -- Found gbm, version 19.3.1 -- Checking for module 'libudev' -- Found libudev, version 244 CMake Error at cmake/Modules/WaffleValidateOptions.cmake:116 (message): glx dependency is missing: x11-xcb Call Stack (most recent call first): CMakeLists.txt:43 (include) -- Configuring incomplete, errors occurred! See also "/build/1st/waffle-1.6.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Should be fixed in 1.6.0-3. (Didn't close in changelog due to typo.)--- End Message ---
Bug#949638: tesseract: uses -march=native
It is not necessary to patch Tesseract code if for whatever reason -march=native is completely unwanted. `make libtesseract_native_la_CXXFLAGS=` will override the extra compiler flags which are used to produce the native code, so only the default flags which don't include -march=native will be used. Stefan
Bug#949638: tesseract: uses -march=native
> The URL for the patch is 404. s/tessarect/tesseract/ The fixed URL is https://debdiffs.raspbian.org/main/t/tesseract/. Stefan
Bug#948331: marked as done (fonts-noto-core: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1)
Your message dated Fri, 24 Jan 2020 19:35:56 + with message-id and subject line Bug#948331: fixed in fonts-noto 20200103-2 has caused the Debian Bug report #948331, regarding fonts-noto-core: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 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.) -- 948331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fonts-noto-core Version: 20200103-1 Severity: serious On package upgrade dpkg complained: Unpacking fonts-noto-core (20200103-1) over (20181227-1) ...^M ^[[1mdpkg:^[[0m error processing archive /tmp/apt-dpkg-install-jG8reX/16-fonts-noto-core_20200103-1_all.deb (--unpack):^M trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1^M ^[[1mdpkg-deb:^[[0m ^[[1;31merror:^[[0m paste subprocess was killed by signal (Broken pipe)^M A follow up `apt upgrade` ran fine, seems a break declaration is missing. --- End Message --- --- Begin Message --- Source: fonts-noto Source-Version: 20200103-2 We believe that the bug you reported is fixed in the latest version of fonts-noto, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated fonts-noto 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: Fri, 24 Jan 2020 13:56:17 -0500 Source: fonts-noto Architecture: source Version: 20200103-2 Distribution: unstable Urgency: high Maintainer: Debian Fonts Task Force Changed-By: Boyuan Yang Closes: 948331 Changes: fonts-noto (20200103-2) unstable; urgency=high . * Team upload. * Declare compliance with Debian Policy 4.5.0. * debian/control: Properly declare Breaks+Replaces relationship with old packages to fix installation failure. (Closes: #948331) Checksums-Sha1: a1091bffea8406ee5d2de531e8e6518c1102ce44 2722 fonts-noto_20200103-2.dsc 225a36a3ca55f5206ec8f1d8738ed4eb2e06e856 109776 fonts-noto_20200103-2.debian.tar.xz 8ab96c99c700886726e721c89250d3974a4869a3 8751 fonts-noto_20200103-2_amd64.buildinfo Checksums-Sha256: ad33ee77d8a626ca43a67d89b5429511ff9fe83bade651fff740dbcd531b4491 2722 fonts-noto_20200103-2.dsc 017a646514fcc402466827a65e1d5dd1ec884d5ed8110e3da2a464ca56ea6751 109776 fonts-noto_20200103-2.debian.tar.xz d38a49129d455d4f8504ec78cf69f2afbb60263f40b117abb4ba9478e73b9690 8751 fonts-noto_20200103-2_amd64.buildinfo Files: a1f1792390c35681d5ff97666bd5 2722 fonts optional fonts-noto_20200103-2.dsc 63f98135afa77d18a1fcfb839b72a866 109776 fonts optional fonts-noto_20200103-2.debian.tar.xz 340c3ceec774ce371fefbe4a7c61ed1b 8751 fonts optional fonts-noto_20200103-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4rQpkACgkQwpPntGGC Ws5Ntg/6AlT8TV5E1qyX0CPMtNVWNTqLIMhodr5Gqmk7dDj0KjWoTGvd7+fw4uV/ KV0jeJefAT+D5BA0naFn9aJV5W4jv5HvSflCYCfKRoLuOGa5ExNWW/HBXNOFZO5o xPQYUd6EfJ0MCASQbZzohKH0zo9ZcT+KdnatYOBqrgZm7KKrbNWrWIoX22lLQrtN KOOgLkwH9MXtr6QStoeQZcefW9MEv54522E9YoKVzPT39w6JIj8vA/hleycVyqL2 J4dgRFcLdxeF4bH+Lf/z3OvlY1wwKAQwg1w8rUos+j7Vb+VtiN7GD/ToO0YNGhXe OMXdnV+6efplnyQpQThXZBm1t8tAN6GUIO5bD0XTgUf7XneAVP7aFeKZdquscwKo P+gIqT+mTopxxU2Pp+W2JDOJMJwPMDgCYF0ZtmMiUZzbD4880o6aEA4Dnyleajyr WcnsZhgclSCijzdxTioAPG+S9RPLaYGYx59kqWIuKRNEUD8w2TVHP8Cv6+7CP6Fd DWT4p3yFi46GvCcH/zS5KSGALJ/EUT2gjO6UYYbq4BD1V7fyugmFoH93dlRqub4B 4yrNFxA4oS2eA1mtsKwwvu/LEcmqy4EXj2Kj4M+6nm7Xj2GmUuKyQ/66adPg7khm R11n1OUhNzYci3RE8cie2zI/DnkeZU7X7VqAzfnUg/2uXAPq26w= =GFBo -END PGP SIGNATURE End Message ---
Processed: don't use the debci log as an installed packages diff, see #764081
Processing commands for cont...@bugs.debian.org: > reassign 949767 src:pocl Bug #949767 [src:libffi] causes autopkgtest regression in libgpuarray Bug reassigned from package 'src:libffi' to 'src:pocl'. No longer marked as found in versions libffi/3.3-3. Ignoring request to alter fixed versions of bug #949767 to the same values previously set > found 949767 1.4-3 Bug #949767 [src:pocl] causes autopkgtest regression in libgpuarray Marked as found in versions pocl/1.4-3. > End of message, stopping processing here. Please contact me if you need assistance. -- 949767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949638: tesseract: uses -march=native
Am 24.01.20 um 19:55 schrieb Jeff Breidenbach: > > Regarding: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638 > > Thank you, Peter. > > 1. The URL for the patch is 404. > > 2. There may be some subtlety with -march=native, specifically related to > detection of SIMD instructions like AVX2. There's been an enormous > amount of back & forth on this topic in upstream over the years, so > I'd like > to take this bug there and let them weigh in. > > Jeff That might be a false alarm. Tesseract supports two different build systems, one based on cmake, one based on autoconf. As far as I know all Linux distributions use the autoconf based build, so they should not be affected by the existing problems from the cmake build. The default autoconf build uses -march=native only if it is supported by the compiler and only for a single file, but not for the rest of the code. The code from that single file is not executed by default, but only if an advanced user runs Tesseract with a special command line option (-c dotproduct=native). Stefan
Processed: Bug#948331 marked as pending in fonts-noto
Processing control commands: > tag -1 pending Bug #948331 [fonts-noto-core] fonts-noto-core: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 Added tag(s) pending. -- 948331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948331: marked as pending in fonts-noto
Control: tag -1 pending Hello, Bug #948331 in fonts-noto reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/fonts-team/fonts-noto/commit/5b31e091bf0ce5913e439a16df2abee7b4e22a4f Fix Breaks+Replaces relationship. (Closes: #948331) (this message was generated automatically) -- Greetings https://bugs.debian.org/948331
Bug#949767: causes autopkgtest regression in libgpuarray
Source: libffi Version: 3.3-3 Severity: serious (This is a "block migration while I investigate" bug: it may well be downgraded or reassigned when I know more.) https://ci.debian.net/packages/libg/libgpuarray/unstable/amd64/ libffi is one of the few that changed: https://ci.debian.net/data/packages/unstable/amd64/libg/libgpuarray/4085247.log
Bug#949638: tesseract: uses -march=native
BCC: Stefan Weil since I don't know if he wants his email posted in bugs.debian.org Regarding: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638 Thank you, Peter. 1. The URL for the patch is 404. 2. There may be some subtlety with -march=native, specifically related to detection of SIMD instructions like AVX2. There's been an enormous amount of back & forth on this topic in upstream over the years, so I'd like to take this bug there and let them weigh in. Jeff
Bug#949711: Build-depends on sgmltools-lite, which is being removed
On Thu, Jan 23, 2020 at 11:34:12PM +0100, Moritz Muehlenhoff wrote: > Source: aboot > Severity: serious > sgmltools-lite is scheduled for removal and aboot is the last package > build depending on it. > There hasn't been any aboot upload since 2013 and it's RC-buggy for a > long time, should we simply remove it? Yes, the arch: all binaries can only be built on an alpha toolchain, for which we have no official builders in Debian. I think it should probably just be removed. -- 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#934119: marked as done (torbrowser-launcher: Erroneously manages /etc/apparmor.d/local/torbrowser.* as conffiles)
Your message dated Fri, 24 Jan 2020 18:51:09 + with message-id and subject line Bug#934119: fixed in torbrowser-launcher 0.3.2-6 has caused the Debian Bug report #934119, regarding torbrowser-launcher: Erroneously manages /etc/apparmor.d/local/torbrowser.* as conffiles 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.) -- 934119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: torbrowser-launcher Version: 0.3.2-1 Severity: normal With this version, /etc/apparmor.d/local/torbrowser.Browser.firefox and /etc/apparmor.d/local/torbrowser.Tor.tor are managed as conffiles again, while they should not: they're supposed to be created/deleted as needed by bits of maintainer scripts generated by dh_apparmor. A problematic consequence is that if I have local tweaks in those files (which is their actual intended purpose), I'm asked on upgrade to resolve the conflict between my configuration and the empty one shipped by the package. I believe we've had the same bug in the past, that got fixed in d0deb2f923edbaf3c2801c46d74b7925c5605593. I'm not sure what exact rm_conffile call would be suitable here (depends on which upgrade paths we shall support). Cheers, -- intrigeri --- End Message --- --- Begin Message --- Source: torbrowser-launcher Source-Version: 0.3.2-6 We believe that the bug you reported is fixed in the latest version of torbrowser-launcher, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Shimizu (supplier of updated torbrowser-launcher 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: Mon, 20 Jan 2020 01:06:01 +0900 Source: torbrowser-launcher Architecture: source Version: 0.3.2-6 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Roger Shimizu Closes: 934119 Changes: torbrowser-launcher (0.3.2-6) unstable; urgency=medium . * debian/rules: - Remove override_dh_auto_test, it seems fine without it. - Add override_dh_auto_install, to exclude local apparmor profile from shipping as conffile nor normal file. * debian/preinst: - Create dummy local apparmor profile if it's nonexisting. (Closes: #934119). - Update the commit SHA-1. * debian/control: - Add a few Depends to Build-Depends to pass dh_auto_test. Checksums-Sha1: 330ef7de0a1119298f08c0bf6dfc415569657015 2259 torbrowser-launcher_0.3.2-6.dsc 012bff37761c59dcbedecdedea32fac48c7cbe3e 21856 torbrowser-launcher_0.3.2-6.debian.tar.xz ef429b390a4b6ab9531a31d841f3fc7f1c257e8e 12493 torbrowser-launcher_0.3.2-6_source.buildinfo Checksums-Sha256: 44d443c8470ab153f48e8aaf3d748c0cd56a92f5543829ffa5d7b7cba335 2259 torbrowser-launcher_0.3.2-6.dsc cc5cdb15bf1fae7d0c05f480d77e47614792c03d9dc8635d958eb6582f016083 21856 torbrowser-launcher_0.3.2-6.debian.tar.xz 38bd314ae28f027cde27f18f7493d1e7ccb476580864102270d26cc94281939d 12493 torbrowser-launcher_0.3.2-6_source.buildinfo Files: df34cdf82c46856c5d295c2de44f926d 2259 contrib/web optional torbrowser-launcher_0.3.2-6.dsc 050b92b18a0b350a9e924d9225d9c628 21856 contrib/web optional torbrowser-launcher_0.3.2-6.debian.tar.xz 4c881f38dbb97e419dea1edb183ae657 12493 contrib/web optional torbrowser-launcher_0.3.2-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl4rOkYQHHJvc2hAZGVi aWFuLm9yZwAKCRCkeGsNpwM0qEhAD/4qJZqX5LxeqieFD4QeGjD1ECU0xhF+dg5J bVHPO1JQGku55ufrkThXtUJ6a1iStiw8vzymE47mEYReR9V5NK/MXDe9folwAksL u/O4y+U0C743KgYtXej0hVxCHhWYKEOn2ZNtfiT4/LPh64fbMb1JQVJbHDFz8neu yfaNFR1NJWtF1ws8naXHoPBaWTQ4P6dCmfraihWRi0Af3JtQvmzraYuy55PoU8Im yXHGuXANpXt/0FnuVY8q/3dGWqsqXZ4n0gI6a2uxrXlB+k52hbgtYILYbk4g1MAx sXS4HofeTsEDCLLdnF8QSgvdnKqyi39hvmRhMYal4OeDc2jcOTllU/HUS6SLxBry OTo6iKxvZlSVNwZ4OXrctj6rkYS1zK9wUvhcCbidanis8Cv9Y3WxpNKaF0xXoN07 jeL5RFvG+NioY5dlIcfsG6chuOi4ed1OGlxRD6FpIfC2CQO7vpy2jFi5sRuPnEsY pFKhcqfV4x+bhgx+kvhGb9j5fo8G1S6PhRG8m9g43P5wKgqPoCsckHG/ba3uRRW6 KFEobZXt4tdgTGFl9jvWf4bDrMjPxQ6YquPQr8HoaHsXjlsfJY6oamKJrr9GqvRV
Bug#947367: marked as done (lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0')
Your message dated Fri, 24 Jan 2020 18:49:56 + with message-id and subject line Bug#947367: fixed in lebiniou 3.40-1 has caused the Debian Bug report #947367, regarding lebiniou breaks lebiniou-data arm64 autopkgtest: ALSA lib confmisc.c:767:(parse_card) cannot find card '0' 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.) -- 947367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lebiniou, lebiniou-data Control: found -1 lebiniou/3.32-1 Control: found -1 lebiniou-data/3.28-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of lebiniou the autopkgtest of lebiniou-data fails in testing on when that autopkgtest is run with the binary packages of lebiniou from unstable. It passes when run with only packages from testing. In tabular form: passfail lebiniou from testing3.32-1 lebiniou-data from testing3.28-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of lebiniou to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=lebiniou https://ci.debian.net/data/autopkgtest/testing/arm64/l/lebiniou-data/3757794/log.gz autopkgtest [14:11:01]: test command1: lebiniou --stats autopkgtest [14:11:01]: test command1: [--- [k] Using default configuration file: /home/debci/.lebiniourc ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4568:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4568:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4568:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5047:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2564:(snd_pcm_open_noupdate) Unknown PCM default O_o error opening PCM device default autopkgtest [14:11:02]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: lebiniou Source-Version: 3.40-1 We believe that the bug you reported is fixed in the latest version of lebiniou, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olivier Girondel (supplier of updated lebiniou 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, 07 Dec 2019 21:25:22 +0100 Source: lebiniou Architecture: source Version: 3.40-1 Distribution: unstable Urgency: low Maintainer: Olivier Girondel Changed-By: Olivier Girondel Closes: 947367 Changes: lebiniou (3.40-1) unstable; urgency=low . * New upstream release 3.40. * debian/control: Add Build-Depends: libjansson-dev, libulfius-dev * debian/tests/control: Fix Test-Command. (Closes: #947367) * debian/lebiniou.lintian-overrides: Commented. * debian/copyright: Update copyright years. * debian/control: Standards-Version: 4.5.0. Checksums-Sha1: af5383ab9c23547d04398ac6213d7e2efe4860f4 2079 lebiniou_3.40-1.dsc dc3c8377e3dc607f2e4a1396567229bafc23c9bf 787800 lebiniou_3.40.orig.tar.gz 2aa3017f40956307c01383f69fad67b226dc336c 4024 lebiniou_3.40-1.debian.tar.xz c38189fd6637d3ebd5d6550681e952a62aabcbd5 6858 lebiniou_3.40-1_source.buildinfo Checksums-Sha256:
Processed: found 938828 in 3.1.0+ds-1
Processing commands for cont...@bugs.debian.org: > found 938828 3.1.0+ds-1 Bug #938828 [src:wiredtiger] wiredtiger: Python2 removal in sid/bullseye Marked as found in versions wiredtiger/3.1.0+ds-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 938828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup
On 23.1.2020 23.08, Paul Gevers wrote: > Hi Timo, > > On 23-01-2020 22:01, Timo Aaltonen wrote: >> Look at the error above, the file shipped by qtbase5-dev requires >> libEGL.so which the libegl-dev dependency provides. It used to be in >> libglvnd-dev but moved to a new package when the EGL headers were added >> upstream. > > So, libglvnd-dev should add a versioned breaks on the old qtbase5-dev, > right? Uh no... The old qtbase5-dev (5.12.5+dfsg-2, in testing) depends on libgl1-mesa-dev. libgl1-mesa-dev (in testing) used to pull in libglvnd-dev which had libEGL.so. New libgl1-mesa-dev depends only on libgl-dev, so you don't get the libEGL.so symlink anymore. I guess libgl1-mesa-dev should depend on libegl-dev too, for now.
Bug#943991: Bug #943991: behave: failing tests with python3.8
Hi, Am Freitag, den 01.11.2019, 22:05 -0700 schrieb Steve Langasek: > For the moment I have worked around the failure in Ubuntu by changing the > packaging to test only against the current version of python3 and not > against all supported versions, but this is a very short-term fix given that > python3.8 will become the default in the next 6 months. I tried to adapt the upstream changes to 1.2.5, but there's just too much change since 2015 to make this feasible. So I've updated behave to 1.2.6 and added the patch there, see attached (debian/-only) debdiff (which includes the unreleased changes), or the MR here: https://salsa.debian.org/python-team/modules/behave/merge_requests/1 Michael -- Michael Banck Projektleiter / Senior Berater Tel.: +49 2166 9901-171 Fax: +49 2166 9901-100 Email: michael.ba...@credativ.de credativ GmbH, HRB Mönchengladbach 12080 USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer Unser Umgang mit personenbezogenen Daten unterliegt folgenden Bestimmungen: https://www.credativ.de/datenschutz diff -Nru behave-1.2.5/debian/changelog behave-1.2.6/debian/changelog --- behave-1.2.5/debian/changelog 2019-09-13 15:19:10.0 +0200 +++ behave-1.2.6/debian/changelog 2019-10-18 16:03:41.0 +0200 @@ -1,3 +1,21 @@ +behave (1.2.6-1) UNRELEASED; urgency=medium + + * New upstream relesae. + + [ Ondřej Nový ] + * Bump Standards-Version to 4.4.1. + + [ Michael Banck ] + * debian/patches/0001-docs-disable-use-of-sphincontrib.cheeseshop.patch: +Removed, no longer needed. + * debian/patches/0002-Python-3.6-compatibility-patch-re.LOCALE-removed.patch: +Removed, no longer needed. + * debian/patches/0003-Backport-for-py38-fixes.patch: New patch, provides +compatibility with Python 3.8. Closes: #943991. + * debian/control: Added python3-sphinx-bootstrap-theme to Build-Depends. + + -- Ondřej Nový Fri, 18 Oct 2019 16:03:41 +0200 + behave (1.2.5-3) unstable; urgency=medium * Team upload. diff -Nru behave-1.2.5/debian/control behave-1.2.6/debian/control --- behave-1.2.5/debian/control 2019-09-13 14:45:20.0 +0200 +++ behave-1.2.6/debian/control 2019-10-18 16:03:41.0 +0200 @@ -13,8 +13,9 @@ python3-parse-type, python3-setuptools, python3-six, - python3-sphinx -Standards-Version: 4.4.0 + python3-sphinx, + python3-sphinx-bootstrap-theme +Standards-Version: 4.4.1 Homepage: https://github.com/behave/behave Vcs-Git: https://salsa.debian.org/python-team/modules/behave.git Vcs-Browser: https://salsa.debian.org/python-team/modules/behave diff -Nru behave-1.2.5/debian/patches/0001-docs-disable-use-of-sphincontrib.cheeseshop.patch behave-1.2.6/debian/patches/0001-docs-disable-use-of-sphincontrib.cheeseshop.patch --- behave-1.2.5/debian/patches/0001-docs-disable-use-of-sphincontrib.cheeseshop.patch 2019-09-13 14:27:54.0 +0200 +++ behave-1.2.6/debian/patches/0001-docs-disable-use-of-sphincontrib.cheeseshop.patch 1970-01-01 01:00:00.0 +0100 @@ -1,23 +0,0 @@ -From ed6df9cf0e8522ada8e3eda1d69dfbebc972f271 Mon Sep 17 00:00:00 2001 -From: Vincent Bernat -Date: Tue, 13 Jun 2017 07:38:03 +0200 -Subject: docs: disable use of sphincontrib.cheeseshop - -Not available in Debian - docs/conf.py | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/docs/conf.py b/docs/conf.py -index e108e30138f4..781eff883837 100644 a/docs/conf.py -+++ b/docs/conf.py -@@ -30,7 +30,7 @@ extensions = [ - "sphinx.ext.autodoc", - "sphinx.ext.extlinks", - # -- PYTHON2 SUPPORT ONLY: --"sphinxcontrib.cheeseshop", -+# "sphinxcontrib.cheeseshop", - ] - # if six.PY2: - # # -- PYTHON2 ONLY: Not ported to python3, yet. diff -Nru behave-1.2.5/debian/patches/0002-Python-3.6-compatibility-patch-re.LOCALE-removed.patch behave-1.2.6/debian/patches/0002-Python-3.6-compatibility-patch-re.LOCALE-removed.patch --- behave-1.2.5/debian/patches/0002-Python-3.6-compatibility-patch-re.LOCALE-removed.patch 2019-09-13 14:27:54.0 +0200 +++ behave-1.2.6/debian/patches/0002-Python-3.6-compatibility-patch-re.LOCALE-removed.patch 1970-01-01 01:00:00.0 +0100 @@ -1,25 +0,0 @@ -From 6c303a1255e86e7c6d8a9f9b958ea83a7db5db70 Mon Sep 17 00:00:00 2001 -From: Vincent Bernat -Date: Sat, 5 Aug 2017 12:44:17 +0200 -Subject: Python 3.6 compatibility patch (re.LOCALE removed) - - behave/configuration.py | 4 +++- - 1 file changed, 3 insertions(+), 1 deletion(-) - -diff --git a/behave/configuration.py b/behave/configuration.py -index a2563dfbf081..134004c1c950 100644 a/behave/configuration.py -+++ b/behave/configuration.py -@@ -661,8 +661,10 @@ class Configuration(object): - :param names: List of name parts or regular expressions (as text). - :return: Compiled regular expression to use. - """ -+# -- NOTE: re.LOCALE is removed in Python 3.6
Bug#949066: lintian: testsuite failures on arm*
Hello, > I have been working with the dpkg maintainers on a solution, which > will not happen anytime soon. The underlying problem is that > dpkg-buildpackage issues a build error when there is simply nothing to > do. > > Fixing that is complicated because source packages nowadays permit the > building of undeclared artifacts. There is no longer a way to tell > from a source package if a build should be attempted. Either way, I > will triage your bug later today. > > Thank you for your patience and for your help in trying to make > Lintian better for everyone. > wow I though the solution was "easy" thanks for keeping it running and rocking! feel free to take your time, I was making sure this bug was not "disappeared" :) I'm not sure if src:file migration to testing is stalled by this bug... grep-excuses file file (1:5.38-3 to 1:5.38-4) Maintainer: Christoph Biedl 7 days old (needed 5 days) Migration status for file (1:5.38-3 to 1:5.38-4): Waiting for test results, another package or too young (no action required now - check later) Issues preventing migration: autopkgtest for binutils: amd64: Test in progress (will not be considered a regression), arm64: Test in progress autopkgtest for lintian/2.46.0: amd64: Pass, arm64: Reference test in progress, but real test failed already Additional info: Piuparts tested OK - https://piuparts.debian.org/sid/source/f/file.html 7 days old (needed 5 days) G.
Processed: affects 949757
Processing commands for cont...@bugs.debian.org: > affects 949757 src:python-packaging Bug #949757 [dh-python] python-packaging: test failures due to wrong arch check Bug #948319 [dh-python] Fix setting _PYTHON_HOST_PLATFORM Added indication that 949757 affects src:python-packaging Added indication that 948319 affects src:python-packaging > thanks Stopping processing here. Please contact me if you need assistance. -- 948319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948319 949757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 916178, reassign 916178 to src:roger-router
Processing commands for cont...@bugs.debian.org: > tags 916178 - wontfix Bug #916178 [src:cups] roger-router-cli: missing dependency on cups Removed tag(s) wontfix. > reassign 916178 src:roger-router Bug #916178 [src:cups] roger-router-cli: missing dependency on cups Bug reassigned from package 'src:cups' to 'src:roger-router'. No longer marked as found in versions cups/2.3.1-1. Ignoring request to alter fixed versions of bug #916178 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 916178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949764: ksh: ksh/2020.0.0-3 will not uninstall cleanly (piuparts error)
Source: ksh Version: 2020.0.0-3 Severity: serious https://piuparts.debian.org/sid/fail/ksh_2020.0.0-3.log 0m14.4s DEBUG: Modified(user, group, mode, size, target): /etc/shells expected(root, root, - 100644, 73, None) != found(root, root, - 100644, 100, None) 0m14.4s ERROR: FAIL: After purging files have been modified: /etc/shellsnot owned 0m14.4s ERROR: FAIL: Installation and purging test. This often indicates that the handling of /etc/shells has bugs. Please take a look into it. -- Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#949066: lintian: testsuite failures on arm*
Hi Gianfranco, On Fri, Jan 24, 2020 at 8:39 AM Gianfranco Costamagna wrote: > > Felix gentle ping please? > (in Ubuntu I disabled that test BTW and the result package autopkgtestsuite > was green on all archs) The release took place solely to facilitate upgrading lintian.d.o, which has been down for months. Details are in #949398; your bug is mentioned there. I have been working with the dpkg maintainers on a solution, which will not happen anytime soon. The underlying problem is that dpkg-buildpackage issues a build error when there is simply nothing to do. Fixing that is complicated because source packages nowadays permit the building of undeclared artifacts. There is no longer a way to tell from a source package if a build should be attempted. Either way, I will triage your bug later today. Thank you for your patience and for your help in trying to make Lintian better for everyone. Kind regards Felix
Bug#949066: lintian: testsuite failures on arm*
hello, On Fri, 17 Jan 2020 09:29:57 +0100 Gianfranco Costamagna wrote: > Hello, > > > > > A list of the test packages that failed to build on arm* would be helpful. > > sure, you can grab all the test results from here > http://autopkgtest.ubuntu.com/packages/lintian > > (you can use 2.45.0ubuntu1 as reference to 2.45.0, the only difference is > this patch > http://launchpadlibrarian.net/460879291/lintian_2.45.0_2.45.0ubuntu1.diff.gz > please apply it!) > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949065 so 2.47.0 didn't hit the fix for this bug... Felix gentle ping please? (in Ubuntu I disabled that test BTW and the result package autopkgtestsuite was green on all archs) G.
Bug#916178: roger-router-cli: missing dependency on cups
control: tags -1 -wontfixcontrol: reassign -1 src:roger-router >I'm not going to engage in reassign combat, but my understanding is that the >following code from roger-router-cli.postinst _assumes_ that a local CUPS >daemon is available (as no -h is specified): you can do it, as said before, I wasn't really sure about the reassign either(I know such packages can have a working subset of functionalities and having an additional dependency is sometimes not the right thing to do!) >if which lpadmin >/dev/null >then > lpadmin -p "Roger-Router-Fax" -E -v roger-cups:/ -P >/usr/share/roger/roger-fax.ppd> >fi> > the postinst of roger-router-cli depends on a running, local, cups-daemon, >it has to grow a dependency on the daemon itself, and cups-client will not >grow that dependency. > >I'm tagging this bug as wontfix in CUPS, feel free to remove that tag when >reassigning back to roger-router-cli. thanks for the explanation! I'm not an user of roger-router myself, I just tried to fix RC bugs, but I'll be happy to see an upload or to upload it if youhave a patch :) otherwise, I think people will just need to install the cups dependency theirselves(or I can just add that dependency and live happy, but I have the feeling that the postinst/postrm can be tweaked to ignore the missing dependency?) Gianfranco
Processed: forcibly merging 948319 949757
Processing commands for cont...@bugs.debian.org: > forcemerge 948319 949757 Bug #948319 [dh-python] Fix setting _PYTHON_HOST_PLATFORM Bug #949757 [dh-python] python-packaging: test failures due to wrong arch check Removed indication that 949757 affects src:python-packaging Marked as found in versions dh-python/4.20191017. Added tag(s) bullseye, sid, and patch. Bug #948319 [dh-python] Fix setting _PYTHON_HOST_PLATFORM Added tag(s) ftbfs. Merged 948319 949757 > thanks Stopping processing here. Please contact me if you need assistance. -- 948319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948319 949757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948723: marked as done (tcmu-runner, (build-)dependencies unsatisfiable on mipsel.)
Your message dated Fri, 24 Jan 2020 16:19:48 + with message-id and subject line Bug#948723: fixed in tcmu 1.5.2-4 has caused the Debian Bug report #948723, regarding tcmu-runner, (build-)dependencies unsatisfiable on mipsel. 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.) -- 948723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tcmu-runner Version: 1.5.2-3 Severity: serious The binary packages built from the ceph source package were recently removed from mipsel, because the new version of ceph runs out of address space during the build. Your package build-depends on libradios-dev and librbd-dev and depends on librados2 and librbd1 which are built from the ceph source package. So tcmu-runner is now uninstallable and the tcmu source package is unbuildable on mipsel. If possible please build your package without rados/rbd support on mipsel (if this is not possible then it will probablly be nessacery to request removal of the tcemu binaries on mipsel). --- End Message --- --- Begin Message --- Source: tcmu Source-Version: 1.5.2-4 We believe that the bug you reported is fixed in the latest version of tcmu, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond (supplier of updated tcmu 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: Fri, 24 Jan 2020 17:00:41 +0100 Source: tcmu Architecture: source Version: 1.5.2-4 Distribution: unstable Urgency: medium Maintainer: Freexian Packaging Team Changed-By: Sebastien Delafond Closes: 948723 Changes: tcmu (1.5.2-4) unstable; urgency=medium . * Build without rbd support on mipsel (Closes: #948723) Checksums-Sha1: 8a63d37879510b9160e60576ca3b2aabd3aeb2d8 1703 tcmu_1.5.2-4.dsc abe1cd8540e2a35d89da4bf9c41cf2b23276b470 6112 tcmu_1.5.2-4.debian.tar.xz 059fd0112e0290705896ad9d9be9daafd1135d24 8771 tcmu_1.5.2-4_amd64.buildinfo Checksums-Sha256: 098a4893bc735aa53118ef0db9aa236e2d4ff4bd72783d2e376fac12cafef121 1703 tcmu_1.5.2-4.dsc cae5849515b3d9337a20529230cb582b1211dec0bf8ab4cee5d46cd3cea653a7 6112 tcmu_1.5.2-4.debian.tar.xz 4a8b9f8ac8eb330d7c9555f6b45b2491ccd370295bfd696a8773457a3e1a3c98 8771 tcmu_1.5.2-4_amd64.buildinfo Files: f8996bf7893c0ddaa35c57cd62645f59 1703 admin optional tcmu_1.5.2-4.dsc bf40fba694c7a2cbdfb5aac73ccb97a8 6112 admin optional tcmu_1.5.2-4.debian.tar.xz 24acfd81b4fc20ca7dd29cbd80e58929 8771 admin optional tcmu_1.5.2-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAl4rFXwACgkQEL6Jg/PV nWQNjggAwdZNjBml10hTXygy/VzAkDoL31c5ebNBch7tc1lFkjjYpyHZw5Vi/uuB C17L7/ILPV4mgKlYPt/ATtgk9Ftc3l5dcu0VyTUIlT7KSNbHstEl4Wtfte//gphG Wp6MuSNofMhYp2RIQoyIU5e9ENisjOtp/kicBWUliW9vKvgyathghKyletDHsSG8 J8dWiPbc3gcqSmbaqcPuzX/+E6LAlofE+9NUPYRyn7rHqUWTNAuNuLOZmFeUd8dh 99YGH/QzIRmpdZobVhvIbdq1HIUoEJNcQhY+lhOGbUiJpsrTgCcJDu+kgIDC5ajV 8Nsp7yZPI3xShEJZSj9xTC7traV6Ag== =s7Ho -END PGP SIGNATURE End Message ---
Processed: affects 949757
Processing commands for cont...@bugs.debian.org: > affects 949757 src:python-packaging Bug #949757 [dh-python] python-packaging: test failures due to wrong arch check Added indication that 949757 affects src:python-packaging > thanks Stopping processing here. Please contact me if you need assistance. -- 949757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#949757: python-packaging: test failures due to wrong arch check
Processing control commands: > reassign -1 dh-python Bug #949757 [src:python-packaging] python-packaging: test failures due to wrong arch check Bug reassigned from package 'src:python-packaging' to 'dh-python'. No longer marked as found in versions python-packaging/19.2-1. Ignoring request to alter fixed versions of bug #949757 to the same values previously set -- 949757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949757: python-packaging: test failures due to wrong arch check
Control: reassign -1 dh-python On 24.01.20 16:43, Adrian Bunk wrote: > Source: python-packaging > Version: 19.2-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=python-packaging=all=20.0-1=1578410735=0 > > ... >> assert linux_platform == "linux_x86_64" > E AssertionError: assert 'linux_amd64' == 'linux_x86_64' > E - linux_amd64 > E + linux_x86_64 > ... > > > Seems to be related to #938969. No, it's a bug in dh-python.
Bug#949759: bootcd: Missing build dependencies on python3-docutils and shellia
Source: bootcd Version: 6.00 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=bootcd=all=6.00=1576857218=0 ... debian/rules build-indep make[1]: Entering directory '/<>' make[1]: rst2man: Command not found make[1]: *** [Makefile:51: bootcdwrite.1] Error 127
Processed: tagging 948723
Processing commands for cont...@bugs.debian.org: > tags 948723 + pending Bug #948723 [tcmu-runner] tcmu-runner, (build-)dependencies unsatisfiable on mipsel. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 948723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949758: archmage: Missing build dependencies on python3-sgmllib3k and python3-chm
Source: archmage Version: 1:0.4.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=archmage=all=1%3A0.4.1-1=1577227085=0 ... ERRORS _ ERROR collecting .pybuild/cpython3_3.8/build/tests/test_openclose.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.8/build/tests/test_openclose.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: tests/test_openclose.py:1: in import sys, archmage.cli, pathlib, tempfile, errno, shutil, contextlib archmage/cli.py:57: in from archmage.CHM import CHMFile, Action archmage/CHM.py:34: in from archmage.CHMParser import SitemapFile, PageLister, ImageCatcher, TOCCounter#, HeadersCounter archmage/CHMParser.py:24: in import sgmllib, urllib.request, urllib.error, urllib.parse E ModuleNotFoundError: No module named 'sgmllib' ...
Bug#949757: python-packaging: test failures due to wrong arch check
Source: python-packaging Version: 19.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-packaging=all=20.0-1=1578410735=0 ... > assert linux_platform == "linux_x86_64" E AssertionError: assert 'linux_amd64' == 'linux_x86_64' E - linux_amd64 E + linux_x86_64 ... Seems to be related to #938969.
Bug#949756: staticsite FTBFS: FAIL: test_site (tests.test_page_filter.TestPageFilter)
Source: staticsite Version: 1.4.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=staticsite=all=1.4.1-1=1578410781=0 ... == FAIL: test_site (tests.test_page_filter.TestPageFilter) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.8/build/tests/test_page_filter.py", line 22, in test_site self.assertEqual(select(site, path="blog/*"), [ AssertionError: Lists differ: ['/blog/post2', '/blog/post1'] != ['/blog/post1', '/blog/post2'] First differing element 0: '/blog/post2' '/blog/post1' - ['/blog/post2', '/blog/post1'] + ['/blog/post1', '/blog/post2'] -- Ran 55 tests in 3.425s FAILED (failures=1)
Bug#949753: mycli fails to run - cli_helpers issue
Package: mycli
Version: 1.20.1-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The latest update of the mycli package resolves #949596. However a clean run
results in:
root@kiev:~# mycli mythconverg
Traceback (most recent call last):
File "/usr/bin/mycli", line 11, in
load_entry_point('mycli==1.20.1', 'console_scripts', 'console')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2852,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2443,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2449,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/share/mycli/mycli/main.py", line 36, in
from .packages.tabular_output import sql_format
File "/usr/share/mycli/mycli/packages/tabular_output/sql_format.py", line 5,
in
from cli_helpers.utils import filter_dict_by_key
ModuleNotFoundError: No module named 'cli_helpers'
I am not a python person, but my guess is a missing module. A search on
packages.debian.org reveals:
/usr/lib/python3/dist-packages/openscap_daemon/cli_helpers.py openscap-daemon
so there is a package with that python file in it - it either needs to be
included in mycli, or rolled as a
deb for use by all possible python programs.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mycli depends on:
ii python3 3.7.5-3
ii python3-click 7.0-3
ii python3-configobj 5.0.6-3
ii python3-cryptography2.6.1-4
ii python3-pkg-resources 44.0.0-1
ii python3-prompt-toolkit 2.0.10-2
ii python3-pygments2.3.1+dfsg-1
ii python3-pymysql 0.9.3-2
ii python3-sqlparse0.2.4-3
ii python3-tabulate0.8.2-1.1
ii python3-terminaltables 3.1.0-3
mycli recommends no packages.
mycli suggests no packages.
-- no debconf information
Bug#922589: FTBFS against opencv 4.0.1 (exp)
On Tue, Jan 07, 2020 at 05:15:14PM +0100, Samuel Thibault wrote: > > > pkg-config file has been marked deprecated by upstream. > > > > I admit I have no idea what to do now. Any hint? > > Apparently there is a opencv4.pc file? With this patch[1] opencv4 is detected - but the code is not compatible with opencv4. I get lots of errors like this: ... g++ -DHAVE_CONFIG_H -I. -Isrc/processor/headers/ -DINSTALLDIR='"/usr/share/opencfu"' -pthread -I/usr/include/gtkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 -I/usr/include/gdkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/ pango-1.0 -I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/ lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Isrc/gui/headers/ -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/opencv4/opencv -I/usr/include/ opencv4 -fopenmp -Isrc/ -Wall -g -O2 -fdebug-prefix-map=/build/opencfu-3.9.0=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/processor/src/opencfu-ArgumentParser.o `test -f 'src/ processor/src/ArgumentParser.cpp' || echo './'`src/processor/src/ArgumentParser.cpp In file included from src/processor/headers/ProcessingOptions.hpp:8, from src/processor/headers/ArgumentParser.hpp:5, from src/main.cpp:21: src/processor/headers/MaskROI.hpp: In constructor 'MaskROI::MaskROI(const string&)': src/processor/headers/MaskROI.hpp:16:29: error: 'CV_LOAD_IMAGE_GRAYSCALE' was not declared in this scope 16 | cv::imread(path,CV_LOAD_IMAGE_GRAYSCALE).copyTo(m_original_mat); | ^~~ src/processor/headers/MaskROI.hpp: In constructor 'MaskROI::MaskROI(cv::Mat, int)': src/processor/headers/MaskROI.hpp:25:13: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 25 | if(typepp != MASK_TYPE_NONE) | ^~ src/processor/headers/MaskROI.hpp:27:17: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 27 | img.copyTo(m_mat); | ^~~ In file included from src/processor/headers/ArgumentParser.hpp:5, from src/main.cpp:21: src/processor/headers/ProcessingOptions.hpp: In member function 'bool ProcessingOptions::setImage(std::string)': src/processor/headers/ProcessingOptions.hpp:114:46: error: 'CV_LOAD_IMAGE_ANYDEPTH' was not declared in this scope 114 | cv::Mat tmpImg = cv::imread(str, CV_LOAD_IMAGE_ANYDEPTH | CV_LOAD_IMAGE_COLOR); | ^~ src/processor/headers/ProcessingOptions.hpp:114:71: error: 'CV_LOAD_IMAGE_COLOR' was not declared in this scope 114 | cv::Mat tmpImg = cv::imread(str, CV_LOAD_IMAGE_ANYDEPTH | CV_LOAD_IMAGE_COLOR); | ^~~ ... When trying to build opencfu. Is there any short guideline how to port from opencv < 4 to opencv version 4? Any help would be appreciated Andreas, [1] https://salsa.debian.org/med-team/opencfu/blob/master/debian/patches/0017_opencv4.patch -- http://fam-tille.de
Processed: Re: Patch for FTBFS
Processing commands for cont...@bugs.debian.org: > tags 914056 + patch Bug #914056 [src:cclive] cclive FTBFS with boost 1.67 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 914056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949749: freeboard: Depends: libjs-codemirror (< 5.49.2.0~) but 5.50.2-1 is to be installed
Package: freeboard Version: 1.1.0+dfsg.1-2 Severity: serious bin-NMUs are not possible for binary-all, this needs a source upload.
Bug#949750: geoalchemy2: Cannot fulfill the build dependencies
Source: geoalchemy2 Version: 0.6.3-1.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=geoalchemy2=sid geoalchemy2 build-depends on missing: - postgresql-11-postgis-2.5:amd64 The buildds for unstable only consider the first alternative of build dependencies.
Bug#942138: marked as done (apt: installation of glade destroys system)
Your message dated Fri, 24 Jan 2020 15:26:00 +0100 with message-id <20200124142600.dsqfdlmpmaqlzxae@crossbow> and subject line Re: Bug#942138: apt: installation of glade destroys system has caused the Debian Bug report #942138, regarding apt: installation of glade destroys system 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.) -- 942138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 1.8.2 Severity: critical Justification: breaks the whole system Dear Maintainer, This report comes from a different (not broken) system. When I was asked for the apt-files by the bugreport program, I moved the old ones to the system I am using now (hope this worked). I tried to install "glade" on my system. This removed a lot of packages. This destroyed my system. I could have prevented this problem by checking the packages that will be removed, but I do not always do that. My desktop environment was XFCE4 and the system used the Vesa driver. The display manager was lightdm and Gnome was not installed (only some Gnome apps). I tried to use the rescue mode on a debian DVD and the rescue mode that was available in GRUB. But I had to reinstall my system (rescue mode was not working). I think this information will have the most value for you (/var/log/apt/history.log): Start-Date: 2019-10-02 20:45:38 Commandline: apt-get install glade Install: libpython3.7-minimal:amd64 (3.7.3-2, automatic), libx265-165:amd64 (2.9-4, automatic), libgpgmepp6:amd64 (1.12.0-6, automatic), libgupnp- igd-1.0-4:amd64 (0.2.5-3, automatic), node-normalize.css:amd64 (8.0.1-3, automatic), startpar:amd64 (0.61-1, automatic), libmbedtls12:amd64 (2.16.0-1, automatic), gir1.2-gtksource-4:amd64 (4.0.3-2, automatic), libvulkan1:amd64 (1.1.97-2, automatic), libwayland-egl1:amd64 (1.16.0-1, automatic), python3-distutils:amd64 (3.7.3-1, automatic), libgtksourceview-4-common:amd64 (4.0.3-2, automatic), libvkd3d1:amd64 (1.1-3, automatic), libobjc-8-dev:amd64 (8.3.0-6, automatic), libegl1:amd64 (1.1.0-1, automatic), libllvm7:amd64 (1:7.0.1-8, automatic), libmbedcrypto3:amd64 (2.16.0-1, automatic), valac-0.42-vapi:amd64 (0.42.5-1, automatic), libegl-mesa0:amd64 (18.3.6-2, automatic), libswresample3:amd64 (7:4.1.4-1~deb10u1, automatic), libqt5sensors5:amd64 (5.11.3-2, automatic), libnumbertext-data:amd64 (1.0.5-1, automatic), libbrotli1:amd64 (1.0.7-2, automatic), libmtdev-dev:amd64 (1.1.5-1+b1, automatic), libsndio7.0:amd64 (1.5.0-3, automatic), libnice10:amd64 (0.1.14-1, automatic), libsrtp2-1:amd64 (2.2.0-1, automatic), libgl1:amd64 (1.1.0-1, automatic), gcc-8-base:amd64 (8.3.0-6, automatic), gcc-8-base:i386 (8.3.0-6, automatic), gcc-8-base:armhf (8.3.0-6, automatic), libcrypt-openssl-random-perl:amd64 (0.15-1+b1, automatic), clang-7:amd64 (1:7.0.1-8, automatic), libwoff1:amd64 (1.0.2-1, automatic), libzmf-0.0-0:amd64 (0.0.2-1+b2, automatic), libvala-0.42-0:amd64 (0.42.5-1, automatic), libjsonrpc-glib-1.0-1:amd64 (3.30.1-2, automatic), libgupnp-1.0-4:amd64 (1.0.3-3, automatic), perl-modules-5.28:amd64 (5.28.1-6, automatic), libncurses6:amd64 (6.1+20181013-2+deb10u1, automatic), gir1.2-ggit-1.0:amd64 (0.27.7-1, automatic), insserv:amd64 (1.18.0-2, automatic), libpython3.7:amd64 (3.7.3-2, automatic), libimagequant0:amd64 (2.12.2-1.1, automatic), python3.7:amd64 (3.7.3-2, automatic), gir1.2-template-1.0:amd64 (3.30.0-2, automatic), libselinux1-dev:amd64 (2.8-1+b1, automatic), libfribidi-dev:amd64 (1.0.5-3.1, automatic), python3.7-dev:amd64 (3.7.3-2, automatic), libasan5:amd64 (8.3.0-6, automatic), libgles2:amd64 (1.1.0-1, automatic), libdazzle-1.0-0:amd64 (3.30.2-2, automatic), libwacom-dev:amd64 (0.32-1, automatic), libclang-common-7-dev:amd64 (1:7.0.1-8, automatic), libpython3.7-stdlib:amd64 (3.7.3-2, automatic), libclang1-6.0:amd64 (1:6.0.1-10, automatic), python3.7-minimal:amd64 (3.7.3-2, automatic), libyaml- cpp0.6:amd64 (0.6.2-4, automatic), libaom0:amd64 (1.0.0-3, automatic), libxmlsec1-nss:amd64 (1.2.27-2, automatic), libmount-dev:amd64 (2.33.1-0.1, automatic), libqxp-0.0-0:amd64 (0.0.2-1, automatic), libperl5.28:amd64 (5.28.1-6, automatic), pango1.0-tools:amd64 (1.42.4-7~deb10u1, automatic), libxnvctrl0:amd64 (418.74-1, automatic), libnumbertext-1.0-0:amd64 (1.0.5-1, automatic), libgcc-8-dev:amd64 (8.3.0-6, automatic), libunbound8:amd64 (1.9.0-2, automatic), libglib2.0-dev-bin:amd64 (2.58.3-2+deb10u1, automatic), libva2:amd64 (2.4.0-1, automatic), libllvm6.0:amd64 (1:6.0.1-10, automatic), libx264-155:amd64 (2:0.155.2917+git0a84d98-2, automatic),
Processed: tagging 914353
Processing commands for cont...@bugs.debian.org: > tags 914353 + ftbfs Bug #914353 [src:hdbc-odbc] hdbc-odbc: Missing build-dependency on concurrent-extra Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 914353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 914352
Processing commands for cont...@bugs.debian.org: > tags 914352 + ftbfs Bug #914352 [src:haskell-hmt] haskell-hmt: Missing build-dependency on modular-arithmetic Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 914352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949695: marked as done (thunderbird does not start anymore)
Your message dated Fri, 24 Jan 2020 14:38:48 +0100 with message-id <8700c447-be92-64c7-0eb8-81f2e27fe...@debian.org> and subject line Re: Bug#949695: Acknowledgement (thunderbird does not start anymore) has caused the Debian Bug report #949695, regarding thunderbird does not start anymore 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.) -- 949695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: thunderbird Version: 1:68.4.1-1+b1 Severity: serious Hey, one of the last days testing and or unstable updates let thunderbird stop starting. I just get: $ thunderbird ExceptionHandler::GenerateDump cloned child 3482 ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child me@gnu:~$ Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='UTF-8'> BrokenPipeError: [Errno 32] Broken pipe Also with a new profile, also with the version from testing and unstable. So I think some dependecie crashes thunderbird -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- With todays updates it works again Am 23.01.2020 um 19:51 schrieb Debian Bug Tracking System: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 949695: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949695. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Carsten Schoenert > > If you wish to submit further information on this problem, please > send it to 949...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: https://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */--- End Message ---
Bug#949730: marked as done (pyutilib ftbfs from source, calling python instead of python3)
Your message dated Fri, 24 Jan 2020 13:20:06 +
with message-id
and subject line Bug#949730: fixed in pyutilib 5.7.3-1
has caused the Debian Bug report #949730,
regarding pyutilib ftbfs from source, calling python instead of python3
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.)
--
949730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyutilib
Version: 5.7.1-1
Severity: serious
Tags: sid bullseye
[...]
==
FAIL: test_driver_1 (pyutilib.workflow.tests.test_doc.Test)
--
Traceback (most recent call last):
File "/<>/pyutilib/th/pyunit.py", line 451, in
func = lambda
self,c1=cwd,c2=cmd,c3=os.path.abspath(outfile),c4=baseline,c5=filter,c6=cmdfile,c7=tolerance,c8=exact,c9=forceskip:
_run_cmd_baseline_test(self,cwd=c1,cmd=c2,outfile=c3,baseline=c4,filter=c5,cmdfile=c6,tolerance=c7,exact=c8,forceskip=c9)
File "/<>/pyutilib/th/pyunit.py", line 221, in
_run_cmd_baseline_test
outfile, baseline, filter=filter, tolerance=tolerance)
File "/<>/pyutilib/th/pyunit.py", line 370, in
assertFileEqualsBaseline
baseline + "\nDiffs:\n" + diffs)
AssertionError: Unexpected output difference at line 1:
testfile=/<>/doc/workflow/examples/driver_1.out
baseline=/<>/doc/workflow/examples/driver_1.txt
Diffs:
--- /<>/doc/workflow/examples/driver_1.txt
+++ /<>/doc/workflow/examples/driver_1.out
@@ -1 +1 @@
-z: 7
+/<>/doc/workflow/examples/driver_1.sh: 4: python: not found
==
FAIL: test_driver_2 (pyutilib.workflow.tests.test_doc.Test)
--
Traceback (most recent call last):
File "/<>/pyutilib/th/pyunit.py", line 451, in
func = lambda
self,c1=cwd,c2=cmd,c3=os.path.abspath(outfile),c4=baseline,c5=filter,c6=cmdfile,c7=tolerance,c8=exact,c9=forceskip:
_run_cmd_baseline_test(self,cwd=c1,cmd=c2,outfile=c3,baseline=c4,filter=c5,cmdfile=c6,tolerance=c7,exact=c8,forceskip=c9)
File "/<>/pyutilib/th/pyunit.py", line 221, in
_run_cmd_baseline_test
outfile, baseline, filter=filter, tolerance=tolerance)
File "/<>/pyutilib/th/pyunit.py", line 370, in
assertFileEqualsBaseline
baseline + "\nDiffs:\n" + diffs)
AssertionError: Unexpected output difference at line 1:
testfile=/<>/doc/workflow/examples/driver_2.out
baseline=/<>/doc/workflow/examples/driver_2.txt
Diffs:
--- /<>/doc/workflow/examples/driver_2.txt
+++ /<>/doc/workflow/examples/driver_2.out
@@ -1 +1 @@
-usage: myprog TaskZ [-h] [--x X] [--y Y]
+/<>/doc/workflow/examples/driver_2.sh: 4: python: not found
==
FAIL: test_driver_3 (pyutilib.workflow.tests.test_doc.Test)
--
Traceback (most recent call last):
File "/<>/pyutilib/th/pyunit.py", line 451, in
func = lambda
self,c1=cwd,c2=cmd,c3=os.path.abspath(outfile),c4=baseline,c5=filter,c6=cmdfile,c7=tolerance,c8=exact,c9=forceskip:
_run_cmd_baseline_test(self,cwd=c1,cmd=c2,outfile=c3,baseline=c4,filter=c5,cmdfile=c6,tolerance=c7,exact=c8,forceskip=c9)
File "/<>/pyutilib/th/pyunit.py", line 221, in
_run_cmd_baseline_test
outfile, baseline, filter=filter, tolerance=tolerance)
File "/<>/pyutilib/th/pyunit.py", line 370, in
assertFileEqualsBaseline
baseline + "\nDiffs:\n" + diffs)
AssertionError: Unexpected output difference at line 1:
testfile=/<>/doc/workflow/examples/driver_3.out
baseline=/<>/doc/workflow/examples/driver_3.txt
Diffs:
--- /<>/doc/workflow/examples/driver_3.txt
+++ /<>/doc/workflow/examples/driver_3.out
@@ -1 +1 @@
-usage: myprog [-h] {TaskY,TaskZ} ...
+/<>/doc/workflow/examples/driver_3.sh: 4: python: not found
--
Ran 576 tests in 10.308s
FAILED (SKIP=38, errors=3, failures=26)
--- End Message ---
--- Begin Message ---
Source: pyutilib
Source-Version: 5.7.3-1
We believe that the bug you reported is fixed in the latest version of
pyutilib, 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 949...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian
Bug#949730: python -> python3 done in new upload
A new version 5.7.3 is out, so I have addressed the "python" in the test routines and wherever I encountered them. Some tests still fail since files are written to the install folder where they are not tested. Other comparisons now fail since there is a linebreak in the help output where there was none before if I interpret this right. If someone could send a patch for that this would be much appreciated. Steffen
Processed: affects 877496
Processing commands for cont...@bugs.debian.org: > affects 877496 - src:ocsigenserver Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type Obj.t but an expression was expected of type extension_constructor Removed indication that 877496 affects src:ocsigenserver > thanks Stopping processing here. Please contact me if you need assistance. -- 877496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949736: enigmail: uninstallable in stretch (since thunderbird was upgraded to version 68 due to security upgrade)
Package: enigmail Version: 2:2.0.8-5~deb9u1 Justification: renders package unusable Severity: grave Tags: stretch Dear Maintainer, Current version of Thunderbird in Debian stretch is 68, which is incompatible with the enigmail currently packaged in stretch. The issue was fixed in Debian buster and Debian jessie by upgrading the version of enigmail, but this has not been done in stretch yet. Then, * for new installs, enigmail cannot be installed, * the computers that were already running stretch need to choose between upgrading Thunderbird to get the security updates (and then enigmail will be uninstalled), or keeping the old version of Thunderbird with a working enigmail (but having unpatched security vulnerabilities). There will be a release point for stretch soon and it would be great if it carries a new version of enigmail solving this issue for stretch. Thanks! -- Laura Arjona https://wiki.debian.org/LauraArjona -- System Information: Debian Release: 9.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-11-amd64 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages enigmail depends on: ii gnupg 2.1.18-8~deb9u4 ii gnupg-agent2.1.18-8~deb9u4 ii icedove1:68.4.1-1~deb9u1 ii thunderbird [icedove] 1:68.4.1-1~deb9u1 Versions of packages enigmail recommends: ii pinentry-gnome3 [pinentry-x11] 1.0.0-2 enigmail suggests no packages. -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#949669: marked as done (votca-csg ftbfs with gromacs 2020-2)
Your message dated Fri, 24 Jan 2020 11:00:36 + with message-id and subject line Bug#949669: fixed in votca-csg 1.6~rc1-1 has caused the Debian Bug report #949669, regarding votca-csg ftbfs with gromacs 2020-2 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.) -- 949669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: votca-csg Version: 1.5.1-1 Severity: serious Justification: ftbfs Tags: ftbfs sid bullseye Dear maintainer, gromacs started a transition and I scheduled binNMUs for votca-csg. However, they failed. Please investigate. Paul https://buildd.debian.org/status/package.php?p=votca-csg Tail of log for votca-csg on amd64: | ^~~~ In file included from /usr/include/gromacs/trajectory/trajectoryframe.h:50, from /<>/src/libcsg/modules/io/gmxtrajectorywriter.h:28, from /<>/src/libcsg/trajectorywriter.cc:30: /usr/include/gromacs/utility/arrayref.h:273:106: error: expected unqualified-id before ‘>’ token 273 | ArrayRef::value, const typename T::value_type, typename T::value_type>> | ^~ make[3]: *** [src/libcsg/CMakeFiles/votca_csg.dir/build.make:404: src/libcsg/CMakeFiles/votca_csg.dir/trajectorywriter.cc.o] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:396: src/libcsg/CMakeFiles/votca_csg.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[1]: *** [Makefile:133: all] Error 2 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:29: binary-arch] Error 25 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: votca-csg Source-Version: 1.6~rc1-1 We believe that the bug you reported is fixed in the latest version of votca-csg, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas Breen (supplier of updated votca-csg 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: Thu, 23 Jan 2020 18:34:42 -0800 Source: votca-csg Binary: libvotca-csg-dev libvotca-csg6 libvotca-csg6-dbgsym votca-csg votca-csg-dbgsym votca-csg-scripts votca-csg-tutorials Architecture: source amd64 all Version: 1.6~rc1-1 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Nicholas Breen Description: libvotca-csg-dev - VOTCA's coarse-graining library, development kit libvotca-csg6 - VOTCA's coarse-graining library votca-csg - VOTCA's coarse-graining engine votca-csg-scripts - VOTCA's coarse-graining scripts votca-csg-tutorials - VOTCA's coarse-graining tutorials Closes: 949669 Changes: votca-csg (1.6~rc1-1) unstable; urgency=medium . * New upstream release candidate. - SONAME bump to libvotca-csg6. - Discard existing debian/patches/*.patch, incorporated upstream. * Increment Depends: on gromacs to >= 2020-2 - minimum 2020 version with necessary headers. (Closes: #949669) * d/patches/directory-with-tilde.patch: Fix builds with certain special characters in the build path, such as the ~ in "1.6~rc1". * Update Standards-Version to 4.5.0, no changes required. Checksums-Sha1: 8f7bbda56820849dc71cdf77f5bb9cabbe908191 2838 votca-csg_1.6~rc1-1.dsc 2e030947afc810cb955f897ebcec829b6b3ea7b5 5946622 votca-csg_1.6~rc1.orig-tutorials.tar.gz c2a9b4d8a8bbbc32b785884120b8234f81e3f616 479265 votca-csg_1.6~rc1.orig.tar.gz 5c5bbc7a8192995e359329f69abc965b4979a19c 5208 votca-csg_1.6~rc1-1.debian.tar.xz 6574bc79f264d571d58f1feb18b8961a15751d3a 39924 libvotca-csg-dev_1.6~rc1-1_amd64.deb 89fbf670979d4a03d394315467378ec5ab30971e 18760308 libvotca-csg6-dbgsym_1.6~rc1-1_amd64.deb 39f9df069ca17aaff7ac8966586a21545d0f1546 318088 libvotca-csg6_1.6~rc1-1_amd64.deb c41346d3b7efcc66a287654608ab9e693e1b6534 13246888 votca-csg-dbgsym_1.6~rc1-1_amd64.deb 05242d1533ad5cf182ff94685d6deda4f0c4e5e9 70560
Bug#937727: marked as done (python-enable: convert package to Python 3)
Your message dated Fri, 24 Jan 2020 11:00:34 + with message-id and subject line Bug#937727: fixed in python-enable 4.8.1-1 has caused the Debian Bug report #937727, regarding python-enable: convert package to Python 3 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.) -- 937727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-enable Version: 4.5.1-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-enable If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-enable Source-Version: 4.8.1-1 We believe that the bug you reported is fixed in the latest version of python-enable, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Varun Hiremath (supplier of updated python-enable 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: Thu, 23 Jan 2020 16:04:30 -0800 Source: python-enable Binary: python3-enable python3-enable-dbgsym Architecture: source amd64 Version: 4.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Varun Hiremath Description: python3-enable - Drawing and interaction packages (Python 3) Closes: 937727 Changes: python-enable (4.8.1-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/watch: Use https protocol * d/control: Remove ancient X-Python-Version field * Convert git repository from git-dpm to gbp layout . [ Varun Hiremath ] * New upstream release * Switch to Python 3 (Closes: #937727) * Add python3-enable package * debian/rules: switch to dh-* and pybuild * d/patches: - Drop gcc5, fonttools, pillow, 0007-fix-FTBFS-with-SWIG-3 patches - Add cython_speedups patch to fix build with Python 3.8 - Add
Processed: affects 877496
Processing commands for cont...@bugs.debian.org: > affects 877496 - ocsigenserver Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type Obj.t but an expression was expected of type extension_constructor Removed indication that 877496 affects > thanks Stopping processing here. Please contact me if you need assistance. -- 877496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10
Package: python-pip Version: 18.1-5 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, When invoking `usr/bin/pip' with any command of it, the program crashes with the message : "Traceback (most recent call last): File "/usr/bin/pip", line 9, in from pip._internal import main ImportError: No module named _internal" I tried making a workaround by replacing the line "from pip._internal import main" by "from pip import main" in '/usr/bin/pip' but it did crash after having downloaded the module. -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/16 CPU cores) 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-pip depends on: ii ca-certificates 20190110 ii python 2.7.17-2 ii python-pip-whl 18.1-5 Versions of packages python-pip recommends: ii build-essential12.8 ii python-all-dev 2.7.17-2 ii python-setuptools 44.0.0-1 ii python-wheel 0.33.6-2 python-pip suggests no packages. -- no debconf information
Bug#949658: Different tests for r-cran-recipes - "wrong" test prevents migration of r-cran-testthat
Hi,
when looking at the CI page for r-cran-recipes which is linked from
tracker.d.o[1]
all tests are passing. The latest log[2] says:
...
Attaching package: 'recipes'
The following object is masked from 'package:stats':
step
>
> if (requireNamespace("xml2")) {
+ test_check("recipes", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"), CheckReporter$new(
+ } else {
+ test_check("recipes")
+ }
Loading required namespace: xml2
== testthat results ===
[ OK: 1434 | SKIPPED: 8 | WARNINGS: 0 | FAILED: 0 ]
>
autopkgtest [19:42:48]: test run-unit-test: ---]
autopkgtest [19:42:48]: test run-unit-test: - - - - - - - - - - results - - -
- - - - - - -
run-unit-testPASS
autopkgtest [19:42:48]: summary
However, if I look at the tracker page of r-cran-testthat[3] there is
a blocker for testing migration:
autopkgtest for r-cran-recipes/0.1.9+dfsg-1: amd64: Regression ♻ , arm64:
Regression ♻
It links to a log[4] that seems to run on testing which says:
...
Attaching package: 'recipes'
The following object is masked from 'package:stats':
step
>
> if (requireNamespace("xml2")) {
+ test_check("recipes", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"), CheckReporter$new(
+ } else {
+ test_check("recipes")
+ }
Loading required namespace: xml2
3 packages are needed for this model and are not installed. (RSpectra, igraph,
RANN). Start a clean R session then run: install.packages(c("RSpectra",
"igraph", "RANN"))-- 1. Error: quasiquotation (@test_slice.R#40)
`call` must be a call
== testthat results ===
[ OK: 1428 | SKIPPED: 9 | WARNINGS: 0 | FAILED: 1 ]
1. Error: quasiquotation (@test_slice.R#40)
Error: testthat unit tests failed
Execution halted
autopkgtest [13:11:23]: test run-unit-test: ---]
autopkgtest [13:11:23]: test run-unit-test: - - - - - - - - - - results - - -
- - - - - - -
run-unit-testFAIL non-zero exit status 1
autopkgtest [13:11:23]: summary
run-unit-testFAIL non-zero exit status 1
I guess one difference [install.packages(c("RSpectra", "igraph", "RANN"))]
is missing above since I just uploaded a new version including these
Build-Depends. But there is this remaining
1. Error: quasiquotation (@test_slice.R#40)
`call` must be a call
and I have no idea how to fix this. May be there is some unspecified
versioned Build-Depends or something like this.
Is there any chance to let r-cran-testthat and r-cran-recipes (as well
as all its rdepends) migrate easily? Otherwise the only chance I see is
to deactivate the according test, let packages migrate and activate it
once this had happened.
Any better advise would be perfectly welcome.
Kind regards
Andreas.
[1] https://ci.debian.net/packages/r/r-cran-recipes/unstable/amd64/
[2]
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-recipes/4080660/log.gz
[3] https://tracker.debian.org/pkg/r-cran-testthat
[4]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-recipes/4072773/log.gz
--
http://fam-tille.de
Processed: retitle 949731 to qemu: CVE-2020-1711: block: iscsi: OOB heap access via an unexpected response of iSCSI Server
Processing commands for cont...@bugs.debian.org: > # fix subject > retitle 949731 qemu: CVE-2020-1711: block: iscsi: OOB heap access via an > unexpected response of iSCSI Server Bug #949731 [src:qemu] qemu: VE-2020-1711: block: iscsi: OOB heap access via an unexpected response of iSCSI Server Changed Bug title to 'qemu: CVE-2020-1711: block: iscsi: OOB heap access via an unexpected response of iSCSI Server' from 'qemu: VE-2020-1711: block: iscsi: OOB heap access via an unexpected response of iSCSI Server'. > thanks Stopping processing here. Please contact me if you need assistance. -- 949731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949732: package ftbfs on some archs, and has missing dependencies
Package: src:mlpack Version: 3.2.2-2 Severity: serious Tags: sid bullseye package ftbfs on some archs, and has missing dependencies: missing build on i386 missing build on mipsel uninstallable on arch amd64, autopkgtest delayed there uninstallable on arch arm64, autopkgtest delayed there Additional info: python3-mlpack/amd64 unsatisfiable Depends: python3.7-mlpack python3-mlpack/arm64 unsatisfiable Depends: python3.7-mlpack python3-mlpack/armel unsatisfiable Depends: python3.7-mlpack python3-mlpack/armhf unsatisfiable Depends: python3.7-mlpack python3-mlpack/mips64el unsatisfiable Depends: python3.7-mlpack python3-mlpack/ppc64el unsatisfiable Depends: python3.7-mlpack python3-mlpack/s390x unsatisfiable Depends: python3.7-mlpack
Bug#949730: pyutilib ftbfs from source, calling python instead of python3
Package: src:pyutilib
Version: 5.7.1-1
Severity: serious
Tags: sid bullseye
[...]
==
FAIL: test_driver_1 (pyutilib.workflow.tests.test_doc.Test)
--
Traceback (most recent call last):
File "/<>/pyutilib/th/pyunit.py", line 451, in
func = lambda
self,c1=cwd,c2=cmd,c3=os.path.abspath(outfile),c4=baseline,c5=filter,c6=cmdfile,c7=tolerance,c8=exact,c9=forceskip:
_run_cmd_baseline_test(self,cwd=c1,cmd=c2,outfile=c3,baseline=c4,filter=c5,cmdfile=c6,tolerance=c7,exact=c8,forceskip=c9)
File "/<>/pyutilib/th/pyunit.py", line 221, in
_run_cmd_baseline_test
outfile, baseline, filter=filter, tolerance=tolerance)
File "/<>/pyutilib/th/pyunit.py", line 370, in
assertFileEqualsBaseline
baseline + "\nDiffs:\n" + diffs)
AssertionError: Unexpected output difference at line 1:
testfile=/<>/doc/workflow/examples/driver_1.out
baseline=/<>/doc/workflow/examples/driver_1.txt
Diffs:
--- /<>/doc/workflow/examples/driver_1.txt
+++ /<>/doc/workflow/examples/driver_1.out
@@ -1 +1 @@
-z: 7
+/<>/doc/workflow/examples/driver_1.sh: 4: python: not found
==
FAIL: test_driver_2 (pyutilib.workflow.tests.test_doc.Test)
--
Traceback (most recent call last):
File "/<>/pyutilib/th/pyunit.py", line 451, in
func = lambda
self,c1=cwd,c2=cmd,c3=os.path.abspath(outfile),c4=baseline,c5=filter,c6=cmdfile,c7=tolerance,c8=exact,c9=forceskip:
_run_cmd_baseline_test(self,cwd=c1,cmd=c2,outfile=c3,baseline=c4,filter=c5,cmdfile=c6,tolerance=c7,exact=c8,forceskip=c9)
File "/<>/pyutilib/th/pyunit.py", line 221, in
_run_cmd_baseline_test
outfile, baseline, filter=filter, tolerance=tolerance)
File "/<>/pyutilib/th/pyunit.py", line 370, in
assertFileEqualsBaseline
baseline + "\nDiffs:\n" + diffs)
AssertionError: Unexpected output difference at line 1:
testfile=/<>/doc/workflow/examples/driver_2.out
baseline=/<>/doc/workflow/examples/driver_2.txt
Diffs:
--- /<>/doc/workflow/examples/driver_2.txt
+++ /<>/doc/workflow/examples/driver_2.out
@@ -1 +1 @@
-usage: myprog TaskZ [-h] [--x X] [--y Y]
+/<>/doc/workflow/examples/driver_2.sh: 4: python: not found
==
FAIL: test_driver_3 (pyutilib.workflow.tests.test_doc.Test)
--
Traceback (most recent call last):
File "/<>/pyutilib/th/pyunit.py", line 451, in
func = lambda
self,c1=cwd,c2=cmd,c3=os.path.abspath(outfile),c4=baseline,c5=filter,c6=cmdfile,c7=tolerance,c8=exact,c9=forceskip:
_run_cmd_baseline_test(self,cwd=c1,cmd=c2,outfile=c3,baseline=c4,filter=c5,cmdfile=c6,tolerance=c7,exact=c8,forceskip=c9)
File "/<>/pyutilib/th/pyunit.py", line 221, in
_run_cmd_baseline_test
outfile, baseline, filter=filter, tolerance=tolerance)
File "/<>/pyutilib/th/pyunit.py", line 370, in
assertFileEqualsBaseline
baseline + "\nDiffs:\n" + diffs)
AssertionError: Unexpected output difference at line 1:
testfile=/<>/doc/workflow/examples/driver_3.out
baseline=/<>/doc/workflow/examples/driver_3.txt
Diffs:
--- /<>/doc/workflow/examples/driver_3.txt
+++ /<>/doc/workflow/examples/driver_3.out
@@ -1 +1 @@
-usage: myprog [-h] {TaskY,TaskZ} ...
+/<>/doc/workflow/examples/driver_3.sh: 4: python: not found
--
Ran 576 tests in 10.308s
FAILED (SKIP=38, errors=3, failures=26)
Bug#949731: qemu: VE-2020-1711: block: iscsi: OOB heap access via an unexpected response of iSCSI Server
Source: qemu Version: 1:4.2-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg05535.html Hi, The following vulnerability was published for qemu. CVE-2020-1711[0]: | block: iscsi: OOB heap access via an unexpected response of iSCSI | Server 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-2020-1711 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1711 [1] https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg05535.html [2] https://www.openwall.com/lists/oss-security/2020/01/23/3 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1794290 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
