Bug#951806: ruby-serverengine: FTBFS aginst Ruby2.5 and Ruby2.7
Hi, I've investigated it and it seems that failure happens with ruby-rspec 3.9.0c1e0m1s2-1, not 3.8.0c0e1m0s0-1 in buster. > Just FTR, this package has no reverse-dependencies or > reverse-build-dependencies. Is it a good sign for it to be filed for > removal? No, fluentd needs it (ITPed as https://bugs.debian.org/926692 ) -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#953342: src:oz: fails to migrate to testing for too long
Source: oz Version: 0.17.0-1 Severity: serious Control: fixed -1 0.17.0-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:oz in its current version in unstable has been trying to migrate for 195 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Bug#953341: src:rust-no-panic: fails to migrate to testing for too long
Source: rust-no-panic Version: 0.1.6-1 Severity: serious Control: fixed -1 0.1.11-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:rust-no-panic in its current version in unstable has been trying to migrate for 195 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Bug#953344: src:colord: fails to migrate to testing for too long
Source: colord Version: 1.4.3-4 Severity: serious Control: fixed -1 1.4.4-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:colord in its current version in unstable has been trying to migrate for 193 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:colord: fails to migrate to testing for too long
Processing control commands: > fixed -1 1.4.4-1 Bug #953344 [src:colord] src:colord: fails to migrate to testing for too long Marked as fixed in versions colord/1.4.4-1. -- 953344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:rust-no-panic: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.1.11-1 Bug #953341 [src:rust-no-panic] src:rust-no-panic: fails to migrate to testing for too long Marked as fixed in versions rust-no-panic/0.1.11-1. -- 953341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 950840 in 3.0.3-1
Processing commands for cont...@bugs.debian.org: > found 950840 3.0.3-1 Bug #950840 [lxc-templates] English India selected during installation breaks locale in lxc Marked as found in versions lxc-templates/3.0.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 950840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:oz: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.17.0-2 Bug #953342 [src:oz] src:oz: fails to migrate to testing for too long Marked as fixed in versions oz/0.17.0-2. -- 953342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:gengetopt: fails to migrate to testing for too long
Processing control commands: > fixed -1 2.22.6+dfsg0-4 Bug #953343 [src:gengetopt] src:gengetopt: fails to migrate to testing for too long Marked as fixed in versions gengetopt/2.22.6+dfsg0-4. -- 953343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953343: src:gengetopt: fails to migrate to testing for too long
Source: gengetopt Version: 2.22.6+dfsg0-3 Severity: serious Control: fixed -1 2.22.6+dfsg0-4 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:gengetopt in its current version in unstable has been trying to migrate for 195 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:rust-proc-macro-hack: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.5.9-1 Bug #953340 [src:rust-proc-macro-hack] src:rust-proc-macro-hack: fails to migrate to testing for too long Marked as fixed in versions rust-proc-macro-hack/0.5.9-1. -- 953340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953340: src:rust-proc-macro-hack: fails to migrate to testing for too long
Source: rust-proc-macro-hack Version: 0.5.7-2 Severity: serious Control: fixed -1 0.5.9-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:rust-proc-macro-hack in its current version in unstable has been trying to migrate for 195 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:rust-strum-macros: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.15.0-3 Bug #953339 [src:rust-strum-macros] src:rust-strum-macros: fails to migrate to testing for too long Marked as fixed in versions rust-strum-macros/0.15.0-3. -- 953339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:libhibernate-validator-java: fails to migrate to testing for too long
Processing control commands: > fixed -1 5.3.6-1 Bug #953338 [src:libhibernate-validator-java] src:libhibernate-validator-java: fails to migrate to testing for too long Marked as fixed in versions libhibernate-validator-java/5.3.6-1. -- 953338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953339: src:rust-strum-macros: fails to migrate to testing for too long
Source: rust-strum-macros Version: 0.15.0-2 Severity: serious Control: fixed -1 0.15.0-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:rust-strum-macros in its current version in unstable has been trying to migrate for 195 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Bug#953338: src:libhibernate-validator-java: fails to migrate to testing for too long
Source: libhibernate-validator-java Version: 4.3.4-1 Severity: serious Control: fixed -1 5.3.6-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:libhibernate-validator-java in its current version in unstable has been trying to migrate for 198 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:datalad-container: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.5.0-1 Bug #953337 [src:datalad-container] src:datalad-container: fails to migrate to testing for too long Marked as fixed in versions datalad-container/0.5.0-1. -- 953337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953337: src:datalad-container: fails to migrate to testing for too long
Source: datalad-container Version: 0.2.2-2 Severity: serious Control: fixed -1 0.5.0-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:datalad-container in its current version in unstable has been trying to migrate for 207 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Bug#953336: src:android-platform-build: fails to migrate to testing for too long
Source: android-platform-build Version: 1:8.1.0+r23-2 Severity: serious Control: fixed -1 1:8.1.0+r23-3 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:android-platform-build in its current version in unstable has been trying to migrate for 220 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:android-platform-build: fails to migrate to testing for too long
Processing control commands: > fixed -1 1:8.1.0+r23-3 Bug #953336 [src:android-platform-build] src:android-platform-build: fails to migrate to testing for too long Marked as fixed in versions android-platform-build/1:8.1.0+r23-3. -- 953336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953086:
Just commenting to confirm -- I am also having this problem after upgrading from Buster to Sid. The package failed to upgrade and is unusable.
Processed: more information
Processing commands for cont...@bugs.debian.org: > severity 952896 normal Bug #952896 [kmail] kmail: message body section of kmail flickers rapidly and displays no content Severity set to 'normal' from 'critical' > reassign 952896 libqt5webenginecore5 Bug #952896 [kmail] kmail: message body section of kmail flickers rapidly and displays no content Bug reassigned from package 'kmail' to 'libqt5webenginecore5'. No longer marked as found in versions kmail/4:19.08.3-1. Ignoring request to alter fixed versions of bug #952896 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 952896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947578: marked as done (FTBFS with scons 3.1.2-1)
Your message dated Sun, 08 Mar 2020 01:19:47 + with message-id and subject line Bug#947578: fixed in rafkill 1.2.2-7 has caused the Debian Bug report #947578, regarding FTBFS with scons 3.1.2-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.) -- 947578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rafkill Version: 1.2.2-6 Severity: important Usertags: scons_ftbfs Hello, in the context of the change to Python3 also Scons was revised. With the current version 3.1.2-1 from Experimental the changeover is finished so far. However, an error occurred while building your package. The build log is attached. Please check it and fix the error. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. dh clean dh_auto_clean make -j1 clean make[1]: Entering directory '/data/entwicklung/linux/debian/trans_scons/rafkill-1.2.2' scons -c scons: Reading SConscript files ... Use 'scons -h' for help NameError: name 'Options' is not defined: File "/data/entwicklung/linux/debian/trans_scons/rafkill-1.2.2/SConstruct", line 22: opts = Options( 'rafkill.conf' ) make[1]: *** [Makefile:8: clean] Error 2 make[1]: Leaving directory '/data/entwicklung/linux/debian/trans_scons/rafkill-1.2.2' dh_auto_clean: make -j1 clean returned exit code 2 make: *** [debian/rules:4: clean] Error 255 signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: rafkill Source-Version: 1.2.2-7 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of rafkill, 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. Håvard Flaget Aasen (supplier of updated rafkill 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 Mar 2020 21:19:37 +0100 Source: rafkill Architecture: source Version: 1.2.2-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard Flaget Aasen Closes: 947578 Changes: rafkill (1.2.2-7) unstable; urgency=medium . * QA upload. * d/control - Update Standards-Version to 4.5.0 - Change to debhelper-compat - Bump debhelper to 12 - Remove outdated Vcs-* fields - Wrap and sort build-dependencies - Remove duplicated section field - Add Rules-Requires-Root: no * d/copyright - Use secure URI * Add 106_scons_python3_patch closes: # 947578 Checksums-Sha1: 110cdd7051e6c7913c43946348c1ab47f183db9f 1815 rafkill_1.2.2-7.dsc 81caa834a7e4e2ca80d2902c5fb4fe3b4b8939ed 11912 rafkill_1.2.2-7.debian.tar.xz 16546735dc624d98c028d290c145a78e0d3022c2 6878 rafkill_1.2.2-7_source.buildinfo Checksums-Sha256: 4905ad1a8a48dbba9daf718bdd6d9925df6e643205b57361165afb0c08c935b2 1815 rafkill_1.2.2-7.dsc f367f0f4f54f31e989e373b892449a7f7b8800c21e0503439aaec88058b3d431 11912 rafkill_1.2.2-7.debian.tar.xz 8731ecc4b2cc026eaa42f6e94af7e9ab7b477c9f125483e25b2842de96084f5e 6878 rafkill_1.2.2-7_source.buildinfo Files: eec4ad1ce2cc0f2cd81dd901826de574 1815 games optional rafkill_1.2.2-7.dsc 87d58d09dcd6c52a2b0985c353cb4ddd 11912 games optional rafkill_1.2.2-7.debian.tar.xz bd522b0b0a7fdc2a308447822417c6f2 6878 games optional rafkill_1.2.2-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl5kQ0gACgkQweDZLphv fH4zqxAAul+OY0jVCmfuNOHtYzDUOf8UVuPSAKAV/3gdpJRB3bq9+k3F+L4pnQ0Y Zl+eGBJOssawCea5joCa2/Cbaz/p/Xf5k8D1CQGjUx52W6I6pk0DcVTaFLY1x58/ V0Owmmz1BHXRxjmiYik6QefuqN96l9bkbzuv5hKWEY2kUr3ZxtNlxXAPJpemgRPG 7iK4NC6lItvN4iirkdlBg/r4AoGXBXoXhdIozivGwtn6/hY84x31Gd
Bug#953158: sdpa: hardcoded old mumps-seq dependency
Hi, I suggest assigning this bug to mumps package. Best regards, Nobuhiro On Fri, Mar 06, 2020 at 12:07:48AM +0900, Makoto Yamashita wrote: > Dear Gianfranco Costamagna, > > Thank you very much for checking our package. > Unfortunately, it is outside of this package, and we cannot do anything for > your comment, > so please close this bug. > > Thanks. > Makoto > > > > 2020年3月5日(木) 21:15 Gianfranco Costamagna : > > > Source: sdpa > > Version: 7.3.12+dfsg-1 > > Severity: serious > > > > Hello, hardcoding the mumps library as runtime dependency breaks binNMUs, > > and it is actually keeping your package out from testing. > > > > Please let shlibs find the dependency if required, or if needed but not > > linked, ask mumps people to add a virtual provide for the runtime > > dependency, so it won't break on next binNMU. > > > > thanks > > > > Gianfranco > >
Bug#952782: marked as done (python-dnspython: Python 2 binary should not be released with bullseye)
Your message dated Sun, 08 Mar 2020 01:04:44 + with message-id and subject line Bug#952782: fixed in dnspython 1.16.0-2 has caused the Debian Bug report #952782, regarding python-dnspython: Python 2 binary should not be released with 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.) -- 952782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-dnspython Version: 1.16.0-1 Severity: serious As the primary maintianer of dnspython, I don't think it is suitable to leave with a python2 binary for the bullseye release. Scott K --- End Message --- --- Begin Message --- Source: dnspython Source-Version: 1.16.0-2 Done: Scott Kitterman We believe that the bug you reported is fixed in the latest version of dnspython, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated dnspython 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, 07 Mar 2020 19:31:03 -0500 Source: dnspython Architecture: source Version: 1.16.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Scott Kitterman Closes: 936427 952782 Changes: dnspython (1.16.0-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Scott Kitterman ] * Drop python2 support (Closes: #952782, #936427) * Bump standards-version to 4.5.0 without further change * Bump debhelper-compat to 12 without further change * Drop ancient python3-all version requirements * Add missing Depends on netbase * Add Recommends for python3-pycryptodome, python3-ecdsa, python3-idna to support DNSSEC and modern DNS with IDNA capabilities * Add autopkgtests using upstream test suite * Include README.md in package Checksums-Sha1: 4345c968f44ffcf173bfddef557c19628517dcdc 2221 dnspython_1.16.0-2.dsc e1d82146f302ee4466822fb6721317f07d2d3d08 4652 dnspython_1.16.0-2.debian.tar.xz de809c1288fd0486da1e322595754b210f41d873 6045 dnspython_1.16.0-2_source.buildinfo Checksums-Sha256: f740a50515a9fa6e0652e644b0ec7ef164652264f0e3af66a0a291fa4000873f 2221 dnspython_1.16.0-2.dsc 7881fdcfb9660ba7ae17645f38212374661f437c9db187d23234f1a4922d6265 4652 dnspython_1.16.0-2.debian.tar.xz 0793dade6a32fbb429970f54d99f8b7f7386b161a0cdffd7fac9c509c191c2b0 6045 dnspython_1.16.0-2_source.buildinfo Files: 96f726def805e4c21bfa6594d75181a5 2221 python optional dnspython_1.16.0-2.dsc 69b2e30ab9237f14c66e51731107a25c 4652 python optional dnspython_1.16.0-2.debian.tar.xz be058c21933a7e36d2b7ce611ab58eca 6045 python optional dnspython_1.16.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl5kPv0ACgkQeNfe+5rV mvFErg/+LgMNIMksub8v+t7bxKpm2uscxMU0t4DWVl83BkCodMohw+S9X1txuYJm V7bEKe/LV6Biu42IBo6GSQnqKv4vsMsGZ9dlGdFiiiuxKpGcHDFjluxiabHOyrh+ RPSImrFxXL49ZKCOrPUGGSN80zlHlwgqXJuEDxFyN+IdgjKbdMAvA6BSRbpLuI9L UfWTNhA1A3nXCJpP8DuEGjDYPvUnHzSFRrLQq5wbGDXbk46fqPeF7Msa+ShcxCZc Pi3VQasoPkTDADa/PIl5UrvEYiEIZf7D0ZS72tvhMaXImtGoH6YWLhB4ohHaI29Z 8A7BF1s0yJNk41GhzdrdFZiPGV9AJEI8KzRstT/yLXNyRlkKGaQGwMmeUJcl/bAK V/cqYqmlrjh4C8wAB5AsXxYJ0YqFFlc4iNNCvvATYwKPpzjYj/1SfZKoogAl7WRT nFI38ZfP5PgnBIhP4qkZOL6hB//rvvovS/k7L0/jwcG/WfEN8rynYJo8mU+IhsC1 fwZvDyjRtloNCaQEoBHXFozC0IEUH2iaq8P4SLmXjEKZ5c628Vk0Kqx6pgdHXB1e fSyrWKQ7pY/fcvZehNjCRZpNIB2wWgpeM1yWh5gKmTfoXOqXNB/eSFgv3uiJY+wI bO3VPZ1Log5qO8ItAUUkdBLU6COgpR8h2rzgplrQF77uyJq0Jto= =wJPD -END PGP SIGNATURE End Message ---
Bug#952009: marked as done (c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant)
Your message dated Sun, 08 Mar 2020 00:34:21 + with message-id and subject line Bug#952009: fixed in c-icap-modules 1:0.5.4-1 has caused the Debian Bug report #952009, regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant 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.) -- 952009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: c-icap-modules Version: 1:0.5.3-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE > -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall > -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module > -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath > /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo > libtool: link: gcc -shared -fPIC -DPIC .libs/clamd_mod_la-clamd_mod.o-g > -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro > -Wl,-z -Wl,now -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so > In file included from /usr/include/clamav.h:69, > from clamav_mod.c:27: > clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant > 108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE]; > | ^~ > clamav_mod.c: In function ‘clamav_set_versions’: > clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’ > 645 | CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0'; > | ^~ > make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: c-icap-modules Source-Version: 1:0.5.4-1 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of c-icap-modules, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated c-icap-modules 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 Mar 2020 15:59:45 +0100 Source: c-icap-modules Architecture: source Version: 1:0.5.4-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard Flaget Aasen Closes: 952009 Changes: c-icap-modules (1:0.5.4-1) unstable; urgency=medium . * QA upload. [ Debian Janitor ] * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. . [ Håvard Flaget Aasen ] * New upstream version 0.5.4 fix in upstream version closes: #952009 * Update Standards-Version to 4.5.0 * Remove libltdl3-dev as build-dependency * Disable autopkgtest which needs internet access * d/tests/toolbox.sh, add sleep before reading pid file Checksums-Sha1: 4739fea338e24251283ba1ea0bd2950b4aff4058 2167 c-icap-modules_0.5.4-1.dsc ec7bb138d7775895cd8b2e12adc41dbf48eba1b7 450411 c-icap-modules_0.5.4.orig.tar.gz 9be737a527b672ed02d6990826b0c4aa4c6f8ecb 6004 c-icap-modules_0.5.4-1.debian.tar.xz 4cf2348b748eb42d7f879d25941d904d18eb96f1 6615 c-icap-modules_0.5.4-1_source.buildinfo Checksums-Sha256: b486f19689067e3d575421450be71bfcedd6a7ff80a219afc
Processed: block 874915 with 872788
Processing commands for cont...@bugs.debian.org: > block 874915 with 872788 Bug #874915 [src:heimdall-flash] [heimdall-flash] Future Qt4 removal from Buster 874915 was not blocked by any bugs. 874915 was not blocking any bugs. Added blocking bug(s) of 874915: 872788 > thanks Stopping processing here. Please contact me if you need assistance. -- 874915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#952782 marked as pending in dnspython
Processing control commands: > tag -1 pending Bug #952782 [python-dnspython] python-dnspython: Python 2 binary should not be released with bullseye Added tag(s) pending. -- 952782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952782: marked as pending in dnspython
Control: tag -1 pending Hello, Bug #952782 in dnspython 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/dnspython/-/commit/f7d06bcc673b23554cdb81943c8a52a3e8b89ca8 Drop python2 support (Closes: #952782, #936427) (this message was generated automatically) -- Greetings https://bugs.debian.org/952782
Bug#927136: marked as done (src:zabbix-cli: Please update to python3)
Your message dated Sat, 07 Mar 2020 23:24:48 + with message-id and subject line Bug#953307: Removed package(s) from unstable has caused the Debian Bug report #927136, regarding src:zabbix-cli: Please update to 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.) -- 927136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:zabbix-cli Version: 1.7.0-1 Severity: important Python2.7 will go out of upstream security support during the Bullseye development cycle. It is not safe to assume it will be included in the next release, so if you want to be sure zabbix-cli can stay in Debian, please update it to the python3 version available from upstream.. Personally, I want to remove some packages I maintain, particularly python- ipaddr, which zabbix-cli depends on during the Bullseye cycle, regardless of what happens to python2.7, so please update (python3 includes the ipaddress module, which was developed from ipaddr, in the standard library). --- End Message --- --- Begin Message --- Version: 1.7.0-1+rm Dear submitter, as the package zabbix-cli has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/953307 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938877: marked as done (zabbix-cli: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Mar 2020 23:24:48 + with message-id and subject line Bug#953307: Removed package(s) from unstable has caused the Debian Bug report #938877, regarding zabbix-cli: 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.) -- 938877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:zabbix-cli Version: 1.7.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:zabbix-cli 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 --- Version: 1.7.0-1+rm Dear submitter, as the package zabbix-cli has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/953307 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#936172: marked as done (autotrash: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Mar 2020 23:25:51 + with message-id and subject line Bug#953309: Removed package(s) from unstable has caused the Debian Bug report #936172, regarding autotrash: 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.) -- 936172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:autotrash Version: 0.1.5-1.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:autotrash 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 --- Version: 0.1.5-1.1+rm Dear submitter, as the package autotrash has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/953309 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#866965: marked as done (dosemu: DPMI unhandled exception instability back again)
Your message dated Sat, 07 Mar 2020 23:22:46 + with message-id and subject line Bug#953284: Removed package(s) from unstable has caused the Debian Bug report #866965, regarding dosemu: DPMI unhandled exception instability back again 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.) -- 866965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dosemu Version: 1.4.0.7+2013 Severity: grave Justification: renders package unusable Identical symptoms were reported in https://bugs.debian.org/797378, but they're back again. That report stated that the problem was in the Linux kernel and was fixed in Linux 4.2-rc7. I'm running kernel 4.9.x, as installed from the Stretch repos. What's going on this time? -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.15-x86_64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages dosemu depends on: pn libasound2 ii libc62.24-11+deb9u1 ii libgpm2 1.20.4-6.2+b1 pn libsdl1.2debian ii libslang22.3.1-5 pn libsndfile1 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 pn libxxf86vm1 pn xfonts-utils dosemu recommends no packages. dosemu suggests no packages. --- End Message --- --- Begin Message --- Version: 1.4.0.7+20130105+b028d3f-2+rm Dear submitter, as the package dosemu has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/953284 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#800450: marked as done (jirc: missing perl module POE::Filter::XML::Utils, no longer provided by libpoe-filter-xml-perl)
Your message dated Sat, 07 Mar 2020 23:21:36 + with message-id and subject line Bug#953282: Removed package(s) from unstable has caused the Debian Bug report #800450, regarding jirc: missing perl module POE::Filter::XML::Utils, no longer provided by libpoe-filter-xml-perl 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.) -- 800450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jirc Version: 1.0-1 Severity: important Dear Maintainer, installing jirc on a jessie system and trying to start results in $ jirc --help given is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 140. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 142. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 147. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 152. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 159. given is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 161. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 163. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 171. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 176. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 190. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 231. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 236. given is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 254. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 256. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 280. given is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 285. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 287. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 296. given is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 332. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 334. when is experimental at /usr/share/perl5/POE/Component/Jabber/XMPP.pm line 341. given is experimental at /usr/share/perl5/POE/Component/Jabber/Legacy.pm line 79. when is experimental at /usr/share/perl5/POE/Component/Jabber/Legacy.pm line 81. when is experimental at /usr/share/perl5/POE/Component/Jabber/Legacy.pm line 88. given is experimental at /usr/share/perl5/POE/Component/Jabber/Legacy.pm line 90. when is experimental at /usr/share/perl5/POE/Component/Jabber/Legacy.pm line 92. when is experimental at /usr/share/perl5/POE/Component/Jabber/Legacy.pm line 99. when is experimental at /usr/share/perl5/POE/Component/Jabber/J14.pm line 65. given is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 132. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 134. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 140. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 146. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 161. given is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 163. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 165. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 173. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 184. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 198. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 228. when is experimental at /usr/share/perl5/POE/Component/Jabber/J2.pm line 234. given is experimental at /usr/share/perl5/POE/Component/Jabber.pm line 836. when is experimental at /usr/share/perl5/POE/Component/Jabber.pm line 838. when is experimental at /usr/share/perl5/POE/Component/Jabber.pm line 850. Can't locate POE/Filter/XML/Utils.pm in @INC (you may need to install the POE::Filter::XML::Utils module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /usr/bin/jirc line 46. BEGIN failed--compilation aborted at /usr/bin/jirc line 46. The "experimental" warnings are just annoying, but there is apparently no package providing POE::Filter::XML::Utils in Jessie. -- Syst
Bug#932386: marked as done (mythtvfs: Package obsolete and redundant)
Your message dated Sat, 07 Mar 2020 23:22:10 + with message-id and subject line Bug#953283: Removed package(s) from unstable has caused the Debian Bug report #932386, regarding mythtvfs: Package obsolete and redundant 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.) -- 932386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mythtvfs Version: 0.6.1-3+b2 Severity: serious Dear Maintainer, It' an obsolute utility for a package, which is not available from official Debian repositories. Best regards Janusz On Thu, Jul 11 2019 at 21:30 +02, Christian Marillat wrote: > On 11 juil. 2019 21:04, jsb...@mimuw.edu.pl (Janusz S. Bień) wrote: > > [...] > >> BTW, is mythtvfs supposed to work? My attempt to use it failed > > mythtvvfs isn't a package from my repository. > > Otherwise this package is 10 years old and the latest mythtv protocol > supported is 50 : > > http://outflux.net/software/pkgs/mythtvfs-fuse/ > > The latest protocol version is 91 : > > https://www.mythtv.org/wiki/Category:Myth_Protocol -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mythtvfs depends on: ii fuse 2.9.9-1 ii libc6 2.28-10 ii libfuse2 2.9.9-1 ii libglib2.0-0 2.58.3-2 mythtvfs recommends no packages. mythtvfs suggests no packages. -- no debconf information -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien --- End Message --- --- Begin Message --- Version: 0.6.1-3+rm Dear submitter, as the package mythtvfs-fuse has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/953283 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#925784: marked as done (mythtvfs-fuse: ftbfs with GCC-9)
Your message dated Sat, 07 Mar 2020 23:22:10 +
with message-id
and subject line Bug#953283: Removed package(s) from unstable
has caused the Debian Bug report #925784,
regarding mythtvfs-fuse: 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.)
--
925784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mythtvfs-fuse
Version: 0.6.1-3
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/mythtvfs-fuse_0.6.1-3_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.
[...]
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --parallel
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_auto_clean -O--parallel
dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
dh_clean -O--parallel
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
debian/rules build-arch
dh build-arch --parallel
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_update_autotools_config -a -O--parallel
dh_auto_configure -a -O--parallel
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libexecdir=\${prefix}/lib/mythtvfs-fuse
--disable-maintainer-mode --disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking whether gcc and cc understand -c and -o together... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for MYTHTVFS... yes
checking for pod2man... pod2man
checking for fuse_opt_parse... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-maintainer-mode
dh_auto_build -a -O--parallel
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
make -j4
make[1]: Entering directory '/<>'
make all-am
make[2]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I. -D_REENTRANT -DFUSE_USE_VERSION=26
-D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2
Bug#953331: ldb: FTBFS with Python 3.8
Source: ldb Version: 2:2.0.8-1 Severity: serious Tags: ftbfs patch Hi Maintainer ldb FTBFS on some architectures when rebuilt with Python 3.8 [1]. dpkg-gensymbols: error: new libraries appeared in the symbols file: libpyldb-util.cpython-38-x86-64-linux-gnu.so.2 dpkg-gensymbols: error: some libraries disappeared in the symbols file: libpyldb-util.cpython-37m-x86-64-linux-gnu.so.2 The attached patch fixed the problem in Ubuntu. Regards Graham [1] https://buildd.debian.org/status/package.php?p=ldb&suite=unstable diff -Nru ldb-2.0.8/debian/changelog ldb-2.0.8/debian/changelog --- ldb-2.0.8/debian/changelog 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/changelog 2020-01-27 18:12:42.0 + @@ -1,3 +1,9 @@ +ldb (2:2.0.8-1ubuntu1) focal; urgency=medium + + * d/python3-ldb.symbols*: update symbols for python 3.8 + + -- Andreas Hasenack Mon, 27 Jan 2020 15:12:42 -0300 + ldb (2:2.0.8-1) unstable; urgency=medium [ Debian Janitor ] diff -Nru ldb-2.0.8/debian/control ldb-2.0.8/debian/control --- ldb-2.0.8/debian/control 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/control 2020-01-27 18:12:42.0 + @@ -1,7 +1,8 @@ Source: ldb Section: devel Priority: optional -Maintainer: Debian Samba Maintainers +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Debian Samba Maintainers Uploaders: Jelmer Vernooij , Mathieu Parent Build-Depends: dh-exec, diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.amd64 ldb-2.0.8/debian/python3-ldb.symbols.amd64 --- ldb-2.0.8/debian/python3-ldb.symbols.amd64 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/python3-ldb.symbols.amd64 2020-01-27 18:12:42.0 + @@ -1,3 +1,3 @@ -libpyldb-util.cpython-37m-x86-64-linux-gnu.so.2 python3-ldb #MINVER# - PYLDB_UTIL.CPYTHON_37M_X86_64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_X86_64_LINUX_GNU_2.0.8 2:2.0.8 +libpyldb-util.cpython-38-x86-64-linux-gnu.so.2 python3-ldb #MINVER# + PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.0.8 2:2.0.8 #include "python3-ldb.symbols.common" diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.arm64 ldb-2.0.8/debian/python3-ldb.symbols.arm64 --- ldb-2.0.8/debian/python3-ldb.symbols.arm64 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/python3-ldb.symbols.arm64 2020-01-27 18:12:42.0 + @@ -1,3 +1,3 @@ -libpyldb-util.cpython-37m-aarch64-linux-gnu.so.2 python3-ldb #MINVER# - PYLDB_UTIL.CPYTHON_37M_AARCH64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_AARCH64_LINUX_GNU_2.0.8 2:2.0.8 +libpyldb-util.cpython-38-aarch64-linux-gnu.so.2 python3-ldb #MINVER# + PYLDB_UTIL.CPYTHON_38_AARCH64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_AARCH64_LINUX_GNU_2.0.8 2:2.0.8 #include "python3-ldb.symbols.common" diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.armhf ldb-2.0.8/debian/python3-ldb.symbols.armhf --- ldb-2.0.8/debian/python3-ldb.symbols.armhf 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/python3-ldb.symbols.armhf 2020-01-27 18:12:42.0 + @@ -1,3 +1,3 @@ -libpyldb-util.cpython-37m-arm-linux-gnueabihf.so.2 python3-ldb #MINVER# - PYLDB_UTIL.CPYTHON_37M_ARM_LINUX_GNUEABIHF_2.0.8@PYLDB_UTIL.CPYTHON_37M_ARM_LINUX_GNUEABIHF_2.0.8 2:2.0.8 +libpyldb-util.cpython-38-arm-linux-gnueabihf.so.2 python3-ldb #MINVER# + PYLDB_UTIL.CPYTHON_38_ARM_LINUX_GNUEABIHF_2.0.8@PYLDB_UTIL.CPYTHON_38_ARM_LINUX_GNUEABIHF_2.0.8 2:2.0.8 #include "python3-ldb.symbols.common" diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.i386 ldb-2.0.8/debian/python3-ldb.symbols.i386 --- ldb-2.0.8/debian/python3-ldb.symbols.i386 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/python3-ldb.symbols.i386 2020-01-27 18:12:42.0 + @@ -1,3 +1,3 @@ -libpyldb-util.cpython-37m-i386-linux-gnu.so.2 python3-ldb #MINVER# - PYLDB_UTIL.CPYTHON_37M_I386_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_I386_LINUX_GNU_2.0.8 2:2.0.8 +libpyldb-util.cpython-38-i386-linux-gnu.so.2 python3-ldb #MINVER# + PYLDB_UTIL.CPYTHON_38_I386_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_I386_LINUX_GNU_2.0.8 2:2.0.8 #include "python3-ldb.symbols.common" diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.ppc64el ldb-2.0.8/debian/python3-ldb.symbols.ppc64el --- ldb-2.0.8/debian/python3-ldb.symbols.ppc64el 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/python3-ldb.symbols.ppc64el 2020-01-27 18:12:42.0 + @@ -1,3 +1,3 @@ -libpyldb-util.cpython-37m-powerpc64le-linux-gnu.so.2 python3-ldb #MINVER# - PYLDB_UTIL.CPYTHON_37M_POWERPC64LE_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_POWERPC64LE_LINUX_GNU_2.0.8 2:2.0.8 +libpyldb-util.cpython-38-powerpc64le-linux-gnu.so.2 python3-ldb #MINVER# + PYLDB_UTIL.CPYTHON_38_POWERPC64LE_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_POWERPC64LE_LINUX_GNU_2.0.8 2:2.0.8 #include "python3-ldb.symbols.common" diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.s390x ldb-2.0.8/debian/python3-ldb.symbols.s390x --- ldb-2.0.8/debian/python3-ldb.symbols.s390x 2020-01-27 09:45:29.0 + +++ ldb-2.0.8/debian/python3-ldb.symbols.s390x 2020-01
Processed: tagging python3.8 ftbfs bugs
Processing commands for cont...@bugs.debian.org: > tags 953316 + ftbfs Bug #953316 [src:volume-key] volume-key: FTBFS with python3.8 Added tag(s) ftbfs. > tags 951779 + ftbfs Bug #951779 [src:pitivi] pitivi: missing libpython link? Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 951779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951779 953316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953144: origami install fails with "ERROR: WGET RETRIEVAL FAILED!"
Followup-For: Bug #953144 origami is missing a dependency on lsb-release (needed for os identification). The URL https://zelut.org/projects/misc/finstall is no longer available and causes the reported error. There is no validation (e.g. hash/signature checking) on the downloaded bits, which contain code to be executed ... BTW, as a downloader package, why isn't this in contrib? Andreas
Processed: tagging 953243, tagging 930663, tagging 930673, tagging 931133, found 953308 in 3.0.4-1 ...
Processing commands for cont...@bugs.debian.org: > tags 953243 + sid bullseye Bug #953243 [ssh-import-id] ssh-import-id: Fails with Python 3.8 Added tag(s) sid and bullseye. > tags 930663 + sid bullseye Bug #930663 [apt-move] apt-move: Port to apt 1.9 Added tag(s) bullseye and sid. > tags 930673 + sid bullseye Bug #930673 [openscap] openscap: Port to apt 1.9.0 Added tag(s) bullseye and sid. > tags 931133 + sid bullseye Bug #931133 [apt-xapian-index] apt-xapian-index: unusable after recent python-apt update due to usage of deprecated Package.section attribute Added tag(s) sid and bullseye. > found 953308 3.0.4-1 Bug #953308 [src:libqapt] libqapt: Port to apt 1.9.0 and apt 1.9.11 changes Marked as found in versions libqapt/3.0.4-1. > tags 953308 + sid bullseye Bug #953308 [src:libqapt] libqapt: Port to apt 1.9.0 and apt 1.9.11 changes Added tag(s) sid and bullseye. > found 953311 0.90 Bug #953311 [synaptic] synaptic: Port to apt 1.9.11 Marked as found in versions synaptic/0.90. > notfound 953311 0.84.6ubuntu3 Bug #953311 [synaptic] synaptic: Port to apt 1.9.11 There is no source info for the package 'synaptic' at version '0.84.6ubuntu3' with architecture '' Unable to make a source version for version '0.84.6ubuntu3' No longer marked as found in versions 0.84.6ubuntu3. > fixed 953215 8.0-3 Bug #953215 [libreadline-dev] [libreadline-dev] libreadline-dev in stable lacks a .pc file for pkg-config Marked as fixed in versions readline/8.0-3. > notfound 953215 7.0.5 Bug #953215 [libreadline-dev] [libreadline-dev] libreadline-dev in stable lacks a .pc file for pkg-config There is no source info for the package 'libreadline-dev' at version '7.0.5' with architecture '' Unable to make a source version for version '7.0.5' No longer marked as found in versions 7.0.5. > found 953215 7.0-3 Bug #953215 [libreadline-dev] [libreadline-dev] libreadline-dev in stable lacks a .pc file for pkg-config Marked as found in versions readline/7.0-3. > severity 953215 important Bug #953215 [libreadline-dev] [libreadline-dev] libreadline-dev in stable lacks a .pc file for pkg-config Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 930663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930663 930673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930673 931133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931133 953215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953215 953243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953243 953308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953308 953311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: wireless-tools: diff for NMU version 30~pre9-13.1
Processing control commands: > tags 925857 + pending Bug #925857 [src:wireless-tools] wireless-tools: ftbfs with GCC-9 Added tag(s) pending. -- 925857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925857: wireless-tools: diff for NMU version 30~pre9-13.1
Control: tags 925857 + pending Dear maintainer, I've prepared an NMU for wireless-tools (versioned as 30~pre9-13.1) and uploaded it to mentor for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru wireless-tools-30~pre9/debian/changelog wireless-tools-30~pre9/debian/changelog --- wireless-tools-30~pre9/debian/changelog 2018-09-15 15:35:08.0 +0100 +++ wireless-tools-30~pre9/debian/changelog 2020-03-07 20:59:05.0 + @@ -1,3 +1,11 @@ +wireless-tools (30~pre9-13.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs. (Closes: #925857) +- Thanks Reiner Herrmann. + + -- Sudip Mukherjee Sat, 07 Mar 2020 20:59:05 + + wireless-tools (30~pre9-13) unstable; urgency=medium * Call /sbin/ip instead of ifconfg in if-pre-up script. (Closes: 908886) diff -Nru wireless-tools-30~pre9/debian/patches/gcc9.patch wireless-tools-30~pre9/debian/patches/gcc9.patch --- wireless-tools-30~pre9/debian/patches/gcc9.patch1970-01-01 01:00:00.0 +0100 +++ wireless-tools-30~pre9/debian/patches/gcc9.patch2020-03-07 20:59:05.0 + @@ -0,0 +1,15 @@ +Author: Reiner Herrmann +Description: Fix build with gcc9 by moving linked libraries to the end +Bug-Debian: https://bugs.debian.org/925857 + +--- a/Makefile b/Makefile +@@ -150,7 +150,7 @@ + + # Compilation of the dynamic library + $(DYNAMIC): $(OBJS:.o=.so) +- $(CC) -shared -o $@ -Wl,-soname,$@ $(STRIPFLAGS) $(LIBS) $(LDFLAGS) -lc $^ ++ $(CC) -shared -o $@ -Wl,-soname,$@ $(STRIPFLAGS) $(LDFLAGS) $^ -lc $(LIBS) + + # Compilation of the static library + $(STATIC): $(OBJS:.o=.so) diff -Nru wireless-tools-30~pre9/debian/patches/series wireless-tools-30~pre9/debian/patches/series --- wireless-tools-30~pre9/debian/patches/series2018-06-05 20:29:11.0 +0100 +++ wireless-tools-30~pre9/debian/patches/series2020-03-07 20:59:05.0 + @@ -5,3 +5,4 @@ add-import-type-to-udev-rules fix-typos improve-make-install +gcc9.patch
Bug#951884: marked as done (binutils-arm-none-eabi FTBFS: error: invalid or non-existing path to the source directory)
Your message dated Sat, 07 Mar 2020 12:10:14 -0800 with message-id <87tv30yli1@keithp.org> and subject line Close bug 951884 has caused the Debian Bug report #951884, regarding binutils-arm-none-eabi FTBFS: error: invalid or non-existing path to the source directory 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.) -- 951884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-arm-none-eabi Version: 13 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/binutils-arm-none-eabi.html ... dh_auto_configure -Dbinutils-2.34-2 -Bbuild -- --target=arm-none-eabi --prefix=/usr/lib --bindir=/usr/bin --libdir=/usr/lib/arm-none-eabi --infodir=/usr/share/doc/binutils-arm-none-eabi/info --htmldir=/usr/share/doc/binutils-arm-none-eabi/html --pdfdir=/usr/share/doc/binutils-arm-none-eabi/pdf --mandir=/usr/share/man --disable-nls --disable-werror --enable-plugins --enable-interwork --with-system-zlib "--with-pkgversion=2.34-2+13" CFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong -Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong -Wformat -Werror=format-security" FCFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong" FFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong" GCJFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong" LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2 -ffile-prefix-map=/build/1st/binutils-arm-none-eabi-13=. -fstack-protector-strong -Wformat -Werror=format-security" dh_auto_configure: error: invalid or non-existing path to the source directory: binutils-2.34-2 make[1]: *** [debian/rules:51: override_dh_auto_configure] Error 25 --- End Message --- --- Begin Message --- Source: binutils-arm-none-eabi Version: 14 Handle new binutils source -- -keith signature.asc Description: PGP signature --- End Message ---
Bug#953326: axtls: CVE-2019-9689 CVE-2019-10013
Source: axtls Version: 2.1.5+ds-1 Severity: grave Tags: security upstream Hi, The following vulnerabilities were published for axtls. CVE-2019-9689[0]: | process_certificate in tls1.c in Cameron Hamilton-Rich axTLS through | 2.1.5 has a Buffer Overflow via a crafted TLS certificate handshake | message with zero certificates. CVE-2019-10013[1]: | The asn1_signature function in asn1.c in Cameron Hamilton-Rich axTLS | through 2.1.5 has a Buffer Overflow that allows remote attackers to | cause a denial of service (memory and CPU consumption) via a crafted | certificate in the TLS certificate handshake message, because the | result of get_asn1_length() is not checked for a minimum or maximum | size. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-9689 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9689 [1] https://security-tracker.debian.org/tracker/CVE-2019-10013 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10013 [2] https://seclists.org/bugtraq/2019/Nov/44 Regards, Salvatore
Processed: Re: garagemq: autopkgtest failure: github.com/valinurovam/garagemq/srvstorage [no test files]
Processing control commands: > tags -1 + help Bug #953227 [src:garagemq] garagemq: autopkgtest failure: github.com/valinurovam/garagemq/srvstorage [no test files] Added tag(s) help. -- 953227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953227: garagemq: autopkgtest failure: github.com/valinurovam/garagemq/srvstorage [no test files]
Control: tags -1 + help Hello Paul Gevers, Thanks for your bug report. On Fri, Mar 06, 2020 at 09:25:22AM +0100, Paul Gevers wrote: > Source: garagemq > Version: 0.0~git20200204.15e6a9d+ds-1 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: fails-always > > Dear maintainers, > > Your new pacakge garagemq has an autopkgtest, great. However, it fails > on amd64 (but passes on arm64). I copied some of the output at the > bottom of this report. > > Currently this regression is blocking the migration to testing [1]. Can > you please investigate the situation and fix it? Sorry, but I have no idea what's going on here. Some reflections: a/ I can't spot any test that's actually failing! (They all seem to report PASS.) Yet somehow the exit code is 1. b/ I can *sometimes* reproduce the problem locally, but need a few things to trigger it: - test cache must be disabled - output must be to terminal (not redirected to file or piped) When running the tests like this I can trigger the problem 50% of the time: go test -count=1 -vet=off -v -p 2 github.com/valinurovam/garagemq/server (Note the '-count=1' to disable test cache.) Somehow something seems racy, but I don't know at all where to look (as I can't see one particular test actually fail). (I also have no particular knowledge about the go debhelper that hooks up the go tests to autopkgtest.) > > 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=garagemq > > https://ci.debian.net/data/autopkgtest/testing/amd64/g/garagemq/4442139/log.gz > > === RUN Test_QueueDelete_Failed_QueueNotExists > badger 2020/03/03 04:17:38 INFO: All 0 tables opened in 0s > badger 2020/03/03 04:18:07 INFO: All 0 tables opened in 0s > FAIL github.com/valinurovam/garagemq/server 182.668s > ? github.com/valinurovam/garagemq/srvstorage [no test files] > ? github.com/valinurovam/garagemq/storage [no test files] > FAIL > dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 > github.com/valinurovam/garagemq github.com/valinurovam/garagemq/admin > github.com/valinurovam/garagemq/amqp > github.com/valinurovam/garagemq/auth > github.com/valinurovam/garagemq/binding > github.com/valinurovam/garagemq/config > github.com/valinurovam/garagemq/consumer > github.com/valinurovam/garagemq/exchange > github.com/valinurovam/garagemq/interfaces > github.com/valinurovam/garagemq/metrics > github.com/valinurovam/garagemq/msgstorage > github.com/valinurovam/garagemq/pool > github.com/valinurovam/garagemq/protocol > github.com/valinurovam/garagemq/qos > github.com/valinurovam/garagemq/queue > github.com/valinurovam/garagemq/safequeue > github.com/valinurovam/garagemq/server > github.com/valinurovam/garagemq/srvstorage > github.com/valinurovam/garagemq/storage returned exit code 1 > make: *** [debian/rules:4: build] Error 25 > autopkgtest [04:18:31]: test dh-golang-autopkgtest: ---] > Regards, Andreas Henriksson
Bug#953323: src:macs: fails to migrate to testing for too long
Source: macs Version: 2.2.4-1 Severity: serious Control: fixed -1 2.2.6-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:macs in its current version in unstable has been trying to migrate for 69 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:macs: fails to migrate to testing for too long
Processing control commands: > fixed -1 2.2.6-3 Bug #953323 [src:macs] src:macs: fails to migrate to testing for too long Marked as fixed in versions macs/2.2.6-3. -- 953323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:changeo: fails to migrate to testing for too long
Processing control commands: > fixed -1 0.4.6-1 Bug #953321 [src:changeo] src:changeo: fails to migrate to testing for too long Marked as fixed in versions changeo/0.4.6-1. -- 953321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:sec: fails to migrate to testing for too long
Processing control commands: > fixed -1 2.8.2-1 Bug #953322 [src:sec] src:sec: fails to migrate to testing for too long Marked as fixed in versions sec/2.8.2-1. -- 953322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953322: src:sec: fails to migrate to testing for too long
Source: sec Version: 2.8.1-1 Severity: serious Control: fixed -1 2.8.2-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:sec in its current version in unstable has been trying to migrate for 219 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Bug#953320: src:python-sievelib: fails to migrate to testing for too long
Source: python-sievelib Version: 1.1.0-1 Severity: serious Control: fixed -1 1.1.1-3 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:python-sievelib in its current version in unstable has been trying to migrate for 225 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Bug#953321: src:changeo: fails to migrate to testing for too long
Source: changeo Version: 0.4.5-1 Severity: serious Control: fixed -1 0.4.6-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:changeo in its current version in unstable has been trying to migrate for 224 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: OpenPGP digital signature
Processed: src:python-sievelib: fails to migrate to testing for too long
Processing control commands: > fixed -1 1.1.1-3 Bug #953320 [src:python-sievelib] src:python-sievelib: fails to migrate to testing for too long Marked as fixed in versions python-sievelib/1.1.1-3. -- 953320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953318: hplip: Failed to upgrade/install: dpkg-statoverride: warning: no override present
Package: hplip Severity: grave Version: 3.20.2+dfsg0-2 X-Debbugs-CC: d...@debian.org j...@debian.org m...@debian.org Dear Debian hplip maintainers, The latest version of hplip caused piuparts regression: https://piuparts.debian.org/sid/fail/hplip_3.20.2+dfsg0-2.log It also failed to install and/or upgrade on my system: [...] Setting up hplip (3.20.2+dfsg0-2) ... Creating/updating hplip user account... dpkg-statoverride: warning: no override present dpkg: error processing package hplip (--configure): installed hplip package post-installation script subprocess returned error exit status 2 [...] Please revise the changes made around dpkg-statoverride in the latest upload. Thanks! -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#953316: volume-key: FTBFS with python3.8
Source: volume-key Severity: grave Version: 0.3.12-3 X-Debbugs-CC: mp...@debian.org bi...@debian.org Dear package volume-key maintainer in Debian, Your package currently FTBFS with python3.8. Ubuntu proposed the fix in 0.3.12-2ubuntu2 and it can be considered as a solution. -- Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#951722:
Hello, This doesn't seem to be arm64 related since the same occurs on ppc64el. I've been reproducing this failure consistently by running the autopkgtest suite on a stressed host. I think that the failure appears under similar high-load circumstances on the debian ci host. dovecot-lda communicates with dovecot through the socket at /var/run/dovecot/auth-userdb but on a stressed host it's possible for dovecot-lda to call connect() before listen() is called on this socket by dovecot. By applying the suggested patch, the failure has been vanished since dovecot-lda is called only after the socket becomes ready. Regards, Mpampis diff --git a/debian/tests/control b/debian/tests/control index 7abd238c3..5bf1dc94b 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -6,5 +6,5 @@ Tests: systemd Depends: dovecot-core, systemd-sysv Test-Command: run-parts --report --exit-on-error debian/tests/usage -Depends: dovecot-imapd, dovecot-pop3d, python3 +Depends: dovecot-imapd, dovecot-pop3d, python3, netcat-openbsd Restrictions: needs-root, breaks-testbed, allow-stderr diff --git a/debian/tests/usage/00_setup b/debian/tests/usage/00_setup index 2eeeb2f73..e90ca7e92 100755 --- a/debian/tests/usage/00_setup +++ b/debian/tests/usage/00_setup @@ -29,6 +29,17 @@ chown nobody:nogroup /srv/dovecot-dep8 echo "Restarting the service" systemctl restart dovecot +echo "Waiting for the service to be available" +c=0 +while ! nc -z -U /var/run/dovecot/auth-userdb; do + c=$(($c+1)) + sleep 2 + if [ $c -gt 30 ]; then + echo "Timed out waiting for the service to be available" >&2 + exit 1 + fi +done + echo "Sending a test message via the LDA" /usr/lib/dovecot/dovecot-lda -f "t...@example.com" -d dep8 <
Bug#925630: aide: ftbfs with GCC-9
On Wed, Mar 27, 2019 at 07:44:01PM +, Matthias Klose wrote: > Package: src:aide > Version: 0.16.1-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. Is it possible to test this again? I tried to build aide_0.16.1-1 and I did not get any failure. Build Architecture: amd64 Build Type: full Build-Space: 26244 Build-Time: 31 Distribution: unstable Host Architecture: amd64 Install-Time: 37 Job: /home/sudip/debian/aide/aide_0.16.1-1.dsc Lintian: info Machine Architecture: amd64 Package: aide Package-Time: 70 Source-Version: 0.16.1-1 Space: 26244 Status: successful Version: 0.16.1-1 Did I miss something? -- Regards Sudip
Bug#953222: Bug#953223 closed by Debian FTP Masters (reply to Laszlo Boszormenyi (GCS) ) (Bug#953223: fixed in fuse3 3.9.0-2)
Hey, I'm wondering is this shouldn't be fixed in debian stable (fuse and fuse3) as well Kind regards, Laurent Bigonville Le 7/03/20 à 12:54, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the fuse3 package: #953223: Stop explicitly removing /etc/fuse.conf on purge It has been closed by Debian FTP Masters (reply to Laszlo Boszormenyi (GCS) ). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Debian FTP Masters (reply to Laszlo Boszormenyi (GCS) ) by replying to this email.
Bug#943495: Can't reproduce
severity 943495 normal thanks I was unable to reproduce a problem when building with the latest packages from Unstable. It appears to be building the Python 3.8 stuff in the cpython3_3.8 directory. I've installed the gcc package from experimental to make all the gcc links point to version 10, it still has no problems. Please tell us how to reproduce this problem and give us build logs showing the error. If "a new compiler" means something other than GCC 10 please tell us what it is. I also don't know why we would want to have this warning ignored if it happens at some future time. Why not just fix the code to have all fields initialised? Please provide build instructions for how to reproduce this issue and a rationale for using -Wno-error=missing-field-initializers instead of initialising all the fields. Please don't change the priority without explaining how this is a problem. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/
Processed: Can't reproduce
Processing commands for cont...@bugs.debian.org: > severity 943495 normal Bug #943495 [src:setools] fix building with a new compiler warning when building for python3.8 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 943495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 953311
Processing commands for cont...@bugs.debian.org: > tags 953311 + patch Bug #953311 [synaptic] synaptic: Port to apt 1.9.11 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 953311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 953308
Processing commands for cont...@bugs.debian.org: > tags 953308 + patch Bug #953308 [src:libqapt] libqapt: Port to apt 1.9.0 and apt 1.9.11 changes Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 953308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953311: synaptic: Port to apt 1.9.11
Package: synaptic Version: 0.84.6ubuntu3 Severity: serious User: de...@lists.debian.org Usertags: apt-1.9.11 Patches for apt 1.9.11 have been submitted as a pull request #49: https://github.com/mvo5/synaptic/pull/49 -- System Information: Debian Release: bullseye/sid APT prefers focal APT policy: (991, 'focal'), (500, 'focal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-17-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages synaptic depends on: ii hicolor-icon-theme 0.17-2 ii libapt-pkg5.90 1.9.10 ii libc62.30-0ubuntu3 ii libept1.5.90 1.1+nmu3ubuntu1 ii libgcc-s1 [libgcc1] 10-20200304-1ubuntu1 ii libgcc1 1:10-20200304-1ubuntu1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-2 ii libglib2.0-0 2.64.0-1 ii libgtk-3-0 3.24.13-1ubuntu1 ii libpango-1.0-0 1.44.7-1ubuntu3 ii libstdc++6 10-20200304-1ubuntu1 ii libvte-2.91-00.59.91-0ubuntu1 ii libxapian30 1.4.14-2 ii policykit-1 0.105-26ubuntu1 Versions of packages synaptic recommends: ii libgtk3-perl 0.036-1 ii xdg-utils 1.1.3-1ubuntu2 Versions of packages synaptic suggests: pn apt-xapian-index ii deborphan1.7.32 pn dwww ii menu 2.1.47ubuntu3 ii software-properties-gtk 0.98.7 ii tasksel 3.34ubuntu16 -- no debconf information -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#953308: libqapt: Port to apt 1.9.0 and apt 1.9.11 changes
Source: libqapt
Severity: serious
User: de...@lists.debian.org
Usertags: apt-1.9.11 apt-1.9.0
The attached patch series has been applied in Ubuntu to make libqapt work with
recent APT. Except for apt-1.9.11.patch, all patches are upstream:
0001-Fix-Package-supportedUntil-never-getting-the-date.patch
apt-1.9.0.patch
apt-1.9.11.patch
These patches require a Build-Depends on apt (>= 1.9.11~).
-- System Information:
Debian Release: bullseye/sid
APT prefers focal
APT policy: (991, 'focal'), (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-17-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
From: Julian Andres Klode
Date: Wed Jun 19 12:01:15 2019 +0200
Forwarded: https://phabricator.kde.org/D21896
Subject: Port to APT 1.9.0
commit ed4f360b7f2488b6712291699e5cf70c8b0207e4
Use APT::Progress::PackageManager for install progress
commit 926793a426611a1d044f8dd8bdb6e764a1cf8f7d
Use ActiveSubprocess instead of Mode
commit 27f72cae73434a1da70a7f0b68f34795a6396816
Read CurrentSize from CurrentItem rather than worker
APT 1.9.0 moves CurrentSize to items, so we use CurrentItem
for now - but that should go away so we can have multiple
current items for http/2 later.
commit 2e7d9dff47c95f7890fbb6cad497593ce9071b4a
worker: Include unistd.h for usleep()
usleep() is defined in that header, but the header is not
included.
commit 2cec444890da35646252f57dd425e979cc542cc9
Use all hashes in aptWorker when acquiring files
Seriously
commit cb19796f31c98be4c2e827da4850a0b0dec99afd
Port pkgAcquire setup to use constructor
The Setup() method went away, use the constructor instead.
commit b8d623587ec1707ac0f827788826e84c982ffab9
Port Package::md5Sum()
Probably want to export HashStringList instead
commit d0ec0481bb134dba3d04df63a2506a977dac63a1
src/package.cpp: Use candidate version's section
Packages do not really have a section, this moved to Version a few
years ago (they can differ between versions). Let's just use the
candidate's section, if there is one.
commit 912f2e7bc51208eabc1997d147bf514ab6894107
Use GetCandidateVersion() instead of GetCandidateVer()
GetCandidateVer() never actually returned the correct candidate,
so this probably also fixes something.
commit 9253eb628a9f32e3c510c243ad1c9aa67ab6a69b
Port pin writing to pkgTagSection::Write()
commit 46c91979a06f4a2977b220f939997dd946cc2040
Port to APT::Upgrade
commit 674e4e541e0ce673dcf4152f2e16af738955fedf
Use std::string instead of string
APT 1.9 drops a few "using" uses in headers, so we have to use
the namespaced name now.
commit 417dd6b4102f55a8f4c05293ee7918ec6d54503a
Include additional headers needed in apt 1.9
APT 1.9 dropped some includes from headers, so we actually
need to include the headers we're using.
commit 2a2901a66ba37b540d40804f22c103a9abd31f55
Ignore missing apt-inst library, merged into apt-pkg in apt 1.9
--- a/autotests/sourceslisttest.cpp
+++ b/autotests/sourceslisttest.cpp
@@ -24,6 +24,7 @@
#include
#include
+#include
QTEST_MAIN(SourcesListTest);
--- a/cmake/modules/FindAptPkg.cmake
+++ b/cmake/modules/FindAptPkg.cmake
@@ -23,6 +23,11 @@ FIND_PATH( APTPKG_INCLUDE_DIR apt-pkg/in
FIND_LIBRARY(APTPKG_LIBRARY_RELEASE NAMES apt-pkg )
FIND_LIBRARY(APTINST_LIBRARY NAMES apt-inst )
+# apt-inst is optional these days!
+IF ( NOT APTINST_LIBRARY )
+SET( APTINST_LIBRARY "" )
+ENDIF( )
+
FIND_LIBRARY(APTPKG_LIBRARY_DEBUG NAMES apt-pkg apt-pkgd HINTS /usr/lib/debug/usr/lib/ )
IF( APTPKG_LIBRARY_RELEASE OR APTPKG_LIBRARY_DEBUG AND APTPKG_INCLUDE_DIR )
--- a/src/backend.cpp
+++ b/src/backend.cpp
@@ -26,6 +26,7 @@
#include
// Apt includes
+#include
#include
#include
#include
@@ -33,10 +34,13 @@
#include
#include
#include
+#include
+#include
#include
#include
#include
#include
+#include
// Xapian includes
#undef slots
@@ -324,7 +328,7 @@ void Backend::setInitError()
{
Q_D(Backend);
-string message;
+std::string message;
if (_error->PopMessage(message))
d->initErrorMessage = QString::fromStdString(message);
}
@@ -356,7 +360,7 @@ void Backend::loadPackagePins()
pkgTagSection tags;
while (tagFile.Step(tags)) {
-string name = tags.FindS("Package");
+std::string name = tags.FindS("Package");
Package *pkg = package(QLatin1String(name.c_str()));
if (pkg)
pkg->setPinned(true);
@@ -635,7 +639,
Bug#927136: src:zabbix-cli: Please update to python3
On Fri, Dec 27, 2019 at 07:52:09PM +0100, Moritz Mühlenhoff wrote: > On Sun, Aug 25, 2019 at 01:21:29AM -0400, Scott Kitterman wrote: > > On Mon, 15 Apr 2019 08:56:40 -0400 Scott Kitterman > > wrote: > > > Package: src:zabbix-cli > > > Version: 1.7.0-1 > > > Severity: important > > > > > > Python2.7 will go out of upstream security support during the Bullseye > > > development cycle. It is not safe to assume it will be included in the > > > next release, so if you want to be sure zabbix-cli can stay in Debian, > > please > > > update it to the python3 version available from upstream.. > > > > > > Personally, I want to remove some packages I maintain, particularly > > > python- > > > ipaddr, which zabbix-cli depends on during the Bullseye cycle, regardless > > > of > > > what happens to python2.7, so please update (python3 includes the > > > ipaddress > > > module, which was developed from ipaddr, in the standard library). > > > > Bumping to serious because python-ipaddr will be removed soon. Upstream > > support python3. Please update to a new version or ack that you've lost > > interest in the package and I'll ask to have it removed. > > Current 2.1.x versions support Python 3, are there any plans to update the > package? > Otherwise I'll file a removal bug. I've filed a removal bug now. Cheers, Moritz
Bug#953306: aptitude: port to apt 1.9.11
Package: aptitude
Version: 0.8.12-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Control: user de...@lists.debian.org
Control: usertag -1 apt-1.9.11
In Ubuntu, the attached patch was applied to achieve the following:
* Update for apt 1.9.11
Thanks for considering the patch.
Note that if this gets uploaded before new apt lands in unstable,
the change from Index() to MapPointer() might need to be wrapped
inside an #if APT_PKG_ABI >= 600 so it can still build with apt in
unstable.
*** /tmp/tmp3dwel3so/aptitude_0.8.12-1ubuntu4.debdiff
diff -Nru aptitude-0.8.12/debian/control aptitude-0.8.12/debian/control
--- aptitude-0.8.12/debian/control 2020-02-19 13:51:33.0 +0100
+++ aptitude-0.8.12/debian/control 2020-02-27 09:14:00.0 +0100
@@ -1,15 +1,14 @@
Source: aptitude
Section: admin
Priority: optional
-Maintainer: Ubuntu Developers
-XSBC-Original-Maintainer: Aptitude Development Team
+Maintainer: Aptitude Development Team
Uploaders: Manuel A. Fernandez Montecelo ,
Axel Beckert
Build-Depends: debhelper (>= 11~),
autoconf-archive,
dpkg-dev (>= 1.16.1),
gettext,
- libapt-pkg-dev (>= 1.1),
+ libapt-pkg-dev (>= 1.9.11~),
libboost-dev,
libboost-iostreams-dev,
libboost-system-dev,
diff -Nru aptitude-0.8.12/debian/patches/06_apt1.9.11
aptitude-0.8.12/debian/patches/06_apt1.9.11
--- aptitude-0.8.12/debian/patches/06_apt1.9.11 1970-01-01 01:00:00.0
+0100
+++ aptitude-0.8.12/debian/patches/06_apt1.9.11 2020-02-27 09:14:00.0
+0100
@@ -0,0 +1,50 @@
+Description: Adjust for apt 1.9.11
+ pkgDPkgPM should not be used directly, use _system->CreatePM() instead;
+ also compare map_pointer in cache against new MapPointer() method instead
+ of Index().
+Author: Julian Andres Klode
+Last-Update: 2020-02-27
+
+--- a/src/generic/apt/apt.cc
b/src/generic/apt/apt.cc
+@@ -1724,8 +1724,8 @@ namespace aptitude
+ return;
+ }
+
+- pkgDPkgPM pm(*apt_cache_file);
+- pm.GetArchives(&fetcher, &l, apt_package_records);
++ std::unique_ptr
pm(_system->CreatePM(*apt_cache_file));
++ pm->GetArchives(&fetcher, &l, apt_package_records);
+ if (_error->PendingError())
+ return;
+
+--- a/src/generic/apt/download_install_manager.cc
b/src/generic/apt/download_install_manager.cc
+@@ -33,6 +33,7 @@
+ #include
+ #include
+ #include
++#include
+
+ #include
+
+@@ -44,7 +45,7 @@ using namespace std;
+
+ download_install_manager::download_install_manager(bool _download_only,
+ const
run_dpkg_in_terminal_func &_run_dpkg_in_terminal)
+- : log(NULL), download_only(_download_only), pm(new
pkgDPkgPM(*apt_cache_file)),
++ : log(NULL), download_only(_download_only),
pm(_system->CreatePM(*apt_cache_file)),
+ run_dpkg_in_terminal(_run_dpkg_in_terminal)
+ {
+ }
+--- a/src/generic/apt/aptitude_resolver.cc
b/src/generic/apt/aptitude_resolver.cc
+@@ -1085,7 +1085,7 @@ void aptitude_resolver::add_default_reso
+ pkgCache::VerIterator instVer(*cache, NULL);
+
+ // See if we have a match that's not through a Provides.
+- for( ; *curr != NULL && (*curr)->ParentPkg == p.Index(); ++curr)
++ for( ; *curr != NULL && (*curr)->ParentPkg == p.MapPointer(); ++curr)
+ {
+ pkgCache::PkgIterator currPkg(*cache, cache->GetCache().PkgP +
(*curr)->ParentPkg);
+ if((*cache)[currPkg].CandidateVer != *curr)
diff -Nru aptitude-0.8.12/debian/patches/series
aptitude-0.8.12/debian/patches/series
--- aptitude-0.8.12/debian/patches/series 2020-02-19 13:51:33.0
+0100
+++ aptitude-0.8.12/debian/patches/series 2020-02-27 09:14:00.0
+0100
@@ -1,3 +1,4 @@
03_branding
04_changelog
05_error
+06_apt1.9.11
-- System Information:
Debian Release: bullseye/sid
APT prefers focal
APT policy: (991, 'focal'), (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-17-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Bug#953238: marked as done (llvm-toolchain-10: autopkgtest failure: /usr/lib/llvm-10/lib/libclang-cpp.so.10 doesn't exist)
Your message dated Sat, 7 Mar 2020 13:09:08 +0100 with message-id <47effac9-91fb-46ab-9a40-b0fd701ae...@debian.org> and subject line done! has caused the Debian Bug report #953238, regarding llvm-toolchain-10: autopkgtest failure: /usr/lib/llvm-10/lib/libclang-cpp.so.10 doesn't exist 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.) -- 953238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-10 Version: 1:10.0.0~+rc2-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainers, Your new package llvm-toolchain-10 has an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=llvm-toolchain-10 https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-10/4416064/log.gz mkdir cmaketest/standard cmaketest/explicit # "Test: CMake find LLVM and Clang in default path" (cd cmaketest/standard && CC=clang-$VERSION CXX=clang++-$VERSION cmake .. > /dev/null) CMake Error at /usr/lib/llvm-10/lib/cmake/clang/ClangTargets.cmake:636 (message): The imported target "clang-cpp" references the file "/usr/lib/llvm-10/lib/libclang-cpp.so.10" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-10/lib/cmake/clang/ClangTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/cmake/clang-10/ClangConfig.cmake:19 (include) CMakeLists.txt:9 (find_package) autopkgtest [21:19:31]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 15276--- End Message ---
Bug#832491: marked as done (aboot: please remove build dependency on obsolete package sp)
Your message dated Sat, 07 Mar 2020 12:04:18 + with message-id and subject line Bug#832491: fixed in aboot 1.0~pre20200212-1 has caused the Debian Bug report #832491, regarding aboot: please remove build dependency on obsolete package sp 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.) -- 832491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: aboot Version: 1.0~pre20040408-4 Severity: normal Tags: patch Dear maintainer, The sp package is obsolete and will be removed from Debian. Please change the build dependency in aboot accordingly (patch attached) or, if you prefer, I can NMU it. Regards. diff -u aboot-1.0~pre20040408/debian/control aboot-1.0~pre20040408/debian/control --- aboot-1.0~pre20040408/debian/control +++ aboot-1.0~pre20040408/debian/control @@ -1,5 +1,5 @@ Source: aboot -Build-Depends: debhelper (>= 9), sp, sgmlspl, docbook-utils +Build-Depends: debhelper (>= 9), opensp, sgmlspl, docbook-utils Build-Depends-Indep: sgmltools-lite Section: admin Priority: standard diff -u aboot-1.0~pre20040408/srmbootfat/Makefile aboot-1.0~pre20040408/srmbootfat/Makefile --- aboot-1.0~pre20040408/srmbootfat/Makefile +++ aboot-1.0~pre20040408/srmbootfat/Makefile @@ -14,10 +14,10 @@ $(CC) $(CFLAGS) $(LDFLAGS) -o srmbootraw srmbootraw.c srmbootfat.1: srmbootfat.sgml - nsgmls srmbootfat.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl + onsgmls srmbootfat.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl srmbootraw.8: srmbootraw.sgml - nsgmls srmbootraw.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl + onsgmls srmbootraw.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl clean: rm -f srmbootfat srmbootraw srmbootfat.1 srmbootraw.8 manpage.links manpage.log manpage.refs --- End Message --- --- Begin Message --- Source: aboot Source-Version: 1.0~pre20200212-1 Done: John Paul Adrian Glaubitz We believe that the bug you reported is fixed in the latest version of aboot, 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 832...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Paul Adrian Glaubitz (supplier of updated aboot 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, 07 Mar 2020 12:12:47 +0100 Source: aboot Architecture: source Version: 1.0~pre20200212-1 Distribution: unstable Urgency: medium Maintainer: John Paul Adrian Glaubitz Changed-By: John Paul Adrian Glaubitz Closes: 832491 949711 950591 Changes: aboot (1.0~pre20200212-1) unstable; urgency=medium . * New upstream version * Set myself as maintainer in debian/control (Closes: #950591) * Add libext2fs-dev to Build-Depends for alpha in debian/control * Drop sgmlspl from Build-Depends in debian/control * Drop sp from Build-Depends in debian/control (Closes: #832491) * Drop sgmltools-lite from Build-Depends-Indep in debian/control (Closes: #949711) * Use rename to adjust filenames for German manpages - Add rename to Build-Depends in debian/control - Run rename to adjust German manpage filenames in debian/rules * Switch package to source format 3.0 (quilt) * Update Vcs-* fields for new Salsa project in debian/control Checksums-Sha1: 50644f68f67c83d305b2a697ba9efb9de859f63b 1988 aboot_1.0~pre20200212-1.dsc 52e5ca4d95d9be106dafa0e35e9f738b69158369 174031 aboot_1.0~pre20200212.orig.tar.gz 15d765dc8936b35d2178163524345922926ff2d2 9196 aboot_1.0~pre20200212-1.debian.tar.xz 47f45947b0df78788177b4a40ab2916b71754bb9 8487 aboot_1.0~pre20200212-1_amd64.buildinfo Checksums-Sha256: 2b37e1dbd63bd9dc3a22656e3ad19a1392f546d6df26ad95512b1fc4bb527f28 1988 aboot_1.0~pre20200212-1.dsc aaf7dee3a445d320fa39206c6f97cd78f9ce475b3164565404affbc495b68bac 174031 aboot_1.0~pre20200212.orig.tar.gz a6fc39bb6774f995d7febc482692f5d7454e5aca680c39f3c2132c2ecc6217e0 9196 aboot_1.0~pre20200212-1.debian.tar.xz 101ab89fc9996d789e16ccb30bfbddf65bfd317d49f6a235ed0dc9649e3ae323 8487 aboot_1.0~pre20200212-1_amd64.buildinfo Files: 2558c1d3e358b2758eef7df6ed069bc8 1988 admin standard aboot_1.0~pre2020021
Processed: Re: Bug#953238: llvm-toolchain-10: autopkgtest failure: /usr/lib/llvm-10/lib/libclang-cpp.so.10 doesn't exist
Processing commands for cont...@bugs.debian.org: > fixed 953238 1:10.0.0~+rc2-3 Bug #953238 [src:llvm-toolchain-10] llvm-toolchain-10: autopkgtest failure: /usr/lib/llvm-10/lib/libclang-cpp.so.10 doesn't exist Marked as fixed in versions llvm-toolchain-10/1:10.0.0~+rc2-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 953238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949711: marked as done (Build-depends on sgmltools-lite, which is being removed)
Your message dated Sat, 07 Mar 2020 12:04:18 + with message-id and subject line Bug#949711: fixed in aboot 1.0~pre20200212-1 has caused the Debian Bug report #949711, regarding Build-depends on sgmltools-lite, which is being removed 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.) -- 949711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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? Cheers, Moritz --- End Message --- --- Begin Message --- Source: aboot Source-Version: 1.0~pre20200212-1 Done: John Paul Adrian Glaubitz We believe that the bug you reported is fixed in the latest version of aboot, 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. John Paul Adrian Glaubitz (supplier of updated aboot 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, 07 Mar 2020 12:12:47 +0100 Source: aboot Architecture: source Version: 1.0~pre20200212-1 Distribution: unstable Urgency: medium Maintainer: John Paul Adrian Glaubitz Changed-By: John Paul Adrian Glaubitz Closes: 832491 949711 950591 Changes: aboot (1.0~pre20200212-1) unstable; urgency=medium . * New upstream version * Set myself as maintainer in debian/control (Closes: #950591) * Add libext2fs-dev to Build-Depends for alpha in debian/control * Drop sgmlspl from Build-Depends in debian/control * Drop sp from Build-Depends in debian/control (Closes: #832491) * Drop sgmltools-lite from Build-Depends-Indep in debian/control (Closes: #949711) * Use rename to adjust filenames for German manpages - Add rename to Build-Depends in debian/control - Run rename to adjust German manpage filenames in debian/rules * Switch package to source format 3.0 (quilt) * Update Vcs-* fields for new Salsa project in debian/control Checksums-Sha1: 50644f68f67c83d305b2a697ba9efb9de859f63b 1988 aboot_1.0~pre20200212-1.dsc 52e5ca4d95d9be106dafa0e35e9f738b69158369 174031 aboot_1.0~pre20200212.orig.tar.gz 15d765dc8936b35d2178163524345922926ff2d2 9196 aboot_1.0~pre20200212-1.debian.tar.xz 47f45947b0df78788177b4a40ab2916b71754bb9 8487 aboot_1.0~pre20200212-1_amd64.buildinfo Checksums-Sha256: 2b37e1dbd63bd9dc3a22656e3ad19a1392f546d6df26ad95512b1fc4bb527f28 1988 aboot_1.0~pre20200212-1.dsc aaf7dee3a445d320fa39206c6f97cd78f9ce475b3164565404affbc495b68bac 174031 aboot_1.0~pre20200212.orig.tar.gz a6fc39bb6774f995d7febc482692f5d7454e5aca680c39f3c2132c2ecc6217e0 9196 aboot_1.0~pre20200212-1.debian.tar.xz 101ab89fc9996d789e16ccb30bfbddf65bfd317d49f6a235ed0dc9649e3ae323 8487 aboot_1.0~pre20200212-1_amd64.buildinfo Files: 2558c1d3e358b2758eef7df6ed069bc8 1988 admin standard aboot_1.0~pre20200212-1.dsc 7d901a1f2fab636d0197c27c2b209bd0 174031 admin standard aboot_1.0~pre20200212.orig.tar.gz dcdf2dae29b26929fbee1af68c1919ef 9196 admin standard aboot_1.0~pre20200212-1.debian.tar.xz 1b4b309a392699408c137bb47321de07 8487 admin standard aboot_1.0~pre20200212-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAl5jhR4ACgkQdCY7N/W1 +RMaZRAAmjGS17klY4sb7BKsUSMcpqShFFMSGfU7S78IK5QSWoqLS2W1/3EXneqH HZnYtY+mExLfxLNQ16WDoTf0SZr2eVwV8gJS0o/5cvTU6UcAVxE84Sq1Z4qS5WTm aMQwDogrQ6Ve/s5m6bwCQX4Laprqe+/Uz+s3MmRKh8Yydmz9/dZq9Zt5Xovw0DbL uAs+z8irYvZGerfETAsFjws63rC8lrThLzI6lZyczLt4uivypGaMRGjbBi2zy0xO sF9Q398xyMJVqpF9gP8pdKGFZ6Au2rynJ5uFZdaCb+VjT2sGVy7v6TT5DlTrLu8Z 78xE+9/Fpf8fWzFp5o3Z14/fHZWtDZ+nevrUWS9+HIpE7F2Z93I0zJNABJaFyyWv znVtqA7B7W6xgbUpBCI66ISnYD9oY0lnF7aKOKstt1O7k2fUJ+1X6jNoTe+Scrve kzS+JkYK+sIF5+9OieqKdRx6oifRAIzdhJhd0awoo+yPGyxMeJPxjJKLaU6zlKfo adVVgol+oztjf66Qz9/Qv70ONWeD8laCLxE3njN2RwNw1oNNCDAfwCXgsuGkTQvt hQSJbCzeuHvQWd5BJaF6NyGLWED2UkmKmqiCDoM2DYkRwxQHQqIVKd+dHkle2x9Q bKOIRRbJ41rVH0WjCARCcM92dOoOEzRT6m9H1H6nVyDfsHmW3VA= =qRZ1 -END PGP SIGNATURE End Message ---
Bug#953223: marked as done (Stop explicitly removing /etc/fuse.conf on purge)
Your message dated Sat, 07 Mar 2020 11:49:50 + with message-id and subject line Bug#953223: fixed in fuse3 3.9.0-2 has caused the Debian Bug report #953223, regarding Stop explicitly removing /etc/fuse.conf on purge 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.) -- 953223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fuse3 Version: 3.9.0-1 Severity: serious Hi, I discovered today that for some reasons the /etc/fuse.conf (conffile) was missing on my machine while I didn't remember deleting it myself. After some investigations I discovered that both the fuse and fuse3 are providing /etc/fuse.conf and are explicitly removing that file in their postrm scripts on purge. IMHO this is not OK (and even a policy violation) Please stop removing /etc/fuse.conf and let dpkg handle that Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages fuse3 depends on: ii adduser 3.118 ii libc6 2.29-10 ii libfuse3-3 3.9.0-1 ii lsb-base11.1.0 ii mount 2.34-0.1 ii sed 4.7-1 fuse3 recommends no packages. fuse3 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: fuse3 Source-Version: 3.9.0-2 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of fuse3, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated fuse3 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 Mar 2020 11:10:15 + Source: fuse3 Architecture: source Version: 3.9.0-2 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 953223 Changes: fuse3 (3.9.0-2) unstable; urgency=medium . * Don't explicitly remove fuse.conf on purge (closes: #953223). Checksums-Sha1: 3c4918a4f2e113465496f33d9c433b67e2f00b36 2330 fuse3_3.9.0-2.dsc 643a657c27dec0d2c1e4a7c6d6eeae8c2a46b399 9560 fuse3_3.9.0-2.debian.tar.xz Checksums-Sha256: 5a65f1d19c5bf1f78aef19242be6876417f79b8baeb8d07232bbc36e995b60a3 2330 fuse3_3.9.0-2.dsc 92bb66e37ab2fb4559b0aea21d88996943b906a07c9cc2ec9eada58143f281bb 9560 fuse3_3.9.0-2.debian.tar.xz Files: ad050570f6235ae09435076ffd0bc94e 2330 utils optional fuse3_3.9.0-2.dsc e0fc0fbcd758cc14ec2e78b871012ed4 9560 utils optional fuse3_3.9.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl5jhv4ACgkQ3OMQ54ZM yL+XJg//RNUfmW0vvRRinDkSgXbcxc9CVdU822xX++MFnsfUVi9pH2OB8SpOdB1f WXt06JCh2wWnugvIfBbsb9CS8Ce4B7dYW3MFzV6eshUC0JRrvnGXrQz89qEWQinW 5bI6xDY+SzOfGyPHHd0vV1L8rQQgZniQ9wLCaEWeWwDM7YhHzL34vHOs6QiNGb6X GRykLaW/j8/tdTxc3ZJ8MU3MMVxAPXjpR+tL9F31J5X8YFa9xUbr52oFsn0ObvSe bDTt+YjAnmWOsRaOw3ps/bGCHaahoUjwa4a3rTipggeI20fOKuI9r1lRnm2XFViC BIM7tgDg+Tk5oarD6TY21nK+BLz11Xi/3C875dwYutMJqmYyyhAx9qQiF079/Sej 2I4JBHjl4IIIoSdDnPpCNaQeD2rFVXox7WFUfL9enwIwyslz34ZOztp8/QaIrbS6 eN6EMeIUgVj8BhsE9ADFJwbkuqJto0WJYw2ClueF4eMedyTnIt+aEUZpgy8rJ/Yl feDU+X+RDopx3O0ZyPRzJb0RmMZ4GMQIdNnTm49xgngOwx48fnnEwQS6SeY7JZXq mRieZOq2l94m3Pl1bM0G2YJCLxxfiypE8BgadVId34+C0JEO1PDpFFkmiToymHup zNHCAK8wCURfMxc2L0mvNH8w/TtZy3L7BFx0IOZd4/43HH5QzPU= =2RKe -END PGP SIGNATURE End Message ---
Bug#953222: marked as done (Stop explicitly removing /etc/fuse.conf on purge)
Your message dated Sat, 07 Mar 2020 11:49:41 + with message-id and subject line Bug#953222: fixed in fuse 2.9.9-3 has caused the Debian Bug report #953222, regarding Stop explicitly removing /etc/fuse.conf on purge 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.) -- 953222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fuse Version: 2.9.9-1 Severity: serious Hi, I discovered today that for some reasons the /etc/fuse.conf (conffile) was missing on my machine while I didn't remember deleting it myself. After some investigations I discovered that both the fuse and fuse3 are providing /etc/fuse.conf and are explicitly removing that file in their postrm scripts on purge. IMHO this is not OK (and even a policy violation) Please stop removing /etc/fuse.conf and let dpkg handle that Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: fuse Source-Version: 2.9.9-3 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of fuse, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated fuse 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 Mar 2020 11:09:49 + Source: fuse Architecture: source Version: 2.9.9-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 953222 Changes: fuse (2.9.9-3) unstable; urgency=medium . * Don't explicitly remove fuse.conf on purge (closes: #953222). Checksums-Sha1: db9a5ecc1c5e3f7255a9d5ba79c77f74e3753994 2290 fuse_2.9.9-3.dsc a0751f7e45625e8e6606e5ee3a9d24e5e8329a06 22420 fuse_2.9.9-3.debian.tar.xz Checksums-Sha256: 038f14cf5a64ed61a74fc913f3137547d84351eb4ce8d9085659d08952701bc6 2290 fuse_2.9.9-3.dsc cc56758c83421488320eabf963379cac88336a5e438d1113560a30e4e280e76f 22420 fuse_2.9.9-3.debian.tar.xz Files: 0d60c29ddacf6fbab31c7165e3514298 2290 utils optional fuse_2.9.9-3.dsc 4b7d791231de6b81c76a500cefb01ad3 22420 utils optional fuse_2.9.9-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl5jhv4ACgkQ3OMQ54ZM yL+jtQ//dRqdUHO9Sj1gTc4X9plYkzjPMY5d5ANuS5/MldCh67FDBoYl3iuPvSJz ZULKYDksRi8F7Nrx1BzuQSqa+bRq81BryxN2Yb4YWGCCPDiACXNUc7j5Abml3q2g B9ptMDsvTs7YAqMK1YM3I+jVh0rXlNVGiTrGVmrbmRHOc57bh5Apaaf4dp8P7iRQ 2KgOAPFRSW4734CdXzp32ex1j1O4XnqDOAZNeNpFxFJUUqhTLXFCnfvYoRKF7npE kxSuebSfnf2INzzRRa5H+P+S+PrMdsnAVL2lz4sN9gI8OSh0onOV9apTvuqzNsLy kiqK8iM9uSu17OkY22DRssVnh/AlTdUiHkK+0/LeMUXTwzluugGxcfxKB3XjX7cG 9+y9EYCMJBpAqsQtPxzKn8kJiF356OvLiA+RemsUzXHKaf/u0pqRXTJ4QZdNmMJw /UFub0lTQhQY1D9rmvPoCuKch45l33NUdOD7NSN52ymlJ73CN6SeUw67gB6AyuTY aAAdZdLX09Ygi+vZqw4pcDvyMHRdhDXEHQICtq3YQi51AD13v7Y6SlsXo1Utx/38 l7teqjwHNvuD0kHacbF8ZBAYs4uZmH6RmlxZHUttJ+QEvsZtpseuH+TD3NCOVGNz ybuHTTWbYJ03VfXMgXvWAB1sgUrJD11yLjpkRFiXp1Z70mLDxnA= =+66z -END PGP SIGNATURE End Message ---
Bug#952222: marked as done (google-authenticator: FTBFS: dh_auto_test: error: cd libpam && make -j4 test VERBOSE=1 returned exit code 2)
Your message dated Sat, 07 Mar 2020 11:34:25 + with message-id and subject line Bug#95: fixed in google-authenticator 20191231-1 has caused the Debian Bug report #95, regarding google-authenticator: FTBFS: dh_auto_test: error: cd libpam && make -j4 test VERBOSE=1 returned exit code 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.) -- 95: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: google-authenticator Version: 20170702-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/libpam' > FAIL: tests/pam_google_authenticator_unittest > = >google-authenticator 1.03: ./test-suite.log > = > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: tests/pam_google_authenticator_unittest > = > > pam_google_authenticator_unittest: > tests/pam_google_authenticator_unittest.c:335: main: Assertion > `num_prompts_shown == (expected_bad_prompts_shown)' failed. > Secret file "/tmp/.google_authenticator_czSEyP" must be owned by "user42" > FAIL tests/pam_google_authenticator_unittest (exit status: 1) > > > Testsuite summary for google-authenticator 1.03 > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See ./test-suite.log > Please report to hab...@google.com > > make[4]: *** [Makefile:1283: test-suite.log] Error 1 > make[4]: Leaving directory '/<>/libpam' > make[3]: *** [Makefile:1391: check-TESTS] Error 2 > make[3]: Leaving directory '/<>/libpam' > make[2]: *** [Makefile:1598: check-am] Error 2 > make[2]: Leaving directory '/<>/libpam' > dh_auto_test: error: cd libpam && make -j4 test VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/google-authenticator_20170702-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: google-authenticator Source-Version: 20191231-1 Done: Janos Lenart We believe that the bug you reported is fixed in the latest version of google-authenticator, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Janos Lenart (supplier of updated google-authenticator 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 Mar 2020 09:53:25 + Source: google-authenticator Binary: libpam-google-authenticator libpam-google-authenticator-dbgsym Architecture: source amd64 Version: 20191231-1 Distribution: unstable Urgency: medium Maintainer: Janos Lenart Changed-By: Janos Lenart Description: libpam-google-authenticator - Two-step verification Closes: 919888 95 Changes: google-authenticator (20191231-1) unstable; urgency=medium . * Upstream release (2c7415d, v1.08) (Closes: #919888). * Fixed FTBFS (Closes: #95). * Removed the TOTP debugger (totp.html) due to privacy concerns (it loads external resources). Checksums-Sha1: 922bf135433ded4489fae8370e02e43efbe12554 1905 google-authenticator_20191231-1.dsc e6f8dea6b8a14e58f1604c28d3f20206e37c9f75 627
Processed: Raising severity of apt-1.9.0 bugs to serious
Processing control commands: > severity -1 serious Bug #930673 [openscap] openscap: Port to apt 1.9.0 Severity set to 'serious' from 'normal' -- 930673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Raising severity of apt-1.9.0 bugs to serious
Processing control commands: > severity -1 serious Bug #930663 [apt-move] apt-move: Port to apt 1.9 Severity set to 'serious' from 'normal' -- 930663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Raising severity of apt-1.9.0 bugs to serious
Processing control commands: > severity -1 serious Bug #931024 [kthresher] kthresher: Uses Package.section, incompatible with python-apt 1.9 Severity set to 'serious' from 'normal' -- 931024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Raising severity of apt-1.9.0 bugs to serious
Processing control commands: > severity -1 serious Bug #931133 [apt-xapian-index] apt-xapian-index: unusable after recent python-apt update due to usage of deprecated Package.section attribute Severity set to 'serious' from 'important' -- 931133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953301: opensmtpd-extras: bad API version error while using the sqlite plugin
Package: opensmtpd-extras Version: 5.7.1-4+b2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I'm trying to set up opensmtpd for virtual domains, with a sqlite table backend to read alias, domains, users and infos * What exactly did you do (or not do) that was effective (or ineffective)? After setting the /etc/smtpd.conf as described in the manual to access sqlite backend, opensmtpd refuse to start, issuing the following warning: warn: table-proc: pipe closed * What was the outcome of this action? see previous bullet * What outcome did you expect instead? I expect that opensmtpd starts and access sqlite db to read user data I see another similar issue with the LDAP plugin. The reporter hinted that the problem may be caused by a release mismatch. It may be, but in this case, the issue is not limited to ldap plugin but to the all opensmtpd-extras package. Regards, larzeni -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages opensmtpd-extras depends on: ii libc6 2.28-10 ii libevent-2.1-6 2.1.8-stable-4 ii libhiredis0.14 0.14.0-3 ii libmariadb3 1:10.3.22-0+deb10u1 ii libpq5 11.7-0+deb10u1 ii libsqlite3-03.27.2-3 ii libssl1.1 1.1.1d-0+deb10u2 ii opensmtpd 6.0.3p1-5+deb10u4 opensmtpd-extras recommends no packages. opensmtpd-extras suggests no packages. -- no debconf information
Bug#872234: marked as done (mlpy: FTBFS: Needs build-dep on latexmk, pngmath replaced with imgmath)
Your message dated Sat, 07 Mar 2020 11:00:34 + with message-id and subject line Bug#872234: fixed in mlpy 3.5.0+ds-1 has caused the Debian Bug report #872234, regarding mlpy: FTBFS: Needs build-dep on latexmk, pngmath replaced with imgmath 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.) -- 872234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mlpy Version: 2.2.0~dfsg1-3 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.6 Dear maintainer, mlpy fails to build with Sphinx 1.6, currently available in experimental: PYTHONPATH=/<>/build/lib.linux-x86_64-2.7 /usr/bin/make -C docs/build/latex all-pdf make[1]: Entering directory '/<>/docs/build/latex' latexmk -pdf -dvi- -ps- 'mlpy.tex' make[1]: latexmk: Command not found Makefile:33: recipe for target 'mlpy.pdf' failed make[1]: *** [mlpy.pdf] Error 127 Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1]. Adding a build-dependency on latexmk should help. [1]: https://github.com/sphinx-doc/sphinx/pull/3082 -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mlpy Source-Version: 3.5.0+ds-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mlpy, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated mlpy 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: Wed, 26 Feb 2020 21:34:01 +0100 Source: mlpy Binary: python-mlpy-doc python3-mlpy python3-mlpy-lib python3-mlpy-lib-dbgsym Architecture: source all amd64 Version: 3.5.0+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Description: python-mlpy-doc - documentation and examples for mlpy python3-mlpy - high-performance Python package for predictive modeling python3-mlpy-lib - low-level implementations and bindings for mlpy Closes: 651118 807216 872234 902770 937055 Changes: mlpy (3.5.0+ds-1) unstable; urgency=medium . * Team upload. . [Bas Couwenberg ] * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev. Closes: #807216 . [ Andreas Tille ] * Move package to Debian Science team maintenance * debian/gbp.conf: Deleted since default repository layout is used * Point watch file to sourceforge to fetch latest upstream version Also exclude cython results to force recreating these using cython3 Closes: #651118 * Standards-Version: 4.5.0 (routine-update) * debhelper-compat 12 (routine-update) * Testsuite: autopkgtest-pkg-python (routine-update) * Build-Depends: s/python-sphinx/python3-sphinx/ (routine-update) * Add salsa-ci file (routine-update) * Trim trailing whitespace. * Use versioned copyright format URI. * Change packaging system from cdbs to dh * Drop Python2 package and create Python3 package only Closes: #937055, #902770 * (Build-)Depends: python3-scipy * Fix sphinx extensions, Build-Depends: latexmk Closes: #872234 * No manpages since no scripts are installed * Install docs to /usr/share/doc/python3-mlpy * Hardening Checksums-Sha1: bc32a7e84ba33f7afc1de405f6b8f2f6cd386961 2292 mlpy_3.5.0+ds-1.dsc 7adeb59906d23f7561b49ec67ab790c8d49d597e 1472016 mlpy_3.5.0+ds.orig.tar.xz 15ead3f2aa176d3cddcb99939802b4eda211068f 4352 mlpy_3.5.0+ds-1.debian.tar.xz 6200efced92926737516a724487bdd8afbe6588a 10480 mlpy_3.5.0+ds-1_amd64.buildinfo 04c7007383190fad239020aa02a2fb6db012df3b 2692444 python-mlpy-doc_3.5.0+ds-1_all.deb 97a3a51ef78e356a97c12ef8b994cf02711ce7b6 3148808 python3-mlpy-lib-dbgsym_3.5.0+ds-1_amd64.deb 459593fa2a80f0eaaec4618ca40511c0394f8ab3 547392 python3-mlpy-lib_3.5.0+ds-1_amd64.deb cf71ee1ffbc01644fb77adf9ee859422cd75675d 33544 python3-mlpy_3.5.0+ds-1_all.deb Checksums-Sha256: e1b0f476b2a21b7cc84e12abc2729d3998ad4f2fba8c2796153b6ea8b35dd481 2292 mlpy_3.5.0+ds-1.dsc bf7b960fdb80eb6baf49831c831d
Bug#937055: marked as done (mlpy: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Mar 2020 11:00:34 + with message-id and subject line Bug#937055: fixed in mlpy 3.5.0+ds-1 has caused the Debian Bug report #937055, regarding mlpy: 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.) -- 937055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mlpy Version: 2.2.0~dfsg1-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:mlpy 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: mlpy Source-Version: 3.5.0+ds-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mlpy, 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. Andreas Tille (supplier of updated mlpy 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: Wed, 26 Feb 2020 21:34:01 +0100 Source: mlpy Binary: python-mlpy-doc python3-mlpy python3-mlpy-lib python3-mlpy-lib-dbgsym Architecture: source all amd64 Version: 3.5.0+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Description: python-mlpy-doc - documentation and examples for mlpy python3-mlpy - high-performance Python package for predictive modeling python3-mlpy-lib - low-level implementations and bindings for mlpy Closes: 651118 807216 872234 902770 937055 Changes: mlpy (3.5.0+ds-1) unstable; urgency=medium . * Team upload. . [Bas Couwenberg ] * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev. Closes: #807216 . [ Andreas Tille ] * Move package to Debian Science team maintenance * debian/gbp.conf: Deleted since default repository layout is used * Point watch file to sourceforge to fetch latest upstream version Also exclude cython resu
Bug#952240: marked as done (clevis: FTBFS: dh_install: error: missing files, aborting)
Your message dated Sat, 07 Mar 2020 11:00:16 + with message-id and subject line Bug#952240: fixed in clevis 12-1 has caused the Debian Bug report #952240, regarding clevis: FTBFS: dh_install: error: missing files, aborting 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.) -- 952240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clevis Version: 11-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary >dh_testroot >dh_prep >dh_auto_install > cd obj-x86_64-linux-gnu && DESTDIR=/<>/debian/tmp > LC_ALL=C.UTF-8 ninja install > [0/1] Installing files. > Installing src/luks/udisks2/clevis-luks-udisks2 to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu > Installing src/pins/sss/clevis-decrypt-sss to > /<>/debian/tmp/usr/bin > Installing src/pins/sss/clevis-encrypt-sss to > /<>/debian/tmp/usr/bin > Installing clevis-luks-unbind.1 to > /<>/debian/tmp/usr/share/man/man1 > Installing clevis-luks-unlock.1 to > /<>/debian/tmp/usr/share/man/man1 > Installing clevis-luks-bind.1 to > /<>/debian/tmp/usr/share/man/man1 > Installing clevis-luks-unlockers.7 to > /<>/debian/tmp/usr/share/man/man7 > Installing clevis-encrypt-sss.1 to > /<>/debian/tmp/usr/share/man/man1 > Installing clevis-encrypt-tang.1 to > /<>/debian/tmp/usr/share/man/man1 > Installing clevis-decrypt.1 to /<>/debian/tmp/usr/share/man/man1 > Installing clevis.1 to /<>/debian/tmp/usr/share/man/man1 > Installing > /<>/obj-x86_64-linux-gnu/src/luks/systemd/dracut/module-setup.sh > to /<>/debian/tmp/usr/lib/dracut/modules.d/60clevis > Installing > /<>/obj-x86_64-linux-gnu/src/luks/systemd/dracut/clevis-hook.sh > to /<>/debian/tmp/usr/lib/dracut/modules.d/60clevis > Installing > /<>/obj-x86_64-linux-gnu/src/luks/systemd/clevis-luks-askpass.service > to /<>/debian/tmp/lib/systemd/system > Installing /<>/src/luks/systemd/clevis-luks-askpass.path to > /<>/debian/tmp/lib/systemd/system > Installing /<>/src/luks/systemd/clevis-luks-askpass to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu > Installing > /<>/obj-x86_64-linux-gnu/src/luks/udisks2/clevis-luks-udisks2.desktop > to /<>/debian/tmp/etc/xdg/autostart > Installing /<>/src/luks/clevis-luks-unbind to > /<>/debian/tmp/usr/bin > Installing /<>/src/luks/clevis-luks-unlock to > /<>/debian/tmp/usr/bin > Installing /<>/src/luks/clevis-luks-bind to > /<>/debian/tmp/usr/bin > Installing /<>/src/pins/tang/clevis-decrypt-tang to > /<>/debian/tmp/usr/bin > Installing /<>/src/pins/tang/clevis-encrypt-tang to > /<>/debian/tmp/usr/bin > Installing /<>/src/clevis-decrypt to > /<>/debian/tmp/usr/bin > Installing /<>/src/clevis to /<>/debian/tmp/usr/bin >dh_install > dh_install: warning: Cannot find (any matches for) > "usr/bin/clevis-decrypt-tpm2" (tried in ., debian/tmp) > > dh_install: warning: clevis-tpm2 missing files: usr/bin/clevis-decrypt-tpm2 > dh_install: warning: Cannot find (any matches for) > "usr/bin/clevis-encrypt-tpm2" (tried in ., debian/tmp) > > dh_install: warning: clevis-tpm2 missing files: usr/bin/clevis-encrypt-tpm2 > dh_install: error: missing files, aborting > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/02/22/clevis_11-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: clevis Source-Version: 12-1 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of clevis, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated clevis package) (This message was generated automatically at their request; if you believe that there is a problem with it p
Bug#807216: marked as done (mlpy: Update build dependencies for GSL 2.x)
Your message dated Sat, 07 Mar 2020 11:00:34 + with message-id and subject line Bug#807216: fixed in mlpy 3.5.0+ds-1 has caused the Debian Bug report #807216, regarding mlpy: Update build dependencies for GSL 2.x 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.) -- 807216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mlpy Version: 2.2.0~dfsg1-3 Severity: normal Tags: patch Dear Maintainer, Please update your package for the ongoing gsl transition (#804246). The attached patch updates the build dependencies to use libgsl-dev. This change is required to not pull in GSL 1.x via libgsl0-dev. Kind Regards, Bas diff -Nru mlpy-2.2.0~dfsg1/debian/changelog mlpy-2.2.0~dfsg1/debian/changelog --- mlpy-2.2.0~dfsg1/debian/changelog 2015-08-29 14:08:51.0 +0200 +++ mlpy-2.2.0~dfsg1/debian/changelog 2015-11-22 19:30:01.0 +0100 @@ -1,3 +1,10 @@ +mlpy (2.2.0~dfsg1-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev. + + -- Bas Couwenberg Sun, 22 Nov 2015 19:29:55 +0100 + mlpy (2.2.0~dfsg1-3) unstable; urgency=medium * Maintenance upload. Thanks to Matthias Klose for the previous NMU. diff -Nru mlpy-2.2.0~dfsg1/debian/control mlpy-2.2.0~dfsg1/debian/control --- mlpy-2.2.0~dfsg1/debian/control 2015-08-29 13:51:14.0 +0200 +++ mlpy-2.2.0~dfsg1/debian/control 2015-11-22 19:29:53.0 +0100 @@ -7,7 +7,7 @@ Build-Depends: cdbs, debhelper (>= 5.0.38), dh-python, - libgsl0-dev, + libgsl-dev, python-all-dev, python-numpy, python-sphinx, --- End Message --- --- Begin Message --- Source: mlpy Source-Version: 3.5.0+ds-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mlpy, 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 807...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated mlpy 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: Wed, 26 Feb 2020 21:34:01 +0100 Source: mlpy Binary: python-mlpy-doc python3-mlpy python3-mlpy-lib python3-mlpy-lib-dbgsym Architecture: source all amd64 Version: 3.5.0+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Description: python-mlpy-doc - documentation and examples for mlpy python3-mlpy - high-performance Python package for predictive modeling python3-mlpy-lib - low-level implementations and bindings for mlpy Closes: 651118 807216 872234 902770 937055 Changes: mlpy (3.5.0+ds-1) unstable; urgency=medium . * Team upload. . [Bas Couwenberg ] * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev. Closes: #807216 . [ Andreas Tille ] * Move package to Debian Science team maintenance * debian/gbp.conf: Deleted since default repository layout is used * Point watch file to sourceforge to fetch latest upstream version Also exclude cython results to force recreating these using cython3 Closes: #651118 * Standards-Version: 4.5.0 (routine-update) * debhelper-compat 12 (routine-update) * Testsuite: autopkgtest-pkg-python (routine-update) * Build-Depends: s/python-sphinx/python3-sphinx/ (routine-update) * Add salsa-ci file (routine-update) * Trim trailing whitespace. * Use versioned copyright format URI. * Change packaging system from cdbs to dh * Drop Python2 package and create Python3 package only Closes: #937055, #902770 * (Build-)Depends: python3-scipy * Fix sphinx extensions, Build-Depends: latexmk Closes: #872234 * No manpages since no scripts are installed * Install docs to /usr/share/doc/python3-mlpy * Hardening Checksums-Sha1: bc32a7e84ba33f7afc1de405f6b8f2f6cd386961 2292 mlpy_3.5.0+ds-1.dsc 7adeb59906d23f7561b49ec67ab790c8d49d597e 1472016 mlpy_3.5.0+ds.orig.tar.xz 15ead3f2aa176d3cddcb99939802b4eda211068f 4352 mlpy_3.5.0+ds-1.debian.tar.xz 62
Bug#952050: marked as done (nfs-ganesha: FTBFS: handle_syscalls.c:78:59: error: unknown type name ‘xfs_bstat_t’; did you mean ‘xfs_bstime_t’?)
Your message dated Sat, 07 Mar 2020 11:00:38 + with message-id and subject line Bug#952050: fixed in nfs-ganesha 3.2-1 has caused the Debian Bug report #952050, regarding nfs-ganesha: FTBFS: handle_syscalls.c:78:59: error: unknown type name ‘xfs_bstat_t’; did you mean ‘xfs_bstime_t’? 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.) -- 952050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nfs-ganesha Version: 2.7.6-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/src/obj-x86_64-linux-gnu/FSAL/FSAL_VFS/xfs && /usr/bin/cc > -DHAS_DOFF -D_GNU_SOURCE -D__USE_GNU -Dfsalxfs_EXPORTS -I/usr/include/uuid > -I/<>/src/obj-x86_64-linux-gnu/include > -I/<>/src/include -I/<>/src/include/os/linux > -I/include -I/usr/include/ntirpc -I/<>/src/FSAL/FSAL_VFS/. -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE > -D_FILE_OFFSET_BITS=64 -O2 -g -DNDEBUG -fPIC -o > CMakeFiles/fsalxfs.dir/handle_syscalls.c.o -c > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c:78:59: error: > unknown type name ‘xfs_bstat_t’; did you mean ‘xfs_bstime_t’? >78 | static int xfs_fsal_bulkstat_inode(int fd, xfs_ino_t ino, xfs_bstat_t > *bstat) > | ^~~ > | xfs_bstime_t > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c: In function > ‘xfs_fsal_inode2handle’: > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c:92:2: error: unknown > type name ‘xfs_bstat_t’; did you mean ‘xfs_bstime_t’? >92 | xfs_bstat_t bstat; > | ^~~ > | xfs_bstime_t > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c:105:7: warning: > implicit declaration of function ‘xfs_fsal_bulkstat_inode’ > [-Wimplicit-function-declaration] > 105 | if ((xfs_fsal_bulkstat_inode(fd, ino, &bstat) < 0) || > | ^~~ > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c:119:29: error: > request for member ‘bs_gen’ in something not a structure or union > 119 | hdl->ha_fid.fid_gen = bstat.bs_gen; > | ^ > /<>/src/FSAL/FSAL_VFS/xfs/handle_syscalls.c:120:29: error: > request for member ‘bs_ino’ in something not a structure or union > 120 | hdl->ha_fid.fid_ino = bstat.bs_ino; > | ^ > make[4]: *** [FSAL/FSAL_VFS/xfs/CMakeFiles/fsalxfs.dir/build.make:105: > FSAL/FSAL_VFS/xfs/CMakeFiles/fsalxfs.dir/handle_syscalls.c.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/nfs-ganesha_2.7.6-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: nfs-ganesha Source-Version: 3.2-1 Done: Christoph Martin We believe that the bug you reported is fixed in the latest version of nfs-ganesha, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Martin (supplier of updated nfs-ganesha 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, 02 Mar 2020 10:10:27 +0100 Source: nfs-ganesha Binary: nfs-ganesha nfs-ganesha-ceph nfs-ganesha-ceph-dbgsym nfs-ganesha-dbgsym nfs-ganesha-doc nfs-ganesha-gluster nfs-ganesha-gluster-dbgsym nfs-ganesha-gpfs nfs-ganesha-gpfs-dbgsym nfs-ganesha-mem nfs-ganesha-mem-dbgsym nfs-ganesha-mount-9p nfs-ganesha-nullfs nfs-ganesha-nullfs-dbgsym nfs-ganesha-proxy nfs-ganesha-proxy-dbgsym
Bug#951735: marked as done (klayout: FTBFS against Ruby2.7 on different $arch)
Your message dated Sat, 07 Mar 2020 10:49:59 + with message-id and subject line Bug#951735: fixed in klayout 0.26.2-2 has caused the Debian Bug report #951735, regarding klayout: FTBFS against Ruby2.7 on different $arch 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.) -- 951735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: klayout Version: 0.26.2-1 Severity: critical User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition Dear Maintainer, There's FTBFS against Ruby2.7 on different architectures which is blocking our transition going on right now. I reported this upstream, too (https://github.com/KLayout/klayout/issues/506). The failures against Ruby2.7 on different $arch could be found here: https://buildd.debian.org/status/package.php?p=klayout Requesting you to please take a look at it and help us in fixing them :) Best, Utkarsh --- -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=U Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages klayout depends on: ii libc6 2.29-10 ii libgcc-s1 [libgcc1] 10-20200211-1 ii libgcc1 1:10-20200211-1 ii libpython3.7 3.7.6-1+b1 ii libqt5core5a 5.12.5+dfsg-8 pn libqt5designer5 ii libqt5gui55.12.5+dfsg-8 pn libqt5multimedia5 pn libqt5multimediawidgets5 ii libqt5network55.12.5+dfsg-8 pn libqt5printsupport5 pn libqt5sql5 ii libqt5svg55.12.5-2 ii libqt5widgets55.12.5+dfsg-8 pn libqt5xml5 pn libqt5xmlpatterns5 ii libruby2.52.5.7-1+b1 ii libstdc++610-20200211-1 ii python3 3.7.5-3 ii zlib1g1:1.2.11.dfsg-1.2 --- End Message --- --- Begin Message --- Source: klayout Source-Version: 0.26.2-2 Done: Ruben Undheim We believe that the bug you reported is fixed in the latest version of klayout, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ruben Undheim (supplier of updated klayout 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, 06 Mar 2020 19:17:11 +0100 Source: klayout Architecture: source Version: 0.26.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Ruben Undheim Closes: 951735 Changes: klayout (0.26.2-2) unstable; urgency=medium . * Change build-dependency to libpython3-dev * Update patch to debian/patches/0001-Prefer-Newer-Python3.patch * All explicit dependencies on python3.7 have been removed. Fixes FTBFS (Closes: #951735) Checksums-Sha1: 115b1cbee7860fd08edeed21b063d0341d1d0dc2 2194 klayout_0.26.2-2.dsc 6cbaeea7b7f92dec903048ccc894da31a5c9b34c 6136 klayout_0.26.2-2.debian.tar.xz Checksums-Sha256: f05545d568901a7701025b0c24f203ccb66d84e6d630a2d5d066eb44c34795fa 2194 klayout_0.26.2-2.dsc 9221ee0c3844e93507bb8cee70d156cf88116e5fda47e38e221ba77e0e72bd4f 6136 klayout_0.26.2-2.debian.tar.xz Files: c7c9f6c23dc7d706525ba03adac61a52 2194 electronics optional klayout_0.26.2-2.dsc 200fb3c8cd703cac56a8171dfacb1276 6136 electronics optional klayout_0.26.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENHTECWcp7QxRgH085pgix+ApWM0FAl5jVQIACgkQ5pgix+Ap WM1oqQ//YQ9azDGzfBx2t5Q8aoDdV+/6Hc1R7mfJea+/yXLDt7AbkHJZLukrpC5b 9oH2Piao0m/b8F88Zt2DUadU2e9tqPKV3vkI9I6e+LHaRaAQ14p2eD1vrp09jHtw 08nD+SZA/S39GB0gkIFWGOB3bkPaYxVKDWA+y1wAOz/gAP4v07GhX5uZ4vMY/CDz XPOiLJDPZXSVEXCEr/TZmxoHgAYcXCOFKAivqphgjWlc/2yBagQIw6XPxWL+qymI y4pcJgwj/V3dsbHGJE5vGLBMWuFTHWBP8ObP7A4ya1/nJYlVY0RTD8J9+qJzEwhd M2f6BDrDt9DgnCEVNLhp9ODv9dIpQPXCnoHta8mU6RiK3KFNMRXAgX6ABpPjnkY2 2D73DnGFOhs3VC01u
Bug#951966: marked as done (kio-extras: FTBFS: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1497: undefined reference to `sftp_lstat')
Your message dated Sat, 07 Mar 2020 08:35:39 + with message-id and subject line Bug#951966: fixed in kio-extras 4:19.12.3-1 has caused the Debian Bug report #951966, regarding kio-extras: FTBFS: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1497: undefined reference to `sftp_lstat' 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.) -- 951966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kio-extras Version: 4:19.08.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/kio_sftp.dir/kio_sftp.cpp.o: in function > `sftpProtocol::sftpGet(QUrl const&, int&, long long, int)': > ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1497: undefined reference to > `sftp_lstat' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1522: undefined > reference to `sftp_attributes_free' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1506: undefined > reference to `sftp_attributes_free' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1519: undefined > reference to `sftp_open' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1527: undefined > reference to `sftp_read' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1541: undefined > reference to `sftp_rewind' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1499: undefined > reference to `sftp_get_error' > /usr/bin/ld: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1562: undefined > reference to `sftp_seek64' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/kio-extras_19.08.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: kio-extras Source-Version: 4:19.12.3-1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kio-extras, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kio-extras 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 Mar 2020 09:22:41 +0100 Source: kio-extras Architecture: source Version: 4:19.12.3-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 951966 Changes: kio-extras (4:19.12.3-1) unstable; urgency=medium . * Team upload. * New upstream release: - fixes build with newer libssh (Closes: #951966) * Update watch file to the new release-service location. * Update the build dependencies according to the upstream build system: - add libkf5activitiesstats-dev - drop libkf5khtml-dev, no more used - bump libssh-dev to 0.7.0 - add kio, as it provides the kfileitemactionplugin.desktop file, used at build time - explicitly add gettext * Switch from dhmk to the dh sequencer: - invoke the dh sequencer using the kf5 addon - explicitly link in as-needed mode - manually force the generation of the substvars for the kde-l10n breaks * Pass -DBUILD_TESTING=OFF to cmake to disable the build of tests, as they are not run at build time anyway. * Switch from the debhelper build dependency to debhelper-compat - remove debian/compat * Tweak the install wildcard for libmolletnetwork5, so it does not depend on the year in the version number. * Explicitly remove the development files we do not ship, instead of listing them in not-installed, so it is harder to ship them by chance
Bug#953287: libpsl: binary-all FTBFS
Source: libpsl Version: 0.21.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libpsl&arch=all&ver=0.21.0-1&stamp=1583346789&raw=0 ... dh_installman -i dh_installman: error: Cannot find (any matches for) "usr/share/man/man1/psl-make-dafsa.1" (tried in ., debian/tmp) dh_installman: error: Aborting due to earlier error make: *** [debian/rules:6: binary-indep] Error 25
Processed: tagging 951966
Processing commands for cont...@bugs.debian.org: > tags 951966 + pending Bug #951966 [src:kio-extras] kio-extras: FTBFS: ./obj-x86_64-linux-gnu/sftp/./sftp/kio_sftp.cpp:1497: undefined reference to `sftp_lstat' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 951966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
