Processed: yapra: diff for NMU version 0.1.2-7.2
Processing control commands: > tags 965908 + patch pending Bug #965908 [src:yapra] yapra: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending and patch. -- 965908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019158: graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv
On Mon, 5 Sep 2022, László Böszörményi wrote: On Mon, Sep 5, 2022 at 4:09 PM Bob Friesenhahn wrote: On Sun, 4 Sep 2022, Paul Gevers wrote: gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv This issue is caused by Mercurial changeset 16712:acb5f7fa99cf: "colorMapSize() method for returning the number of colormap entries should be a const method." Apparently this change impacts the ABI. How do you plan to solve this problem? Seems you either revert it or the library needs a soname bump. Mercurial changeset 16739:a152f76afeab restores non-const Image::colorMapSize() while still providing the new const version. I think that this should solve the problem. Please let me know if it doesn't or there is some new problem. The changes are also in the snapshot version GraphicsMagick-1.4.020220905. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
Bug#1015044: marked as done (sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Mon, 05 Sep 2022 23:04:42 + with message-id and subject line Bug#1015044: fixed in sshuttle 1.1.1-1 has caused the Debian Bug report #1015044, regarding sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sshuttle Version: 1.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_clean > rm -rf tmp > rm -rf docs/.build docs/_build > make[1]: Leaving directory '/<>' > dpkg-source -b . > dpkg-source: warning: upstream signing key but no upstream tarball signature > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building sshuttle using existing > ./sshuttle_1.1.0.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > sshuttle-1.1.0/sshuttle/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/sshuttle_1.1.0-1.diff.ZSRWtN > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T05:53:09Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/sshuttle_1.1.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=lu...@debian.org=1=1=1=1#results 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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: sshuttle Source-Version: 1.1.1-1 Done: Brian May We believe that the bug you reported is fixed in the latest version of sshuttle, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian May (supplier of updated sshuttle 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: Tue, 06 Sep 2022 08:44:19 +1000 Source: sshuttle Architecture: source Version: 1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Brian May Changed-By: Brian May Closes: 1015044 Changes: sshuttle (1.1.1-1) unstable; urgency=medium . * New upstream version. * Removes setuptools-scm. Closes: #1015044. Checksums-Sha1: 4c746b393169b79411b0cac81c1fc9a566189520 1964 sshuttle_1.1.1-1.dsc 35a428e61ea2d109055aeec6232031845b5f3bf2 89103 sshuttle_1.1.1.orig.tar.gz 9d79d645020620d84734fb2ec43066cd08bff8c7 6244 sshuttle_1.1.1-1.debian.tar.xz 0dcc116235687c0ad00e04a057294276f36aac42 7926 sshuttle_1.1.1-1_source.buildinfo Checksums-Sha256: 74e73ada082441d57945a09001185976747cf43f47727d32a63b2de6d779367d 1964 sshuttle_1.1.1-1.dsc 87b6343da4b7ea164cc1638a3ff25c41cf9dbc70bbc84bc4df8c41f963a4b0b9 89103 sshuttle_1.1.1.orig.tar.gz 6dc1121d7356a06f73a44dc8f9d065a779057953225769bf473d0f43fafb3676 6244 sshuttle_1.1.1-1.debian.tar.xz 2d07c528b57adeb2d6d93a367fc3c732e68504ceb92286099e4d8ebcebdbe0f5 7926 sshuttle_1.1.1-1_source.buildinfo Files: 67fb40652f326c46a9cf26bd38ed4873 1964 net optional sshuttle_1.1.1-1.dsc 0c3f6c29042b410733feb0c4677e3390 89103 net optional
Processed: bug 1016825 is forwarded to https://salsa.debian.org/r-pkg-team/r-cran-rsconnect/-/merge_requests/1
Processing commands for cont...@bugs.debian.org:
> forwarded 1016825
> https://salsa.debian.org/r-pkg-team/r-cran-rsconnect/-/merge_requests/1
Bug #1016825 {Done: Paul Gevers } [src:r-cran-rsconnect]
src:r-cran-rsconnect: fails to migrate to testing for too long: autopkgtest
regression
Set Bug forwarded-to-address to
'https://salsa.debian.org/r-pkg-team/r-cran-rsconnect/-/merge_requests/1'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1019233: conserver FTBFS on IPV6-only buildds
Source: conserver Version: 8.2.4-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=conserver=amd64 ... dh_auto_test -a make -j4 test VERBOSE=1 make[1]: Entering directory '/<>' ( cd test && ./dotest ) || exit 1 starting conserver...pid 16243 executing test #1...failed (diffs in test1.diff) executing test #2...failed (diffs in test2.diff) executing test #3...failed (diffs in test3.diff) executing test #4...failed (diffs in test4.diff) executing test #5...failed (diffs in test5.diff) moving in second config file executing test #6...failed (diffs in test6.diff) executing test #7...failed (diffs in test7.diff) executing test #8...failed (diffs in test8.diff) executing test #9...failed (diffs in test9.diff) executing test #10...failed (diffs in test10.diff) executing test #11...failed (diffs in test11.diff) executing test #12...failed (diffs in test12.diff) executing test #13...failed (diffs in test13.diff) executing test #14...failed (diffs in test14.diff) executing test #15...failed (diffs in test15.diff) make[1]: *** [Makefile:36: test] Error 1
Processed: reassign 1015044 to sshuttle
Processing commands for cont...@bugs.debian.org: > reassign 1015044 sshuttle 1.0.1-1 Bug #1015044 [sshutle] sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Warning: Unknown package 'sshutle' Bug reassigned from package 'sshutle' to 'sshuttle'. No longer marked as found in versions 1.0.1-1. Ignoring request to alter fixed versions of bug #1015044 to the same values previously set Bug #1015044 [sshuttle] sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 There is no source info for the package 'sshuttle' at version '1.0.1-1' with architecture '' Unable to make a source version for version '1.0.1-1' Marked as found in versions 1.0.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: roger-router: bump severity to serious for ongoing evolution transition
Processing control commands: > severity -1 serious Bug #1017985 [src:roger-router] roger-router: Fails to build with evolution-data-server 3.45 Severity set to 'serious' from 'important' -- 1017985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: chatty: bump severity to serious for ongoing evolution transitions
Processing control commands: > severity -1 serious Bug #1018134 [src:chatty] chatty: Fails to build with evolution-data-server 3.45 Severity set to 'serious' from 'important' -- 1018134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003928: marked as done (gnome-todo: Gnome-ToDo does not longer work when change date of an entry)
Your message dated Mon, 05 Sep 2022 22:03:57 + with message-id and subject line Bug#1003928: fixed in endeavour 42.0-4 has caused the Debian Bug report #1003928, regarding gnome-todo: Gnome-ToDo does not longer work when change date of an entry 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.) -- 1003928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-todo Version: 41.0-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** When I update a date for an entry the app does not work. It is blocked and I have to kill it -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (710, 'unstable'), (670, 'testing'), (660, 'experimental'), (600, 'stable'), (500, 'stable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, arm64 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-todo depends on: ii evolution-data-server 3.42.3-1 ii gnome-todo-common 41.0-1 ii gsettings-desktop-schemas 41.0-2 ii libadwaita-1-0 1.0.1-1 ii libc6 2.34-0experimental2 ii libecal-2.0-1 3.42.3-1 ii libedataserver-1.2-26 3.42.3-1 ii libgirepository-1.0-1 1.70.0-3 ii libglib2.0-0 2.71.0-2 ii libgoa-1.0-0b 3.40.1-2 ii libgraphene-1.0-0 1.10.6+dfsg1-2 ii libgtk-4-1 4.6.0+ds1-3 ii libical3 3.0.12-1 ii libpango-1.0-0 1.50.3+ds1-3 ii libpeas-1.0-0 1.30.0-4 ii libportal-gtk4-1 0.5-2 ii libportal1 0.5-2 gnome-todo recommends no packages. gnome-todo suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: endeavour Source-Version: 42.0-4 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of endeavour, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated endeavour 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, 05 Sep 2022 17:49:13 -0400 Source: endeavour Built-For-Profiles: noudeb Architecture: source Version: 42.0-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 1003928 Changes: endeavour (42.0-4) unstable; urgency=medium . * Cherry-pick patch to fix date picker (Closes: #1003928) * Build against libsoup3 libraries Checksums-Sha1: c9750a6b670460f9a30997ef77cbae43c35c8d4f 2456 endeavour_42.0-4.dsc 8bfb4a263f9bc494691bd7797798fcd2140d3ae0 7664 endeavour_42.0-4.debian.tar.xz 6a01a0d65e7ab588489ef319ef7546489a2d91da 22187 endeavour_42.0-4_source.buildinfo Checksums-Sha256: 9b80fb0298edf3cd61e214b009614f458cc9af911a0028f1ece484403ca6aead 2456 endeavour_42.0-4.dsc 0dca80416c5ca5543504535e612bfd11a32ab5a94876605b9a755fc7ef8f5a61 7664 endeavour_42.0-4.debian.tar.xz 205c56b19760632521f1fcb7317a2a06991c615b9a26a900bdca2559e051af1f 22187 endeavour_42.0-4_source.buildinfo Files: 8af64fc471888bf560acc80865bfd0ea 2456 gnome optional endeavour_42.0-4.dsc 7f82b771808984b70ac66f68b1de02e1 7664 gnome optional endeavour_42.0-4.debian.tar.xz 449cf2663b3237f6da60ab6de738b293 22187 gnome optional endeavour_42.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMWbv4ACgkQ5mx3Wuv+ bH2/QhAAqNehhf+FxXf9AUh3GKRw+M8DwOZmLXXHYFOkjn9cP0MuqYQVEIf02DL5
Bug#1019151: marked as done (pydevd: flaky autopkgtest on armel: timeout too short?)
Your message dated Mon, 05 Sep 2022 21:54:27 + with message-id and subject line Bug#1019151: fixed in pydevd 2.8.0+git20220826.8ee4065+ds-1 has caused the Debian Bug report #1019151, regarding pydevd: flaky autopkgtest on armel: timeout too short? 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.) -- 1019151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pydevd Version: 2.8.0+git20220602.1b1fb8b+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on armel. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/p/pydevd/testing/armel/ https://ci.debian.net/data/autopkgtest/testing/armel/p/pydevd/25054651/log.gz OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pydevd Source-Version: 2.8.0+git20220826.8ee4065+ds-1 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of pydevd, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated pydevd 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: Mon, 05 Sep 2022 21:56:24 +0100 Source: pydevd Architecture: source Version: 2.8.0+git20220826.8ee4065+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julian Gilbey Closes: 1019151 Changes: pydevd (2.8.0+git20220826.8ee4065+ds-1) unstable; urgency=medium . * New upstream snapshot * Skip another failing test on armel * Mark autopkgtests as flaky on architectures other than amd64 and i386 (closes: #1019151) * Improve tests based on Spyder test process Checksums-Sha1: 706008ba1c0b3ec4c920a0d25cef9fa0c221a700 3215 pydevd_2.8.0+git20220826.8ee4065+ds-1.dsc ae12e019ffc2d168fe90b66a42e61de101418e60 900348 pydevd_2.8.0+git20220826.8ee4065+ds.orig.tar.xz 0106043398c07bad6a863f726d9c9d9894959bc9 20004 pydevd_2.8.0+git20220826.8ee4065+ds-1.debian.tar.xz 3805432534fa73bb5662951202e30c82aa9a2ce1 16118 pydevd_2.8.0+git20220826.8ee4065+ds-1_amd64.buildinfo Checksums-Sha256: 54946b6ed6ec4a0607bb8ece17f215535723f71d5dd3b7042e40277e5fd0924a 3215 pydevd_2.8.0+git20220826.8ee4065+ds-1.dsc dbb9bca4b8494adbb0174e23208043e230d4f3cf7a1a4f678ee5159be9bb18c8 900348 pydevd_2.8.0+git20220826.8ee4065+ds.orig.tar.xz f064fbb7ad5a9b03ba1d46ba5fdb76256f4929b307a3d92255c923dc69d13f08 20004 pydevd_2.8.0+git20220826.8ee4065+ds-1.debian.tar.xz ebe4ebaac4c7500b8141f9c897be59f5354f643d7d137ca6ad19234589a38f17 16118 pydevd_2.8.0+git20220826.8ee4065+ds-1_amd64.buildinfo Files: b1335f8f611b74e4b66787194b5f0b55 3215 python optional pydevd_2.8.0+git20220826.8ee4065+ds-1.dsc 5c28597750d7d16972758cb706f5885d 900348 python optional pydevd_2.8.0+git20220826.8ee4065+ds.orig.tar.xz 395c6e8e35a580ea505823a34ad39503 20004 python optional pydevd_2.8.0+git20220826.8ee4065+ds-1.debian.tar.xz e5cde622f77451f862277fa3f3e17ed1 16118 python optional pydevd_2.8.0+git20220826.8ee4065+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmMWaTcPHGpkZ0BkZWJp YW4ub3JnAAoJEGlcQpMWwHv+AtIQAJW8cxTvz1SEDzfty67RO198/n233XYz1abj 9WtGkURwo2r4bajOAFDIRq/E/BqhB1ons7QjbB/rHQGCJVOEImdLC5oZs6hdW//n jyvVR+ervX6Rb/k6mg9bVFrgm6JbWQkStAojx8qmPu5R1MoqANGFUOfOiXsnT6M5 N4IR1bNwMMySverOxEibmNWaDRKJLelRaEObFPZvyfkOfgzTOUlGoMUSn+EWAAB8 BVXge6wfHw9T3PfycOiy+xCW1OHGRTTEMppG0G4Aox9AQNWxLo8WWxfRLZL4Vqgr I6iLMFmQFZ9Ul53+3eZ8pvqCVB2WdV4VoLWLCaOITpJK5eTqYmp8u1omy3eUdxqi 8wBjNBJwl+YbV6kWsWT2o1Knpw183YoLiwemdRlNOb0+a0KvjMZ52Lb7AFC4vTkZ
Processed (with 1 error): Re: Bug#1019050: dh_fortran_mod postrm template: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
Processing commands for cont...@bugs.debian.org: > reassign 1019050 dh-fortran-mod Bug #1019050 [libsuperlu-dist-dev] libsuperlu-dist-dev: postrm failure Bug reassigned from package 'libsuperlu-dist-dev' to 'dh-fortran-mod'. No longer marked as found in versions superlu-dist/8.1.0+dfsg1-2. Ignoring request to alter fixed versions of bug #1019050 to the same values previously set > retitle 1019050 postrm template: failed to remove Bug #1019050 [dh-fortran-mod] libsuperlu-dist-dev: postrm failure Changed Bug title to 'postrm template: failed to remove' from 'libsuperlu-dist-dev: postrm failure'. > '/usr/lib/*/fortran/gfortran': No such file or directory Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1019050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019050: dh_fortran_mod postrm template: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
reassign 1019050 dh-fortran-mod retitle 1019050 postrm template: failed to remove '/usr/lib/*/fortran/gfortran': No such file or directory thanks This bug does not belong to libsuperlu-dist-dev. The postrm code addressing removal of /usr/lib/*/fortran/gfortran comes from the template provided by dh-fortran-mod. Note the preinstall template refers to fortran/gfortran-* where postrm refers to fortran/gfortran.
Processed: Bug#1003928 marked as pending in gnome-todo
Processing control commands: > tag -1 pending Bug #1003928 [src:endeavour] gnome-todo: Gnome-ToDo does not longer work when change date of an entry Added tag(s) pending. -- 1003928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017491: marked as done (gnome-maps: Switch to libsoup3)
Your message dated Mon, 05 Sep 2022 21:49:29 + with message-id and subject line Bug#1017491: fixed in gnome-maps 43~rc-1 has caused the Debian Bug report #1017491, regarding gnome-maps: Switch to libsoup3 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.) -- 1017491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-maps Severity: serious Version: 42.3-2 Forwarded: https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/457 gnome-maps needs to switch to libsoup3. Currently it uses libsoup2.4 and depends on several libraries that are being switched to use libsoup3. It's not possible for an app to link against both libsoup2.4 and libsoup3. We also don't intend to maintain multiple copies of those libraries to preserve the libsoup2.4 build option. Therefore, I believe we will need to temporarily remove gnome-maps from Testing. I believe gnome-maps will be ported to libsoup3 in time for Debian 12. Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Source: gnome-maps Source-Version: 43~rc-1 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of gnome-maps, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gnome-maps 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, 05 Sep 2022 17:27:40 -0400 Source: gnome-maps Built-For-Profiles: noudeb Architecture: source Version: 43~rc-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 1017491 Changes: gnome-maps (43~rc-1) unstable; urgency=medium . * New upstream release * debian/control.in: Bump minimum libshumate to 1.0.0~beta * Drop librest patch: applied in new release * Add patch to not attempt to install test gresource file * Upload to unstable (Closes: #1017491) Checksums-Sha1: 2d090c6b667f96e5228b28a2dafe843171a4d143 2618 gnome-maps_43~rc-1.dsc dfca142dd37e5082e3e4aae5a03b85e3c6d093cb 2332296 gnome-maps_43~rc.orig.tar.xz ef1cb15724a944871949e6d30b05d9ca8ed53264 8680 gnome-maps_43~rc-1.debian.tar.xz 82e6d7e1d601a9a23e38b9fa0b63b2df3fca495a 18117 gnome-maps_43~rc-1_source.buildinfo Checksums-Sha256: 6eb46a40ff8e86401a6bab8906384f22135e73c229318132ea51463f1f799e06 2618 gnome-maps_43~rc-1.dsc 341a92f0e4e8fa539a3a082b7585d803fe0e77b6f2885ef3b6af736712924399 2332296 gnome-maps_43~rc.orig.tar.xz babd7c3c22369f339d88b36edec76e5beacdd57bbf2ad8e0dfe670213b3ca99e 8680 gnome-maps_43~rc-1.debian.tar.xz a04124f73139fce7dede4f0082044af04a26fbcd5e1c8feaf78f3080de17639f 18117 gnome-maps_43~rc-1_source.buildinfo Files: 19f876eba5f3c4ab443f6361222f8c41 2618 gnome optional gnome-maps_43~rc-1.dsc a9c8dc8168eea2bc0b0e276c42332a3a 2332296 gnome optional gnome-maps_43~rc.orig.tar.xz 68a72c84a345a7540cbb99dad32c09ca 8680 gnome optional gnome-maps_43~rc-1.debian.tar.xz bf798c11b0cc528279a59c06fbd11ad5 18117 gnome optional gnome-maps_43~rc-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMWaiMACgkQ5mx3Wuv+ bH2Apw/+OzOc8KrV/YyGjXK69TOv/u/eVwBmx+DrL9ThwEkFdlC2ivhcrAbT6P2V uvHBJMp/yhvkqUd4QNHxgxPQCQF0EBoQxb5JAzTnQr50y+B0IZ5Eg6yTbYLAooRq y2Nn1wHU0xaHkBjQOvhG1SbVvH5T0muQhtO0EUXC8KTwaNduoDCYHemKSVve+y2x shtzI07CgoH6bXQHXalW+DCsTMgTcuB6cAJ78CXnO9rUN05tGXLAzX7jfgUa0zG4 Ys/WhUfSZyxRcmPxmmcNSt1l3gOVRveeXGnvJhXgBLVvvmN5sBtGOAMoTNzQ47zz SRMrFaNjnivZxYOUYP+7p9M4qLtJzBHqk3wrgtXRPBSewnyZVunh9D8lScBRJIZj kPs9nL8WfBVV0gUyndV8WIpgCrFHBbWsKR9zZACa3qS1W/FVBEDp0qk4gRGYG0Is A0WPpfWfuUigNEj5KnqUGJWxyEmWzl4ZviXa5Qt+lhoyx3/5Ry73PtAsd7KUj0i2 Dgv49IPS5lgFlaLsXRl/kiwFwh5alj2GYR2ukXXfFiDmHM3ZEPgWJcQcNqI7n+y/ kV4GKhq/eVDx6SQFhRmXI8j1BrES4gLnZIkq8+PKXFCUDxzE8AnoXJRHPrLuSVzx JiDEsyOm58cZdU2/UJjfdTF/YwFEqUxWn17yTwntSUIDVqA4xzY= =eJZM -END PGP SIGNATURE End Message ---
Bug#1003928: marked as pending in gnome-todo
Control: tag -1 pending Hello, Bug #1003928 in gnome-todo 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/gnome-team/endeavour/-/commit/a8ee7678c92547dbcee6c3f4642793d857bf4d6a Cherry-pick patch to fix date picker Closes: #1003928 (this message was generated automatically) -- Greetings https://bugs.debian.org/1003928
Bug#1017053: marked as done (fenics-dolfinx: FTBFS on mips64el)
Your message dated Mon, 05 Sep 2022 21:34:37 + with message-id and subject line Bug#1017053: fixed in fenics-dolfinx 1:0.4.1-5 has caused the Debian Bug report #1017053, regarding fenics-dolfinx: FTBFS on mips64el 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.) -- 1017053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fenics-dolfinx Version: 1:0.4.1-4 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer Your package FTBFS on mips64el during the recent rebuilds for Python 3.10 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.debian.org/status/package.php?p=fenics-dolfinx Traceback (most recent call last): File "/<>/python/setup.py", line 67, in setup(name='fenics-dolfinx', File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in setup return distutils.core.setup(**attrs) File "/usr/lib/python3.10/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command cmd_obj.run() File "/usr/lib/python3.10/distutils/command/build.py", line 135, in run self.run_command(cmd_name) File "/usr/lib/python3.10/distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command cmd_obj.run() File "/<>/python/setup.py", line 41, in run self.build_extension(ext) File "/<>/python/setup.py", line 64, in build_extension subprocess.check_call(['cmake', '--build', '.'] + build_args, cwd=self.build_temp, env=env) File "/usr/lib/python3.10/subprocess.py", line 369, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j3']' returned non-zero exit status 2. chrpath -d /<>/debian/tmp*/usr/lib/python*/dist-packages/dolfinx/*.so open: No such file or directory elf_open: Invalid argument --- End Message --- --- Begin Message --- Source: fenics-dolfinx Source-Version: 1:0.4.1-5 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of fenics-dolfinx, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated fenics-dolfinx 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: Mon, 05 Sep 2022 22:54:50 +0200 Source: fenics-dolfinx Architecture: source Version: 1:0.4.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Closes: 1017053 Changes: fenics-dolfinx (1:0.4.1-5) unstable; urgency=medium . * apply build flag -Wno-error=maybe-uninitialized on mips64el to prevent xtensor (xtl/xsequence.hpp) causing build failure. Closes: #1017053 Checksums-Sha1: 56a7f135a0792525b52dfb720a90e5f9848849f4 3953 fenics-dolfinx_0.4.1-5.dsc 0c56cb3a723a280417863afb23298bcf848e4a7b 35504 fenics-dolfinx_0.4.1-5.debian.tar.xz 0ddd026df190aa8c32ed47f5bb7f85336fab7ef7 19257 fenics-dolfinx_0.4.1-5_source.buildinfo Checksums-Sha256: 5e9c240c59f9209eea9f849198f338583b06896b21ed93eb5270fcb8cfdcffd3 3953 fenics-dolfinx_0.4.1-5.dsc 3a0f6492c62bbbd1dda017a9aecef412af4fecafd1299e7b5206f1236cc965d3 35504 fenics-dolfinx_0.4.1-5.debian.tar.xz c6ce148e79adf7ea244ccad75c1fcdd36e82c0ba4befa4292d5666d75f1afcb6 19257 fenics-dolfinx_0.4.1-5_source.buildinfo Files: 575cc5683fc2a3f848c2bbc9d3d1cd84 3953 math optional fenics-dolfinx_0.4.1-5.dsc 976ecd407c2ca85559becd74f66102e4 35504 math optional fenics-dolfinx_0.4.1-5.debian.tar.xz 5e94fa14ca4483e6ac45c590355d0888 19257 math optional fenics-dolfinx_0.4.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmMWYrQUHGRwYXJzb25z QGRlYmlhbi5vcmcACgkQVz7x5L1aAfrJDw/8CEp/wMo8z9cPuEi6TWAYbvnp4EA8
Bug#1019230: Current version is EOLed
Source: snort Version: 2.9.15.1-6 Severity: serious Per https://blog.snort.org/2021/07/29150-has-reached-its-end-of-life.html the version currently in sid is EOLed and no longer compatible with current rule updates. In general snort seems unsuitable for standard stable given that the engine needs to keep up with rule sets, so if it should be included in bookworm, it should probably get updated via -updates as we do for clamav. Cheers, Moritz -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1019061: Root cause is #1019061
Hi, thanks for bug report. The main problem is #1017698. Gnuplot cannot be built due to missing build-dep on emacs-nox. Regards Anton
Processed: retitle 1017794 to modemmanager: corrupted double-linked list after upgrade to glib2.0 2.73.x
Processing commands for cont...@bugs.debian.org: > retitle 1017794 modemmanager: corrupted double-linked list after upgrade to > glib2.0 2.73.x Bug #1017794 [modemmanager] glib2.0: 2.73 breaks modemmanager Changed Bug title to 'modemmanager: corrupted double-linked list after upgrade to glib2.0 2.73.x' from 'glib2.0: 2.73 breaks modemmanager'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1017794
Processing commands for cont...@bugs.debian.org: > affects 1017794 - modemmanager Bug #1017794 [modemmanager] glib2.0: 2.73 breaks modemmanager Removed indication that 1017794 affects modemmanager > thanks Stopping processing here. Please contact me if you need assistance. -- 1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1017794 is forwarded to https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/876
Processing commands for cont...@bugs.debian.org: > forwarded 1017794 > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/876 Bug #1017794 [modemmanager] glib2.0: 2.73 breaks modemmanager Changed Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/876' from 'https://gitlab.gnome.org/GNOME/glib/-/issues/2729'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 1017794 in glib2.0/2.73.3-2
Processing commands for cont...@bugs.debian.org: > notfound 1017794 glib2.0/2.73.3-2 Bug #1017794 [modemmanager] glib2.0: 2.73 breaks modemmanager Ignoring request to alter found versions of bug #1017794 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1017794 to modemmanager
Processing commands for cont...@bugs.debian.org: > reassign 1017794 modemmanager 1.18.10-1 Bug #1017794 [src:glib2.0] glib2.0: 2.73 breaks modemmanager Bug reassigned from package 'src:glib2.0' to 'modemmanager'. No longer marked as found in versions glib2.0/2.73.3-2. Ignoring request to alter fixed versions of bug #1017794 to the same values previously set Bug #1017794 [modemmanager] glib2.0: 2.73 breaks modemmanager Marked as found in versions modemmanager/1.18.10-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017148: soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression
Control: tags -1 + patch upstream fixed-upstream
Control: forwarded -1 https://github.com/SOCI/soci/pull/886
On 14/08/22 09:18 AM, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> > /<>/tests/catch.hpp:6490:33: error: size of array
> > ‘altStackMem’ is not an integral constant-expression
> > 6490 | static char altStackMem[SIGSTKSZ];
> > | ^~~~
> > /<>/tests/catch.hpp:6541:45: error: size of array
> > ‘altStackMem’ is not an integral constant-expression
> > 6541 | char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
> > | ^~~~
This is likely fixed with a new upstream release
Version 4.0.3 differs from 4.0.2 in the following ways:
Changes affecting all or multiple backends:
- Fix opening sessions from pool (#891).
- Fix default backend search path (#928).
>- Fix build with latest glibc versions where SIGSTKSZ is not constant
(#886).
- Document using SOCI as a CMake subdirectory (#925).
- Document using SOCI with Conan (#877).
The fix looks easy enough
https://github.com/SOCI/soci/pull/886/commits/7719b5a8242a5ec016f73666a51e80b3bd7f8956
@William: Any opinion on targeted fix vs. new upstream version?
As one of the package I somewhat care about (linphone) is affected by
this removal from testing I would NMU a targeted fix end of September.
Bernhard
Processed: Re: Bug#1017148: soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression
Processing control commands: > tags -1 + patch upstream fixed-upstream Bug #1017148 [src:soci] soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression Added tag(s) patch, fixed-upstream, and upstream. > forwarded -1 https://github.com/SOCI/soci/pull/886 Bug #1017148 [src:soci] soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression Set Bug forwarded-to-address to 'https://github.com/SOCI/soci/pull/886'. -- 1017148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019224: sssd: autopkgtest regression
Source: sssd Version: 2.7.3-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of sssd the autopkgtest of sssd fails in testing when that autopkgtest is run with the binary packages of sssd from unstable. It passes when run with only packages from testing. In tabular form: passfail sssd from testing2.7.3-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration 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=sssd https://ci.debian.net/data/autopkgtest/testing/amd64/s/sssd/25725560/log.gz + . debian/tests/util + . debian/tests/common-tests + mydomain=example.com + myhostname=ldap.example.com + mysuffix=dc=example,dc=com + admin_dn=cn=admin,dc=example,dc=com + admin_pw=secret + ldap_user=testuser1 + ldap_user_pw=testuser1secret + ldap_group=ldapusers + adjust_hostname ldap.example.com + local myhostname=ldap.example.com + echo ldap.example.com + hostname ldap.example.com + grep -qE ldap.example.com /etc/hosts + echo 127.0.1.10 ldap.example.com + reconfigure_slapd + debconf-set-selections + rm -rf /var/backups/*slapd* /var/backups/unknown*ldapdb + dpkg-reconfigure -fnoninteractive -pcritical slapd Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.5.12+dfsg-2+b1... done. Moving old database directory to /var/backups: - directory unknown... done. Creating initial configuration... done. Creating LDAP directory... done. + generate_certs ldap.example.com + local cn=ldap.example.com + local cert=/etc/ldap/server.pem + local key=/etc/ldap/server.key + local cnf=/etc/ldap/openssl.cnf + cat + openssl req -new -x509 -nodes -out /etc/ldap/server.pem -keyout /etc/ldap/server.key -config /etc/ldap/openssl.cnf .. - + chmod 0640 /etc/ldap/server.key + chgrp openldap /etc/ldap/server.key + [ ! -f /etc/ldap/server.pem ] + [ ! -f /etc/ldap/server.key ] + enable_ldap_ssl + cat + cat + ldapmodify -H ldapi:/// -Y EXTERNAL -Q modifying entry "cn=config" + populate_ldap_rfc2307 + cat + ldapadd -x -D cn=admin,dc=example,dc=com -w secret adding new entry "ou=People,dc=example,dc=com" adding new entry "ou=Group,dc=example,dc=com" adding new entry "uid=testuser1,ou=People,dc=example,dc=com" adding new entry "cn=testuser1,ou=Group,dc=example,dc=com" adding new entry "cn=ldapusers,ou=Group,dc=example,dc=com" + configure_sssd_ldap_rfc2307 + cat + chmod 0600 /etc/sssd/sssd.conf + systemctl restart sssd + enable_pam_mkhomedir + grep -qE ^session.*pam_mkhomedir\.so /etc/pam.d/common-session + echo session optional pam_mkhomedir.so + run_common_tests + echo Assert local user databases do not have our LDAP test data + check_local_user testuser1 + local local_user=testuser1 + grep -q ^testuser1 /etc/passwd Assert local user databases do not have our LDAP test data + check_local_group testuser1 + local local_group=testuser1 + grep -q ^testuser1 /etc/group + check_local_group ldapusers + local local_group=ldapusers + grep -q ^ldapusers /etc/group + echo The LDAP user is known to the system via getent + check_getent_user testuser1 + local getent_user=testuser1 + local output The LDAP user is known to the system via getent + getent passwd testuser1 + output= autopkgtest [23:15:03]: test ldap-user-group-ldap-auth OpenPGP_signature Description: OpenPGP digital signature
Bug#1018016: bind9-libs not found for sid
Hi, I’ve recently moved, so everything is in but of disarray including my builder machine. The git repository should be up to date, so if this cannot wait a day or two until I connect rest of my network, anybody should be able to build and upload new upstream version using git-buildpackage. Alternatively, just wait a few days, I am almost there re-connecting stuff… I just came back from vacation and stumbled over this, sorry I couldn't help earlier. You had uploaded 9.18.6-1, but somehow this ended up as an amd64 upload binary to unstable, so it did not migrate. And it did not migrate because a binNMU to bind-dyndb-ldap is necessary, see #1014503. I have just made a no-change source-only upload, so the first problem should be resolved. For the second I have filed Bug#1019220 . Now, I'm still utterly confused how this problem could have happened at all. I was able to verify at this point that sid was indeed lacking bind9-libs:amd64. But it was built on the buildds https://buildd.debian.org/status/fetch.php?pkg=bind9=amd64=1%3A9.18.4-2=1657022678=0 and (due to the migration issues) the package version that was lacking in sid is still present in testing, including bind9-libs:amd64 bind9-libs | 1:9.18.4-2 | testing| amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x https://packages.debian.org/bookworm/bind9-libs http://ftp.de.debian.org/debian/pool/main/b/bind9/bind9-libs_9.18.4-2_amd64.deb http://snapshot.debian.org/package/bind9/1%3A9.18.4-2/#bind9-libs_1:3a:9.18.4-2 Bernhard
Bug#1019223: python-pytest-asyncio breaks python-channels-redis autopkgtest: async_generator' object has no attribute 'send'
Source: python-pytest-asyncio, python-channels-redis
Control: found -1 python-pytest-asyncio/0.19.0-1
Control: found -1 python-channels-redis/3.3.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-pytest-asyncio the autopkgtest of
python-channels-redis fails in testing when that autopkgtest is run with
the binary packages of python-pytest-asyncio from unstable. It passes
when run with only packages from testing. In tabular form:
passfail
python-pytest-asyncio from testing0.19.0-1
python-channels-redis from testing3.3.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of
python-pytest-asyncio to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-pytest-asyncio
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-channels-redis/25749566/log.gz
= test session starts
==
platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.yuamnrh_/downtmp/autopkgtest_tmp
plugins: asyncio-0.19.0
asyncio: mode=strict
collected 66 items / 34 deselected / 32 selected
tests/test_core.py F.F.F.FF...FF..
[ 84%]
tests/test_pubsub.py F
[100%]
=== FAILURES
===
__ test_send_receive
___
channel_layer =
@pytest.mark.asyncio
async def test_send_receive(channel_layer):
"""
Makes sure we can send a message to a normal channel then
receive it.
"""
await channel_layer.send(
"test-channel-1", {"type": "test.message", "text": "Ahoy-hoy!"}
)
E AttributeError: 'async_generator' object has no attribute 'send'
tests/test_core.py:83: AttributeError
__ test_send_capacity
__
channel_layer =
@pytest.mark.asyncio
async def test_send_capacity(channel_layer):
"""
Makes sure we get ChannelFull when we hit the send capacity
"""
await channel_layer.send("test-channel-1", {"type": "test.message"})
E AttributeError: 'async_generator' object has no attribute 'send'
tests/test_core.py:133: AttributeError
___ test_process_local_send_receive
channel_layer =
@pytest.mark.asyncio
async def test_process_local_send_receive(channel_layer):
"""
Makes sure we can send a message to a process-local channel
then receive it.
"""
channel_name = await channel_layer.new_channel()
E AttributeError: 'async_generator' object has no attribute
'new_channel'
tests/test_core.py:159: AttributeError
___ test_reject_bad_channel
channel_layer =
@pytest.mark.asyncio
async def test_reject_bad_channel(channel_layer):
"""
Makes sure sending/receiving on an invalic channel name fails.
"""
with pytest.raises(TypeError):
await channel_layer.send("=+135!", {"type": "foom"})
E AttributeError: 'async_generator' object has no attribute 'send'
tests/test_core.py:189: AttributeError
test_reject_bad_client_prefix
_
channel_layer =
@pytest.mark.asyncio
async def test_reject_bad_client_prefix(channel_layer):
"""
Makes sure receiving on a non-prefixed local channel is not
allowed.
"""
with pytest.raises(AssertionError):
await channel_layer.receive("not-client-prefix!local_part")
E AttributeError: 'async_generator' object has no attribute
'receive'
tests/test_core.py:200: AttributeError
___ test_group_send_capacity
___
channel_layer =
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fbf7021c100>
@pytest.mark.asyncio
async def test_group_send_capacity(channel_layer, caplog):
"""
Makes sure we dont group_send messages to channels that are
over capacity.
Make sure number of channels with full capacity are logged as
an exception to help debug errors.
"""
> channel = await channel_layer.new_channel()
E AttributeError: 'async_generator' object has no attribute
'new_channel'
tests/test_core.py:336: AttributeError
Processed: python-pytest-asyncio breaks python-channels-redis autopkgtest: async_generator' object has no attribute 'send'
Processing control commands: > found -1 python-pytest-asyncio/0.19.0-1 Bug #1019223 [src:python-pytest-asyncio, src:python-channels-redis] python-pytest-asyncio breaks python-channels-redis autopkgtest: async_generator' object has no attribute 'send' Marked as found in versions python-pytest-asyncio/0.19.0-1. > found -1 python-channels-redis/3.3.0-1 Bug #1019223 [src:python-pytest-asyncio, src:python-channels-redis] python-pytest-asyncio breaks python-channels-redis autopkgtest: async_generator' object has no attribute 'send' Marked as found in versions python-channels-redis/3.3.0-1. -- 1019223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019222: cdo: autopkgtest regression: cdo --help fails
Source: cdo Version: 2.0.6-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of cdo the autopkgtest of cdo fails in testing when that autopkgtest is run with the binary packages of cdo from unstable. It passes when run with only packages from testing. In tabular form: passfail cdofrom testing2.0.6-1 all others from testingfrom testing I copied some of the output at the bottom of this report Or I automatically would have if there was any. 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=cdo https://ci.debian.net/data/autopkgtest/testing/amd64/c/cdo/25724634/log.gz autopkgtest [22:16:26]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1019221: nut: autopkgtest regression: Could not find pidfile '/run/nut/upsd.pid'
Source: nut
Version: 2.8.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of nut the autopkgtest of nut fails in testing when
that autopkgtest is run with the binary packages of nut from unstable.
It passes when run with only packages from testing. In tabular form:
passfail
nutfrom testing2.8.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration 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=nut
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nut/25749540/log.gz
test_CVE_2012_2944 (__main__.BasicTest)
Test CVE-2012-2944 ... FAIL
test_daemons_pid (__main__.BasicTest)
Test daemons using PID files ... FAIL
test_daemons_service (__main__.BasicTest)
Test daemons using "service status" ... ok
test_upsc_device_list (__main__.BasicTest)
Test NUT client interface (upsc): device(s) listing ... ok
test_upsd_IPv4 (__main__.BasicTest)
Test upsd IPv4 reachability ... ok
test_upsd_IPv6 (__main__.BasicTest)
Test upsd IPv6 reachability ... ok
test_upsmon_notif (__main__.BasicTest)
Test upsmon notifications ... FAIL
test_upsrw (__main__.BasicTest)
Test upsrw ... FAIL
==
FAIL: test_CVE_2012_2944 (__main__.BasicTest)
Test CVE-2012-2944
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 386, in test_CVE_2012_2944
self._testDaemons(['upsd'])
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 277, in _testDaemons
self.assertTrue(os.path.exists(pidfile), warning)
AssertionError: False is not true : Could not find pidfile
'/run/nut/upsd.pid'
==
FAIL: test_daemons_pid (__main__.BasicTest)
Test daemons using PID files
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 307, in test_daemons_pid
self._testDaemons(daemons)
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 277, in _testDaemons
self.assertTrue(os.path.exists(pidfile), warning)
AssertionError: False is not true : Could not find pidfile
'/run/nut/upsd.pid'
==
FAIL: test_upsmon_notif (__main__.BasicTest)
Test upsmon notifications
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 355, in test_upsmon_notif
self.assertTrue('OB' in report, 'UPS Status: ' + report + 'should
be OB')
AssertionError: False is not true : UPS Status: Init SSL without
certificate database
Error: Driver not connected
should be OB
==
FAIL: test_upsrw (__main__.BasicTest)
Test upsrw
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 338, in test_upsrw
self._nut_setvar('ups.model', 'Test')
File
"/tmp/autopkgtest-lxc.3uxt85o1/downtmp/build.SgZ/src/debian/tests/test-nut.py",
line 284, in _nut_setvar
self.assertTrue(rc == 0, 'upsrw: ' + report)
AssertionError: False is not true : upsrw: Unexpected response from
upsd: ERR DRIVER-NOT-CONNECTED
--
Ran 8 tests in 50.981s
FAILED (failures=4)
Skipping private tests
autopkgtest [15:27:34]: test nut
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1015758: marked as done (ocaml-odoc: autopkgtests failures)
Your message dated Mon, 05 Sep 2022 19:52:19 + with message-id and subject line Bug#1015758: fixed in ocaml-odoc 2.1.1+dfsg-1 has caused the Debian Bug report #1015758, regarding ocaml-odoc: autopkgtests failures 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.) -- 1015758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-odoc Version: 2.1.0+dfsg-1 Severity: serious Hello, as said, the autopkgtests are now failing due to new ocaml or new ocaml libraries. https://ci.debian.net/data/autopkgtest/unstable/amd64/o/ocaml-odoc/23587053/log.gz Please have a look if the new upstream version is enough to fix it. autopkgtest [04:42:43]: test odoc-on-odoc: [--- File series fully applied, ends at patch debian/patches/no-vendored-js-highlight File "src/odoc/bin/main.ml", line 9, characters 51-64: 9 | let convert_syntax : Odoc_document.Renderer.syntax Arg.converter = ^ Error (alert deprecated): Cmdliner.Arg.converter Use Arg.conv' function instead. File "src/odoc/bin/main.ml", line 9, characters 51-64: 9 | let convert_syntax : Odoc_document.Renderer.syntax Arg.converter = ^ Error (alert deprecated): Cmdliner.Arg.converter Use Arg.conv' function instead. File "src/odoc/bin/main.ml", line 21, characters 60-73: 21 | let convert_directory ?(create = false) () : Fs.Directory.t Arg.converter = ^ Error (alert deprecated): Cmdliner.Arg.converter Use Arg.conv' function instead. File "src/odoc/bin/main.ml", line 73, characters 6-17: 73 | Arg.env_var "ODOC_WARN_ERROR" ~doc:(doc ^ " See option $(opt).") ^^^ Error (alert deprecated): Cmdliner.Arg.env_var Use Cmd.Env.info instead. File "src/odoc/bin/main.ml", line 82, characters 14-25: 82 | let env = Arg.env_var "ODOC_PRINT_WARNINGS" ~doc in ^^^ Error (alert deprecated): Cmdliner.Arg.env_var Use Cmd.Env.info instead. File "src/odoc/bin/main.ml", line 217, characters 4-13: 217 | Term.info "compile" ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 113, characters 13-22: 113 | val info : Term.info ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 236, characters 4-13: 236 | Term.info ~doc "support-files" ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 247, characters 4-13: 247 | Term.info ~doc "css" ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 288, characters 13-22: 288 | let info = Term.info ~doc:"Link odoc files together" "link" ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 253, characters 13-22: 253 | val info : Term.info ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 323, characters 18-29: 323 | let env = Arg.env_var "ODOC_SYNTAX" in ^^^ Error (alert deprecated): Cmdliner.Arg.env_var Use Cmd.Env.info instead. File "src/odoc/bin/main.ml", line 326, characters 17-22: 326 | & opt (pconv convert_syntax) Odoc_document.Renderer.OCaml ^ Error (alert deprecated): Cmdliner.Arg.pconv Use Arg.conv or Arg.conv' function instead. File "src/odoc/bin/main.ml", line 338, characters 6-15: 338 | Term.info ~doc R.renderer.name ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info instead. File "src/odoc/bin/main.ml", line 353, characters 18-29: 353 | let env = Arg.env_var "ODOC_SYNTAX" in ^^^ Error (alert deprecated): Cmdliner.Arg.env_var Use Cmd.Env.info instead. File "src/odoc/bin/main.ml", line 356, characters 17-22: 356 | & opt (pconv convert_syntax) Odoc_document.Renderer.OCaml ^ Error (alert deprecated): Cmdliner.Arg.pconv Use Arg.conv or Arg.conv' function instead. File "src/odoc/bin/main.ml", line 368, characters 6-15: 368 | Term.info ~doc (R.renderer.name ^ "-generate") ^ Error (alert deprecated): Cmdliner.Term.info Use Cmd.info
Bug#1017131: marked as done (aspcud: FTBFS: catch.hpp:10822:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’)
Your message dated Mon, 05 Sep 2022 19:03:51 +
with message-id
and subject line Bug#1017131: fixed in aspcud 1:1.9.6-1
has caused the Debian Bug report #1017131,
regarding aspcud: FTBFS: catch.hpp:10822:58: error: call to non-‘constexpr’
function ‘long int sysconf(int)’
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.)
--
1017131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspcud
Version: 1:1.9.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/libcudf/tests && /usr/bin/c++
> -DBOOST_ALL_NO_LIB -I/<>/libcudf -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -MD -MT
> libcudf/tests/CMakeFiles/test_libcudf.dir/main.cc.o -MF
> CMakeFiles/test_libcudf.dir/main.cc.o.d -o
> CMakeFiles/test_libcudf.dir/main.cc.o -c
> /<>/libcudf/tests/main.cc
> In file included from /usr/include/signal.h:328,
> from /<>/libcudf/tests/catch.hpp:8034,
> from /<>/libcudf/tests/main.cc:27:
> /<>/libcudf/tests/catch.hpp:10822:58: error: call to
> non-‘constexpr’ function ‘long int sysconf(int)’
> 10822 | static constexpr std::size_t sigStackSize = 32768 >= MINSIGSTKSZ
> ? 32768 : MINSIGSTKSZ;
> | ^~~
> In file included from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24:
> /usr/include/unistd.h:640:17: note: ‘long int sysconf(int)’ declared here
> 640 | extern long int sysconf (int __name) __THROW;
> | ^~~
> /<>/libcudf/tests/catch.hpp:10881:45: error: size of array
> ‘altStackMem’ is not an integral constant-expression
> 10881 | char FatalConditionHandler::altStackMem[sigStackSize] = {};
> | ^~~~
> make[3]: *** [libcudf/tests/CMakeFiles/test_libcudf.dir/build.make:107:
> libcudf/tests/CMakeFiles/test_libcudf.dir/main.cc.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/08/13/aspcud_1.9.5-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results
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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: aspcud
Source-Version: 1:1.9.6-1
Done: Ralf Treinen
We believe that the bug you reported is fixed in the latest version of
aspcud, 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 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ralf Treinen (supplier of updated aspcud 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: Mon, 05 Sep 2022 20:28:46 +0200
Source: aspcud
Architecture: source
Version: 1:1.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Ralf Treinen
Changed-By: Ralf Treinen
Closes: 1000852 1017131
Changes:
aspcud (1:1.9.6-1) unstable; urgency=medium
.
* New upstream release (closes: #1017131,#1000852).
* Standards-Version 4.6.1 (no change)
Checksums-Sha1:
42177623908ea967b23eb2ecdb2334a2cbae0642 1912 aspcud_1.9.6-1.dsc
d3e4fd636ff2c614d26a4e549b9b05b480ec2d19 70041232 aspcud_1.9.6.orig.tar.gz
61134911050464edbdcbfd2a83af3fe07b6e1509 5700 aspcud_1.9.6-1.debian.tar.xz
5fb0e0f8c97cb6882040f66ea7cb2a229f84666b 7072
Bug#1000852: marked as done (aspcud: FTBFS with glibc 2.34)
Your message dated Mon, 05 Sep 2022 19:03:51 + with message-id and subject line Bug#1000852: fixed in aspcud 1:1.9.6-1 has caused the Debian Bug report #1000852, regarding aspcud: FTBFS with glibc 2.34 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.) -- 1000852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aspcud Version: 1:1.9.5-1 Severity: important Hi Maintainer Your package uses a vendored copy of catch.hpp. It will FTBFS once glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer being defined. You could take this opportunity to switch to using the catch2 package [1] in Debian where this is already fixed. Regards Graham [1] https://tracker.debian.org/pkg/catch2 --- End Message --- --- Begin Message --- Source: aspcud Source-Version: 1:1.9.6-1 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of aspcud, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated aspcud 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: Mon, 05 Sep 2022 20:28:46 +0200 Source: aspcud Architecture: source Version: 1:1.9.6-1 Distribution: unstable Urgency: medium Maintainer: Ralf Treinen Changed-By: Ralf Treinen Closes: 1000852 1017131 Changes: aspcud (1:1.9.6-1) unstable; urgency=medium . * New upstream release (closes: #1017131,#1000852). * Standards-Version 4.6.1 (no change) Checksums-Sha1: 42177623908ea967b23eb2ecdb2334a2cbae0642 1912 aspcud_1.9.6-1.dsc d3e4fd636ff2c614d26a4e549b9b05b480ec2d19 70041232 aspcud_1.9.6.orig.tar.gz 61134911050464edbdcbfd2a83af3fe07b6e1509 5700 aspcud_1.9.6-1.debian.tar.xz 5fb0e0f8c97cb6882040f66ea7cb2a229f84666b 7072 aspcud_1.9.6-1_source.buildinfo Checksums-Sha256: cb6fced1927df7ca460a7c70503bb48fc23f32323e171f002f9e1d097c1e0dec 1912 aspcud_1.9.6-1.dsc 4dddfd4a74e4324887a1ddd7f8ff36231774fc1aa78b383256546e83acdf516c 70041232 aspcud_1.9.6.orig.tar.gz 6b94ea57e15148acc1404a72c09d0ef09d3f9d4633e49a7f5ed64022e1b548ae 5700 aspcud_1.9.6-1.debian.tar.xz 89b49b0880340d5f86cb56f21808bbfc727386fee4cb21a48c2a19203e43a968 7072 aspcud_1.9.6-1_source.buildinfo Files: 3f4395101ea1ee9b7cd1286986f2fdfe 1912 admin optional aspcud_1.9.6-1.dsc 40b2297316721f6e229f57aa3bfdd278 70041232 admin optional aspcud_1.9.6.orig.tar.gz c7b0ca8ead5d733b3e2f157e44364c3b 5700 admin optional aspcud_1.9.6-1.debian.tar.xz 2d6d28ecc8e64a4c2f697764627e0882 7072 admin optional aspcud_1.9.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAmMWQxYACgkQdFxHZtTK zf9IRQ/+OjH3YU8PFe+1zVmZRdjU46gHm3yLrBZpDOxudx22ajZbPCiENclGDZaM VMe5xw6yeVOJodGHpAotc9FWFMuSbq6pJUUCEaBiOAETToiQOukJbhqasxPLWKuC cDlhaf7F/dwNCCaolJIt2obZwYw3K6SDg0s8ZKFRybDoIua51sXYje9jE0E7QGte kDU6ZiR0za7Zv+xsKFwUamZwdsx9OP3GlrASISQ7YoBc7DrthpedcQZE0PK/L9ol Lmg345I+438CmVxCKushZhCVHHajti72osi7NesIgXrhSW2jZCBiNbGUUlDn79Ix A5uIITXFVil7nSNrKnNv2WUHJBwbUZbzbDBIYoj40pz1WGC4xtgnHgV1ed36dZju E9ayZxvzssFGNL9HbuwuGs6NbZ5XQYu60bPq+ZBMv+sSB545/6Z5JJzDrC05uRcx +fxB//RBYGb41Rb1Tp4eUrC38LDVxVPLuw1EhSLS4z+NweBW1wUJ7tZUPbgz4bBZ Nm8FEMukt4xnM7wBmz0VbTGP9CZ8n+6XczZYA2r9XhTj/HsYjExpo5tDEmAS53hx Q7BZLnzvnR11Wv+DgTENgP5UH6T1l6sv53LQyG0kANKl02MTUOsT7uTZsGaGFLSS +ICfsMs7oF2ZGwMAxuJ/fh1GufWoOTgtPwuqoDnT9kEr/TcXEik= =LveB -END PGP SIGNATURE End Message ---
Processed: hunt: diff for NMU version 1.5-6.2
Processing control commands: > tags 965588 + patch pending Bug #965588 [src:hunt] hunt: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965588 to the same tags previously set > tags 998955 + patch pending Bug #998955 [src:hunt] hunt: missing required debian/rules targets build-arch and/or build-indep Ignoring request to alter tags of bug #998955 to the same tags previously set -- 965588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965588 998955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: hunt: diff for NMU version 1.5-6.2
Processing control commands: > tags 965588 + patch pending Bug #965588 [src:hunt] hunt: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending and patch. > tags 998955 + patch pending Bug #998955 [src:hunt] hunt: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch and pending. -- 965588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965588 998955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018812: marked as done (pass-otp: removal of pass-otp makes files disappear from pass-extension-otp)
Your message dated Mon, 05 Sep 2022 18:49:02 + with message-id and subject line Bug#1018812: fixed in pass-otp 1.2.0-6 has caused the Debian Bug report #1018812, regarding pass-otp: removal of pass-otp makes files disappear from pass-extension-otp 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.) -- 1018812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pass-otp Version: 1.2.0-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Control: affects -1 + pass-extension-otp Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install pass-extension-otp/stable # (1) apt-get install pass-otp/testing apt-get remove pass-otp # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: /usr/lib/password-store/extensions/otp.bash /usr/share/bash-completion/completions/pass-otp /usr/share/man/man1/pass-otp.1.gz This is a serious bug violating policy 7.6, see https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces and also see the footnote that describes this incorrect behavior: https://www.debian.org/doc/debian-policy/ch-relationships.html#id13 The pass-otp package has the following relationships with pass-extension-otp: Conflicts: n/a Breaks:n/a Replaces: pass-extension-otp (<< 1.2.0-5~) >From the attached log (scroll to the bottom...): 0m56.3s ERROR: FAIL: After purging files have disappeared: /usr/lib/password-store/extensions/otp.bashowned by: pass-otp /usr/share/bash-completion/completions/pass-otpowned by: pass-otp /usr/share/man/man1/pass-otp.1.gz owned by: pass-otp 0m56.3s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/pass-extension-otp.list not owned cheers, Andreas pass-extension-otp=1.2.0-2_pass-otp=1.2.0-5.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pass-otp Source-Version: 1.2.0-6 Done: Philip Rinn We believe that the bug you reported is fixed in the latest version of pass-otp, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philip Rinn (supplier of updated pass-otp 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, 05 Sep 2022 20:22:12 +0200 Source: pass-otp Architecture: source Version: 1.2.0-6 Distribution: unstable Urgency: medium Maintainer: Philip Rinn Changed-By: Philip Rinn Closes: 1018812 Changes: pass-otp (1.2.0-6) unstable; urgency=medium . * Spell 'Breaks' correctly in d/control (closes: #1018812 * Mark tests depend on bash * Makr two tests failing due to bash 5.2~rc2 Checksums-Sha1: 398f6b64d183a23028e35df6d80d64050937aab3 2256 pass-otp_1.2.0-6.dsc 3457d092f60391c06335166f3e672582a682232a 25220 pass-otp_1.2.0-6.debian.tar.xz facbb1c204afd383595fbdec3957880c9d40145e 7266 pass-otp_1.2.0-6_amd64.buildinfo Checksums-Sha256: adc52b3c6c5762aa399d678866c5b73dfcd3697505eca2483dccbdb30e23395d 2256 pass-otp_1.2.0-6.dsc 3a5e695cae6c3b9a854644132ed1dce593043432d79f4f230b48119d7700efaf 25220 pass-otp_1.2.0-6.debian.tar.xz 138d7275739b086244a7ac245b3b67995adf6e70f73c288769dd9c68a6218a73 7266 pass-otp_1.2.0-6_amd64.buildinfo Files: 596726c80747b8953b25b16aee4fc5de 2256 admin optional pass-otp_1.2.0-6.dsc 707a480b1aa357a7ea6b79c5ab577b36 25220 admin optional pass-otp_1.2.0-6.debian.tar.xz 65b239f557a3ef827a7fb49780247a92 7266 admin optional pass-otp_1.2.0-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEK9jU45eVX3dG2zuJrWkWlnOTmCsFAmMWPywACgkQrWkWlnOT mCvWkRAAtZIfov+L/Mgblerhe2bmXlDo/01mMtSrfD7Q4U7T0Njbic9HKWSXMHi6 94XW/pojYTLlloJ2UDuyL5Cp8o3iBMsVgeAXShgpyRtyIe8W8SP1OXS5ha2b1Jh8
Bug#1017845: Fwd: Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-
Hi, I received the following mail which might be of interest for those debugging this issue: - Forwarded message from "Mark E. Shoulson" - Date: Mon, 5 Sep 2022 09:47:32 -0400 From: "Mark E. Shoulson" To: a...@debian.org Subject: Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el I'm not on the mailing list in question, came across your email while researching the same problem when I had it, and I might have something useful to contribute, in the form of a "golfed" minimal example that causes the problem, so you don't have to pore over huge libraries. My emacs, upon upgrading, did the exact same looping just when executing this: (fset 'yes-or-no-p (symbol-function 'y-or-n-p)) That's all it takes. Finally dawned on me to downgrade emacs. Just in case it helps. ~mark - End forwarded message - (And yes, I asked if I may forward this mail.) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: [bts-link] source package src:endeavour
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:endeavour > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1003928 (http://bugs.debian.org/1003928) > # Bug title: gnome-todo: Gnome-ToDo does not longer work when change date of > an entry > # * https://gitlab.gnome.org/World/Endeavour/-/issues/429 > # * remote status changed: opened -> closed > # * closed upstream > tags 1003928 + fixed-upstream Bug #1003928 [src:endeavour] gnome-todo: Gnome-ToDo does not longer work when change date of an entry Added tag(s) fixed-upstream. > usertags 1003928 - status-opened Usertags were: status-opened. There are now no usertags set. > usertags 1003928 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:glib2.0
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:glib2.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1017794 (http://bugs.debian.org/1017794) > # Bug title: glib2.0: 2.73 breaks modemmanager > # * https://gitlab.gnome.org/GNOME/glib/-/issues/2729 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1017794 + fixed-upstream Bug #1017794 [src:glib2.0] glib2.0: 2.73 breaks modemmanager Added tag(s) fixed-upstream. > usertags 1017794 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017032: awesome: diff for NMU version 4.3-5.1
Control: tags 1017032 + patch Control: tags 1017032 + pending Dear maintainer, I've prepared an NMU for awesome (versioned as 4.3-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru awesome-4.3/debian/changelog awesome-4.3/debian/changelog --- awesome-4.3/debian/changelog 2020-07-22 06:58:50.0 -0300 +++ awesome-4.3/debian/changelog 2022-09-05 13:10:29.0 -0300 @@ -1,3 +1,10 @@ +awesome (4.3-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/tests/control: Add restriction "allow-stderr". (Closes: #1017032) + + -- Marcos Talau Mon, 05 Sep 2022 13:10:29 -0300 + awesome (4.3-5) unstable; urgency=medium * Fix FTBFS with GCC 10. (Closes: #957027) diff -Nru awesome-4.3/debian/tests/control awesome-4.3/debian/tests/control --- awesome-4.3/debian/tests/control 2019-01-29 16:16:41.0 -0200 +++ awesome-4.3/debian/tests/control 2022-09-05 13:10:29.0 -0300 @@ -1,3 +1,4 @@ # lua5.2 is explicitely added, because 5.3 doesn't currently provide lua (#863036) Tests: integration.sh Depends: awesome, lua5.2, xvfb, dbus-x11, xterm, xfonts-base, x11-apps, x11-xserver-utils, x11-utils, gir1.2-gtk-3.0, build-essential, libxcb1-dev, libxcb-util0-dev, libxcb-icccm4-dev +Restrictions: allow-stderr
Processed: awesome: diff for NMU version 4.3-5.1
Processing control commands: > tags 1017032 + patch Bug #1017032 [src:awesome] awesome: flaky autopkgtest: sometimes reports on stderr: Could not resolve keysym XF86EmojiPicker Added tag(s) patch. > tags 1017032 + pending Bug #1017032 [src:awesome] awesome: flaky autopkgtest: sometimes reports on stderr: Could not resolve keysym XF86EmojiPicker Added tag(s) pending. -- 1017032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017818: elpa-jabber: Fails to compile with Emacs 28: Error: Wrong number of arguments: make-obsolete, 2
Yavor Doganov writes: > Package: elpa-jabber > Version: 0.8.92+git98dc8e-7 > Severity: serious > > The upgrade from Emacs 27 to 28 aborts because byte-compilation of > elpa-jabber fails with the following error(s): > > | In toplevel form: > | jabber-vcard.el:67:1: Error: Wrong number of arguments: make-obsolete, 2 > I've pushed a version that fixes this to https://salsa.debian.org/emacsen-team/emacs-jabber It depends on elpa-srv, which is currently NEW, but can also be downloaded from salsa. d
Processed: block 1017818 with 1019205
Processing commands for cont...@bugs.debian.org: > block 1017818 with 1019205 Bug #1017818 [elpa-jabber] elpa-jabber: Fails to compile with Emacs 28: Error: Wrong number of arguments: make-obsolete, 2 1017818 was not blocked by any bugs. 1017818 was not blocking any bugs. Added blocking bug(s) of 1017818: 1019205 > thanks Stopping processing here. Please contact me if you need assistance. -- 1017818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019163: marked as done (rust-smol - unsatisfiable build-dependency)
Your message dated Mon, 05 Sep 2022 15:36:05 + with message-id and subject line Bug#1019163: fixed in rust-smol 1.2.5-3 has caused the Debian Bug report #1019163, regarding rust-smol - unsatisfiable build-dependency 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.) -- 1019163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-smol Version: 1.2.5-2 Severity: serious rust-smol build-depends on librust-nix-0.24+default-dev but the nix crate in debian testing/unstable is now at 0.25 --- End Message --- --- Begin Message --- Source: rust-smol Source-Version: 1.2.5-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-smol, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated rust-smol 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, 05 Sep 2022 16:54:31 +0200 Source: rust-smol Architecture: source Version: 1.2.5-3 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1019163 Changes: rust-smol (1.2.5-3) unstable; urgency=medium . * update patch 2002_nix to accept newer release of crate nix; relax to build-depend and autopkgtest-depend on librust-nix-0+default-dev (not librust-nix-0.24+default-dev); closes: bug#1019163, thanks to Peter Michael Green * relax build-dependencies to drop lower bounds on librust-inotify-0-dev * stop overzealously provide versioned virtual packages Checksums-Sha1: ac75d3e2510e84145e5c21e6d5aab7549d620d39 3683 rust-smol_1.2.5-3.dsc 89da6acc2f260830ce8340eef30a229f53da4271 14284 rust-smol_1.2.5-3.debian.tar.xz fe4590a504a22670a6a32c71a65edbe7bd0742eb 13345 rust-smol_1.2.5-3_amd64.buildinfo Checksums-Sha256: f1f5def9a59c55f66f555b044d4074d7ca819f95956f16230bc5b81c438c 3683 rust-smol_1.2.5-3.dsc d9a013f7c95e4bdede893f661f6165bb888fe05b116f10a78f0efa63e808a898 14284 rust-smol_1.2.5-3.debian.tar.xz 4235595a87b43e2d8665659396358e837eddadcd9ae71bf8b72a076aa7eaeae4 13345 rust-smol_1.2.5-3_amd64.buildinfo Files: 12e736c3b25c97d2a556829645cd27dc 3683 rust optional rust-smol_1.2.5-3.dsc 2cb9889eadc84e77f1bfbdef9bf889c5 14284 rust optional rust-smol_1.2.5-3.debian.tar.xz 8fe9c7c1b120317bd1ab441deae7c5eb 13345 rust optional rust-smol_1.2.5-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMWEC0ACgkQLHwxRsGg ASF4/w//RtgVji+KI5odp/XD7RKSvnvIPKMHTfE0AW3xZ+mvb333GVkPYP3dzLOG 6FD3YNDQu8p3yNPn+6L760LB7dwWYG161rv6w0mSSceaySbzwGFWTKf/Za78V+WC V0wBqWgZLZ6QaziSlOx8k5vWoka3LKtsOHHp13lHzRTUZzrGxC6mQeugoG/4bH3Z WDy9tbkgdRZ5drvig7ziv3BkMSXFt4iLQB3L1r+yx1gw3KuW3GJfq/3FtAJ4nVEW r2HX14JOqD3S/YUuqsKnb3QUjsQvPOOWLWnkyfEqbbywUGqCLOUcb7Ylx5YlfEh8 +P+c6U57lA8K6B1XOwdQdJQwgjRI2AQxjoeZd9Qso93XlRVSJUb7E5HPe7S9ngkP 8htSflKS52PRkhPx+iCdeX6Z59BIfvh1G4MNVXfrltSPluzb6IuzqJfHmBhbK7Yj XcKpIz6xucHBi/+3GicQpyaTW9EFiUhTOSINfBZFNUCMLh0307iJLKAO5KEzjcim 3d4s/ZWDrlVlMkq0MOS+0u3EHtcnW3gPKwhD+kk/zht1DrunD54inJS/91dstldo XAs2cr53wiIJIzGCKEpALL0G4Uo6+9ZXpiRyy2l+5ZVFYX0WYSD2xiMosmWujZII gC1iGMGopDNo18yPQk5/Emdf2OTBmdXR9kLHPA629Aza+4CXZAk= =Sj4J -END PGP SIGNATURE End Message ---
Bug#1019158: graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv
On Mon, Sep 5, 2022 at 4:09 PM Bob Friesenhahn wrote: > On Sun, 4 Sep 2022, Paul Gevers wrote: > > gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: > > undefined symbol: _ZN6Magick5Image12colorMapSizeEv > > This issue is caused by Mercurial changeset 16712:acb5f7fa99cf: > > "colorMapSize() method for returning the number of colormap entries > should be a const method." > > Apparently this change impacts the ABI. How do you plan to solve this problem? Seems you either revert it or the library needs a soname bump. Regards, Laszlo/GCS
Bug#1017515: marked as done (q2-feature-table: needs update for python-biom-format/2.1.12-1)
Your message dated Mon, 05 Sep 2022 15:07:04 + with message-id and subject line Bug#1017515: fixed in q2-feature-table 2022.8.0+dfsg-1 has caused the Debian Bug report #1017515, regarding q2-feature-table: needs update for python-biom-format/2.1.12-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.) -- 1017515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: q2-feature-table Version: 2022.2.0+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of python-biom-format/2.1.12-1, the autopkgtests of q2-feature-table have been failing [1]. I've copied the short test summary below. Regards Graham [1] https://ci.debian.net/packages/q/q2-feature-table/testing/amd64/ === short test summary info FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_feature_metadata FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_filter_empty_samples FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_min_frequency FAILED q2_feature_table/tests/filter/test_filter_features.py::FilterFeaturesTests::test_where FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_combine_exclude_ids_and_features_filters FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_combine_exclude_ids_and_frequency_filters FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_filter_empty_features FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_max_features FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_max_frequency FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_min_features FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_min_frequency FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_sample_metadata FAILED q2_feature_table/tests/filter/test_filter_samples.py::FilterSamplesTests::test_where = 13 failed, 122 passed, 16 warnings in 24.97s = --- End Message --- --- Begin Message --- Source: q2-feature-table Source-Version: 2022.8.0+dfsg-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of q2-feature-table, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated q2-feature-table 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, 05 Sep 2022 20:13:07 +0530 Source: q2-feature-table Architecture: source Version: 2022.8.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1017515 Changes: q2-feature-table (2022.8.0+dfsg-1) unstable; urgency=medium . * Team Upload. * New upstream version 2022.8.0+dfsg (Closes: #1017515) * Updated dependency on qiime/q2-* >= 2022.8.0 Checksums-Sha1: 4f17a92ed2595c2ef570e7a73b052d9f65a06f1d 2310 q2-feature-table_2022.8.0+dfsg-1.dsc 457d88543daad84895db9a1d30065eec60efb711 49404 q2-feature-table_2022.8.0+dfsg.orig.tar.xz 7534b3000d810663ec0e966f286d594c103d0b1f 382776 q2-feature-table_2022.8.0+dfsg-1.debian.tar.xz 25106afd39f5e1876286a0b7d73d1c8285ddc088 12681 q2-feature-table_2022.8.0+dfsg-1_amd64.buildinfo Checksums-Sha256: 83aa37dffc8790d057f703e33d5bd5535a65d8e008aa6234c5b65eaa08752131 2310 q2-feature-table_2022.8.0+dfsg-1.dsc b3a3bb3f6984e4e726ab44188bedeb48cff9f9f7d252352fa3686df33b7bd65b 49404 q2-feature-table_2022.8.0+dfsg.orig.tar.xz f7adbf6861beb5e80cae1ea2033a9d0f449f53c19a7b70b93c4cd61d26ea50fa 382776 q2-feature-table_2022.8.0+dfsg-1.debian.tar.xz 5b3f39f1efae1029cbd0d7c1751d432d44ec8aac69ba372a410fe3cadc6dc551 12681 q2-feature-table_2022.8.0+dfsg-1_amd64.buildinfo Files:
Bug#1019131: r-bioc-dada2: autopkgtest regression in testing
I suspect this failure is related to r-cran-rcppparallel and onetbb. See the previously closed bug #1012141 and the similar bug filed againstr-cran-lamw, #1012142. It seems that all packages depending on r-cran-rcppparallel need to be rebuilt since the change to onetbb and should depend on the version of r-cran-rcppparallel they were built with. The only other package that has not been rebuilt is r-cran-openmx. It is not showing an autopkgtest regression, but maybe worth rebuilding anyway.
Bug#1018787: marked as done (horizon: autopkgtest failure: horizon.test.unit.test_base.RbacHorizonTests)
Your message dated Mon, 05 Sep 2022 14:43:31 +
with message-id
and subject line Bug#1018787: fixed in horizon 3:22.1.0-6
has caused the Debian Bug report #1018787,
regarding horizon: autopkgtest failure:
horizon.test.unit.test_base.RbacHorizonTests
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.)
--
1018787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: horizon
Version: 3:22.1.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package horizon, great.
However, it fails on amd64, i386 and armhf. Currently this failure is
blocking the migration to testing [1]. Can you please investigate the
situation and fix it?
I copied some of the output at the bottom of this report.
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=horizon
https://ci.debian.net/data/autopkgtest/testing/amd64/h/horizon/24859919/log.gz
=== FAILURES
===
__ RbacHorizonTests.test_rbac_panels
___
[gw20] linux -- Python 3.10.6 /usr/bin/python3
self = testMethod=test_rbac_panels>
def test_rbac_panels(self):
context = {'request': self.request}
cats = horizon.get_dashboard("cats")
self.assertEqual(cats._registered_with, base.Horizon)
self.assertQuerysetEqual(cats.get_panels(),
[''])
horizon/test/unit/test_base.py:547: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/django/test/testcases.py:1072: in
assertQuerysetEqual
return self.assertEqual(list(items), values, msg=msg)
E AssertionError: Lists differ: ['', 'tigers>', ''] != ['']
E E First differing element 0:
E ''
E ''
E E First list contains 2 additional elements.
E First extra element 1:
E ''
E E - ['', '', '']
E + ['']
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 3:22.1.0-6
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
horizon, 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 1018...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated horizon 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: Mon, 05 Sep 2022 15:19:18 +0200
Source: horizon
Architecture: source
Version: 3:22.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 1018787
Changes:
horizon (3:22.1.0-6) unstable; urgency=medium
.
* Also blacklist test_rbac_panels in autopkgtest (Closes: #1018787).
Checksums-Sha1:
502dfe16145590cef25b450c46b46a8f21909eaf 4515 horizon_22.1.0-6.dsc
5b8d80cf333dfb3e2c1d85c0be5ffd4612ff5fdb 33008 horizon_22.1.0-6.debian.tar.xz
c6977922954cb26a0e88d472e815be1145ba55e3 17664 horizon_22.1.0-6_amd64.buildinfo
Checksums-Sha256:
19c7b54d6b59e2cc72f2695a9615715614e6f8dde121525f0b0be1b707a20a95 4515
horizon_22.1.0-6.dsc
900241cd12ce826cdb7d563545a9b68cffa6211a7ed5396ebff53e864e523934 33008
horizon_22.1.0-6.debian.tar.xz
dddf5440f235c00ff50b8d6a96cb93301060278b03ab4b665a7086c597fa9ced 17664
horizon_22.1.0-6_amd64.buildinfo
Files:
e20c5fb6260ced5087f9ddb059187607 4515 net optional horizon_22.1.0-6.dsc
4f5b0a71cbd8fe825827e6ef0072f621 33008 net optional
horizon_22.1.0-6.debian.tar.xz
dafac71466c8baa5cf1cfd0bf6599f50 17664 net optional
horizon_22.1.0-6_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmMV/2QACgkQ1BatFaxr
Q/7cEhAAkdSMJnPnkRRvc9QWlU59JWxYptDWINP6WKmArZ7KOO+jEtB0ag1hFxmZ
MQnfI6ADJxZwsx9GF9WJ1+3a/kT3NwQ2fD9JLRyIg66scDgOBLW+s+EqnIcPkvzc
3nm4amVHC+DVl/YchO1ufjXyxMhyNEjwA4uO/6o4EmuuUpcSyMV0LLPO75JTWSyH
Bug#1017514: marked as done (q2-types: needs update for python-biom-format/2.1.12-1)
Your message dated Mon, 05 Sep 2022 14:43:42 + with message-id and subject line Bug#1017514: fixed in q2-types 2022.8.0-1 has caused the Debian Bug report #1017514, regarding q2-types: needs update for python-biom-format/2.1.12-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.) -- 1017514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: q2-types Version: 2022.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of python-biom-format/2.1.12-1, the autopkgtests of q2-types have been failing [1]. I've copied the short test summary below. Regards Graham [1] https://ci.debian.net/packages/q/q2-types/testing/amd64/ === short test summary info FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_table_to_biom_v210_format FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_v100_format_to_biom_table FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_v100_format_to_biom_v210_format FAILED q2_types/feature_table/tests/test_transformer.py::TestTransformers::test_biom_v210_format_to_biom_table == 4 failed, 350 passed, 12 warnings in 3.80s == --- End Message --- --- Begin Message --- Source: q2-types Source-Version: 2022.8.0-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of q2-types, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated q2-types 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, 05 Sep 2022 19:54:52 +0530 Source: q2-types Architecture: source Version: 2022.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1017514 Changes: q2-types (2022.8.0-1) unstable; urgency=medium . * Team upload. * New upstream version 2022.8.0 (Closes: #1017514) Checksums-Sha1: de4eec6784052fabf0524382786a88b887b8d5d4 2224 q2-types_2022.8.0-1.dsc 276ef93d9060cfc02ba40da67437d2599a87ca8f 111632 q2-types_2022.8.0.orig.tar.gz f1761b4eca6cd66ece217f2d8c2d0c3b852f6c87 6268 q2-types_2022.8.0-1.debian.tar.xz 7c1000f618bda4e0a9ef12016b28a23adebfa852 12243 q2-types_2022.8.0-1_amd64.buildinfo Checksums-Sha256: 37812ad0ec4d4698fe178218be879de86f2b120efdf7a1956b88acff7c1ffdcc 2224 q2-types_2022.8.0-1.dsc 4b8563828b683dc28c69f355104fc0343a15b942e429a085c640d359d45a0a3e 111632 q2-types_2022.8.0.orig.tar.gz d2a3cfd36b851975ae6bbd28df321a060c547a4dc238a0c1937150bcdf3f2021 6268 q2-types_2022.8.0-1.debian.tar.xz cf3fabd32c66d5870e968b3b1f04a112e935d9fc5c02857247f6315066ae3c51 12243 q2-types_2022.8.0-1_amd64.buildinfo Files: f1148d160371faffd9c010f4e645a555 2224 science optional q2-types_2022.8.0-1.dsc 7662635566f5084e12d10e50ef474683 111632 science optional q2-types_2022.8.0.orig.tar.gz b08336587788512ca33a42862dce6dae 6268 science optional q2-types_2022.8.0-1.debian.tar.xz 4c78f155f3f75be2d644fa744cdbcf21 12243 science optional q2-types_2022.8.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMWCGgSHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxK9AP+wcPlAlrVAzoXmj8IWPN9BdCCtIc773x kODEQp8Ndv/94plIo6FuoPLcl9T7QUd723OOJa8jv9iqfGtdS4aH8RsHZnm6tQPw SyPxPnjB8FMO4es5w77P5NCbTYgeKehsxs+bPUjwweDULxJfbEA57mFd530z++oz vOsrHs01z7vB+sgfLPxoqKvlXCumQXwCiVhygWG/kwnGZqfTwtZOf+uMOtdl2l1o Z2f9cL1QRyzhTYw9KR1MMLsnLtzd7vU2F53233UVQL3QNFrf3UrsKmAN6rpdvsxQ b8zGpNgf5rqEUJobgzl1Le8wAH+AKZM4LmW2PjpXY3Dad+hodNv5OgnvdMcRpVty PNRBNML9QgC+VUp4oJfrDiMvi/as6sI8+0slhkJr1jCJ2G4TDmD+pJnTvhSZiKzn 26oWbZKBaXvj/2unfsG6/qfKKtWX5k4AxGGb14lQ+6ePbYLyB5+9rVmqGewXeVWp izhRK3uR0Y6+MWbqOhsDJUITDDY1DoTbJsjFQNvTMt5xUTSPZb7Y/MDQQMWGlLm4 vI/gbjZlHDfP7DFzhgDlTTG1rXdzyFXmje580e+K+ASMZEy63DG1QvOPW4VxhdPz A7bexhF5RohcUoLX663Q8RnDcAPQ/cZHJxlZv5sFLIOwNpXrBMXCRXEgRbZBzv3P iSxBjpES3o1F =bp9Y -END PGP
Bug#1015136: marked as done (q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)
Your message dated Mon, 05 Sep 2022 14:43:51 +
with message-id
and subject line Bug#1015136: fixed in q2cli 2022.8.0-1
has caused the Debian Bug report #1015136,
regarding q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.10 returned exit code 13
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.)
--
1015136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: q2cli
Version: 2021.8.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/q2cli
> copying q2cli/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli
> copying q2cli/util.py -> /<>/.pybuild/cpython3_3.10/build/q2cli
> copying q2cli/__main__.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli
> copying q2cli/commands.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli
> copying q2cli/_version.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli
> creating /<>/.pybuild/cpython3_3.10/build/q2cli/builtin
> copying q2cli/builtin/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/builtin
> copying q2cli/builtin/tools.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/builtin
> copying q2cli/builtin/dev.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/builtin
> copying q2cli/builtin/info.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/builtin
> creating /<>/.pybuild/cpython3_3.10/build/q2cli/click
> copying q2cli/click/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/click
> copying q2cli/click/parser.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/click
> copying q2cli/click/option.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/click
> copying q2cli/click/type.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/click
> copying q2cli/click/command.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/click
> creating /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> copying q2cli/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> copying q2cli/tests/test_cli.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> copying q2cli/tests/test_dev.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> copying q2cli/tests/test_usage.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> copying q2cli/tests/test_core.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> copying q2cli/tests/test_tools.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/tests
> creating /<>/.pybuild/cpython3_3.10/build/q2cli/core
> copying q2cli/core/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/core
> copying q2cli/core/usage.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/core
> copying q2cli/core/cache.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/core
> copying q2cli/core/config.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/core
> copying q2cli/core/completion.py ->
> /<>/.pybuild/cpython3_3.10/build/q2cli/core
> running egg_info
> creating q2cli.egg-info
> writing q2cli.egg-info/PKG-INFO
> writing dependency_links to q2cli.egg-info/dependency_links.txt
> writing entry points to q2cli.egg-info/entry_points.txt
> writing top-level names to q2cli.egg-info/top_level.txt
> writing manifest file 'q2cli.egg-info/SOURCES.txt'
> reading manifest file 'q2cli.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'q2cli.egg-info/SOURCES.txt'
> UPDATING /<>/.pybuild/cpython3_3.10/build/q2cli/_version.py
> set /<>/.pybuild/cpython3_3.10/build/q2cli/_version.py to
> '2021.8.0'
> running build_scripts
> creating build
> creating build/scripts-3.10
> copying bin/tab-qiime -> build/scripts-3.10
> changing mode of build/scripts-3.10/tab-qiime from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:239: cd /<>/.pybuild/cpython3_3.10/build;
> python3.10 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.10.5, pytest-7.1.2, pluggy-1.0.0
> rootdir: /<>
>
Bug#1017053: marked as done (fenics-dolfinx: FTBFS on mips64el)
Your message dated Mon, 05 Sep 2022 14:41:49 + with message-id and subject line Bug#1017053: fixed in fenics-dolfinx 1:0.5.0-1exp2 has caused the Debian Bug report #1017053, regarding fenics-dolfinx: FTBFS on mips64el 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.) -- 1017053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fenics-dolfinx Version: 1:0.4.1-4 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer Your package FTBFS on mips64el during the recent rebuilds for Python 3.10 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.debian.org/status/package.php?p=fenics-dolfinx Traceback (most recent call last): File "/<>/python/setup.py", line 67, in setup(name='fenics-dolfinx', File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in setup return distutils.core.setup(**attrs) File "/usr/lib/python3.10/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command cmd_obj.run() File "/usr/lib/python3.10/distutils/command/build.py", line 135, in run self.run_command(cmd_name) File "/usr/lib/python3.10/distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command cmd_obj.run() File "/<>/python/setup.py", line 41, in run self.build_extension(ext) File "/<>/python/setup.py", line 64, in build_extension subprocess.check_call(['cmake', '--build', '.'] + build_args, cwd=self.build_temp, env=env) File "/usr/lib/python3.10/subprocess.py", line 369, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j3']' returned non-zero exit status 2. chrpath -d /<>/debian/tmp*/usr/lib/python*/dist-packages/dolfinx/*.so open: No such file or directory elf_open: Invalid argument --- End Message --- --- Begin Message --- Source: fenics-dolfinx Source-Version: 1:0.5.0-1exp2 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of fenics-dolfinx, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated fenics-dolfinx 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: Mon, 05 Sep 2022 14:56:48 +0200 Source: fenics-dolfinx Architecture: source Version: 1:0.5.0-1exp2 Distribution: experimental Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Closes: 1017053 Changes: fenics-dolfinx (1:0.5.0-1exp2) experimental; urgency=medium . * apply build flag -Wno-error=maybe-uninitialized on mip64el to prevent xtensor (xtl/xsequence.hpp) causing build failure. Closes: #1017053 Checksums-Sha1: 8c5ceecc327a8ec78beef629fa307f88effac65d 3929 fenics-dolfinx_0.5.0-1exp2.dsc 4c754982dfc8d4ac0b1f77b69f566da133d2310f 35904 fenics-dolfinx_0.5.0-1exp2.debian.tar.xz Checksums-Sha256: 5c324210a9797f26410654248fcba06caa56144743650e28dcfd18ab5db6ed5e 3929 fenics-dolfinx_0.5.0-1exp2.dsc a2a901edb86fcc08f12a194b325a8d165c8ea4ba7088ee4f479751e3a1962ec2 35904 fenics-dolfinx_0.5.0-1exp2.debian.tar.xz Files: add3e244407b7139919ee8e7491c026d 3929 math optional fenics-dolfinx_0.5.0-1exp2.dsc 54865542928294590ada3ef0b28be958 35904 math optional fenics-dolfinx_0.5.0-1exp2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmMWALAACgkQVz7x5L1a AfptLw/+LTA0xfhSjBW7CyFmnS0zXWbZ/2GFn3IJ20HFzvxySPhgYguqPFPlYkjj 32qhOpqak/t3/VcUBjiuTxGpVib9jWCf7yQ+JRvGD3iws/hbU3jArgez9K/mvnor yi2JjytbHIAkbS5PFdFW1dg/CU69FJl5VcRV3mshr6LzoYiJeUpnVz4Nu0ciU+Yt 5deeHanZrPwEbYlqK5N8OEDYO4UwZX/sPlDjXaRkXvtqbfm4QGbblojItRhreQ6n
Bug#1017324: libhugetlbfs: FTBFS: morecore.c:368:17: error: ‘__morecore’ undeclared (first use in this function); did you mean ‘thp_morecore’?
Hi, I have created a patch to address this issue. Kindly find my github repository below for details: https://github.com/daichifukui/libhugetlbfs Note that this patch is based on an upstream pull request, which has not been reviewed yet: https://github.com/libhugetlbfs/libhugetlbfs/pull/63 Perhaps we need to review the original patch as well. Best, Fukui On Sun, 14 Aug 2022 10:44:55 +0200 Lucas Nussbaum wrote: > Source: libhugetlbfs > Version: 2.23-4 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220813 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > cc -m64 -Wdate-time -D_FORTIFY_SOURCE=2 -D__LIBHUGETLBFS__ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -fPIC -o obj64/kernel-features.o -c kernel-features.c > > morecore.c: In function ‘__lh_hugetlbfs_setup_morecore’: > > morecore.c:368:17: error: ‘__morecore’ undeclared (first use in this function); did you mean ‘thp_morecore’? > > 368 | __morecore = _morecore; > > | ^~ > > | thp_morecore > > morecore.c:368:17: note: each undeclared identifier is reported only once for each function it appears in > > make[1]: *** [Makefile:298: obj64/morecore.o] Error 1 > > > The full build log is available from: > http://qa-logs.debian.net/2022/08/13/libhugetlbfs_2.23-4_unstable.log > > All bugs filed during this archive rebuild are listed at: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org > or: > https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results > > 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! > > If you reassign this bug to another package, please marking it as 'affects'-ing > this package. See https://www.debian.org/Bugs/server-control#affects > > If you fail to reproduce this, please provide a build log and diff it with mine > so that we can identify if something relevant changed in the meantime. > >
Bug#1019206: librust-criterion+async-std-dev: Package is uninstallable, rust-async-std missing in debian
Package: librust-criterion+async-std-dev Severity: serious Justification: packages must be installable, prevents other packages from reaching testing X-Debbugs-Cc: d...@jones.dk, debian-r...@lists.debian.org The package librust-criterion+async-std-dev is currently uninstallable in unstable and testing, which prevents it and other dependent packages (like rust-rustls) from reaching testing. Currently, this even threats the removal unrelated packages from testing, cf. #1018225 I see two options out here: a) disable the 'async-std' feature b) package 'async-std' Note that while working on the rust-rtnetlink package, a similar issue popped up, and I've opted for option a). Should 'async-std' become available, I'd be happy to change 'rust-rtnetlink' to enable the 'async-std' feature. Best, -rt -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages librust-criterion+async-std-dev depends on: pn librust-async-std-1+default-dev pn librust-criterion-dev librust-criterion+async-std-dev recommends no packages. librust-criterion+async-std-dev suggests no packages.
Bug#1019158: graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv
On Sun, 4 Sep 2022, Paul Gevers wrote: [1] https://qa.debian.org/excuses.php?package=graphicsmagick https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnudatalanguage/25681414/log.gz gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv This issue is caused by Mercurial changeset 16712:acb5f7fa99cf: "colorMapSize() method for returning the number of colormap entries should be a const method." Apparently this change impacts the ABI. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
Bug#1016288: pulseaudio-dlna: crashes on start
Package: pulseaudio-dlna Version: 0.5.3+git20200329-0.1 Followup-For: Bug #1016288 Dear Maintainer, A similar situation occurs on stable: Exception in thread zeroconf-ServiceBrowser__googlecast._tcp.local.: Traceback (most recent call last): File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner self.run() File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1557, in run self._service_state_changed.fire( File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1333, in fire h(**kwargs) File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1427, in on_change listener.add_service(*args) File "/usr/lib/python3/dist-packages/pychromecast/discovery.py", line 65, in add_service self._add_update_service(zconf, typ, name, self.add_callback) File "/usr/lib/python3/dist-packages/pychromecast/discovery.py", line 123, in _add_update_service callback(uuid, name) File "/usr/lib/python3/dist-packages/pychromecast/__init__.py", line 246, in internal_callback callback( File "/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/__init__.py", line 36, in wrapper device = f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/chromecast/__init__.py", line 47, in _on_device_added return ChromecastRendererFactory.from_pychromecast(device) File "/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/chromecast/renderer.py", line 183, in from_pychromecast ip=pychromecast.host, AttributeError: 'Chromecast' object has no attribute 'host' Dependencies of pulseaudio-dlna recently changed quite a bit, so updating to the newest version is likely not going to work well (with other system-installed dependencies and other software depending on those). However, I could without problem build release 0.6.3, which works on Debian stable and also officially should work with the libraries present in Debian stable. Versions > 0.5.2 are available from here: https://github.com/Cygn/pulseaudio-dlna . I am reporting this here even though the previous report was for unstable because quite likely versions of dependencies are the problem in both cases and similar fixes/updates could be made in both cases. Without any change, this package is quite unuseable also on Debian stable, so 'grave' seems to be the correct severity. -- System Information: Debian Release: 11.4 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pulseaudio-dlna depends on: ii flac 1.3.3-2+deb11u1 ii lame 1:3.100-dmo2 ii opus-tools0.1.10-1+b1 ii python3 3.9.2-3 ii python3-chardet 4.0.0-1 ii python3-dbus 1.2.16-5 ii python3-distutils 3.9.2-1 ii python3-docopt0.6.2-3 ii python3-gi3.38.0-2 ii python3-lxml 4.6.3+dfsg-0.1+deb11u1 ii python3-netifaces 0.10.9-0.2+b3 ii python3-notify2 0.3-4 ii python3-psutil5.8.0-1 ii python3-pychromecast 7.7.1-2 ii python3-pyroute2 0.5.14-2 ii python3-requests 2.25.1+dfsg-2 ii python3-setproctitle 1.2.1-1+b1 ii sox 14.4.2+git20190427-2 ii vorbis-tools 1.4.0-11+b1 Versions of packages pulseaudio-dlna recommends: ii ffmpeg 10:4.4-dmo4+deb11u5 ii gir1.2-rsvg-2.0 2.50.3+dfsg-1 pn gir1.2-rsvg-3.0 pn libav-tools ii python3-cairo1.16.2-4+b2 pulseaudio-dlna suggests no packages. -- no debconf information
Processed: Bug#1018787 marked as pending in horizon
Processing control commands: > tag -1 pending Bug #1018787 [src:horizon] horizon: autopkgtest failure: horizon.test.unit.test_base.RbacHorizonTests Added tag(s) pending. -- 1018787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018787: marked as pending in horizon
Control: tag -1 pending Hello, Bug #1018787 in horizon 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/openstack-team/services/horizon/-/commit/6029258ef977bc48065f848ffb689e419a21334f Also blacklist test_rbac_panels in autopkgtest (Closes: #1018787). (this message was generated automatically) -- Greetings https://bugs.debian.org/1018787
Bug#1017070: marked as done (python-etelemetry: server offline, DEP8 tests fail)
Your message dated Mon, 5 Sep 2022 18:59:59 +0530
with message-id <20220905132959.wjwfmfr72i2ao...@nileshpatra.info>
and subject line Re: python-etelemetry: server offline, DEP8 tests fail
has caused the Debian Bug report #1017070,
regarding python-etelemetry: server offline, DEP8 tests fail
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.)
--
1017070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-etelemetry
Version: 0.3.0-2
Severity: normal
Dear Maintainer,
the rig.mit.edu server that seems to be used by default by
python-etelemetry is offline:
$ python3
Python 3.10.6 (main, Aug 10 2022, 11:19:32) [GCC 12.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import etelemetry
>>> etelemetry.get_project("nipy/nipype")
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
174, in _new_conn
conn = connection.create_connection(
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py",
line 96, in create_connection
raise err
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py",
line 86, in create_connection
sock.connect(sa)
TimeoutError: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py",
line 704, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py",
line 387, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py",
line 1043, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
358, in connect
self.sock = conn = self._new_conn()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
179, in _new_conn
raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError:
(,
'Connection to rig.mit.edu timed out. (connect timeout=5)')
(...)
This was noted in an upstream bug report[1] from August 2021, and is
failing debci[2] and ubuntu[3] dep8 tests:
E urllib3.exceptions.ConnectTimeoutError:
(,
'Connection to rig.mit.edu timed out. (connect timeout=5)')
I'm unsure how to proceed here, as it looks like that that server is
essential for this package to operate. Maybe skip those tests, but
still, the package itself won't be in a working state (see backtrace
above, with commands taken straight out from upstream README file
showing how to use the module).
Maybe the PR at [4] can help, as it allows for custom endpoints.
1. https://github.com/sensein/etelemetry-client/issues/35
2.
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-etelemetry/24654839/log.gz
3.
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/p/python-etelemetry/20220812_192355_57dbb@/log.gz
4. https://github.com/sensein/etelemetry-client/pull/39
--- End Message ---
--- Begin Message ---
Upstream restarted the server so it is working now.
https://github.com/sensein/etelemetry-client/issues/35#issuecomment-1233496493
Even if the support for custom endpoints is merged, it is difficult to
keep it floating w/o hosting a server of our own.
In any case, there is not much that can be done from debian side right now.
So I am closing this bug.
--
Best,
Nilesh
signature.asc
Description: PGP signature
--- End Message ---
Bug#976467: marked as done (rust-core-arch FTBFS error[E0635]: unknown feature `mmx_target_feature`)
Your message dated Mon, 05 Sep 2022 13:03:37 +
with message-id
and subject line Bug#1010322: Removed package(s) from unstable
has caused the Debian Bug report #976467,
regarding rust-core-arch FTBFS error[E0635]: unknown feature
`mmx_target_feature`
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.)
--
976467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-core-arch
Version: 0.1.5-4
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> export RUSTC_BOOTSTRAP=1; \
> dh_auto_test
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu,
> aarch64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'aarch64-unknown-linux-gnu'],) {}
>Compiling core_arch v0.1.5 (/<>)
> Running `CARGO_MANIFEST_DIR=/<> CARGO_PKG_VERSION_MAJOR=0
> CARGO_PKG_NAME=core_arch CARGO_PKG_VERSION_PATCH=5 CARGO=/usr/bin/cargo
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_HOMEPAGE='https://github.com/rust-lang-nursery/stdsimd'
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION=0.1.5
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang-nursery/stdsimd'
> CARGO_PKG_VERSION_PRE= CARGO_PKG_DESCRIPTION='`core::arch` - Rust'\''s core
> library architecture-specific intrinsics.' CARGO_PKG_AUTHORS='Alex Crichton
> :Andrew Gallant :Gonzalo Brito
> Gadeschi ' rustc --crate-name build_script_build
> build.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin
> --emit=dep-info,link -C debuginfo=2 -C metadata=0c9e369f53803bd6 -C
> extra-filename=-0c9e369f53803bd6 --out-dir
> /<>/target/debug/build/core_arch-0c9e369f53803bd6 -C
> incremental=/<>/target/debug/incremental -L
> dependency=/<>/target/debug/deps`
> Running
> `/<>/target/debug/build/core_arch-0c9e369f53803bd6/build-script-build`
> [core_arch 0.1.5] cargo:rustc-cfg=core_arch_docs
> Running
> `OUT_DIR=/<>/target/aarch64-unknown-linux-gnu/debug/build/core_arch-bdd71fb3715c8655/out
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_VERSION_MAJOR=0
> CARGO_PKG_NAME=core_arch CARGO_PKG_VERSION_PATCH=5 CARGO=/usr/bin/cargo
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_HOMEPAGE='https://github.com/rust-lang-nursery/stdsimd'
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION=0.1.5
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang-nursery/stdsimd'
> CARGO_PKG_VERSION_PRE= CARGO_PKG_DESCRIPTION='`core::arch` - Rust'\''s core
> library architecture-specific intrinsics.' CARGO_PKG_AUTHORS='Alex Crichton
> :Andrew Gallant :Gonzalo Brito
> Gadeschi ' rustc --crate-name core_arch src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi --crate-type lib
> --emit=dep-info,metadata,link -C debuginfo=2 -C metadata=20c0c8735dc138e4 -C
> extra-filename=-20c0c8735dc138e4 --out-dir
> /<>/target/aarch64-unknown-linux-gnu/debug/deps --target
> aarch64-unknown-linux-gnu -C
> incremental=/<>/target/aarch64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/aarch64-unknown-linux-gnu/debug/deps
> -L dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints
> warn -C linker=aarch64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
> --remap-path-prefix
> /<>=/usr/share/cargo/registry/core-arch-0.1.5 --cfg
> core_arch_docs`
> warning: unused import: `mem::transmute`
> --> src/arm/neon.rs:3:38
> |
> 3 | use crate::{core_arch::simd_llvm::*, mem::transmute};
> | ^^
> |
> = note: `#[warn(unused_imports)]` on by default
>
> warning: the feature `align_offset` has been stable since 1.36.0 and no
> longer requires an attribute to enable
> --> src/lib.rs:20:5
>|
> 20 | align_offset,
>|
>|
>= note: `#[warn(stable_features)]` on by default
>
> warning: the feature `maybe_uninit` has been stable since 1.36.0 and no
> longer requires an attribute to enable
> --> src/lib.rs:21:5
>|
> 21 | maybe_uninit,
>|
>
> error[E0635]: unknown feature `mmx_target_feature`
> --> src/lib.rs:23:5
>|
> 23 | mmx_target_feature,
>| ^^
>
>
Bug#1017300: marked as done (gokey 0.1.0 and 0.1.1 FTBFS with golang-1.19)
Your message dated Mon, 05 Sep 2022 12:34:48 + with message-id and subject line Bug#1017300: fixed in gokey 0.1.1-1 has caused the Debian Bug report #1017300, regarding gokey 0.1.0 and 0.1.1 FTBFS with golang-1.19 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.) -- 1017300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gokey Version: 0.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- -timeout 6h > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -timeout 6h > github.com/cloudflare/gokey github.com/cloudflare/gokey/cmd/gokey > github.com/cloudflare/gokey/rsa > === RUN TestDRNG > --- PASS: TestDRNG (0.01s) > === RUN TestDRNGwithSeed > --- PASS: TestDRNGwithSeed (0.02s) > === RUN TestEncryptedSeed > --- PASS: TestEncryptedSeed (0.01s) > === RUN TestGetPass > --- PASS: TestGetPass (0.02s) > === RUN TestGetKey > gokey_test.go:161: keys with same invocation options do not match > --- FAIL: TestGetKey (1.71s) > === RUN TestGetKeyUnsafe > --- PASS: TestGetKeyUnsafe (0.00s) > === RUN TestParseX25519 > --- PASS: TestParseX25519 (0.00s) > === RUN TestParseEd25519 > --- PASS: TestParseEd25519 (0.00s) > === RUN TestGenX25519 > --- PASS: TestGenX25519 (0.01s) > === RUN TestGenEd25519 > --- PASS: TestGenEd25519 (0.01s) > === RUN TestGenPass > --- PASS: TestGenPass (0.00s) > === RUN TestAllowedChars > --- PASS: TestAllowedChars (0.00s) > FAIL > FAIL github.com/cloudflare/gokey 1.787s > ? github.com/cloudflare/gokey/cmd/gokey [no test files] > === RUN TestKnownKey > keygen_test.go:129: generated RSA 2048 does not match the expected result > --- FAIL: TestKnownKey (0.21s) > === RUN TestStdKey > keygen_test.go:149: mitigating crypto/internal/randutil.MaybeReadByte... > keygen_test.go:149: mitigating crypto/internal/randutil.MaybeReadByte... > keygen_test.go:149: mitigating crypto/internal/randutil.MaybeReadByte... > keygen_test.go:194: RSA key generation algorithm from stdlib deviates > from the one in gokey > --- FAIL: TestStdKey (0.10s) > FAIL > FAIL github.com/cloudflare/gokey/rsa 0.330s > FAIL > dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 > -timeout 6h github.com/cloudflare/gokey github.com/cloudflare/gokey/cmd/gokey > github.com/cloudflare/gokey/rsa returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/08/13/gokey_0.1.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results 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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: gokey Source-Version: 0.1.1-1 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of gokey, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated gokey 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: Mon, 05 Sep 2022 06:04:50 -0600 Source: gokey Architecture: source Version: 0.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Anthony Fok Closes: 1017300 Changes: gokey (0.1.1-1) unstable; urgency=medium . * New
Bug#1017053: fenics-dolfinx: FTBFS on mips64el
Source: fenics-dolfinx Followup-For: Bug #1017053 For what it's worth the same error warning from tensor/xtl also shows up in xtensor's own tests on amd64. Not clear why it gives dolfinx a problem only on mips64el. I'd expect the problem to be the same on all arches. Any any case, I think the work-around is to treat this error warning as a warning not an error, which is what xtensor itself does.
Processed: dolfinx
Processing commands for cont...@bugs.debian.org: > forwarded 1017053 https://github.com/xtensor-stack/xtl/issues/260 Bug #1017053 [src:fenics-dolfinx] fenics-dolfinx: FTBFS on mips64el Set Bug forwarded-to-address to 'https://github.com/xtensor-stack/xtl/issues/260'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017717: marked as done (cp2k: FTBFS: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load)
Your message dated Mon, 05 Sep 2022 11:49:52 + with message-id and subject line Bug#1017356: fixed in pmix 4.2.0+really.4.1.2-3 has caused the Debian Bug report #1017356, regarding cp2k: FTBFS: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cp2k Version: 9.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hello, cp2k fails to build on amd64: cd tools/manual && \ /home/merkys/cp2k-9.1/exe/*/cp2k.psmp --xml && \ saxonb-xslt -o index.html -ext:on cp2k_input.xml cp2k_input.xsl orted: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load [barriere:463328] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716 [barriere:463328] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172 -- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value Unable to start a daemon on the local node (-127) instead of ORTE_SUCCESS -- -- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "Unable to start a daemon on the local node" (-127) instead of "Success" (0) -- *** An error occurred in MPI_Init_thread *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, ***and potentially your MPI job) [barriere:463328] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! Andrius --- End Message --- --- Begin Message --- Source: pmix Source-Version: 4.2.0+really.4.1.2-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pmix, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated pmix 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: Mon, 05 Sep 2022 12:26:30 +0100 Source: pmix Architecture: source Version: 4.2.0+really.4.1.2-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1017356 1017730 Changes: pmix (4.2.0+really.4.1.2-3) unstable; urgency=medium . * Drop B-D on pandoc. Closes: #1017356, #1017730 Checksums-Sha1: 7093e37e3cb8f0c145fcdb05c69aebc90ecaba2d 2401 pmix_4.2.0+really.4.1.2-3.dsc 539e871f8f7badb3620b518e74e8187d62963ae6 10372 pmix_4.2.0+really.4.1.2-3.debian.tar.xz Checksums-Sha256: a57ceaf0368ce756e50317ab070e314db8ca4f8936488cfc1709ca1162f14121 2401 pmix_4.2.0+really.4.1.2-3.dsc e537b15de13c1ad98be797758c57176b1de6a5b30617dd1d6255b489c812512e 10372 pmix_4.2.0+really.4.1.2-3.debian.tar.xz
Bug#1017356: marked as done (libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load)
Your message dated Mon, 05 Sep 2022 11:49:52 + with message-id and subject line Bug#1017356: fixed in pmix 4.2.0+really.4.1.2-3 has caused the Debian Bug report #1017356, regarding libpmix2: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpmix2 Version: 4.2.0~rc1-2 Severity: grave Justification: renders package unusable Starting with version 4.2.0~rc1-1, the mca_pmix_ext3x.so library lost the pmix_value_load symbols. This causes issues on depending packages: https://buildd.debian.org/status/fetch.php?pkg=dolfin=amd64=2019.2.0%7Egit20220407.d29e24d-5%2Bnmu1=1660479825=0 https://ci.debian.net/data/autopkgtest/testing/amd64/m/mpi4py/24786981/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmpi/24786982/log.gz --- End Message --- --- Begin Message --- Source: pmix Source-Version: 4.2.0+really.4.1.2-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pmix, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated pmix 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: Mon, 05 Sep 2022 12:26:30 +0100 Source: pmix Architecture: source Version: 4.2.0+really.4.1.2-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1017356 1017730 Changes: pmix (4.2.0+really.4.1.2-3) unstable; urgency=medium . * Drop B-D on pandoc. Closes: #1017356, #1017730 Checksums-Sha1: 7093e37e3cb8f0c145fcdb05c69aebc90ecaba2d 2401 pmix_4.2.0+really.4.1.2-3.dsc 539e871f8f7badb3620b518e74e8187d62963ae6 10372 pmix_4.2.0+really.4.1.2-3.debian.tar.xz Checksums-Sha256: a57ceaf0368ce756e50317ab070e314db8ca4f8936488cfc1709ca1162f14121 2401 pmix_4.2.0+really.4.1.2-3.dsc e537b15de13c1ad98be797758c57176b1de6a5b30617dd1d6255b489c812512e 10372 pmix_4.2.0+really.4.1.2-3.debian.tar.xz Files: 709181c7df829e57ca71315cf75e3621 2401 net optional pmix_4.2.0+really.4.1.2-3.dsc 195c62dcde1d42697272ce4b1b5303a0 10372 net optional pmix_4.2.0+really.4.1.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmMV3vMACgkQy+a7Tl2a 06X3pw//ReYPV45uoA/DxLuVt4P1ERuRVwisBRcHQMYh2DU+Y/IGIhVra9yT+Sn+ ZrPQa7xfxpiPFXH7ald/hJ2bYEyFZxqzLpU9ONJ+MXZseDVlGccOSA9N4bwyngOM 5L9ido+MHlFcv3oo8aoRNZMIUAewFfKzuV4cpHI7BwnqMBURXcfw7EGW7S+JOQPS +x9ke972zp0xNHLTY5bmnpj3nb0Ls9f2JNvSFLUcfovP11t1u0aBGtDsxf3eJgPm 1bcoI5pxpmwJGe0YDp5aDzmx5LPP/879gLpaphXcvYCTEPEo3TgWEqQ3Ykb8l1Wd 5xkCsIDKHXOAH0EIZGzUG4qN3dkKEIWdjNlhZhfKp3GECa8e342Es4YTNopO19yJ FK113QPXYzOjg5He51hrPx2YjOhYresUQbsW6k+Tjx9YHcRBPebduX1AKDVcDCqy qZlVkqo/qfJ+3vaOJAUFr1VafMq/RKGWOKGW/utt8jiHUEwHnSLRvgx4JWKfbrGN 9Fh1xR7mHspkci2ZbRXpsoIw/cE8/pBH4mqGQd4CbuTsA9uLVysuzRmyn62e14OP PD2t9k6i5dikKnePb2/6GUhC36hqJ1PXnuWyAw9GPaDkvUbyQzpqGZfG2YBxGzcj +MlNHqlMCW1LNR/xHhd/e+KQhDhwxYYarYRaZfjZIdn5M2WdQhI= =M5hO -END PGP SIGNATURE End Message ---
Processed: tagging 1000851
Processing commands for cont...@bugs.debian.org: > tags 1000851 + pending Bug #1000851 [src:segyio] segyio: FTBFS with glibc 2.34 Bug #1017156 [src:segyio] segyio: FTBFS: catch.hpp:7431:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’ Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000851 1017156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018924: marked as done (libgc FTBFS: architecture-specific symbol handling removed)
Your message dated Mon, 05 Sep 2022 11:33:59 + with message-id and subject line Bug#1018924: fixed in libgc 1:8.2.2-2 has caused the Debian Bug report #1018924, regarding libgc FTBFS: architecture-specific symbol handling 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.) -- 1018924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgc Version: 1:8.2.2-1 Severity: serious Tags: ftbfs Hi, what happend to libgc? It ftbfs on all 32bit architectures and its symbol handling is essentially stripped of all the architecture-specific patterns that we have accumulated over the years. The general quality of the upload seems questionable as well: * A possibly breaking change for a core package is often done to experimental first to reduce disruption of development on unstable. Doing so would have prevented major pain here. * The debian/changelog entry contains duplicates. * Lots of symbols were dropped from the symbols file without bumping soname. Possibly, this may lead to incorrect dependencies on libgc in downstream builds. * debian/changelog says that you removed libatomic_ops handling, but for every new architecture libatomic_ops is still opted in leading to unnecessary porting work even though built-in atomics generally work well. I am also wondering whether this actually is a package hijack as there is no visible acknowledgement from any existing maintainers to adding Ian to uploaders. I am quite disappointed by this upload and the downstream pain it causes to QA. Helmut --- End Message --- --- Begin Message --- Source: libgc Source-Version: 1:8.2.2-2 Done: Ian Wienand We believe that the bug you reported is fixed in the latest version of libgc, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Wienand (supplier of updated libgc 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: Mon, 05 Sep 2022 21:17:49 +1000 Source: libgc Architecture: source Version: 1:8.2.2-2 Distribution: unstable Urgency: medium Maintainer: Christoph Egger Changed-By: Ian Wienand Closes: 1018924 Changes: libgc (1:8.2.2-2) unstable; urgency=medium . * Remove libatomic_ops as a build-dep; remove matching from build to simplify future porting. * libgccpp.so.1 : add back differing 32-bit C++ symbols (Closes: #1018924) Checksums-Sha1: bf07d186fc7924a3bab09eb95f071dd5ac135ee9 1910 libgc_8.2.2-2.dsc 80cd4d29841bf26df5e2e6a1faff78e73eaa946c 11380 libgc_8.2.2-2.debian.tar.xz 09e61ba9da2a1870597654da9272c0dd6013b150 8109 libgc_8.2.2-2_amd64.buildinfo Checksums-Sha256: 704aea545f48b3e81239bac46fea108739659455887d919d9d4c7ae4c10febbc 1910 libgc_8.2.2-2.dsc 00f6e74cf5a9bd7a2b77fa331b66b906c7098d61a7c4987bbae2bec3b96417bc 11380 libgc_8.2.2-2.debian.tar.xz 3cf9b798140bfb8e6b3ad8b5c4b40c279ba24f3eb3637d45e4db12a8a7f18a12 8109 libgc_8.2.2-2_amd64.buildinfo Files: f5010a9562d4e43d114df787c3540e9e 1910 libs optional libgc_8.2.2-2.dsc 701ec10248c209a1207f0adefdb59024 11380 libs optional libgc_8.2.2-2.debian.tar.xz 63bd157478861f20d1bf58ff260cb25d 8109 libs optional libgc_8.2.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/jNmIQptCYnCR/1utqb7i5YVrsgFAmMV24gACgkQtqb7i5YV rsg+og/8D64ncYvItrNHLI3A+Dx6zKJMHcxUnqvjZPVfKI+Gcl6DNleyT3PvonB4 SoMcgqSR3ufdhjfsrqYDKKaEw7o0+XRQCwaerpHeC6Rnj9SMf90jxAziggkBoAxy pLbI76sjDDvFvtTbsVFK8QnrQodP+Sa3zjSaoAWjWGk8PjoPOUSfp+sXN+HTQ0Z+ XiIOeyrNtL1zukE1iHmYegg3Jn6/KilV0AOHCwLtonwnMgsUnU2+y5/QTjwqEWUe vzcEixmw3jnMJtRsJm/1q9fjKUlDM3MNJyAGqWVaiK1yjOCeOmVZ6wAWzLKlOFji lFnXa3Zg6gDAdZRHB65G3oqUNstyZqMMwxl+/8u7TcENlymd3GmkQezzYwbfxras LxMVbcfXUwXibtFG7S5ZY53ayiv/lXNMJ9BCxZ9JWGPrqEc+7VKGJvCY/4Hf13U4 TDm0aycOM9bKg6Mbd6hpLRC/eNgCrSaIos0MC8UF30CFhz6SAy8ZNIhYLhm/J8IL sbOJLv0v7a7e/SC+3WDXJXlUcF9VVAFIco7pwJ/4z3ZnSJyNNRKJHOYhPNFuYJ+G MsdLr1Mr42MOVzisY66oc4vvXv7tlT8oK+Cd/ZtJFrfSwVclXot4VTFwVjjCt3zT gavIMaHkSLhSgYuUMKbZKmaVBXq3+qwkvu8tzZhrU/58BDU5m+U= =kgxF -END PGP SIGNATURE End Message ---
Bug#1019137: marked as done (FTBFS: FAIL: TestNewCmdCompletion/zsh_completion)
Your message dated Mon, 05 Sep 2022 11:20:29 + with message-id and subject line Bug#1019137: fixed in gh 2.14.7+dfsg1-1 has caused the Debian Bug report #1019137, regarding FTBFS: FAIL: TestNewCmdCompletion/zsh_completion 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.) -- 1019137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gh Version: 2.14.4+dfsg1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: z...@debian.org --- FAIL: TestNewCmdCompletion (0.00s) --- PASS: TestNewCmdCompletion/no_arguments (0.00s) --- FAIL: TestNewCmdCompletion/zsh_completion (0.00s) --- PASS: TestNewCmdCompletion/fish_completion (0.00s) --- PASS: TestNewCmdCompletion/PowerShell_completion (0.00s) --- PASS: TestNewCmdCompletion/unsupported_shell (0.00s) Caused by golang-github-spf13-cobra 1.5.0 https://salsa.debian.org/go-team/packages/golang-github-spf13-cobra/-/commit/37d481d4 --- End Message --- --- Begin Message --- Source: gh Source-Version: 2.14.7+dfsg1-1 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of gh, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated gh 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: Mon, 05 Sep 2022 03:25:09 -0600 Source: gh Architecture: source Version: 2.14.7+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Anthony Fok Closes: 1019137 Changes: gh (2.14.7+dfsg1-1) unstable; urgency=medium . * New upstream version 2.14.7+dfsg1 * Update versioned dependencies as per go.mod * Refresh 0001-set-defaultEditor-as-per-debian-policy.patch * Apply 0002-Bump-github.com-spf13-cobra-from-v1.4.0-to-v1.5.0.patch: Cobra v1.5.0 contains a fix for the zsh autocompletion #compdef line to only complete , not _ the completion function itself, See https://github.com/cli/cli/pull/6196. TestNewCmdCompletion for zsh, which checks that #compdef line, is updated accordingly. Fixes "FTBFS: FAIL: TestNewCmdCompletion/zsh_completion" with golang-github-spf13-cobra-dev (>= 1.5.0). Thanks to Shengjing Zhu for reporting the issue. (Closes: #1019137) Checksums-Sha1: 860a0f9359eac57a710fd52be952d64d5d413d6a 3897 gh_2.14.7+dfsg1-1.dsc bfe94542b179e7804ec08558d6149b49666184df 426920 gh_2.14.7+dfsg1.orig.tar.xz bef46727c753c9009063d2f50d06475fa00f3db4 940500 gh_2.14.7+dfsg1-1.debian.tar.xz 7644da2858011854608f20257bf579e6e67d91a4 12541 gh_2.14.7+dfsg1-1_amd64.buildinfo Checksums-Sha256: 50441729bac3754b897892d59c35a9257857a49a878ad7f8dd61dc9fd6e95d84 3897 gh_2.14.7+dfsg1-1.dsc e2e825ef31dc7c666743eabbc19e1f804fb51a5868cb6aeba71ed588b58fa7b8 426920 gh_2.14.7+dfsg1.orig.tar.xz ca669b3cc19418520f3eb24f5904e19263d383e30277a5e1a95ff042fd526796 940500 gh_2.14.7+dfsg1-1.debian.tar.xz 372691b5cf8579f1d6498f6c948c12728c1967ee71a8a48a8440049e43c88d81 12541 gh_2.14.7+dfsg1-1_amd64.buildinfo Files: 6a7635faed285ac4a52653263929a760 3897 golang optional gh_2.14.7+dfsg1-1.dsc 052b0414785fe2eff55ca32198718f1a 426920 golang optional gh_2.14.7+dfsg1.orig.tar.xz bb30cb24439813a3889202b3931b18e7 940500 golang optional gh_2.14.7+dfsg1-1.debian.tar.xz f1897cedc3f7d90a9ec40031de21738e 12541 golang optional gh_2.14.7+dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmMV1pwQHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWazzC4D/9aKxW8M/YYYczjotpJS179qwA+jKXVvbm2 vQ3l3sZs8PWRvyEQUj6dVrEjSsuk0PONPHVFjPxK1eiLfDKOeqfkOfVANuCtCrw7 gY8u+zuqMozQD8yQFPtaC9aUcdpzJCOqd0n5hAdKW+cLdmUufWRtRLs7C/3lHoTp rhPwnqyxC/6FQs9T9fMY2iASOQthojlfhOXfXNqkRndInVXABLP3ktW/v9LbBmM4 T7Mc4uhC8iIvamDwYyMepwtT4GcRWg/Inz3TsyoziC6WEvX0I6POtp4efiROK0K5 pFtpN2Ca3tGaMVMO83/Lx2ewM0DjfbYWMtIcFdosqDxsJ4Rcs0xd6/+kt1baqrFn mt8dBAv+HliUl0BeHScZQSnUeKN8rhl5RQxwq4ybNaE+F/Ub9ZDA0AiArw+2AF+p lhNiR524ZZG7njguJThaTqIRIyQwVyi89mvM3x0u9TSik4MWkQdhIUJVcYb2C/gB J4zAOe49uaWI/1qprozSriyzI7u8IZEZ8FJ0eWaBfP7p28Miqh1bYhMPUWrFNfSy
Bug#1018043: zutils: statically linked
On 9/2/22 14:31, Adam Borowski wrote: > ♥ thank you for bringing it up. ;) > merged-usr is unrelated here: we have dropped support for booting the system > without /usr /etc /var mounted several years ago; merged usr is about moving > things around replacing them with symlinks. jftr, I'm aware - however, for an invidual package "needlessly" removing existing compatibility for standlone-/usr without "reason" is not nice (eventhough I've never needed that, and that it's not supported as a general concept anymore since a several releases). what I've tried to say is that with merged-/usr, this is an additional reason on top of the others for why it doesn't make sense anymore to keep it statically compiled. Regards, Daniel
Bug#1002239: google-authenticator: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2
Hi, On Tue, Dec 21, 2021 at 05:33:17PM +0100, Lucas Nussbaum wrote: > Source: google-authenticator > Version: 20191231-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. I'm not the maintainer but noticed that google-authenticator is being held out of testing due to this bug. But this package seems to rebuild successfully for me locally, and https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/google-authenticator.html seems to concur. Can this bug be closed, please? Thanks, Robie signature.asc Description: PGP signature
Bug#1017369: Thanks for the report and the pre-work
Hi, thanks Peter for the report and debdiff. Ack to the d/control dependency change and the d/rules cleanup improvement. For the code changes [1] landed upstream now and I think I'll use that instead. [1]: https://github.com/mdevctl/mdevctl/commit/58cd8604db2e5a3fb9ceb76cbbf09675873cce77
Bug#1018924: libgc FTBFS: architecture-specific symbol handling removed
On Mon, Sep 05, 2022 at 08:13:49AM +0200, Helmut Grohne wrote: > To make your (and my) life easier, I suggest that you use modern symbol > features (man deb-src-symbols). In particular, you can restrict symbols > to 32bit or 64bit using "(arch-bits=32)symbol..." and you can use C++ > symbol mangling using "(c++)unmangled...". I think I'd like to investigate that for the C++ library when this is resolved. > I happen to not understand which symbols are internal and which are not. > I really cannot tell. I'm more than happy if those really are unused. >> My opinion this should not lead to incorrect dependencies on libgc >> but how could we figure it out practically. If it would turn out >> later that some of dropped symbols are nonetheless in use, then I >> think it would not be complicated to fix it on the libgc side. This was our original discussion with the C library. I think it is still valid. > If you look into the differences, it's not just C++ symbols that have > been dropped. Here is a list of dropped symbols: This was per the discussion above. > Also note the (arch-bits=...) handling for C++ mangled symbols. I > suspect that putting this back fixes the FTBFS already. I've had a close look and I belive https://salsa.debian.org/debian/libgc/-/merge_requests/9 fixes these. > > > * debian/changelog says that you removed libatomic_ops > > >handling, but for every new architecture libatomic_ops is still > > >opted in leading to unnecessary porting work even though built-in > > >atomics generally work well. > That and the handling in debian/rules. In particular, the handling of > ATOMIC_BUILTIN_ARCHS is relevant to porting. Essentially, we'd want that > to be opt-out rather than opt-in. Basically every new architecture has > to add itself there, which seems useless busywork. I agree with this; the idea was to have this as a build-dep and opt-in these platforms, but I can see that we are better off just dropping it. https://salsa.debian.org/debian/libgc/-/merge_requests/10 proposes this. I would appreciate another set of eyes on that one just to double check it (and the other bits, but this one in particular). We can upload from the master branch then. -i
Bug#1018043: marked as done (zutils: statically linked)
Your message dated Mon, 05 Sep 2022 09:50:41 + with message-id and subject line Bug#1018043: fixed in zutils 1.12~pre2-2 has caused the Debian Bug report #1018043, regarding zutils: statically linked 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.) -- 1018043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zutils Version: 1.11-5, 1.12~pre2-1 Severity: serious Justification: Policy 10.1 Hi! This package has a massive size, as it's pointlessly statically built. Not only this violates a "must" requirement of the Policy, it also does so for no benefit at all: in the case libraries it's linked with would be subverted/corrupted, both the compressor and the actual tool invoked won't be able to run anyway. On the other hand, any security hole in any library the program links with potentially requires a recompile. Even glibc itself receives several CVEs per year; they are in functions you almost surely don't use but the binary doesn't provide this information anymore -- requiring the Security Team to analyze what is going on. That's why the Policy hates this seemingly minor issue so much. Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.3-00017-g519775569157 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages zutils depends on: ii libc6 2.35-0experimental1 ii libgcc-s1 12.2.0-1 ii libstdc++6 12.2.0-1 Versions of packages zutils recommends: ii bzip2 1.0.8-5 ii lzip 1.23-4 ii xz-utils 5.2.5-2.1 ii zstd 1.5.2+dfsg-1 zutils suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: zutils Source-Version: 1.12~pre2-2 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of zutils, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated zutils 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, 05 Sep 2022 11:23:09 +0200 Source: zutils Architecture: source Version: 1.12~pre2-2 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1018043 Changes: zutils (1.12~pre2-2) sid; urgency=medium . * Uploading to sid. * Building zutils dynamically as static-workaround is not necessary anymore (Closes: #1018043). Checksums-Sha1: bc70b39680971e9da7278a27c87f9c3629656b12 1931 zutils_1.12~pre2-2.dsc 7d78f4cbc4890f732b06f95150908341a9acb2f5 7096 zutils_1.12~pre2-2.debian.tar.xz cb2a5a4b87af8d5363f09fa7fa4cc0afef9f2f99 6593 zutils_1.12~pre2-2_amd64.buildinfo Checksums-Sha256: 7a9ebbaf4043568274471a8f2849737351d877d1fdaa9ca1b9c549dae6c8f189 1931 zutils_1.12~pre2-2.dsc b079f6194d4acc502bf7f45d95a3c39b5e1fe1734e70e529284e6f97fa65439d 7096 zutils_1.12~pre2-2.debian.tar.xz 22fe8737a518707524b64aba6139d72eb815bc268f172f2198417dd920433b8d 6593 zutils_1.12~pre2-2_amd64.buildinfo Files: 2e4ec49dd0513e22c558ced412ed7564 1931 utils optional zutils_1.12~pre2-2.dsc 7f660410dd7ab77a40327788356a84c2 7096 utils optional zutils_1.12~pre2-2.debian.tar.xz 162e3a46746d77bbdf22555c3ffc8d69 6593 utils optional zutils_1.12~pre2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmMVwHUACgkQVc8b+Yar ucddsw//eyUe/55D3FF5LhgD5+/IZG7qn05jKmZfPrtQ7cBOfSE9w/FbuPkK47VQ CIYs5wVHw+LPGeOx2CWsoxIQ0pbnRwWYcngHXMXXUFalLEOV7Ozj6PZ9fFLkSh6T gfVaa96PZECGrvYLjbjnxTda1b5RT9XQ/fmUJHEKQUFfeS2/OxNdw6+ZVcufZk+1 7X4n0tiyC0iCUz2ws1t3Pxo1VyonnEa8QZcaWITE1ztGg556NxWxHul1sk94AmxX d7XmWi6yVkNWymeMO8st6hwjbI20jG+IBLW5M7dEUCGuZc8nMNwgXCGxMbHD15wF BOxlH7YnFYnMQgwZSWHqvmL/ga95ydBdiLnU1kAtwDkXO6vHolxJ1gVtqaFNMUZm
Bug#1019095: marked as done (promod3 FTBFS with multiarchified openstructure)
Your message dated Mon, 05 Sep 2022 08:51:11 + with message-id and subject line Bug#1019095: fixed in promod3 3.2.1+ds-5 has caused the Debian Bug report #1019095, regarding promod3 FTBFS with multiarchified openstructure 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.) -- 1019095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: promod3 Version: 3.2.1+ds-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=promod3=amd64=3.2.1%2Bds-4%2Bb1=1662229682=0 ... CMake Error at cmake_support/FindOPENSTRUCTURE.cmake:37 (message): Could not find library ost_io. Please specify the location of your OpenStructure installation with OST_ROOT Call Stack (most recent call first): cmake_support/FindOPENSTRUCTURE.cmake:98 (find_OPENSTRUCTURE) CMakeLists.txt:106 (find_package) -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: promod3 Source-Version: 3.2.1+ds-5 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of promod3, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated promod3 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, 05 Sep 2022 02:57:08 -0400 Source: promod3 Architecture: source Version: 3.2.1+ds-5 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1019095 Changes: promod3 (3.2.1+ds-5) unstable; urgency=medium . * Adjust the build to multiarchified openstructure (Closes: #1019095) Checksums-Sha1: 104afda7b5a45cef03a7dc77235b7102520fc406 3225 promod3_3.2.1+ds-5.dsc e259ea759d3bd215744aa959736fdaddfc38293e 6140 promod3_3.2.1+ds-5.debian.tar.xz 1a2024004b0d66196643e6445ed113b09014f19e 8265 promod3_3.2.1+ds-5_source.buildinfo Checksums-Sha256: 094127aaf0eae9c1e06799fcae083f488a6f063745daf21dc6de508b85710a2d 3225 promod3_3.2.1+ds-5.dsc 9fbe419d07e73566d06a4678831c26578f3a866458b2d7f0bd44d1b2e0a83707 6140 promod3_3.2.1+ds-5.debian.tar.xz b7b78611046ab30be481b2a0e935c176c67f01330f43edbd02bcd4f969ed2c77 8265 promod3_3.2.1+ds-5_source.buildinfo Files: 2e675c0253ac6a5602df23dd4de2dc8a 3225 science optional promod3_3.2.1+ds-5.dsc b04dbf10bfb84dbb4b969c5934e059c7 6140 science optional promod3_3.2.1+ds-5.debian.tar.xz 561cf79914a58a84a73f8409b0b650ce 8265 science optional promod3_3.2.1+ds-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmMVtTgSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHhLkP/14OtsOXAmNp5hHY4chAAepdyhNJ+5WT eMarA2/aD39sbTeTs/nwGI4kp8op8R746qm4SVXb9+Nlpl4H/Vj4XCJTrvcUZMmw 9QkaTA3exefWn3SIXydJgCsr9yAR3ccChmDvADuhGYqvLYGpwI96UadCMZ1Xw0BP 4bMdsTOVqztpQ5SX7HfrP8lrwWCFW5atKEX0hBAT0WapBbUqROJbIDv7OL1QD/A7 QtC5OBR/Uj5xlcHn1O8bGnePEba2Q9cy36HpXHO9uAsGa7hKBGT+MkUBvUGpHulx InYWJDMo1qn4egXZ7O9A81bVohEDRqvJn3zi7cIKy29ifOKJzFC3vFRI4pkGurib WXLrboyP+76tHshKJLGy6Tn0foPt1ni2lBjClRKZeVwLMRWdEakMhqW9LKyrXk9L oajlFLOIB3c4Xa1QfqHr68MhjSuPrBB1p+O8uEw8Ju7Bhh4XZpxHTZB/gcYFFpU1 69HhAE2b14S488gJ5yRqN496AYfQgm6Vp9KsJ8fxJ42ftBgPs68ldI8cWzRSh7pX vOQQx6eVt0nu03vWPqzOg2GZ5n3wicPlxJLoi+t6eWvSMPeRuSXumyG/r2U4fbUf THAbjWjpsiJlyQOOvysQlmdyl4N7Zxa33JHIgdN7l0uf5MrCtwzfOr9DTSIriwBc PJlPjlNc4m7C =2v0h -END PGP SIGNATURE End Message ---
Bug#1009073: marked as done (virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data())
Your message dated Mon, 05 Sep 2022 10:19:14 +0200 with message-id <87b498c6ecae1690cc31a7592c4f63ca0016ecd0.ca...@debian.org> and subject line virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data() has caused the Debian Bug report #1009073, regarding virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data() 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.) -- 1009073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: virglrenderer Version: 0.8.2-5 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for virglrenderer. CVE-2022-0135[0]: | out-of-bounds write in read_transfer_data() If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-0135 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0135 [1] https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/654 [2] https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/95e581fd181b213c2ed7cdc63f2abc03eaaa77ec Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.10.0-1 thanks --- End Message ---
Processed: tagging 1018801
Processing commands for cont...@bugs.debian.org: > tags 1018801 + ftbfs Bug #1018801 [src:stdx-allocator] stdx-allocator ftbfs: assertThrown failed: No Exception was thrown. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1018801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018924: libgc FTBFS: architecture-specific symbol handling removed
Hi Ivan, On Mon, Sep 05, 2022 at 12:17:10AM +0300, Ivan Maidanski wrote: > Let me go thru all items you warry about. Please be sure both Ian and I pay > attention to the quality of the prepared releases. Sometimes mistakes happen > — it is essential to promptly react and think of the proper fix or workaround > in such situations. Thank you. I concur. Please upload a fixed version quickly. This currently breaks half of the bootstrap ci jobs, which makes me blind to breakage in other packages. Urgency is needed here. > The builds fail because of a change in some mangled names — probably the > reason is changing of noexcept/throw() specification in operator delete > (libgc tries to follow C++ standard but if this breaks some ABI, it could be > configured at build time thru macros). I need more time to check the > situation deeper. That would sound reasonable if the upload had been done to experimental. The combination of urgency and "need more time" is unfortunate. I fear that doing it improperly would be making it worse as symbol issues can have a rippling effect. Admittedly all missing symbols on the most recent upload seem to be C++ symbols. That much is plausible at least. To make your (and my) life easier, I suggest that you use modern symbol features (man deb-src-symbols). In particular, you can restrict symbols to 32bit or 64bit using "(arch-bits=32)symbol..." and you can use C++ symbol mangling using "(c++)unmangled...". > > its symbol handling is essentially stripped of all the > >architecture-specific patterns that we have accumulated over the years > > These stripped symbols are actually «leaked» internal symbols of libgc, > additionally I am not aware of any libgc client S/W which relies on these > internal symbols. Let me know please if someone is using any of the stripped > symbols. There is no practical reason of keeping these symbols in libgc > except for a formal one. Please correct me if I am wrong. I happen to not understand which symbols are internal and which are not. I really cannot tell. I'm more than happy if those really are unused. > > * Lots of symbols were dropped from the symbols file without bumping > >soname. Possibly, this may lead to incorrect dependencies on libgc in > >downstream builds. > > Bumping soname indicates no backward compatibility. This has some negative > drawback (e.g. system should have 2 versions of libraries, client S/W does > not benefit from the new library version until client binary is rebuilt). I > avoid deletion or incompatible changes of API symbols between libgc releases. > (Unfortunately there’s an issues with a mangled name I wrote above.) I’ve > explained the situation about dropping of lots of symbols above. My opinion > this should not lead to incorrect dependencies on libgc but how could we > figure it out practically. If it would turn out later that some of dropped > symbols are nonetheless in use, then I think it would not be complicated to > fix it on the libgc side. If you look into the differences, it's not just C++ symbols that have been dropped. Here is a list of dropped symbols: < GC_FirstDLOpenedLinkMap@Base 1:7.2d < (arch=kfreebsd-amd64 kfreebsd-i386)GC_FreeBSDGetDataStart@Base 1:7.2d < (arch=sparc sparc64)GC_SysVGetDataStart@Base 1:7.2d < (arch=!nios2 !sh4)GC_acquire_mark_lock@Base 1:8.0 < (arch=!nios2 !sh4)GC_active_count@Base 1:8.0 < GC_add_ext_descriptor@Base 1:7.2d < GC_add_map_entry@Base 1:7.2d < GC_add_roots_inner@Base 1:7.2d < GC_add_smashed@Base 1:7.2d < GC_add_to_black_list_normal@Base 1:7.2d < GC_add_to_black_list_stack@Base 1:7.2d < GC_add_to_fl@Base 1:7.2d < GC_add_to_heap@Base 1:7.2d < GC_adj_bytes_allocd@Base 1:7.2d < GC_all_bottom_indices@Base 1:7.2d < GC_all_bottom_indices_end@Base 1:7.2d < GC_alloc_large@Base 1:7.2d < GC_alloc_large_and_clear@Base 1:7.2d < GC_alloc_reclaim_list@Base 1:7.2d < GC_allocate_ml@Base 1:8.0 < GC_allochblk@Base 1:7.2d < GC_allochblk_nth@Base 1:7.2d < GC_allocobj@Base 1:7.2d < GC_apply_to_all_blocks@Base 1:7.2d < GC_approx_sp@Base 1:7.2d < GC_array_kind@Base 1:7.2d < GC_array_mark_proc@Base 1:7.2d < GC_array_mark_proc_index@Base 1:7.2d < GC_avail_descr@Base 1:7.2d < GC_bl_init@Base 1:7.2d < GC_bl_init_no_interiors@Base 1:7.2d < GC_black_list_spacing@Base 1:7.2d < GC_block_empty@Base 1:7.2d < GC_block_nearly_full@Base 1:7.2d < GC_block_was_dirty@Base 1:7.2d < GC_bm_table@Base 1:7.2d < (arch=!kfreebsd-amd64 !kfreebsd-i386)GC_brief_async_signal_safe_sleep@Base 1:7.6.4 < GC_build_fl2@Base 1:7.2d < GC_build_fl4@Base 1:7.2d < GC_build_fl@Base 1:7.2d < GC_build_fl_clear2@Base 1:7.2d < GC_build_fl_clear4@Base 1:7.2d < (arch=!nios2 !sh4)GC_bytes_allocd_tmp@Base 1:8.0 < GC_bytes_found@Base 1:7.2d < GC_check_annotated_obj@Base 1:7.2d < GC_check_finalizer_nested@Base 1:7.2d < GC_check_heap@Base 1:7.2d < GC_check_heap_block@Base 1:7.2d < GC_check_heap_proc@Base 1:7.2d < GC_check_leaked@Base 1:7.2d <
Bug#1017592: marked as done (mmdebstrap: autopkgtest fails because getpwnam is broken in fakechroot since glibc 2.34)
Your message dated Mon, 05 Sep 2022 06:03:42 + with message-id and subject line Bug#1017592: fixed in mmdebstrap 1.2.0-1 has caused the Debian Bug report #1017592, regarding mmdebstrap: autopkgtest fails because getpwnam is broken in fakechroot since glibc 2.34 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.) -- 1017592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mmdebstrap Version: 1.1.0-1 Severity: serious X-Debbugs-Cc: jo...@debian.org Control: block -1 by 1017590 Hi, since the upload of src:glibc 2.34, getpwnam are not wrapped anymore by fakechroot. This breaks the autopkgtest of mmdebstrap. See https://bugs.debian.org/1017590 for details. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: mmdebstrap Source-Version: 1.2.0-1 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of mmdebstrap, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Schauer Marin Rodrigues (supplier of updated mmdebstrap 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, 05 Sep 2022 07:48:37 +0200 Source: mmdebstrap Architecture: source Version: 1.2.0-1 Distribution: unstable Urgency: medium Maintainer: Johannes Schauer Marin Rodrigues Changed-By: Johannes Schauer Marin Rodrigues Closes: 1017592 1017795 1018957 Changes: mmdebstrap (1.2.0-1) unstable; urgency=medium . * new upstream release - fix mmdebstrap hanging if apt in download step failed (closes: #1017795) - remove proot mode (closes: #1018957) * fix autopkgtests (closes: #1017592) Checksums-Sha1: 2bb82dc234904026d28a878c517cbe5fe2b67387 2329 mmdebstrap_1.2.0-1.dsc f46cd3ccca3ebd01b0a12e3ee5b029268871c1d7 126066 mmdebstrap_1.2.0.orig.tar.gz 4100f34df86a9451f0a8662629527fb827c36d00 10936 mmdebstrap_1.2.0-1.debian.tar.xz Checksums-Sha256: 8cd25a0c58b40fcc38ebe49b0d5be41352dfa9ec3148e91f4de1637f7b8b3259 2329 mmdebstrap_1.2.0-1.dsc 71ce0d4d9fbe99b985be5d35ca5fb595ad52b5d0a8c46ded039c422b788e4f0b 126066 mmdebstrap_1.2.0.orig.tar.gz 8def63a6b3a33532cff9ed661df5bb8f16b52f838dc79f19705e79b945f8e649 10936 mmdebstrap_1.2.0-1.debian.tar.xz Files: a80268c54126acbe2e9fb6351c1c2355 2329 admin optional mmdebstrap_1.2.0-1.dsc c99f91dcfc285636d25cc0209d01afea 126066 admin optional mmdebstrap_1.2.0.orig.tar.gz d2982c64a2d3578900f893cce9aae727 10936 admin optional mmdebstrap_1.2.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmMVjd4ACgkQ8sulx4+9 g+FZ3Q/9GNPiBq38Ngnd6UoAfYGgssMTXP7aBfSNKprmnupxgudHPAyBa/5ssjXm laXULbGyElIVB/7Nm0Ppb0laBmdrG3vfkYmJRacKWfQ0f9D4sUKpzxrDW2e1hx3I 9zaYqWh5+gQ7yv85jqd/JJWyOoiPnAWW7D5B86eqzYqa+6Vn5CbRG+0c7K6qqfiU tC4QJERu5c2y24MFxyVPtduhhbdbU0cHWawReVaa2y3rgKT/DgnnXXXtcxUv/9uO ouYaG68l4uctGhbtKR+nw8f8hhcw/F5en2q5a49scNnFLu0t1/gXv232M4FeK6Q+ Qq8n3sZFidQW3103ygQ/MtFEoaxkBVFDd1c/+Fp4G634Q8AGzcJhAdQr1j5UyRyc +I6PwBrjXgME+sVOyo713yvZxwW6P7mBgG75xhtQi5JJJFc51xa6VkJ2pFcpqgE6 aOQ/WYrUcNalrZQlnnPnpieR9SajP9RBpIYg5ubeHrqayARjOBrZlB3k444WAY54 En9vfmlOjveJ3b1UkZWnIMefpw+7EhqVKiUE5X2t6y2X3/Rz+rBhOzwCHan1zzLs 2bGVO18pH2KOLN73BFspGEVlefxP3OGhs9QI7PDUY0tHZyTgJSyjBmLH6RVRWGAk WQU/qB256zZUJ0UlymuFqXT11OcTarxRJ0fBYBTtJIA+65Fdw08= =r3qz -END PGP SIGNATURE End Message ---
