Bug#1030444: marked as done (pdb2pqr: FTBFS: make[1]: *** [debian/rules:21: override_dh_installman] Error 1)
Your message dated Sun, 05 Feb 2023 08:39:05 + with message-id and subject line Bug#1030444: fixed in pdb2pqr 3.5.2+dfsg-3 has caused the Debian Bug report #1030444, regarding pdb2pqr: FTBFS: make[1]: *** [debian/rules:21: override_dh_installman] Error 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.) -- 1030444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdb2pqr Version: 3.5.2+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > PYTHONPATH=. help2man debian/pdb2pqr/usr/bin/dx2cube --no-info > --version-string 3.5.2+dfsg > dx2cube.1 > help2man: can't get `--help' info from debian/pdb2pqr/usr/bin/dx2cube > Try `--no-discard-stderr' if option outputs to stderr > make[1]: *** [debian/rules:21: override_dh_installman] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/03/pdb2pqr_3.5.2+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: pdb2pqr Source-Version: 3.5.2+dfsg-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of pdb2pqr, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pdb2pqr 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: Sun, 05 Feb 2023 09:02:21 +0100 Source: pdb2pqr Architecture: source Version: 3.5.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1030444 Changes: pdb2pqr (3.5.2+dfsg-3) unstable; urgency=medium . * Standards-Version: 4.6.2 (routine-update) * cme fix dpkg-control * Drop version restriction from docutils Closes: #1030444 Checksums-Sha1: b71365439011339632c0ca021e6a8e95f1b9bef5 2490 pdb2pqr_3.5.2+dfsg-3.dsc ffdd80247c48306b03f8e310e76ccbd83613c79c 9816 pdb2pqr_3.5.2+dfsg-3.debian.tar.xz 7493158c2ba41977fc7f17a5ee8f7d4be7887e6a 8780 pdb2pqr_3.5.2+dfsg-3_amd64.buildinfo Checksums-Sha256: 4895477420299cf7df205008c7715d878dfd5db512eaba90a97982795980efab 2490 pdb2pqr_3.5.2+dfsg-3.dsc 795683c209541843d15ba700b5e3d839732291737e951ab9473896424b3779f4 9816 pdb2pqr_3.5.2+dfsg-3.debian.tar.xz cee5c54971e9cd02d08f9266421859efecdcc2c7ee75727c4cd5d7ed7cec88ef 8780 pdb2pqr_3.5.2+dfsg-3_amd64.buildinfo Files: 8b6fb08cbd445ec4b99aaf624087b92f 2490 science optional pdb2pqr_3.5.2+dfsg-3.dsc 45a834aefff7976995513d90e3edba7c 9816 science optional pdb2pqr_3.5.2+dfsg-3.debian.tar.xz 9d6b7bad524534046398c2a4954780ca 8780 science optional pdb2pqr_3.5.2+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPfY88RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHPgQ/+Lx56XVM5bDAxwqkrR7DsUJvVbjSw8t4v P9qYSolM5DBlW2z/Jao4C8iq7XKNOiKKOH6d6Y59ngF1KbKk1llbjHtp5bx6yCTN VIPvXZ69ttOF3Tuk/lztN3Z7HXNgC1o9m5+xZpbGfwDM0mnihi+XAR34r6ZKeG8H Ei+ErmlLy3xd924DOsxNm+LLrODi2OOiAnPs9LKKW32Ih15av4V7C5HbfAm7WJ36 Ln9jyXS4yzAGOTs6oyEtGOEMXBvIEEPtR9qypFDTFru0z4zjbdpAPF7sny05bI/P 0HY9b5Zc1pz/QXS0SjnWp9oilSqo6yG5KI8FB
Bug#1030463: marked as done (uc-echo: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: python3-scipy:native)
Your message dated Sun, 05 Feb 2023 08:40:18 + with message-id and subject line Bug#1030463: fixed in uc-echo 1.12-18 has caused the Debian Bug report #1030463, regarding uc-echo: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: python3-scipy:native 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.) -- 1030463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uc-echo Version: 1.12-16 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -sa > dpkg-buildpackage: info: source package uc-echo > dpkg-buildpackage: info: source version 1.12-16 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Graham Inggs > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-scipy:native > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting > dpkg-buildpackage: warning: (Use -d flag to override.) > > Build finished at 2023-02-04T03:05:19Z The full build log is available from: http://qa-logs.debian.net/2023/02/03/uc-echo_1.12-16_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: uc-echo Source-Version: 1.12-18 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of uc-echo, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated uc-echo 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: Sun, 05 Feb 2023 08:45:28 +0100 Source: uc-echo Architecture: source Version: 1.12-18 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1030463 Changes: uc-echo (1.12-18) unstable; urgency=medium . * Fix Build-Depends Closes: #1030463 Checksums-Sha1: 47e2e301de6c2705a3a15e516c93e9a160482ac5 2106 uc-echo_1.12-18.dsc 4192c22537b7beff6bd3a6954562d40cee750171 8732 uc-echo_1.12-18.debian.tar.xz 9dceab42f536d985939ac1ecd0d09751f8ab196f 7486 uc-echo_1.12-18_amd64.buildinfo Checksums-Sha256: cce46744aaa94a9ef6ec21577578c12930b242cb1978bbd56550e324dd8ce9a8 2106 uc-echo_1.12-18.dsc 8dc6edf6c7abc97cfdee0cd42da63669afabe7d37305bc7330eb7b10e6908080 8732 uc-echo_1.12-18.debian.tar.xz 142bb5593df551091b2b8f766d15140911f4145b89f9276f212d884c24d16365 7486 uc-echo_1.12-18_amd64.buildinfo Files: 7a8fc22aefba6aa053d5e05540aa94b6 2106 science optional uc-echo_1.12-18.dsc 97ad0583d388f44de3c6a1b8483bc84b 8732 science optional uc-echo_1.12-18.debian.tar.xz f0faf2c19d5fc0d3dd5b8bd6a9714f83 7486 science optional uc-echo_1.12-18_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPfX5ARHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFlGQ//bOw+mPVYQMsPvRcGgQD96Nnzw9ULs0Mq /MDWtYxzsnis4O+6YihbtpJ0YYddoz92e2ptUIawgYdcsb
Bug#1030558: marked as done (toil build-depends on missing python3-xdist)
Your message dated Sun, 05 Feb 2023 08:40:10 + with message-id and subject line Bug#1030558: fixed in toil 5.9.2-1 has caused the Debian Bug report #1030558, regarding toil build-depends on missing python3-xdist 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.) -- 1030558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: toil Version: 5.9.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=toil&suite=sid toil build-depends on missing: - python3-xdist:amd64 Should this be python3-pytest-xdist? --- End Message --- --- Begin Message --- Source: toil Source-Version: 5.9.2-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of toil, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated toil 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: Sun, 05 Feb 2023 08:38:00 +0100 Source: toil Architecture: source Version: 5.9.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1030558 Changes: toil (5.9.2-1) unstable; urgency=medium . * Team upload. * New upstream version * Build-Depends: s/python3-xdist/python3-pytest-xdist/ Closes: #1030558 Checksums-Sha1: a7cf3ac1fec740144823519b2aa179adec4945ea 2640 toil_5.9.2-1.dsc aea63cf779668579463835102c883b72c50f9d1d 7667311 toil_5.9.2.orig.tar.gz d39806025da3282205d43dc4552b4c36f3a666b6 16336 toil_5.9.2-1.debian.tar.xz e07b49caf1b0e3d9253a7626a9c6d546ed985096 21885 toil_5.9.2-1_source.buildinfo Checksums-Sha256: 37d27837c93b46fdfc0bb55e28a89926f0d3286501d05a98a67c1a7c59f36d70 2640 toil_5.9.2-1.dsc 8207afd9ccd174f1137d9a131b1bb2da44875243dea4a0223f8f09f376e49916 7667311 toil_5.9.2.orig.tar.gz d978c660ac5cf70927402ae4b8ed2d049c4ba4ca1c5da77b25886b859b4aa0a8 16336 toil_5.9.2-1.debian.tar.xz bb116d991202796ea3135d13ad02fc84be6e12e7f365ed8e159faee093df2948 21885 toil_5.9.2-1_source.buildinfo Files: 16d1a618416e0ae0abc3328115631b77 2640 net optional toil_5.9.2-1.dsc 64b89a12f3e0fa3a5575aa8546c01d89 7667311 net optional toil_5.9.2.orig.tar.gz df5a9aa6acd85f888ad6cfa087730ea2 16336 net optional toil_5.9.2-1.debian.tar.xz 3421dc3d75ae5e73ab520ac1590419dd 21885 net optional toil_5.9.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPfYw8OHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtGyWQ//Vi6Bro6Y8R+M3hSidRuo/S9JTPG4iB0KyGS9 jMjPB3V6ki2aTLnkLYx0K7GUnwM75U/4wHgPePnQc0TVmh7jKUa+X5kDlq4MhXGy 9YJIFzTYaZD9YpOh/yHCJr/EGRhK5HmW8Y62D5bbyHRYG05dAZ518H8ra5OCr+9z dhLT4mltOFwDEEoeKCuWXuZ1z+4qYjBNQYEjRL038gtbI/EhV+xMnwBpo6xpPJxm TJyNj29EV1uZyRfzgEA7uPDjnW6wRqKfmEYuiyFyeBiNJBGGe6AkNrnOWYOIyoIn SLk1myRO8194/4rrsHh1B8brGWmXo/3mVs2a0H9PLbtDe0VzP2Rjz2vNb6sV4qrn 7hoSS7ZerqQz3NTKW8Ybj/CMpqQ9EtONnPY2ICuL3AhZFWGrmpTVW0+jLHz0Ne0R GLOIr795LMTfg4hj8XR0WQZZI/z9SHCv4+zD7FGvPcIokjrsZhMYL4en/S+wiYN+ I0yllKZNySxAmVra7v8oSxX7HIyfdpoVPkRxR8BpHzwvWVtNwf6kEirjMmuwjuOm 9fOQZjMgx8xdpoJEpEFIsnExFxkIzcwJb67Iz68SwOY5+NYLAV6OVMja9LDy3P3v pk1oyqvY4vVQKDLKw8AjQ0owqTJMy6pbFDVM6yh4ZZUc7yr6CZ+Omleoei5YpsL2 2ExMK4g= =ThPP -END PGP SIGNATURE End Message ---
Bug#1030096: #1030096 dask.distributed autopkgtest fail
Am Sat, Feb 04, 2023 at 10:43:59PM + schrieb Rebecca N. Palmer: > That removed most of the test failures, but there seem to be a few > apparently random ones left (2 runs both failed, but with different errors). > > On 04/02/2023 21:35, Andreas Tille wrote: > > Any reason to not push to master directly? > > I don't do that with packages that aren't mine. Also see above. Per our team policy that's fine and simply easier for other team members. Thanks a lot for your work Andreas. -- http://fam-tille.de
Bug#1030574: debian-edu-router-config: Missing dependency on procps
Package: debian-edu-router-config Version: 2.12.2 Severity: serious https://piuparts.debian.org/sid/fail/debian-edu-router-config_2.12.2.log ... /var/lib/dpkg/info/debian-edu-router-config.postinst: line 1485: sysctl: command not found dpkg: error processing package debian-edu-router-config (--configure): installed debian-edu-router-config package post-installation script subprocess returned error exit status 127 Processing triggers for libc-bin (2.36-8) ... Errors were encountered while processing: debian-edu-router-config E: Sub-process /usr/bin/dpkg returned an error code (1)
Processed: Re: Bug#916596: iptables.postinst failure on link creation
Processing control commands: > tags -1 - moreinfo Bug #916596 [iptables] iptables.postinst failure on link creation Removed tag(s) moreinfo. > severity -1 serious Bug #916596 [iptables] iptables.postinst failure on link creation Severity set to 'serious' from 'important' -- 916596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029594: New TB 1:102.7.1-1 from Mozilla
Hello Pete, Am 04.02.23 um 21:58 schrieb Pete Elliott: Hello, I'm ignorant as to how packages get updated. It appears that there is a newer version of TB 1:102.7.1-1 available from Mozilla than the one offered via the Debian package management system. Will this update at some point? we will update the package once the underlying issue is fixed. Mozilla is fist providing new version by a candidates/ tree and that is synced to releases/. If you compare the signatures for both files you will see they are equal, means both releases are equal. https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/source/thunderbird-102.7.1.source.tar.xz.asc https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build2/source/thunderbird-102.7.1.source.tar.xz.asc The current (new build) version of 102.7.1 might have fixed the OAuth issue on outlook.com, it's not confirmed by Mozilla. (It does seem odd that Mozilla's fix of the Oauth didn't generate a new version number as opposed to fixing a previously broken version.) Well, you can try out the Mozilla binary package to see if this version has a fixed behavior. https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/linux-x86_64/ Just download the language you want to use, extract the binary and start it, it will pick up your configuration automatically. I don't use and ever want to use a email setup on outlook.com, so I can't test anything. As written previously in this issue tracking, it's always possible to downgrade Thunderbird to the previous version. -- Regards Carsten
Bug#1028454: nsscache: build-depends on python3-mox3, to be removed from Debian
Package: nsscache Followup-For: Bug #1028454 Hi Thomas, It looks like the functionality from python3-mock upstream[1] has been included into Python >= 3.3. Would it make sense for nsswitch to migrate from mox3 to the stdlib implementation instead of python3-mock? Thanks, James [1] - https://github.com/testing-cabal/mock/
Bug#1030575: golang-github-hashicorp-go-slug: autopkgtest failure
Source: golang-github-hashicorp-go-slug Version: 0.9.1-1 Severity: serious X-Debbugs-Cc: Thorsten Alteholz https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-hashicorp-go-slug/31053988/log.gz ... dh_auto_test -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 64 github.com/hashicorp/go-slug === RUN TestPack slug_test.go:23: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestPack (0.00s) === RUN TestPackWithoutIgnoring slug_test.go:154: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestPackWithoutIgnoring (0.00s) === RUN TestPack_symlinks === RUN TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:false === RUN TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:false === RUN TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:false === RUN TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:false --- PASS: TestPack_symlinks (0.03s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:true (0.01s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:false (0.00s) === RUN TestUnpack slug_test.go:369: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestUnpack (0.00s) === RUN TestUnpackDuplicateNoWritePerm --- PASS: TestUnpackDuplicateNoWritePerm (0.00s) === RUN TestUnpackPaxHeaders === RUN TestUnpackPaxHeaders/extended_pax_header === RUN TestUnpackPaxHeaders/global_pax_header --- PASS: TestUnpackPaxHeaders (0.00s) --- PASS: TestUnpackPaxHeaders/extended_pax_header (0.00s) --- PASS: TestUnpackPaxHeaders/global_pax_header (0.00s) === RUN TestUnpackErrorOnUnhandledType --- PASS: TestUnpackErrorOnUnhandledType (0.00s) === RUN TestUnpackMaliciousSymlinks === RUN TestUnpackMaliciousSymlinks/symlink_with_absolute_path === RUN TestUnpackMaliciousSymlinks/symlink_with_external_target === RUN TestUnpackMaliciousSymlinks/symlink_with_nested_external_target === RUN TestUnpackMaliciousSymlinks/zipslip_vulnerability === RUN TestUnpackMaliciousSymlinks/nested_symlinks_within_symlinked_dir === RUN TestUnpackMaliciousSymlinks/regular_file_through_symlink === RUN TestUnpackMaliciousSymlinks/
Processed: Fwd
Processing commands for cont...@bugs.debian.org: > owner 978457 ! Bug #978457 [phing] phing: Not compatible with php8.0 Owner recorded as William Desportes . > tags 978457 + pending Bug #978457 [phing] phing: Not compatible with php8.0 Added tag(s) pending. > stop Stopping processing here. Please contact me if you need assistance. -- 978457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030576: rust-nanorand: autopkgtest failure on i386
Source: rust-nanorand Version: 0.7.0-7 Severity: serious https://ci.debian.net/data/autopkgtest/testing/i386/r/rust-nanorand/31043036/log.gz ... error[E0432]: unresolved import `core::arch::x86::_rdseed64_step` --> src/entropy.rs:58:6 | 58 | use core::arch::x86::_rdseed64_step as rdseed; | ^--^^ | || | |help: a similar name exists in the module: `_rdseed16_step` | no `_rdseed64_step` in `core_arch::arch::x86` For more information about this error, try `rustc --explain E0432`. error: could not compile `nanorand` due to previous error Caused by: process didn't exit successfully: `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=nanorand CARGO_MANIFEST_DIR=/usr/share/cargo/registry/nanorand-0.7.0 CARGO_PKG_AUTHORS='Lucy ' CARGO_PKG_DESCRIPTION='A tiny, fast, zero-dep library for random number generation.' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=Zlib CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=nanorand CARGO_PKG_REPOSITORY='https://github.com/Absolucy/nanorand-rs' CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.7.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=7 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 LD_LIBRARY_PATH='/tmp/tmp.Jyi2v4P3Dk/target/debug/deps:/usr/lib' rustc --crate-name nanorand --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="alloc"' --cfg 'feature="chacha"' --cfg 'feature="default"' --cfg 'feature="getrandom"' --cfg 'feature="pcg64"' --cfg 'feature="rdseed"' --cfg 'feature="std"' --cfg 'feature="tls"' --cfg 'feature="wyrand"' --cfg 'feature="zeroize"' -C metadata=afbb08af3d0c46ba -C extra-filename=-afbb08af3d0c46ba --out-dir /tmp/tmp.Jyi2v4P3Dk/target/i686-unknown-linux-gnu/debug/deps --target i686-unknown-linux-gnu -C incremental=/tmp/tmp.Jyi2v4P3Dk/target/i686-unknown-linux-gnu/debug/incremental -L dependency=/tmp/tmp.Jyi2v4P3Dk/target/i686-unknown-linux-gnu/debug/deps -L dependency=/tmp/tmp.Jyi2v4P3Dk/target/debug/deps --extern getrandom=/tmp/tmp.Jyi2v4P3Dk/target/i686-unknown-linux-gnu/debug/deps/libgetrandom-cc172141f5604369.rlib --extern hex=/tmp/tmp.Jyi2v4P3Dk/target/i686-unknown-linux-gnu/debug/deps/libhex-af2e0eff81a4d982.rlib --extern zeroize=/tmp/tmp.Jyi2v4P3Dk/target/i686-unknown-linux-gnu/debug/deps/libzeroize-bd8c23daa5be92bd.rlib -C debuginfo=2 --cap-lints warn -C linker=i686-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /usr/share/cargo/registry/nanorand-0.7.0=/usr/share/cargo/registry/nanorand-0.7.0 --remap-path-prefix /tmp/tmp.Jyi2v4P3Dk/registry=/usr/share/cargo/registry` (exit status: 1) autopkgtest [15:43:56]: test rust-nanorand-0.7:@: ---] autopkgtest [15:43:56]: test rust-nanorand-0.7:@: - - - - - - - - - - results - - - - - - - - - - rust-nanorand-0.7:@ FAIL non-zero exit status 101 ... autopkgtest [15:54:05]: summary rust-nanorand-0.7:@ FAIL non-zero exit status 101 rust-nanorand-0.7-dev:alloc PASS rust-nanorand-0.7-dev:chacha PASS rust-nanorand-0.7-dev:default PASS rust-nanorand-0.7-dev:getrandom PASS rust-nanorand-0.7-dev:pcg64 PASS rust-nanorand-0.7-dev:rdseed FAIL non-zero exit status 101 rust-nanorand-0.7-dev:std PASS rust-nanorand-0.7-dev:tls PASS rust-nanorand-0.7-dev:wyrand PASS rust-nanorand-0.7-dev:zeroize PASS rust-nanorand-0.7: PASS
Bug#1030530: Python 3.10 in bookworm
Why is the current intention not to ship the python3.10 package in bookworm? I was trying to run some experiments in a virtual environment a few days ago, and it turns out that several of the Python packages I needed do not yet run on Python 3.11. I was saved by being able to run in a Python 3.10 venv and download all the required packages from PyPI. If bookworm shipped without python3.10, I would not have been able to do my work. Removing python3.10 from bookworm will seriously affect many of our users in a similar situation to me. Best wishes, Julian P.S. We should also fix #1036268 if we do keep python3.10 in bookworm; I'm happy to do an NMU if needed.
Bug#1030577: simde: autopkgtest regressions on i386 and ppc64el
Source: simde Version: 0.7.4~rc1-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/i386/s/simde/31050074/log.gz ... Summary of Failures: 107/1534 x86/avx512/dbsad/emul/c ERROR 0.01s exit status 1 108/1534 x86/avx512/dbsad/native/c ERROR 0.01s exit status 1 109/1534 x86/avx512/dbsad/emul/cpp ERROR 0.01s exit status 1 110/1534 x86/avx512/dbsad/native/cpp ERROR 0.01s exit status 1 Ok: 1524 Expected Fail: 0 Fail: 4 Unexpected Pass:0 Skipped:6 Timeout:0 Full log written to /tmp/autopkgtest-lxc.tgbnxsqh/downtmp/autopkgtest_tmp/build-gcc/meson-logs/testlog.txt FAILED: meson-internal__test /usr/bin/meson test --no-rebuild --print-errorlogs ninja: build stopped: subcommand failed. autopkgtest [20:10:51]: test run-unit-test: ---] autopkgtest [20:10:51]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1 https://ci.debian.net/data/autopkgtest/testing/ppc64el/s/simde/31050076/log.gz ... Summary of Failures: 268/1534 x86/avx512/range/native/cpp ERROR 0.06s exit status 1 269/1534 x86/avx512/range/native/c ERROR 0.11s exit status 1 271/1534 x86/avx512/range_round/native/c ERROR 0.04s exit status 1 274/1534 x86/avx512/range_round/native/cpp ERROR 0.05s exit status 1 436/1534 x86/sse/native/cERROR 0.09s exit status 1 438/1534 x86/sse/native/cpp ERROR 0.11s exit status 1 440/1534 x86/sse2/native/c ERROR 0.12s exit status 1 442/1534 x86/sse2/native/cpp ERROR 0.10s exit status 1 1364/1534 wasm_simd128/mul/native/c ERROR 0.06s exit status 1 1366/1534 wasm_simd128/mul/native/cpp ERROR 0.08s exit status 1 1424/1534 wasm_simd128/shr/native/c ERROR 0.05s exit status 1 1426/1534 wasm_simd128/shr/native/cpp ERROR 0.07s exit status 1 Ok: 622 Expected Fail: 0 Fail: 12 Unexpected Pass:0 Skipped:900 Timeout:0 Full log written to /tmp/autopkgtest-lxc.h12h1wf1/downtmp/autopkgtest_tmp/build-gcc/meson-logs/testlog.txt FAILED: meson-internal__test /usr/bin/meson test --no-rebuild --print-errorlogs ninja: build stopped: subcommand failed. autopkgtest [19:58:03]: test run-unit-test: ---] autopkgtest [19:58:03]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1
Bug#1017621: marked as done (seahorse-nautilus: Fails to build with Nautilus 43)
Your message dated Sun, 05 Feb 2023 10:37:52 + with message-id and subject line Bug#1017621: fixed in seahorse-nautilus 3.11.92+git20230129.d59dc92f-1 has caused the Debian Bug report #1017621, regarding seahorse-nautilus: Fails to build with Nautilus 43 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.) -- 1017621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seahorse-nautilus Version: 3.11.92-4 Severity: important Tags: ftbfs sid bookworm The newest release of Nautilus, version 43, has switched to GTK4 and includes major changes in the extensions API. seahorse-nautilus will need to be converted to GTK4 and make other changes for the new version. Nautilus 43 is available in Debian Experimental. When we upload nautilus 43 to Debian Unstable, we will need to remove seahorse-nautilus from Testing unless this bug is fixed, because the package will no longer build from source. Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Source: seahorse-nautilus Source-Version: 3.11.92+git20230129.d59dc92f-1 Done: Clément Hermann We believe that the bug you reported is fixed in the latest version of seahorse-nautilus, 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. Clément Hermann (supplier of updated seahorse-nautilus 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: Sun, 5 Feb 2023 11:18:35 CET Source: seahorse-nautilus Binary: Architecture: source Version: 3.11.92+git20230129.d59dc92f-1 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Maintainers Changed-By: Clément Hermann Description: Closes: 1017621 Changes: seahorse-nautilus (3.11.92+git20230129.d59dc92f-1) unstable; urgency=medium . [ Chris Lamb ] * Remove myself from Uploaders . [ Clément Hermann ] * Import latest commits from upstream VCS as 3.11.92+git20230129.d59dc92f: - port to libnautilus-extension-4 (closes: 1017621) - various code and build system fixes - translations fixes * d/patches: - remove obsolete patches - fix-warning.patch: update Forwarded URL - add meson_use_dependency_for_gpme.patch build system to avoid gpgme-config usage (not shipped in Debian currently, and obsolete anyway) (Forwarded) * d/docs: README → README.md * d/control: - add meson (>= 0.51) build-depends - update libnautilus-extension-dev version requirement - update my email in Uploaders to debian.org address - Switch to debhelper-compat 13 (and drop debian/compat file) * Update d/copyright * Declare compliance with Policy v4.6.2 * lintian-overrides: update tag name * d/copyright: remove paragraphs for removed files * update upstream metadata: - Homepage isn't a DEP-12 field - add "extension" to Name * Update debian/watch to version 4 (no change) * d/rules: remove unneeded linker flags '--as-needed' Checksums-Sha256: 7ad18a0179a6090f3aeaf5a6d56a8df9560c1b38a4874bc446c4bcf6f8d451c4 2434 seahorse-nautilus_3.11.92+git20230129.d59dc92f-1.dsc af55e5a4fd8bbf68e5a3d39b48429905b4f270d8183ee4b98799ccbe1f3cf7d8 241441 seahorse-nautilus_3.11.92+git20230129.d59dc92f.orig.tar.gz 71dec72f443cc3a31c904448d003afad2de0b2c9ee41b1200aadaea77527f477 11768 seahorse-nautilus_3.11.92+git20230129.d59dc92f-1.debian.tar.xz 77915a8b4869ada8f155c433b60527379c3caa044eeda5acc63e262db16a8b0a 16768 seahorse-nautilus_3.11.92+git20230129.d59dc92f-1_sourceonly.buildinfo Checksums-Sha1: 18270017e60ff93b7742128a2f17a4147c8675c7 2434 seahorse-nautilus_3.11.92+git20230129.d59dc92f-1.dsc 1fcb41dc185212c5e33088b2cab0fff36c6b6dd6 241441 seahorse-nautilus_3.11.92+git20230129.d59dc92f.orig.tar.gz 6faa98350a80996387ac6ca4460991efc2e31229 11768 seahorse-nautilus_3.11.92+git20230129.d59dc92f-1.debian.tar.xz bf011e860551bf5c418d3996545df53171605766 16768 seahorse-nautilus_3.11.92+git20230129.d59dc92f-1_sourceonly.buildinfo Files: 32333995d040f894ff22be870e1f00d4 2434 gnome optional seahorse-nautilus
Bug#1030516: marked as done (python3-hickle needs a source upload to fix the missing python3-h5py dependency)
Your message dated Sun, 05 Feb 2023 10:34:33 + with message-id and subject line Bug#1030516: fixed in hickle 5.0.2-5 has caused the Debian Bug report #1030516, regarding python3-hickle needs a source upload to fix the missing python3-h5py 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.) -- 1030516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-hickle Version: 5.0.2-4 Severity: serious python3-hickle lacks a dependency on python3-h5py due to #1030274. A no-change rebuild is sufficient, but since binNMUs are not possible for binary-all this needs a source upload. --- End Message --- --- Begin Message --- Source: hickle Source-Version: 5.0.2-5 Done: Edward Betts We believe that the bug you reported is fixed in the latest version of hickle, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Edward Betts (supplier of updated hickle 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: Sun, 05 Feb 2023 11:11:37 +0100 Source: hickle Architecture: source Version: 5.0.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Edward Betts Closes: 1030516 Changes: hickle (5.0.2-5) unstable; urgency=medium . * Add python3-h5py dependency to python3-hickle. (Closes: #1030516) * Update Standards-Version. Checksums-Sha1: f7863b81016222f1a8d12a5712baff9adcb120ff 2276 hickle_5.0.2-5.dsc 44a78c6dc319098dfb0a210ccd9d499de1568ed0 3256 hickle_5.0.2-5.debian.tar.xz ccba9f19e21d247f567e9c8fc6a37214ff3b7b54 10476 hickle_5.0.2-5_source.buildinfo Checksums-Sha256: 9498afe278416705cee54012468c799dec6ceadfd636b3905e00da275bcb8d81 2276 hickle_5.0.2-5.dsc a1b5529c0ebc82e2bf2897d99fc18777b67911dd307dc33902e228e5bc4ec5c3 3256 hickle_5.0.2-5.debian.tar.xz d36258be80f97a6e0e9b7195988b5c6a168d0f03a49a12e6b47e31172cb08858 10476 hickle_5.0.2-5_source.buildinfo Files: 72067a7a20b79636f26300f356a43111 2276 python optional hickle_5.0.2-5.dsc e0fad756b2c2d89fa3afa2a580990eaa 3256 python optional hickle_5.0.2-5.debian.tar.xz dd45cc70f9e1b4290edc1f0dbc76ef7d 10476 python optional hickle_5.0.2-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+4rPp4xyYInDitAmlgWhCYxjuSoFAmPfgYIACgkQlgWhCYxj uSoBYg/6A98Mqli5UrSu5NL+vaQwb66YLyttQ+ogCrrf/tkuemnE+YSnPsG9yz9e G5iofT5fNvKz5g7l/q5FTjnvMC6vFteg4ZXZ/Z7j2jjZnFBVwVNAzyieEsHE70/C ocCOOipqZ8tXOEHaFXataEGnL0DsU6uPtSQUqdJ3nIlumGLAzhn4EBodyvpGDB75 4mFZnSxGhwEwCGZzatkjqaOUJuszJ5HfYCvSVWEIoMnj/fNFBmnWF8LtNyCa1BO5 5SduonCuSeeBafDFvASA0ePXuvmf5oaRz/vJuB3ca+DU4iHJdRDAZW2D8qkaBnDR S9/ttarUkJmzi941oUA+RquEywaWHj9UhK/0/Bjz8S/1HuuWJuZ8fLszoVeuyhOC 8ZpMJSAgCIaveZAwSCAMLWMFrFDHKt1fgWpXiadwD+faNN6GwO3+7b5UVb0Gc56+ xxeyj+Lhl1RPTg98pLLtT1HO0mea31gyHUuMuUJLaj2tZi0bDvb2fI48sC8Z8FV6 d5JN6O65Ej2coD21YbkiF4nv/9VGdwQt8Xs9e2ynyZejFjYj9Z/BEwzrJ7aCyWkN VcP5gznZD+yQXgFFf4pg7ECVrFbXmeDQ6JFEN/sLsEsC7QToAsK51yFV5VtsZruM aaxz4qEqmbdyQW8rucZBgDVMQc261LZJRrcny9/ziS6MmCsDHAs= =xNGz -END PGP SIGNATURE End Message ---
Bug#1029594: Fails to authenticate mit o365
Am 04.02.23 um 23:25 schrieb Chandler Sobel-Sorenson: Frankly, I'm glad it was increased to serious because otherwise listbugs wouldn't have let me stop it, then I have to spend more time figuring out why I suddenly can't retrieve my e-mail and tracking down a solution, downgrading packages, etc. There is only so much time in the day and so much coffee I can drink. ;-) We use O365 at the University and I have enough issues maintaining our Linux systems there. ;-) Last thing I need is problems with workstation to get in the way of my work. If you need your laptop or your workstation for mission critical things than Debian unstable/sid isn't the right choice. If you do so then you will need some knowledge to handle situations like happen now. > Quoting https://www.debian.org/Bugs/Developer.en.html > important > a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone > And that's what this issue is about, most of the users can use > Thunderbird without problems. Do you have statistics for that? What is "most"? The majority of users. :-) And these are obviously not users of Microsoft Cloud products. We haven got reports from GMail user e.g. Debian doesn't have any really resilient statistics as such statistics bases on completely free choice. Debian doesn't collect data from users without any confirmation. I'm pretty sure many Universities and other large organizations across the world are using Office however, if it's anything like our University, "most" of those users are using Windows version of Outlook or Outlook Online. Still, I could not be sure what "most" Thunderbird users are using. Sure the world is mostly owned by Microsoft Desktop systems, and using Exchange or now Outlook 365 is also decreasing the the free choice of a client to interact with the server instance. Most users of Thunderbird are not using M$ products or at least only using a small set of features of Exchange or Outlook.com. Further, the actual bug in mozilla is #1814536 (OAuth2 authentication | 102.7.1. | Linux - fails) - still Open. This is an even broader than just o365 as Google uses OAuth2 as well, etc. That bug was reported here in Debian as grave under #1030112 but you closed it as a duplicate of this bug. That was perhaps mistaken. No, it was not. Having dozen of issues open that are about the same problem is really not helpful to handle the issue. > serious > is a severe violation of Debian policy (roughly, it violates a "must" or "required" directive), > or, in the package maintainer's or release manager's opinion, makes the package unsuitable for release. I don't have the time to currently review the 609 instances of "must" or "required" in the policy, but I believe this makes the package unsuitable for release. I don't really understand your problem. What is the problem here? What does it help if we increase the severity even more? Even right now the the broken package will not migrate to testing. But it will also trigger a remove of the version in testing. What do we win? > grave > makes the package in question unusable or mostly so, or causes data loss, > or introduces a security hole allowing access to the accounts of users who use the package. I think #1030112 should be reopened and/or merged with this bug, with the title being updated to reflect broader issue with OAuth2. As the bug is much broader than is implied here, severity should be maintained at a minimum of serious. And what we get from doing so? The closed issue has added information that further talking is happen here. Since many these days are using Gmail as their only e-mail then could even be argued that thunderbird is now unusable or mostly so, therefore severity of grave is not out of the question either. My GMail account is working with the current version in testing means to me that Google doesn't has changed something on their side. Obviously only MS has changed something. So finally again as written in other answers: If you need to use Thunderbird in a critical environment you shouldn't use unstable/sid as long you don't know how to handle the potential breakage of packages. Debian is providing a stable release for productive use, if you need newer version of software you can add the backport suite. Or if you are more experienced switch to testing. -- Regards Carsten
Bug#1020435: marked as done (ruby-prof: flaky tests cause random FTBFS)
Your message dated Sun, 05 Feb 2023 10:51:19 + with message-id and subject line Bug#1020435: fixed in ruby-prof 1.4.5-1 has caused the Debian Bug report #1020435, regarding ruby-prof: flaky tests cause random FTBFS 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.) -- 1020435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-prof Version: 1.4.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ruby-prof&arch=ppc64el&ver=1.4.3-1%2Bb1&stamp=1663720013&raw=0 1) Failure: PrinterGraphTest#test_graph_results_sorting [/<>/test/printer_graph_test.rb:37]: Array [0.171, 0.171, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, 0.0, 0.0, 0.0, 0.17, 0.17, 0.0, 0.0, 0.169, 0.169, 0.0, 0.0] is not sorted. --- expected +++ actual @@ -1 +1 @@ -[0.171, 0.171, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, 0.0, 0.0, 0.0, 0.17, 0.17, 0.0, 0.0, 0.169, 0.169, 0.0, 0.0] +[0.171, 0.171, 0.17, 0.17, 0.169, 0.169, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0] 51 runs, 687 assertions, 1 failures, 0 errors, 0 skips rake aborted! Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/abstract_printer_test.rb" "test/alias_test.rb" "test/basic_test.rb" "test/call_tree_visitor_test.rb" "test/call_trees_test.rb" "test/duplicate_names_test.rb" "test/enumerable_test.rb" "test/exceptions_test.rb" "test/exclude_methods_test.rb" "test/exclude_threads_test.rb" "test/fiber_test.rb" "test/gc_test.rb" "test/line_number_test.rb" "test/marshal_test.rb" "test/multi_printer_test.rb" "test/no_method_class_test.rb" "test/printer_call_stack_test.rb" "test/printer_call_tree_test.rb" "test/printer_flat_test.rb" "test/printer_graph_html_test.rb" "test/printer_graph_test.rb" "test/printing_recursive_graph_test.rb" "test/profile_test.rb" "test/rack_test.rb" "test/singleton_test.rb" -v] /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `' Tasks: TOP => default (See full trace by running task with --trace) ERROR: Test "ruby3.0" failed. Exiting. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: ruby-prof Source-Version: 1.4.5-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ruby-prof, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated ruby-prof 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: Sun, 05 Feb 2023 15:54:03 +0530 Source: ruby-prof Architecture: source Version: 1.4.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Nilesh Patra Closes: 1020435 Changes: ruby-prof (1.4.5-1) unstable; urgency=medium . * Team Upload. * New upstream version 1.4.5 * Bump Standards-Version to 4.6.2 (no changes needed) * Add "test/printer_graph_test.rb" to skiplist as it looks to be time sensitive and is flaky (Closes: #1020435) * Drop d/p/0001-Fix-requiring-ruby_prof.so-on-Debian.patch (fixed upstream) * debian/ruby-prof.docs: README.rdoc has moved to README.md, install the latter Checksums-Sha1: 3953d6571644de192ff9c9ff0722525b9f28d17c 1407 ruby-prof_1.4.5-1.dsc bdd7113eba5e556ff38aece57b8237eb8e31c394 72436 ruby-prof_1.4.5.orig.tar.xz 541a7831d964de50256d5eda7ae82eda45f61bbc 8232 ruby-prof_1.4.5-1.debian.tar.xz 7b03468014ccf0302ccd6f04d4157edb216a9292 8429 ruby-prof_1.4.5-1_amd64.buildinfo Checksums-Sha256: fb2782d17fb2e63913a0c3460381fd05a543dee0a0da0b5953936a9b5e71de96 1407 ruby-prof_1.4.5-1.dsc 122793938f78915f150a0b540a18cae053826dc6779da3abc13bf16dd2713dcb 72436 ruby-prof_1.4.5.orig.tar.xz ecfce61bd4dfe46e74a19547e638a12fad2f2bd936a96f470fd426fa89909ac2 8232 ruby-prof_1.4.5-1.debian.tar.xz 8e10fb2c82c09b3d8eaf7f9093b64083a521dd94130b
Processed: merge
Processing commands for cont...@bugs.debian.org: > forcemerge 1030489 1030180 Bug #1030489 [src:tiledb-py] tiledb-py: FTBFS: tiledb/cc/array.cc:149:11: error: no matching function for call to ‘pybind11::class_::def(const char [13], )’ Bug #1030180 [src:tiledb-py] tiledb-py: FTBFS: E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build Added tag(s) bookworm and sid. Merged 1030180 1030489 > stop Stopping processing here. Please contact me if you need assistance. -- 1030180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030180 1030489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030579: rust-psa-crypto: autopkgtest failure
Source: rust-psa-crypto Version: 0.9.2-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-psa-crypto/30999064/log.gz ... error: test failed, to rerun pass `--test mod` Caused by: process didn't exit successfully: `/tmp/tmp.zgGN2JwJ3v/target/x86_64-unknown-linux-gnu/debug/deps/mod-5ff8f2a3ba46e536` (signal: 11, SIGSEGV: invalid memory reference) autopkgtest [16:02:17]: test rust-psa-crypto:@: ---] autopkgtest [16:02:17]: test rust-psa-crypto:@: - - - - - - - - - - results - - - - - - - - - - rust-psa-crypto:@FAIL non-zero exit status 101 ... autopkgtest [16:03:55]: summary rust-psa-crypto:@FAIL non-zero exit status 101 librust-psa-crypto-dev:default FAIL non-zero exit status 101 librust-psa-crypto-dev:interface FAIL non-zero exit status 101 librust-psa-crypto-dev:no-std FAIL non-zero exit status 101 librust-psa-crypto-dev:operations FAIL non-zero exit status 101 librust-psa-crypto-dev: FAIL non-zero exit status 101
Bug#1030451: marked as pending in python-pytray
Control: tag -1 pending Hello, Bug #1030451 in python-pytray reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-pytray/-/commit/af866bdfe160ccded9f2329a3f07d86cdd874494 Add patch to fix version (Closes: #1030451) (this message was generated automatically) -- Greetings https://bugs.debian.org/1030451
Processed: Bug#1030451 marked as pending in python-pytray
Processing control commands: > tag -1 pending Bug #1030451 [src:python-pytray] python-pytray: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '-version-' Added tag(s) pending. -- 1030451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030489: marked as done (tiledb-py: FTBFS: tiledb/cc/array.cc:149:11: error: no matching function for call to ‘pybind11::class_::def(const char [13],
Your message dated Sun, 05 Feb 2023 11:09:01 +
with message-id
and subject line Bug#1030489: fixed in tiledb-py 0.20.0-1
has caused the Debian Bug report #1030489,
regarding tiledb-py: FTBFS: tiledb/cc/array.cc:149:11: error: no matching
function for call to ‘pybind11::class_::def(const char [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.)
--
1030489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledb-py
Version: 0.19.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/lib/python3/dist-packages/pybind11/include
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11
> -c tiledb/cc/array.cc -o
> build/temp.linux-x86_64-cpython-311/tiledb/cc/array.o -fvisibility=hidden -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -std=c++17 -Wno-deprecated-declarations
> -fvisibility=hidden
> tiledb/cc/array.cc: In function ‘void
> libtiledbcpp::init_array(pybind11::module&)’:
> tiledb/cc/array.cc:149:11: error: no matching function for call to
> ‘pybind11::class_::def(const char [13], function type>)’
>15 | py::class_(m, "Array")
> | ~
>16 | //.def(py::init py::object,
> |
> ~
>17 | // py::object, py::object>())
> | ~~
>18 | .def(
> | ~
>19 | py::init tiledb_query_type_t>(),
> |
> ~~
>20 | py::keep_alive<1, 2>() /* Array keeps Context alive */)
> | ~~~
>21 | // TODO capsule Array(const Context& ctx, tiledb_array_t*
> carray,
> |
> ~
>22 | // tiledb_config_t* config)
> | ~~~
>23 | .def("is_open", &Array::is_open)
> |
>24 | .def("uri", &Array::uri)
> |
>25 | .def("schema", &Array::schema)
> | ~~
>26 | //.def("ptr", [](Array& arr){ return py::capsule(arr.ptr()); } )
> |
>27 | // open with encryption key
> | ~~~
>28 | .def("open",
> |
>29 |(void (Array::*)(tiledb_query_type_t,
> tiledb_encryption_type_t,
> |
> ~~~
>30 | const std::string &)) &
> | ~~~
>31 |Array::open)
> |
>32 | // open with encryption key and timestamp
> | ~
>33 | .def("open",
> |
>34 |(void (Array::*)(tiledb_query_type_t,
> tiledb_encryption_type_t,
> |
> ~~~
>35 | const std::string &, uint64_t)) &
> | ~
>36 |Array::open)
> |
>37 | .def("reopen", &Array::reopen)
> | ~~
>38 | .def("set_open_timestamp_start",
> &Array::set_open_timestamp_start)
> |
> ~~
>39 | .def("set_open_timestamp_end", &Array::set_open_timestamp_end)
> | ~~
>40 | .def_property_readonly(
Bug#1030180: marked as done (tiledb-py: FTBFS: E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build)
Your message dated Sun, 05 Feb 2023 11:09:01 +
with message-id
and subject line Bug#1030489: fixed in tiledb-py 0.20.0-1
has caused the Debian Bug report #1030489,
regarding tiledb-py: FTBFS: E: pybuild pybuild:388: build: plugin distutils
failed with: exit code=1: /usr/bin/python3 setup.py build
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.)
--
1030489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledb-py
Version: 0.19.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=tiledb-py&arch=amd64&ver=0.19.1-1%2Bb1&stamp=1675121783&raw=0
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/lib/python3/dist-packages/pybind11/include
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11
-c tiledb/cc/array.cc -o build/temp.linux-x86_64-cpython-311/tiledb/cc/array.o
-fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -std=c++17
-Wno-deprecated-declarations -fvisibility=hidden
tiledb/cc/array.cc: In function ‘void
libtiledbcpp::init_array(pybind11::module&)’:
tiledb/cc/array.cc:149:11: error: no matching function for call to
‘pybind11::class_::def(const char [13], )’
15 | py::class_(m, "Array")
| ~
16 | //.def(py::init())
| ~~
18 | .def(
| ~
19 | py::init(),
|
~~
20 | py::keep_alive<1, 2>() /* Array keeps Context alive */)
| ~~~
21 | // TODO capsule Array(const Context& ctx, tiledb_array_t* carray,
| ~
22 | // tiledb_config_t* config)
| ~~~
23 | .def("is_open", &Array::is_open)
|
24 | .def("uri", &Array::uri)
|
25 | .def("schema", &Array::schema)
| ~~
26 | //.def("ptr", [](Array& arr){ return py::capsule(arr.ptr()); } )
|
27 | // open with encryption key
| ~~~
28 | .def("open",
|
29 |(void (Array::*)(tiledb_query_type_t,
tiledb_encryption_type_t,
|
~~~
30 | const std::string &)) &
| ~~~
31 |Array::open)
|
32 | // open with encryption key and timestamp
| ~
33 | .def("open",
|
34 |(void (Array::*)(tiledb_query_type_t,
tiledb_encryption_type_t,
|
~~~
35 | const std::string &, uint64_t)) &
| ~
36 |Array::open)
|
37 | .def("reopen", &Array::reopen)
| ~~
38 | .def("set_open_timestamp_start", &Array::set_open_timestamp_start)
| ~~
39 | .def("set_open_timestamp_end", &Array::set_open_timestamp_end)
| ~~
40 | .def_property_readonly("open_timestamp_start",
| ~~
41 | &Array::open_timestamp_start)
| ~
42 | .def_property_readonly("open_timestamp_end",
&Array::open_timestamp_end)
|
~
Bug#1028779: buildbot: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 --system=custom "--test-args=PYTHONPATH=pkg:{destdir}/{install_dir} PATH=\$PATH:{destdir}/usr/bin trial3 --
Hi Robin, buildbot is marked for removal on Feb 16. Do you intend to make an upload? Thanks Nilesh On Wed, 1 Feb 2023 11:47:56 +0100 s3v wrote: > Dear maintainer, > > Please find attached a patch to avoid deprecation warnings > causing tests to fail. > > Kind Regards signature.asc Description: PGP signature
Bug#1029673: marked as done (python-pytray: autopkgtest regression: Task was destroyed but it is pending!)
Your message dated Sun, 5 Feb 2023 16:46:27 +0530 with message-id <20230205111627.dlghtjqx2ztrf...@nileshpatra.info> and subject line Re: python-pytray: autopkgtest regression: Task was destroyed but it is pending! has caused the Debian Bug report #1029673, regarding python-pytray: autopkgtest regression: Task was destroyed but it is pending! 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.) -- 1029673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pytray Version: 0.3.5-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-pytray the autopkgtest of python-pytray fails in testing when that autopkgtest is run with the binary packages of python-pytray from unstable. It passes when run with only packages from testing. In tabular form: passfail python-pytray from testing0.3.5-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 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=python-pytray https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pytray/30685655/log.gz = test session starts == platform linux -- Python 3.10.9, pytest-7.2.1, pluggy-1.0.0+repack rootdir: /tmp/autopkgtest-lxc.h_510pxi/downtmp/build.wSM/src collected 13 items test/test_aiothreads.py [ 61%] test/test_obj_load.py .. [ 76%] test/test_tree.py ... [100%] == 13 passed in 0.52s == Task was destroyed but it is pending! source_traceback: Object created at (most recent call last): File "/usr/lib/python3.10/threading.py", line 973, in _bootstrap self._bootstrap_inner() File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner self.run() File "/usr/lib/python3.10/threading.py", line 953, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3/dist-packages/pytray/aiothreads.py", line 299, in _run_loop self._loop.run_until_complete(run_loop()) File "/usr/lib/python3.10/asyncio/base_events.py", line 636, in run_until_complete self.run_forever() File "/usr/lib/python3.10/asyncio/base_events.py", line 603, in run_forever self._run_once() File "/usr/lib/python3.10/asyncio/base_events.py", line 1898, in _run_once handle._run() File "/usr/lib/python3.10/asyncio/events.py", line 80, in _run self._context.run(self._callback, *self._args) File "/usr/lib/python3.10/asyncio/tasks.py", line 884, in callback futures._chain_future(ensure_future(coro, loop=loop), future) File "/usr/lib/python3.10/asyncio/tasks.py", line 615, in ensure_future return _ensure_future(coro_or_future, loop=loop) File "/usr/lib/python3.10/asyncio/tasks.py", line 636, in _ensure_future return loop.create_task(coro_or_future) task: coro=.coro() done, defined at /usr/lib/python3/dist-packages/pytray/aiothreads.py:177> wait_for=/usr/lib/python3.10/asyncio/base_events.py:429> cb=[_chain_future.._call_set_state() at /usr/lib/python3.10/asyncio/futures.py:392] created at /usr/lib/python3.10/asyncio/tasks.py:636> Task was destroyed but it is pending! source_traceback: Object created at (most recent call last): File "/usr/lib/python3.10/threading.py", line 973, in _bootstrap self._bootstrap_inner() File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner self.run() File "/usr/lib/python3.10/threading.py", line 953, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3/dist-packages/pytray/aiothreads.py", line 299, in _run_loop self._loop.run_until_complete(run_loop()) File "/usr/lib/python3.10/asyncio/base_events.py", line 636, in run_until_complete self.run_forever() File "/usr/lib/python3.10/asyncio/base_events.py", line 603, in run_forever self._run_once() File "/usr/lib/python3.10/asyncio/base_events.py", line 1898, in _run_once handle._run() File "/usr/lib/python3.10/asyncio/events.py", line 80, in _run self._context.run(self._callback, *self._args) File "/usr/lib/python3.10/asyncio/tasks.py", line 884, in c
Bug#1030451: marked as done (python-pytray: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '-version-')
Your message dated Sun, 05 Feb 2023 11:26:55 +
with message-id
and subject line Bug#1030451: fixed in python-pytray 0.3.5-2
has caused the Debian Bug report #1030451,
regarding python-pytray: FTBFS:
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version:
'-version-'
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.)
--
1030451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytray
Version: 0.3.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 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:240: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> version specified ('${version}') is an invalid version, this may not work as
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440
> for more details.
> warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> version specified ('${version}') is an invalid version, this may not work as
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440
> for more details.
> warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/pretty.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/obj_load.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/weakdict.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/tree.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/aiothreads.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/version.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
> copying pytray/futures.py ->
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_pytray/build;
> python3.11 -m pytest test
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>
> collected 13 items
>
> test/test_aiothreads.py [
> 61%]
> test/test_obj_load.py .. [
> 76%]
> test/test_tree.py ...
> [100%]
>
> == 13 passed in 0.48s
> ==
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=pybuild
>dh_prep -O--buildsystem=pybuild
>dh_auto_install --destdir=debian/python3-pytray/ -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py install --root
> /<>/debian/python3-pytray
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> version specified ('${version}') is an invalid version, this may not work as
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440
> for more details.
> warnings.warn(
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34:
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and
> pip and other standards-based tools.
> warnings.warn(
> running build
> running build_py
> running install_lib
> creating /<>/debian/python3-pytray/usr
> creating /<>/debian/python3-pytray/usr/lib
> creating /<>/debian/python3-pytray/usr/lib/python3.11
> creating
> /<>/debian/python3-pytray/usr/lib/python3.11/dist-packages
> creating
> /<>/debian/python3-pytray/usr/lib/python3.11/dist-packages/pytray
> copying
> /<>/.pybuild/cpython3_3.11_pytray/build/pytray/__init__.py ->
> /<>/debian/python3-pytray/usr/lib/python3.11/dist-packages/pytray
> copying /<>/.pybuild/cpython3_3.11_pytray/build/pytray/pretty.py
> ->
> /<>/debian/python3-pytray/usr/lib/python3.11/dist-packages/pytray
> copying
> /<>/.pybuild/cpython3_3.11_pytray/bu
Bug#991450: marked as done (gcc-arm-none-eabi breaks ubertooth autopkgtest: linking error)
Your message dated Sun, 05 Feb 2023 11:27:51 + with message-id and subject line Bug#991450: fixed in ubertooth 2018.12.R1-5.1 has caused the Debian Bug report #991450, regarding gcc-arm-none-eabi breaks ubertooth autopkgtest: linking error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 991450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-arm-none-eabi, ubertooth Control: found -1 gcc-arm-none-eabi/15:10-2020-q4-major-1 Control: found -1 ubertooth/2018.12.R1-5 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of gcc-arm-none-eabi the autopkgtest of ubertooth fails in testing when that autopkgtest is run with the binary packages of gcc-arm-none-eabi from unstable. It passes when run with only packages from testing. In tabular form: passfail gcc-arm-none-eabi from testing15:10-2020-q4-major-1 ubertooth from testing2018.12.R1-5 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Apart from the freeze, this regression is blocking the migration of gcc-arm-none-eabi 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=gcc-arm-none-eabi https://ci.debian.net/data/autopkgtest/testing/amd64/u/ubertooth/13851210/log.gz Linking: bluetooth_rxtx.elf arm-none-eabi-gcc -T LPC17xx_Linker_Script_with_bootloader.ld -mcpu=cortex-m3 -mthumb -mthumb-interwork -Wl,-Map=bluetooth_rxtx.map -Wl,--gc-sections -L../common -static -Wl,--start-group -lc -lg -lgcc -lm -Wl,--end-group -o bluetooth_rxtx.elf bluetooth_rxtx.o bluetooth.o bluetooth_le.o ubertooth_usb.o ubertooth_rssi.o ubertooth_cs.o ubertooth_clock.o ubertooth_dma.o le_phy.o queue.o cc2400_rangetest.o ego.o debug_uart.o tinyprintf.o ../common/usb_serial.o ../common/serial_fifo.o ../common/LPC17xx_Startup.o ../common/LPC17xx_Interrupts.o ../common/ubertooth.o ../common/lpcusb/target/usbcontrol.o ../common/lpcusb/target/usbinit.o ../common/lpcusb/target/usbhw_lpc.o ../common/lpcusb/target/usbstdreq.o /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: bluetooth.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:34: multiple definition of `used_channels'; bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:34: first defined here /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: bluetooth.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:33: multiple definition of `afh_map'; bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:33: first defined here /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: bluetooth.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:32: multiple definition of `afh_enabled'; bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:32: first defined here /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: bluetooth.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:31: multiple definition of `syncword'; bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:31: first defined here /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: bluetooth.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:30: multiple definition of `target'; bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/bluetooth.h:30: first defined here /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: ubertooth_rssi.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/ubertooth_rssi.h:29: multiple definition of `rssi_count'; bluetooth_rxtx.o:/tmp/test_build_firmware/ubertooth-firmware-source/bluetooth_rxtx/ubertooth_rssi.h:29: first defined here /usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: ubertooth_rssi.o:/tmp/test_b
Bug#1029729: marked as done (texlive-lang: Should not migrate to testing for now.)
Your message dated Sun, 5 Feb 2023 12:31:34 +0100 (GMT+01:00) with message-id <7ff1e559-2ef9-4b73-ac65-ab39c2fd5...@web.de> and subject line Re: Bug#1029729: Acknowledgement (texlive-lang: Should not migrate to testing for now.) has caused the Debian Bug report #1029729, regarding texlive-lang: Should not migrate to testing for now. 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.) -- 1029729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: texlive-lang Version: 2022.20230122-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, TL-base & TL-extra won't migrate to testing for now, cause they break other packages (latexml & pycirkuit). Therefore I block TL-lang too until the other issues are sorted out. Hilmar -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- sigmentation fault signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Time to close the blocker bug. 26.01.2023 21:39:06 Debian Bug Tracking System : > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1029729: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029729. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian TeX Task Force > > If you wish to submit further information on this problem, please > send it to 1029...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1029729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029729 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems--- End Message ---
Bug#1030530: Python 3.10 in bookworm
How about fixing the 3.11 issues if you hit them ? How about using Buster and 3.9 if 3.11 doesn't work (yet) for you ? Thomas Goirand (zigo) On Feb 5, 2023 11:38, Julian Gilbey wrote: > > Why is the current intention not to ship the python3.10 package in > bookworm? > > I was trying to run some experiments in a virtual environment a few > days ago, and it turns out that several of the Python packages I > needed do not yet run on Python 3.11. I was saved by being able to > run in a Python 3.10 venv and download all the required packages from > PyPI. If bookworm shipped without python3.10, I would not have been > able to do my work. Removing python3.10 from bookworm will seriously > affect many of our users in a similar situation to me. > > Best wishes, > > Julian > > P.S. We should also fix #1036268 if we do keep python3.10 in bookworm; > I'm happy to do an NMU if needed. >
Processed: closing 1030554
Processing commands for cont...@bugs.debian.org: > close 1030554 4.0.1+dfsg-2 Bug #1030554 [src:lomiri-camera-app] lomiri-camera-app build-depends on non-existing libgles2-dev The source 'lomiri-camera-app' and version '4.0.1+dfsg-2' do not appear to match any binary packages Marked as fixed in versions lomiri-camera-app/4.0.1+dfsg-2. Bug #1030554 [src:lomiri-camera-app] lomiri-camera-app build-depends on non-existing libgles2-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1030554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997389: marked as done (xrdesktop: FTBFS: dh_install: error: missing files, aborting)
Your message dated Sun, 05 Feb 2023 12:09:22 + with message-id and subject line Bug#997389: fixed in xrdesktop 0.15.1-5.1 has caused the Debian Bug report #997389, regarding xrdesktop: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xrdesktop Version: 0.15.1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with python3 >dh_testroot >dh_prep >dh_auto_install > cd obj-x86_64-linux-gnu && DESTDIR=/<>/debian/tmp > LC_ALL=C.UTF-8 ninja install > [1/21] Generating shader_resources_c with a custom command > [2/21] Compiling C object > src/libxrdesktop-0.15.so.0.15.1.p/meson-generated_.._.._shaders_shader_resources.c.o > [3/21] Compiling C object > examples/hand-shake.p/meson-generated_.._.._shaders_shader_resources.c.o > [4/21] Compiling C object > tests/test_scene_client.p/meson-generated_.._.._shaders_shader_resources.c.o > [5/21] Compiling C object > tests/test_scene_window_size.p/meson-generated_.._.._shaders_shader_resources.c.o > [6/21] Compiling C object > examples/client.p/meson-generated_.._.._shaders_shader_resources.c.o > [7/21] Compiling C object > tests/test_client_switch.p/meson-generated_.._.._shaders_shader_resources.c.o > [8/21] Linking target src/libxrdesktop-0.15.so.0.15.1 > [9/21] Generating symbol file > src/libxrdesktop-0.15.so.0.15.1.p/libxrdesktop-0.15.so.0.15.1.symbols > [10/15] Linking target examples/client > [11/15] Linking target tests/test_scene_client > [12/15] Linking target tests/test_client_switch > [13/15] Linking target examples/hand-shake > [14/15] Linking target tests/test_scene_window_size > [14/15] Installing files. > Installing src/libxrdesktop-0.15.so.0.15.1 to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu > Installing settings/org.xrdesktop.settings.gresource to > /<>/debian/tmp/usr/share/xrdesktop > Installing /<>/src/scene/xrd-scene-model.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-client.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-window.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-pointer.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-object.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-selection.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-background.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-pointer-tip.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-desktop-cursor.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/scene/xrd-scene-renderer.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/overlay/xrd-overlay-pointer-tip.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/overlay/xrd-overlay-desktop-cursor.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/overlay/xrd-overlay-pointer.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/overlay/xrd-overlay-client.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/overlay/xrd-overlay-window.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-window-manager.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-window.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-container.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-settings.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-input-synth.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-shake-compensator.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-client.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-math.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-desktop-cursor.h to > /<>/debian/tmp/usr/include/xrdesktop-0.15 > Installing /<>/src/xrd-button.h to > /<>/debian/
Bug#1030575: marked as pending in golang-github-hashicorp-go-slug
Control: tag -1 pending Hello, Bug #1030575 in golang-github-hashicorp-go-slug 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/go-team/packages/golang-github-hashicorp-go-slug/-/commit/5a9df6b3b64f55e83b61a421cd6d04b0a6a0d51d Import Debian changes 0.9.1-2 golang-github-hashicorp-go-slug (0.9.1-2) unstable; urgency=medium . * reintroduce patch (Closes: #1030575) it is still needed for autpkgtest (this message was generated automatically) -- Greetings https://bugs.debian.org/1030575
Processed: Bug#1030575 marked as pending in golang-github-hashicorp-go-slug
Processing control commands: > tag -1 pending Bug #1030575 [src:golang-github-hashicorp-go-slug] golang-github-hashicorp-go-slug: autopkgtest failure Added tag(s) pending. -- 1030575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030377: marked as done (c-icap: autopkgtest regression)
Your message dated Sun, 05 Feb 2023 13:04:12 + with message-id and subject line Bug#1030377: fixed in c-icap 1:0.5.10-4 has caused the Debian Bug report #1030377, regarding c-icap: autopkgtest regression 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.) -- 1030377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: c-icap Version: 1:0.5.10-3 Severity: serious X-Debbugs-Cc: Chris Hofstaedtler https://ci.debian.net/data/autopkgtest/testing/amd64/c/c-icap/30997072/log.gz ... autopkgtest [14:12:57]: test basic: [--- Enabling c-icap (re-)Starting c-icap Testing c-icap FATAL: c-icap is not running autopkgtest [14:12:57]: test basic: ---] autopkgtest [14:12:57]: test basic: - - - - - - - - - - results - - - - - - - - - - basicFAIL non-zero exit status 1 autopkgtest [14:12:58]: test basic: - - - - - - - - - - stderr - - - - - - - - - - FATAL: c-icap is not running autopkgtest [14:12:58]: summary basicFAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: c-icap Source-Version: 1:0.5.10-4 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of c-icap, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated c-icap 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: Sun, 05 Feb 2023 12:32:08 + Source: c-icap Architecture: source Version: 1:0.5.10-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Chris Hofstaedtler Closes: 1030377 Changes: c-icap (1:0.5.10-4) unstable; urgency=medium . * QA upload. * Fix autopkgtest failure (Closes: #1030377) Checksums-Sha1: b9e6ca8f09eba19b30849c879f6e3b5a7fc53be1 2064 c-icap_0.5.10-4.dsc 1cda473ccd62efe8b5c4ae0cefe2167c00ddc8e8 12356 c-icap_0.5.10-4.debian.tar.xz 2a6e726f2e7b471e4dc7e37aa415ed894dbcaf30 5692 c-icap_0.5.10-4_source.buildinfo Checksums-Sha256: c56d9ca1882e1c9f679d257963e306a37bc51f39f3e9ddfb3b728076ee27494a 2064 c-icap_0.5.10-4.dsc 96f5528ded8537b3b2f08752f5dd609438fbe001c120de1527985ea960e87afd 12356 c-icap_0.5.10-4.debian.tar.xz 6b0a171730b903ddb6fed313b3fc493ca620b3d1dd82921e9a07498dbef60b40 5692 c-icap_0.5.10-4_source.buildinfo Files: fea389f5bba390e35308547cad606e27 2064 net optional c-icap_0.5.10-4.dsc eddf8abf5b972c52a74ed4828be5d5ba 12356 net optional c-icap_0.5.10-4.debian.tar.xz 19be981ae2b3535ea14dcd29cb9cac27 5692 net optional c-icap_0.5.10-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmPfo9kACgkQXBPW25MF LgMtEA/9GkPElNOusUPWiWr4b2Z7ZW/+NCGy8//OgDysjsGrWDIDTyjq1aGWY5pj VyZnKdLh7SaoaS9Qzavs9nUtZaatMnhEEFsZmLclLvkyKIPeMnCY46yhSWTJ7Pvn odgpqvqR7dgfSe1l2aMTJ4ieGKzHjzKAUXJGBl3it1dSkVOwGbcMkEtskF083fqO dnogF7cYK8Ty2FjRv9eKL1dedh9xGJFH3jzpqy7DUEvrVOfiLrLphV6TwRClbS98 mA+fbLN2Emwmxo3qO51C5eNa2d+EPwzjf9iPUQIPp4PyJ7L40CPGYi0gtT+yts2y fPklCzfUEJDU04X2CQknQPvJKPq29AuHCzC+i/TeIEuaga5+J8MtNu+pjJpKbt33 9ZMJj5Dh7/B19LrcUoPUm6EcU9EDVlO7lXbkXt7LbfDks8NWLjAp4RxfXjq9gCyM eymd1RIWzha13eSWu8nzdEvRMRHCDm8e8luoCSopgs1WiYaYQOD6VX8U82+8OGrM eW1QsGmt9NNCzTt0hCUJMP592oHtpGnKHmIa2TAh84KdY7fWGmUaVG2ETWEh522c 4N+bsQvYMp819HLcUNMjWP3BHtuHwVSjjR1/4Ftupv/uR6xVoM64b6YS0lyYypEN IOSlY/LyDGV76HpRTIrTd5hHxyX192BT8zuzyHOfaiyzylEKDZk= =hoKx -END PGP SIGNATURE End Message ---
Bug#1030575: marked as done (golang-github-hashicorp-go-slug: autopkgtest failure)
Your message dated Sun, 05 Feb 2023 13:19:50 + with message-id and subject line Bug#1030575: fixed in golang-github-hashicorp-go-slug 0.9.1-2 has caused the Debian Bug report #1030575, regarding golang-github-hashicorp-go-slug: autopkgtest failure 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.) -- 1030575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-hashicorp-go-slug Version: 0.9.1-1 Severity: serious X-Debbugs-Cc: Thorsten Alteholz https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-hashicorp-go-slug/31053988/log.gz ... dh_auto_test -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 64 github.com/hashicorp/go-slug === RUN TestPack slug_test.go:23: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestPack (0.00s) === RUN TestPackWithoutIgnoring slug_test.go:154: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestPackWithoutIgnoring (0.00s) === RUN TestPack_symlinks === RUN TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:false === RUN TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:false === RUN TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:false === RUN TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:true === RUN TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:false === RUN TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:true === RUN TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:false --- PASS: TestPack_symlinks (0.03s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:true (0.01s) --- PASS: TestPack_symlinks/absolute:true_external:true_targetExists:false_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:true_external:false_targetExists:false_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:true_targetExists:false_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:true_dereference:false (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:true (0.00s) --- PASS: TestPack_symlinks/absolute:false_external:false_targetExists:false_dereference:false (0.00s) === RUN TestUnpack slug_test.go:369: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestUnpack (0.00s) === RUN TestUnpackDuplicateNoWritePerm --- PASS: TestUnpackDuplicateNoWritePerm (0.00s) === RUN TestUnpackPax
Bug#1030430: Reassigning to biojava6-live
Control: reassign -1 biojava6-live Hello, This is a bug in biojava6-live which makes its biojava-structure artifact require unneeded log4j jars. Best, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: Reassigning to biojava6-live
Processing control commands: > reassign -1 biojava6-live Bug #1030430 [src:snpsift] snpsift: FTBFS: [ERROR] Failed to execute goal on project snpsift: Could not resolve dependencies for project org.snpsift:snpsift:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Bug reassigned from package 'src:snpsift' to 'biojava6-live'. No longer marked as found in versions snpsift/5.1+dfsg2-2. Ignoring request to alter fixed versions of bug #1030430 to the same values previously set -- 1030430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030445: Reassigning to biojava6-live
Control: reassign -1 biojava6-live Hello, This is a bug in biojava6-live which makes its biojava-structure artifact require unneeded log4j jars. Best, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: Reassigning to biojava6-live
Processing control commands: > reassign -1 biojava6-live Bug #1030445 [src:snpeff] snpeff: FTBFS: [ERROR] Failed to execute goal on project snpeff: Could not resolve dependencies for project org.snpeff:snpeff:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Bug reassigned from package 'src:snpeff' to 'biojava6-live'. No longer marked as found in versions snpeff/5.1+d+dfsg-3. Ignoring request to alter fixed versions of bug #1030445 to the same values previously set -- 1030445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > merge 1030430 1030445 Bug #1030430 [biojava6-live] snpsift: FTBFS: [ERROR] Failed to execute goal on project snpsift: Could not resolve dependencies for project org.snpsift:snpsift:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Bug #1030445 [biojava6-live] snpeff: FTBFS: [ERROR] Failed to execute goal on project snpeff: Could not resolve dependencies for project org.snpeff:snpeff:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Merged 1030430 1030445 > tags 1030430 pending Bug #1030430 [biojava6-live] snpsift: FTBFS: [ERROR] Failed to execute goal on project snpsift: Could not resolve dependencies for project org.snpsift:snpsift:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Bug #1030445 [biojava6-live] snpeff: FTBFS: [ERROR] Failed to execute goal on project snpeff: Could not resolve dependencies for project org.snpeff:snpeff:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030430 1030445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025279: marked as done (nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CV
Your message dated Sun, 05 Feb 2023 13:36:23 + with message-id and subject line Bug#1025279: fixed in nvidia-graphics-drivers 525.60.13-1 has caused the Debian Bug report #1025279, regarding nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 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.) -- 1025279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5415 CVE-2022-34670 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure. CVE-2022-42263 NVIDIA G
Processed: found 1030430 in 6.1.0+dfsg-3
Processing commands for cont...@bugs.debian.org: > found 1030430 6.1.0+dfsg-3 Bug #1030430 [biojava6-live] snpsift: FTBFS: [ERROR] Failed to execute goal on project snpsift: Could not resolve dependencies for project org.snpsift:snpsift:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] Bug #1030445 [biojava6-live] snpeff: FTBFS: [ERROR] Failed to execute goal on project snpeff: Could not resolve dependencies for project org.snpeff:snpeff:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 1] There is no source info for the package 'biojava6-live' at version '6.1.0+dfsg-3' with architecture '' Unable to make a source version for version '6.1.0+dfsg-3' Marked as found in versions 6.1.0+dfsg-3. Marked as found in versions 6.1.0+dfsg-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030430 1030445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030539: marked as done (d/copyright is wrong)
Your message dated Sun, 05 Feb 2023 13:37:47 + with message-id and subject line Bug#1030539: fixed in php-dompdf-svg-lib 0.5.0-3 has caused the Debian Bug report #1030539, regarding d/copyright is wrong 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.) -- 1030539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php-dompdf-svg-lib Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks As noted in : This package is LGPLv3+ (LGPL-3.0+) not LGPLv3 (LGPL-3.0). Please update your copyright file in another upload before it migrates to testing/stable. -- :wq --- End Message --- --- Begin Message --- Source: php-dompdf-svg-lib Source-Version: 0.5.0-3 Done: William Desportes We believe that the bug you reported is fixed in the latest version of php-dompdf-svg-lib, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Desportes (supplier of updated php-dompdf-svg-lib 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: Sun, 05 Feb 2023 11:47:36 +0100 Source: php-dompdf-svg-lib Built-For-Profiles: noudeb Architecture: source Version: 0.5.0-3 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: William Desportes Closes: 1030539 Changes: php-dompdf-svg-lib (0.5.0-3) unstable; urgency=medium . * Adjust license to LGPL-3.0+ (Closes: #1030539) * Add "Multi-Arch: foreign" * Add branch on Vcs-Git Checksums-Sha1: dc711bc591fc3262bd81068e37162e757e6e2ec8 2195 php-dompdf-svg-lib_0.5.0-3.dsc 944127d2047263f14318abce052744d6663fb7dc 2704 php-dompdf-svg-lib_0.5.0-3.debian.tar.xz b6d76bebc55ba07a40b1edb12a54bfdfcebef9ab 63850 php-dompdf-svg-lib_0.5.0-3_source.buildinfo Checksums-Sha256: c77b9d35e11ebea834ad2d649f303293aa6d7d1422f0ce979709f4585b911a5c 2195 php-dompdf-svg-lib_0.5.0-3.dsc 1516869f1023d4c333754b9784b0da911c7a5aef4a633f1299be89126ca62276 2704 php-dompdf-svg-lib_0.5.0-3.debian.tar.xz ed70385c5eb48e673aec2555f37b8be8b9fa2fd94b0be2baea931bda1d5582f6 63850 php-dompdf-svg-lib_0.5.0-3_source.buildinfo Files: 2c2565672f7872186fd0a216fbd0747e 2195 php optional php-dompdf-svg-lib_0.5.0-3.dsc df5ea41fb3eaeaa88a81e47ab130cdf3 2704 php optional php-dompdf-svg-lib_0.5.0-3.debian.tar.xz e838fe44025ef71f290683fe48a90318 63850 php optional php-dompdf-svg-lib_0.5.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmPfrZUACgkQkKDvG4JR qInzAw//U8c7zj+MlTxUw/bTHZ586p9JfUlJAkLoqwCV8bppYIXIAqdBcBV1JdCm qE7Am7WL1OLDptVUBl78OhqvDe3RV2H8VHIkhz2c/Rxb+WYN6Lnip9ikzjRNOBFO D7lIi8gLTzqNrWkHddStMLpvzilsIVCd5Z5Ry1uKsx4XePTiaQou3h+QzWH2/THK rS4THqwwGmUSiu/c5jiost9Vtfp5pmUQQaXCFNFoKwlvOZ2Zq6uQRpoZcQc1uCW4 iDTjirDCnUqmSrCDFRvLzMa0YxazQQAr2X3ZtUn+Y8E7loXnnhJ6sehkk6vH+Ofn CdTNUVGEtAUwAZYXDh0IWJlOnKDp1tmDv6D5BMh62YOtuiZU85bll9aE64rKBgV0 KOOybJ/WlLfUv4KTE2nGO0G3/cHjNakGOUNUlPNf3wp8VMIOcbaIQ2IX2DetsQ/g 1PKv7jrTQ5tw2fVJro1b79Lp+pYPTOE6Fo1g8KaZ0TM79QHIcEt1GggETP938gv5 Vf3EQVc8oeGE5GADc5jwoIcixYHJTo/tmUNFv0fBb93mKn60N4ce+aFbiHCvS9OW 50gLqiN+A844RZfSCVqWsk93uLBtfLIThsxlaxayqAiYfhlCweQN4/pJ/H5E0hkG iLaYAYAlsLZXL6qecQMQXfr2p99YnlZjOPW/r7nR2iSbBRXz+mU= =xaEq -END PGP SIGNATURE End Message ---
Bug#1030175: libgetdata: FTBFS: dh_install: error: missing files, aborting
Dear Maintainer, > dh_install: warning: Cannot find (any matches for) > "usr/local/lib/python3.10/dist-packages/*" (tried in ., debian/tmp) > > dh_install: warning: python3-pygetdata missing files: > usr/local/lib/python3.10/dist-packages/* > dh_install: error: missing files, aborting > make: *** [debian/rules:28: binary-arch] Error 25 this is caused by a reference to python 3.10 in this file [1] Kind Regards [1] https://sources.debian.org/src/libgetdata/0.11.0-5/debian/python3-pygetdata.install/
Bug#1030530: Python 3.10 in bookworm
Our social contract #4 says "Our priorities are our users and free software". What benefits would having the python3.10 base packages in bookworm bring for our users (as I point out, for some users, this is a necessity) and what disadvantages would it bring (none that I can think of)? Why would we tell a whole bunch of our users: "Don't upgrade to Debian 12 until all of the critical packages you use from PyPI are upgraded to support Python 3.11, or fix those packages yourself"? And may I politely remind you, Thomas, that you are very concerned about breaking things for people: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973617#40 This is likely a far greater impact than the discussion there on many more people. Best wishes, Julian On Sun, Feb 05, 2023 at 12:25:18PM +0100, Thomas Goirand wrote: > How about fixing the 3.11 issues if you hit them ? How about using Buster and > 3.9 if 3.11 doesn't work (yet) for you ? > > Thomas Goirand (zigo) > On Feb 5, 2023 11:38, Julian Gilbey wrote: > > > > Why is the current intention not to ship the python3.10 package in > > bookworm? > > > > I was trying to run some experiments in a virtual environment a few > > days ago, and it turns out that several of the Python packages I > > needed do not yet run on Python 3.11. I was saved by being able to > > run in a Python 3.10 venv and download all the required packages from > > PyPI. If bookworm shipped without python3.10, I would not have been > > able to do my work. Removing python3.10 from bookworm will seriously > > affect many of our users in a similar situation to me. > > > > Best wishes, > > > > Julian > > > > P.S. We should also fix #1036268 if we do keep python3.10 in bookworm; > > I'm happy to do an NMU if needed.
Processed: redis breaks python-fakeredis autopkgtest: Connection refused
Processing control commands: > found -1 redis/5:7.0.8-2 Bug #1030600 [src:redis, src:python-fakeredis] redis breaks python-fakeredis autopkgtest: Connection refused Marked as found in versions redis/5:7.0.8-2. > found -1 python-fakeredis/1.9.0-0.1 Bug #1030600 [src:redis, src:python-fakeredis] redis breaks python-fakeredis autopkgtest: Connection refused Marked as found in versions python-fakeredis/1.9.0-0.1. -- 1030600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030600: redis breaks python-fakeredis autopkgtest: Connection refused
Source: redis, python-fakeredis Control: found -1 redis/5:7.0.8-2 Control: found -1 python-fakeredis/1.9.0-0.1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of redis the autopkgtest of python-fakeredis fails in testing when that autopkgtest is run with the binary packages of redis from unstable. It passes when run with only packages from testing. In tabular form: passfail redis from testing5:7.0.8-2 python-fakeredis from testing1.9.0-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 redis 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=redis https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fakeredis/31066293/log.gz === FAILURES === ___ TestString.test self = Connection def connect(self): "Connects to the Redis server if not already connected" if self._sock: return try: sock = self.retry.call_with_retry( lambda: self._connect(), lambda error: self.disconnect(error) ) /usr/lib/python3/dist-packages/redis/connection.py:611: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = do = . at 0x7f8088401a80> fail = . at 0x7f8088402840> def call_with_retry(self, do, fail): """ Execute an operation that might fail and returns its result, or raise the exception that was thrown depending on the `Backoff` object. `do`: the operation to call. Expects no argument. `fail`: the failure handler, expects the last error that was thrown """ self._backoff.reset() failures = 0 while True: try: return do() /usr/lib/python3/dist-packages/redis/retry.py:46: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ lambda: self._connect(), lambda error: self.disconnect(error) ) /usr/lib/python3/dist-packages/redis/connection.py:612: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = Connection def _connect(self): "Create a TCP socket connection" # we want to mimic what socket.create_connection does to support # ipv4/ipv6, but we want to set options prior to calling # socket.connect() err = None for res in socket.getaddrinfo( self.host, self.port, self.socket_type, socket.SOCK_STREAM ): family, socktype, proto, canonname, socket_address = res sock = None try: sock = socket.socket(family, socktype, proto) # TCP_NODELAY sock.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1) # TCP_KEEPALIVE if self.socket_keepalive: sock.setsockopt(socket.SOL_SOCKET, socket.SO_KEEPALIVE, 1) for k, v in self.socket_keepalive_options.items(): sock.setsockopt(socket.IPPROTO_TCP, k, v) # set the socket_connect_timeout before we connect sock.settimeout(self.socket_connect_timeout) # connect sock.connect(socket_address) # set the socket_timeout now that we're connected sock.settimeout(self.socket_timeout) return sock except OSError as _: err = _ if sock is not None: sock.close() if err is not None: raise err /usr/lib/python3/dist-packages/redis/connection.py:677: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = Connection def _connect(self): "Create a TCP socket connection" # we want to mimic what socket.create_connection does to support # ipv4/ipv6, but we want to set options prior to calling # socket.connect() err = None for res in socket.getaddrinfo( self.host, self.port, self.socket_type, socket.SOCK_STREAM ): family, socktype, proto, canonname, socket_address = res sock = None try: sock = socket.socket(family, socktype, proto) # TCP_NODELAY
Bug#1030601: findent: autopkgtest regression: original program does not compile
Source: findent Version: 4.2.5-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of findent the autopkgtest of findent fails in testing when that autopkgtest is run with the binary packages of findent from unstable. It passes when run with only packages from testing. In tabular form: passfail findentfrom testing4.2.5-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 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=findent https://ci.debian.net/data/autopkgtest/testing/amd64/f/findent/31040771/log.gz ../test-compile.sh: ../progfixed-dos.f will try to compile fortran sources using gfortran findent version 4.2.5 progfixed-dos.f: original program does not compile using: -fcoarray=single -cpp -fopenmp -ffixed-form -ffixed-line-length-none -fd-lines-as-comments -o prog ../progfixed-dos.f OK converted program does not compile using: -fcoarray=single -cpp -fopenmp -ffixed-form -ffixed-line-length-none -fd-lines-as-comments -o prog progfixed-dos.f.try.f END TESTING FINDENT rc=1 If you are sure /tmp/autopkgtest-lxc.uypbn9fi/downtmp/build.fHY/src/debian/tests/test1.sh.tmpdir/progfixed-dos.f.try.f is correct: copy /tmp/autopkgtest-lxc.uypbn9fi/downtmp/build.fHY/src/debian/tests/test1.sh.tmpdir/progfixed-dos.f.try.f to the corresponding .in file in the test directory and configure again. autopkgtest [14:13:32]: test test1.sh OpenPGP_signature Description: OpenPGP digital signature
Bug#1030530: Python 3.10 in bookworm
Hi Julian (2023.02.05_10:38:23_+) > Why is the current intention not to ship the python3.10 package in > bookworm? Because we aim to have a single Python release supported in every stable release. > I was trying to run some experiments in a virtual environment a few > days ago, and it turns out that several of the Python packages I > needed do not yet run on Python 3.11. I was saved by being able to > run in a Python 3.10 venv and download all the required packages from > PyPI. If bookworm shipped without python3.10, I would not have been > able to do my work. Removing python3.10 from bookworm will seriously > affect many of our users in a similar situation to me. By the time bookworm releases, that probably won't be the case any more. But anything that gets removed from Debian, because it isn't ready yet obviously gets hurt in the process... SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1030602: scapy: autopkgtest regression on 32 bit architectures and s390x
Source: scapy Version: 2.5.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of scapy the autopkgtest of scapy fails in testing when that autopkgtest is run with the binary packages of scapy from unstable. It passes when run with only packages from testing. In tabular form: passfail scapy from testing2.5.0+dfsg-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 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=scapy https://ci.debian.net/data/autopkgtest/testing/armel/s/scapy/31071000/log.gz ###(046)=[failed] Fragment exception >>> ex = False >>> try: ... fragments = ISOTP(b"a" * (1 << 32)).fragment() ... except Scapy_Exception: ... ex = True ... Traceback (most recent call last): File "", line 3, in OverflowError: cannot fit 'int' into an index-sized integer OpenPGP_signature Description: OpenPGP digital signature
Bug#1029266: marked as done (rapiddisk-dkms: module fails to build for Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’)
Your message dated Sun, 05 Feb 2023 14:50:11 +
with message-id
and subject line Bug#1029266: fixed in rapiddisk 8.2.0-4.1
has caused the Debian Bug report #1029266,
regarding rapiddisk-dkms: module fails to build for Linux 6.1: error: ‘struct
dm_io_request’ has no member named ‘bi_op’
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.)
--
1029266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rapiddisk-dkms
Version: 8.2.0-4
Severity: serious
Tags: patch
Hi,
rapiddisk-dkms fails to build a module for Linux 6.1:
https://salsa.debian.org/debian/rapiddisk/-/jobs/3824488
E: rapiddisk/8.2.0 failed to build for 6.1.0-2-amd64
== /var/lib/dkms/rapiddisk/8.2.0/build/make.log ==
DKMS make.log for rapiddisk-8.2.0 for kernel 6.1.0-2-amd64 (x86_64)
Fri Jan 20 13:56:26 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.1.0-2-amd64'
CC [M] /var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.o
CC [M] /var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk-cache.o
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk-cache.c: In function
‘dm_io_async_bvec’:
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk-cache.c:178:14: error: ‘struct
dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’?
178 | iorq.bi_op = rw;
| ^
| bi_opf
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk-cache.c:179:13: error: ‘struct
dm_io_request’ has no member named ‘bi_op_flags’
179 | iorq.bi_op_flags = 0;
| ^
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.c: In function ‘rdsk_ioctl’:
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.c:663:38: error: invalid operands
to binary <= (have ‘atomic_t’ and ‘int’)
663 | if (bdev->bd_openers <= 1) {
| ^~
| |
| atomic_t
make[1]: *** [/usr/src/linux-headers-6.1.0-2-common/scripts/Makefile.build:255:
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk-cache.o] Error 1
make[1]: *** Waiting for unfinished jobs
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.c: In function ‘attach_device’:
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.c:808:28: error:
‘QUEUE_FLAG_DISCARD’ undeclared (first use in this function); did you mean
‘QUEUE_FLAG_DAX’?
808 | blk_queue_flag_set(QUEUE_FLAG_DISCARD, disk->queue);
|^~
|QUEUE_FLAG_DAX
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.c:808:28: note: each undeclared
identifier is reported only once for each function it appears in
make[1]: *** [/usr/src/linux-headers-6.1.0-2-common/scripts/Makefile.build:255:
/var/lib/dkms/rapiddisk/8.2.0/build/rapiddisk.o] Error 1
make: *** [/usr/src/linux-headers-6.1.0-2-common/Makefile:2017:
/var/lib/dkms/rapiddisk/8.2.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.1.0-2-amd64'
A patch seems to be available in merge request !1.
Andreas
--- End Message ---
--- Begin Message ---
Source: rapiddisk
Source-Version: 8.2.0-4.1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
rapiddisk, 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 1029...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated rapiddisk 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, 31 Jan 2023 14:28:59 +0100
Source: rapiddisk
Architecture: source
Version: 8.2.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Gürkan Myczko
Changed-By: Andreas Beckmann
Closes: 1027882 1029266
Changes:
rapiddisk (8.2.0-4.1) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Non-maintainer upload.
* Switch to dh-sequence-dkms. (Closes: #1027882)
* Declare Testsuite: autopkgtest-pkg-dkms.
.
[ Andrea Righi ]
* Support linux 6.x. (Closes: #1029266)
Checksums-Sha1:
4abca6159756fb3a896789a229330edeb17d8706 2020 rapiddisk_8.2.0-4.1.dsc
a3ea050732ff89a71b724fdcfb6176ad14
Bug#1030604: mariadb breaks mariadb-10.6 autopkgtest: Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4'
Source: mariadb, mariadb-10.6 Control: found -1 mariadb/1:10.11.1-2 Control: found -1 mariadb-10.6/1:10.6.11-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of mariadb the autopkgtest of mariadb-10.6 fails in testing on amd64 and arm64 when that autopkgtest is run with the binary packages of mariadb from unstable. It passes when run with only packages from testing. In tabular form: passfail mariadbfrom testing1:10.11.1-2 mariadb-10.6 from testing1:10.6.11-2 versioned deps [0] from testingfrom unstable 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 mariadb 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 [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from mariadb/1:10.11.1-2. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=mariadb https://ci.debian.net/data/autopkgtest/testing/amd64/m/mariadb-10.6/31062126/log.gz + which systemctl + echo Found systemctl, continuing smoke test.. + mysql Running test 'smoke' /usr/bin/systemctl Found systemctl, continuing smoke test.. + mysql testdatabase + + mysql --batch --skip-column-names --user=testuser --password=testpassword testdatabase echo SELECT bar+1 FROM foo; + result=42 + [ 42 != 42 ] + mysql --user=testuser --password=testpassword testdatabase + mysql + mariadb ERROR 1231 (42000) at line 1: Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4' autopkgtest [04:36:43]: test smoke OpenPGP_signature Description: OpenPGP digital signature
Processed: mariadb breaks mariadb-10.6 autopkgtest: Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4'
Processing control commands: > found -1 mariadb/1:10.11.1-2 Bug #1030604 [src:mariadb, src:mariadb-10.6] mariadb breaks mariadb-10.6 autopkgtest: Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4' Marked as found in versions mariadb/1:10.11.1-2. > found -1 mariadb-10.6/1:10.6.11-2 Bug #1030604 [src:mariadb, src:mariadb-10.6] mariadb breaks mariadb-10.6 autopkgtest: Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4' Marked as found in versions mariadb-10.6/1:10.6.11-2. -- 1030604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030430: marked as done (snpsift: FTBFS: [ERROR] Failed to execute goal on project snpsift: Could not resolve dependencies for project org.snpsift:snpsift:jar:5.1: The following artifacts could no
Your message dated Sun, 05 Feb 2023 15:07:26 + with message-id and subject line Bug#1030430: fixed in biojava6-live 6.1.0+dfsg-3 has caused the Debian Bug report #1030430, regarding snpsift: FTBFS: [ERROR] Failed to execute goal on project snpsift: Could not resolve dependencies for project org.snpsift:snpsift:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 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.) -- 1030430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snpsift Version: 5.1+dfsg2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 javahelper >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibsnpsift-java --debian-build --keep-pom-version > --maven-repo=/<>/snpsift-5.1\+dfsg2/debian/maven-repo > Failed to parse > /<>/debian/maven-repo/org/biojava/biojava-structure/6.1.0/biojava-structure-6.1.0.pom > javax.xml.stream.XMLStreamException: ParseError at [row,col]:[129,21] > Message: Element type "debian.org.rcsb." must be followed by either attribute > specifications, ">" or "/>". > at > java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:652) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:82) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:57) > at org.debian.maven.repo.Repository.scan(Repository.java:397) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:201) > at org.debian.maven.repo.Repository.scanOnce(Repository.java:196) > at > org.debian.maven.repo.POMTransformer.usePluginVersionsFromRepository(POMTransformer.java:107) > at org.debian.maven.repo.POMTransformer.main(POMTransformer.java:779) > > Failed to parse > /<>/debian/maven-repo/org/biojava/biojava-structure/6.x/biojava-structure-6.x.pom > javax.xml.stream.XMLStreamException: ParseError at [row,col]:[129,21] > Message: Element type "debian.org.rcsb." must be followed by either attribute > specifications, ">" or "/>". > at > java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:652) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:82) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:57) > at org.debian.maven.repo.Repository.scan(Repository.java:397) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:201) > at org.debian.maven.repo.Repository.scanOnce(Repository.java:196) > at > org.debian.maven.repo.POMTransformer.usePluginVersionsFromRepository(POMTransformer.java:107) > at org.debian.maven.repo.POMTransformer.main(POMTransformer.java:779) > >jh_linkjars >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>/snpsift-5.1\+dfsg2 > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/<>/snpsift-5.1\+dfsg2/debian > -Dmaven.repo.local=/<>/snpsift-5.1\+dfsg2/debian/maven-repo > --batch-mode package javadoc:jar javadoc:aggregate -DskipTests > -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and
Bug#1030445: marked as done (snpeff: FTBFS: [ERROR] Failed to execute goal on project snpeff: Could not resolve dependencies for project org.snpeff:snpeff:jar:5.1: The following artifacts could not be
Your message dated Sun, 05 Feb 2023 15:07:26 + with message-id and subject line Bug#1030430: fixed in biojava6-live 6.1.0+dfsg-3 has caused the Debian Bug report #1030430, regarding snpeff: FTBFS: [ERROR] Failed to execute goal on project snpeff: Could not resolve dependencies for project org.snpeff:snpeff:jar:5.1: The following artifacts could not be resolved: org.apache.logging.log4j:log4j-to-slf4j:jar:debian, org.apache.logging.log4j:log4j-api:jar:debian, org.apache.logging.log4j:log4j-core:jar:debian: Cannot access maven (https://repo1.maven.org/maven2/) in offline mode and the artifact org.apache.logging.log4j:log4j-to-slf4j:jar:debian has not been downloaded from it before. -> [Help 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.) -- 1030430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snpeff Version: 5.1+d+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > # We replace the compiling timestamp by the one in d/changelog to enhance > # build reproducibility. > cp src/main/java/org/snpeff/SnpEff.java SnpEff.java.old > sed "s/Gpr\.compile.*/\"$(date --utc --date="@1674244532" +"%Y-%m-%d %H:%M" > )\";/" SnpEff.java.old > src/main/java/org/snpeff/SnpEff.java > dh_auto_configure > mh_patchpoms -plibsnpeff-java --debian-build --keep-pom-version > --maven-repo=/<>/snpeff-5.1\+d\+dfsg/debian/maven-repo > Failed to parse > /<>/debian/maven-repo/org/biojava/biojava-structure/6.1.0/biojava-structure-6.1.0.pom > javax.xml.stream.XMLStreamException: ParseError at [row,col]:[129,21] > Message: Element type "debian.org.rcsb." must be followed by either attribute > specifications, ">" or "/>". > at > java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:652) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:82) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:57) > at org.debian.maven.repo.Repository.scan(Repository.java:397) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:201) > at org.debian.maven.repo.Repository.scanOnce(Repository.java:196) > at > org.debian.maven.repo.POMTransformer.usePluginVersionsFromRepository(POMTransformer.java:107) > at org.debian.maven.repo.POMTransformer.main(POMTransformer.java:779) > > Failed to parse > /<>/debian/maven-repo/org/biojava/biojava-structure/6.x/biojava-structure-6.x.pom > javax.xml.stream.XMLStreamException: ParseError at [row,col]:[129,21] > Message: Element type "debian.org.rcsb." must be followed by either attribute > specifications, ">" or "/>". > at > java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:652) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:82) > at org.debian.maven.repo.POMReader.readPom(POMReader.java:57) > at org.debian.maven.repo.Repository.scan(Repository.java:397) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:394) > at org.debian.maven.repo.Repository.scan(Repository.java:201) > at org.debian.maven.repo.Repository.scanOnce(Repository.java:196) > at > org.debian.maven.repo.POMTransformer.usePluginVersionsFromRepository(POMTransformer.java:107) > at org.debian.maven.repo.POMTransformer.main(POMTransformer.java:779) > > make[1]: Leaving directory '/<>' >jh_linkjars >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>/snpeff-5.1\+d\+dfsg > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/<>/snpeff-5.1\+d\+dfsg/debian > -
Bug#1028835: marked as done (python-aioxmpp: FTBFS: AttributeError: property of 'Mock' object has no setter)
Your message dated Sun, 05 Feb 2023 15:42:13 + with message-id and subject line Bug#1028835: fixed in python-aioxmpp 0.13.3-1 has caused the Debian Bug report #1028835, regarding python-aioxmpp: FTBFS: AttributeError: property of 'Mock' object has no setter 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.) -- 1028835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aioxmpp Version: 0.13.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 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 '/<>' > CI=true pybuild --test --test-pytest > I: pybuild base:240: cd > /<>/.pybuild/cpython3_3.11_aioxmpp/build; python3.11 -m pytest > tests > = test session starts > == > platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack > rootdir: /<> > collected 4529 items > > tests/test_cache.py .. [ > 0%] > tests/test_callbacks.py [ > 1%] > .. [ > 2%] > tests/test_connector.py ... [ > 2%] > tests/test_custom_queue.py ..[ > 2%] > tests/test_dispatcher.py ... [ > 3%] > ... [ > 3%] > tests/test_e2e.py sss[ > 4%] > tests/test_errors.py .. [ > 4%] > tests/test_hashes.py .. [ > 5%] > tests/test_highlevel.py .. [ > 5%] > tests/test_i18n.py ... [ > 6%] > tests/test_network.py ...[ > 7%] > tests/test_node.py . [ > 9%] > .[ > 10%] > tests/test_nonza.py [ > 11%] > .. [ > 12%] > tests/test_protocol.py . [ > 13%] > .[ > 14%] > tests/test_rfc3921.py . [ > 15%] > tests/test_rfc6120.py [ > 15%] > tests/test_sasl.py ..[ > 15%] > tests/test_security_layer.py ... [ > 16%] > ... [ > 17%] > tests/test_service.py .. [ > 18%] > [ > 19%] > [ > 20%] > tests/test_stanza.py ... [ > 21%] > .[ > 22%] > tests/test_statemachine.py . [ > 22%] > tests/test_stream.py ... [ > 24%] > [ > 25%] > [ > 27%] > [ > 28%] > .[ > 28%] > tests/test_stringprep.py . [ > 29%] > tests/test_structs.py ..s... [ > 30%] > [ > 31%] > [ > 32%] > tests/test_tasks.py .. [ > 32%] > tests/test_testutils.py [ > 33%] > .
Processed: owner 1028720
Processing commands for cont...@bugs.debian.org: > owner 1028720 ! Bug #1028720 [src:wss4j] wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 1] Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1028720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027965: Fix for the RC bug in vtk
Hello, Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- a build failure in gdcm caused by missing dependency. The fix proposed by Mathieu seems reasonable to me. Anton: I'm writing to ask your opinion about the commits in salsa since the last upload (June 2022); specifically, do you feel they are suitable for inclusion now? Should I: 1. apply the patch to the lastest in salsa? 2. apply the patch to the last upload sources ignoring salsa? 3. leave it alone and let you deal with it? 4. something else? Appreciate your insight. -Steve signature.asc Description: This is a digitally signed message part.
Bug#1027965: Fix for the RC bug in vtk
Hi Steven. thanks for the notice! vtk9 upload is in my todo list for the next few days. Regards Anton Am So., 5. Feb. 2023 um 17:30 Uhr schrieb Steven Robbins : > > Hello, > > Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- > a build failure in gdcm caused by missing dependency. The fix proposed by > Mathieu seems reasonable to me. > > Anton: I'm writing to ask your opinion about the commits in salsa since the > last upload (June 2022); specifically, do you feel they are suitable for > inclusion now? > > Should I: > > 1. apply the patch to the lastest in salsa? > 2. apply the patch to the last upload sources ignoring salsa? > 3. leave it alone and let you deal with it? > 4. something else? > > Appreciate your insight. > -Steve
Bug#1028720: marked as pending in wss4j
Control: tag -1 pending Hello, Bug #1028720 in wss4j 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/java-team/wss4j/-/commit/3f2c258f8da61894fa5bb310c4bedb70e16ab2f2 Add build-dep on liblog4j1.2-java (Closes: #1028720) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028720
Processed: Bug#1028720 marked as pending in wss4j
Processing control commands: > tag -1 pending Bug #1028720 [src:wss4j] wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 1] Added tag(s) pending. -- 1028720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020617: openlibm: diff for NMU version 0.8.1+dfsg-2.1
Control: tags 1020617 + patch Dear maintainer, I've prepared an NMU for openlibm (versioned as 0.8.1+dfsg-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru openlibm-0.8.1+dfsg/debian/changelog openlibm-0.8.1+dfsg/debian/changelog --- openlibm-0.8.1+dfsg/debian/changelog 2022-07-24 22:44:28.0 +0300 +++ openlibm-0.8.1+dfsg/debian/changelog 2023-02-05 18:38:54.0 +0200 @@ -1,3 +1,10 @@ +openlibm (0.8.1+dfsg-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Unset MARCH during build and test. (Closes: #1020617) + + -- Adrian Bunk Sun, 05 Feb 2023 18:38:54 +0200 + openlibm (0.8.1+dfsg-2) unstable; urgency=medium * Upload to unstable. diff -Nru openlibm-0.8.1+dfsg/debian/rules openlibm-0.8.1+dfsg/debian/rules --- openlibm-0.8.1+dfsg/debian/rules 2022-06-18 23:51:10.0 +0300 +++ openlibm-0.8.1+dfsg/debian/rules 2023-02-05 18:38:49.0 +0200 @@ -6,5 +6,11 @@ %: dh $@ +override_dh_auto_build: + dh_auto_build -- MARCH="" + +override_dh_auto_test: + dh_auto_test -- MARCH="" + override_dh_auto_install: dh_auto_install -- "CC=$(CC)" prefix=/usr
Processed: openlibm: diff for NMU version 0.8.1+dfsg-2.1
Processing control commands:
> tags 1020617 + patch
Bug #1020617 {Done: Paul Gevers } [src:openlibm]
src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and
mips64el
Added tag(s) patch.
--
1020617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
This is now solved on https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31
Bug#1028720: marked as done (wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central
Your message dated Sun, 05 Feb 2023 16:52:39 + with message-id and subject line Bug#1028720: fixed in wss4j 1.6.19-3 has caused the Debian Bug report #1028720, regarding wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 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.) -- 1028720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wss4j Version: 1.6.19-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_autoreconf -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibwss4j-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > [INFO] < org.apache.ws.security:wss4j > > > [INFO] Building Apache WSS4J 1.6.19 > [INFO] ---[ bundle > ]--- > [WARNING] The POM for log4j:log4j:jar:1.2.x is missing, no dependency > information available > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.591 s > [INFO] Finished at: 2023-01-13T20:28:28Z > [INFO] > > [ERROR] Failed to execute goal on project wss4j: Could not resolve > dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot > access central (https://repo.maven.apache.org/maven2) in offline mode and the > artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> > [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [0m[0mdh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify > -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make: *** [debian/rules:4: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/01/13/wss4j_1.6.19-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 contribut
Bug#1030615: opendht: FTBFS on mipsel: /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0'
Source: opendht Version: 2.4.12-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=opendht&arch=mipsel&ver=2.4.12-1.1&stamp=1675583004&raw=0 [ 91%] Built target perftest [ 94%] Linking CXX executable dhtchat cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtchat.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtchat.dir/dhtchat.cpp.o -o dhtchat ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [ 94%] Built target dhtchat [ 97%] Linking CXX executable dhtnode cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtnode.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtnode.dir/dhtnode.cpp.o -o dhtnode ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0' /usr/bin/ld: /usr/lib/mipsel-linux-gnu/libatomic.so.1: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [tools/CMakeFiles/dhtnode.dir/build.make:113: tools/dhtnode] Error 1 make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:155: tools/CMakeFiles/dhtnode.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [100%] Linking CXX executable durl cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/durl.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/durl.dir/durl.cpp.o -o durl ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [100%] Built target durl make[2]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[1]: *** [Makefile:139: all] Error 2 make[1]: Leaving directory '/<>/obj-mipsel-linux-gnu' dh_auto_build: error: cd obj-mipsel-linux-gnu && make -j4 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:19: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Cheers -- Sebastian Ramacher
Bug#1030530: Python 3.10 in bookworm
On Sun, Feb 05, 2023 at 02:41:08PM +, Stefano Rivera wrote: > Hi Julian (2023.02.05_10:38:23_+) > > > Why is the current intention not to ship the python3.10 package in > > bookworm? > > Because we aim to have a single Python release supported in every stable > release. I am not suggesting that we revert to having Python 3.10 as a "supported version" (that would be a whole separate discussion); I am suggesting that we keep just the Python 3.10 interpreter and python3.10-venv in bookworm, so that users can use it to run a virtual environment if they need to do so. > > I was trying to run some experiments in a virtual environment a few > > days ago, and it turns out that several of the Python packages I > > needed do not yet run on Python 3.11. I was saved by being able to > > run in a Python 3.10 venv and download all the required packages from > > PyPI. If bookworm shipped without python3.10, I would not have been > > able to do my work. Removing python3.10 from bookworm will seriously > > affect many of our users in a similar situation to me. > > By the time bookworm releases, that probably won't be the case any more. I honestly don't know if that will be the case or not; some packages will be much slower to adapt than others. That's why I'm suggesting we leave the python3.10 and python3.10-venv packages in bookworm. > But anything that gets removed from Debian, because it isn't ready yet > obviously gets hurt in the process... I'm not sure what you mean here? Best wishes, Julian
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
04.02.2023 23:48, Hilko Bengen wrote: .. Does 7.2+dfsg-1 work? I don't have s390x environment so have no way to deal with this one. No, it doesn't. On the porterbox (zelenka.debian.org) I was only able to install 1:7.2+dfsg-1+b1 without rebuilding. Oh, I forgot about zelenka. Tried that one yesterday. The last non-failing build before[1] also used 1:7.2+dfsg-1+b1, though. This made me think that the hang might be related to a shared library that had been updated since. It is interesting. On zelenka, I can run older versions of qemu-utils, from up to version 6.2 (haven't tried older, - it refer to older versions of liburing and libnettle). I d'loaded the .deb file from snapshot.d.o, extracted it in a local dir and run qemu-img from there. The thing is: I can't find *any* working version of qemu-img, they all hang like described. This includes 1:7.2+dfsg-1+b1 too. So I really wonder if it worked before. I also tried with a few versions of glibc, - also extracting them into a local folder and running with LD_LIBRARY_PATH pointing to it, -- the same issue, qemu-img hangs. [1] https://buildd.debian.org/status/logs.php?pkg=libguestfs&arch=s390x yet, libguestfs definitely worked before. Do we perhaps have something else which broke in between? But I really wonder how it happen that 1:7.2+dfsg-1+b1 worked, and I can't reproduce it :) I'm about to add "found: 6.2" tag to this one :)) /mjt
Bug#1030483: marked as done (beginend-el: FTBFS: error: (file-missing (lambda (arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting current directory" "No such file or directory" "
Your message dated Sun, 05 Feb 2023 17:49:31 + with message-id and subject line Bug#1030483: fixed in beginend-el 2.3.0+git20220902.c8fe2cd-1 has caused the Debian Bug report #1030483, regarding beginend-el: FTBFS: error: (file-missing (lambda (arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting current directory" "No such file or directory" "/tmp/temp-fs-MQAR3w") 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.) -- 1030483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: beginend-el Version: 2.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > skipping upstream build > make[1]: Leaving directory '/<>' >dh_elpa_test > buttercup -L . > Loading /etc/emacs/site-start.d/00debian.el (source)... > Loading /etc/emacs/site-start.d/50autoconf.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Running 40 specs. > > beginend in a dired buffer > ignores . and .. at the beginningMark set > > [32m ignores . and .. at the beginning[0m (37.46ms) > ignores . and .. at the endMark set > > [32m ignores . and .. at the end[0m (7.07ms) > ignores . at the beginning and .. at the endMark set > > [32m ignores . at the beginning and .. at the end[0m (6.98ms) > ignores . and .. in the middleMark set > > [32m ignores . and .. in the middle[0m (6.22ms) > ignores . and .. when they are hiddenMark set > > [32m ignores . and .. when they are hidden[0m (5.17ms) > ignores . and .. when they are not hiddenMark set > > [32m ignores . and .. when they are not hidden[0m (10.38ms) > ignores . and .. when they are hidden and the directory is emptyMark set > > [32m ignores . and .. when they are hidden and the directory is empty[0m > (4.45ms) > ignores . and .. when they are not hidden and the directory is emptyMark set > > [32m ignores . and .. when they are not hidden and the directory is > empty[0m (4.19ms) > > beginend > pushes mark > when going to beginning > if point is not at beginningMark set > > [31m if point is not at beginning[0m[31m FAILED[0m (71.18ms) > only onceMark set > > [31m only once[0m[31m FAILED[0m (38.91ms) > when going to end > if point is not at endMark set > > [31m if point is not at end[0m[31m FAILED[0m (26.99ms) > only onceMark set > > [31m only once[0m[31m FAILED[0m (25.86ms) > does not push mark > when going to beginning > if point is already at beginning > [31m if point is already at beginning[0m[31m FAILED[0m (3.40ms) > if point is at point-min > [31m if point is at point-min[0m[31m FAILED[0m (25.63ms) > when going to end > if point is already at end > [31m if point is already at end[0m[31m FAILED[0m (25.09ms) > if point is at point-max > [31m if point is at point-max[0m[31m FAILED[0m (26.64ms) > > beginend, when narrowing is active, > goes to point-min if beginning is outside the narrowed region > [31m goes to point-min if beginning is outside the narrowed region[0m[31m > FAILED[0m (3.86ms) > goes to beginning if beginning is inside the narrowed regionMark set > > [31m goes to beginning if beginning is inside the narrowed region[0m[31m > FAILED[0m (24.96ms) > goes to point-max if end is outside the narrowed region > [31m goes to point-max if end is outside the narrowed region[0m[31m > FAILED[0m (25.26ms) > goes to end if end is inside the narrowed region > [31m goes to end if end is inside the narrowed region[0m[31m FAILED[0m > (29.04ms) > does not move point > when going to beginning and beginning outside the narrowed region if > point is already at point-min > [31mwhen going to beginning and beginning outside the narrowed region if > point is already at point-min[0m[31m FAILED[0m (3.46ms) > when going to end and end outside the narrowed region if point is already > at point-max > [31mwhen going to end and end outside the narrowed region if point is > already at point-max[0m[31m FAILED[0m (26.75ms) > d
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
Control: tag -1 + help Control: found -1 1:5.2+dfsg-11+deb11u2 05.02.2023 20:30, Michael Tokarev wrote: .. The thing is: I can't find *any* working version of qemu-img, they all hang like described. This includes 1:7.2+dfsg-1+b1 too. There's more: I installed bullseye on zelenka, and tried this qemu-img command there (1:5.2+dfsg-11+deb11u2). It hangs exactly the same way. So it looks like this problem has been there for a very long time and no one noticed it. I don't know if qemu-system-s390x hang is due to this or different, - probably different issue. Now I need a reproducer for qemu-system-s390x hang :) /mjt
Processed: Re: Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
Processing control commands: > tag -1 + help Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x Added tag(s) help. > found -1 1:5.2+dfsg-11+deb11u2 Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x Marked as found in versions qemu/1:5.2+dfsg-11+deb11u2. -- 1030545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
So, many previous versions behave the same, including bullseye. However. 1. I was able to create a 512-bytes qcow2 file once in /home/mjt on zelenka. And. 2. All versions always work fine in /tmp, on a tmpfs. Is it possible that the tests were running on a tmpfs before? /mjt
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
Hi Otto Am 05.02.23 um 17:55 schrieb Otto Kekäläinen: This is now solved on https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31 Mangling the maintainers scripts of another package is a delicate issue as it's often fragile and can cause hard to debug failures in corner cases. Personally, I would have turned the versioned packages into empty transitional packages. This would have made the upgrade process much smoother and avoided this issue altogether (the new empty versioned packages would have no maintainer scripts). It's also common practice for such use cases. Any reason why you didn't consider this approach? Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1030530: python3.10 should not be in bookworm
Package: python3.10 Followup-For: Bug #1030530 Perhaps a strange or seemingly off-topic question, but: is it fair to assume that Python 3.11's improved (typical) performance characteristics should likely result in similar-scale energy consumption reductions? (I'd be likely, although cannot guarantee, to offer assistance -- outside of the Debian project and packaging process -- upstream to DFSG-compatible Python packages that would consider Debian's removal of Python 3.10 from bookworm a blocker, depending on the circumstances and my own capacity and willingness to help)
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
> > This is now solved on > > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31 > > Mangling the maintainers scripts of another package is a delicate issue > as it's often fragile and can cause hard to debug failures in corner cases. > > Personally, I would have turned the versioned packages into empty > transitional packages. This would have made the upgrade process much > smoother and avoided this issue altogether (the new empty versioned > packages would have no maintainer scripts). > It's also common practice for such use cases. > > Any reason why you didn't consider this approach? I did write the code for empty packages and tested it (as visible in the merge request above) but it would have created much more moving parts and failures elsewhere. Fixing the maintainer scripts proved to be the most elegant solution.
Bug#1019914: marked as done (Useless in Debian)
Your message dated Sun, 05 Feb 2023 18:41:05 + with message-id and subject line Bug#1021589: Removed package(s) from unstable has caused the Debian Bug report #1019914, regarding Useless in Debian 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.) -- 1019914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: adldap2 Severity: serious [ Reported by a team member to see the package removed from testing ] adldap2 will be deprecated in favor of LdapRecord (https://github.com/DirectoryTree/LdapRecord), and I don't see a use case any more at the moment. No packages depend on it, so it can be removed from testing easily. Regards Katharina -- --- End Message --- --- Begin Message --- Version: 10.4.1-1.1+rm Dear submitter, as the package adldap2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1021589 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1028862: marked as done (xorg-gtest: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Sun, 05 Feb 2023 18:41:35 + with message-id and subject line Bug#1030548: Removed package(s) from unstable has caused the Debian Bug report #1028862, regarding xorg-gtest: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-gtest Version: 0.7.1-8 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/examples' > FAIL: xorg-gtest-environment-example > PASS: xorg-gtest-example > == >X.org Testing Environment for Google Test 0.7.1: examples/test-suite.log > == > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: xorg-gtest-environment-example > > > [==] Running 6 tests from 2 test cases. > [--] Global test environment set-up. > [--] 5 tests from Test > [ RUN ] Test.DummyXorgServerTest > [ OK ] Test.DummyXorgServerTest (1 ms) > [ RUN ] Test.XIQueryVersion20 > unknown file: Failure > C++ exception with description "Failed to open connection to display. > This usually means that your X server did not start properly. > Check the log file, or set XORG_GTEST_CHILD_STDOUT to see the server's > error messages when starting." thrown in SetUp(). > [ FAILED ] Test.XIQueryVersion20 (1 ms) > [ RUN ] Test.XIQueryVersion22 > [ OK ] Test.XIQueryVersion22 (42 ms) > [ RUN ] Test.CreateWindowProperty > [ OK ] Test.CreateWindowProperty (42 ms) > [ RUN ] Test.CheckWindowProperty > [ OK ] Test.CheckWindowProperty (55 ms) > [--] 5 tests from Test (141 ms total) > > [--] 1 test from SubTest > [ RUN ] SubTest.ExampleAtom > [ OK ] SubTest.ExampleAtom (43 ms) > [--] 1 test from SubTest (43 ms total) > > [--] Global test environment tear-down > Warning: Failed to terminate Xorg server: Success > [==] 6 tests from 2 test cases ran. (1277 ms total) > [ PASSED ] 5 tests. > [ FAILED ] 1 test, listed below: > [ FAILED ] Test.XIQueryVersion20 > > 1 FAILED TEST > FAIL xorg-gtest-environment-example (exit status: 1) > > > Testsuite summary for X.org Testing Environment for Google Test 0.7.1 > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See examples/test-suite.log > > make[5]: *** [Makefile:869: test-suite.log] Error 1 > make[5]: Leaving directory '/<>/examples' > make[4]: *** [Makefile:977: check-TESTS] Error 2 > make[4]: Leaving directory '/<>/examples' > make[3]: *** [Makefile:1057: check-am] Error 2 > make[3]: Leaving directory '/<>/examples' > make[2]: *** [Makefile:464: check-recursive] Error 1 > make[2]: Leaving directory '/<>' > dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2023/01/13/xorg-gtest_0.7.1-8_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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 ch
Bug#1030409: marked as done (precious: FTBFS: build-dependency not installable: librust-test-case-2+default-dev)
Your message dated Sun, 05 Feb 2023 19:53:57 +0100 with message-id <167562323712.1735478.14613972050470450...@auryn.jones.dk> and subject line Re: Bug#1030409: precious: FTBFS: build-dependency not installable: librust-test-case-2+default-dev has caused the Debian Bug report #1030409, regarding precious: FTBFS: build-dependency not installable: librust-test-case-2+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1030409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: precious Version: 0.4.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmark-gfm, debhelper-compat (= 13), dh-cargo, git, > help2man, librust-anyhow-1+default-dev (>= 1.0.66), librust-clap-3+cargo-dev, > librust-clap-3+default-dev, librust-clap-3+derive-dev, > librust-env-logger-0.9+default-dev, librust-fern+colored-dev (<< 7), > librust-fern+default-dev (<< 7), librust-filetime-0.2+default-dev (>= > 0.2.18), librust-globset-0.4+default-dev (>= 0.4.9), > librust-ignore-0.4+default-dev (>= 0.4.18), librust-indexmap-1+default-dev > (>= 1.9.1), librust-indexmap-1+serde-dev (>= 1.9.1), > librust-itertools+default-dev (<< 0.11), librust-log-0.4+default-dev (>= > 0.4.17), librust-md5-0.7+default-dev, librust-once-cell-1+default-dev (>= > 1.16), librust-pathdiff-0.2+default-dev, > librust-pretty-assertions-1+default-dev (>= 1.3), librust-rayon-1+default-dev > (>= 1.5.3), librust-regex-1+default-dev (>= 1.7), librust-serde-1+default-dev > (>= 1.0.147), librust-serde-1+derive-dev (>= 1.0.147), > librust-serial-test-0.9+default-dev, librust-tempfile-3+default-dev (>= 3.3), > librust-test-case-2+default-dev, librust-thiserror-1+default-dev (>= 1.0.37), > librust-toml-0.5+default-dev (>= 0.5.9), librust-which+default-dev (<< 5), > libstring-shellquote-perl, build-essential, fakeroot > Filtered Build-Depends: cmark-gfm, debhelper-compat (= 13), dh-cargo, git, > help2man, librust-anyhow-1+default-dev (>= 1.0.66), librust-clap-3+cargo-dev, > librust-clap-3+default-dev, librust-clap-3+derive-dev, > librust-env-logger-0.9+default-dev, librust-fern+colored-dev (<< 7), > librust-fern+default-dev (<< 7), librust-filetime-0.2+default-dev (>= > 0.2.18), librust-globset-0.4+default-dev (>= 0.4.9), > librust-ignore-0.4+default-dev (>= 0.4.18), librust-indexmap-1+default-dev > (>= 1.9.1), librust-indexmap-1+serde-dev (>= 1.9.1), > librust-itertools+default-dev (<< 0.11), librust-log-0.4+default-dev (>= > 0.4.17), librust-md5-0.7+default-dev, librust-once-cell-1+default-dev (>= > 1.16), librust-pathdiff-0.2+default-dev, > librust-pretty-assertions-1+default-dev (>= 1.3), librust-rayon-1+default-dev > (>= 1.5.3), librust-regex-1+default-dev (>= 1.7), librust-serde-1+default-dev > (>= 1.0.147), librust-serde-1+derive-dev (>= 1.0.147), > librust-serial-test-0.9+default-dev, librust-tempfile-3+default-dev (>= 3.3), > librust-test-case-2+default-dev, librust-thiserror-1+default-dev (>= 1.0.37), > librust-toml-0.5+default-dev (>= 0.5.9), librust-which+default-dev (<< 5), > libstring-shellquote-perl, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [717 B] > Get:5 copy:/<>/apt_archive ./ Packages [788 B] > Fetched 2468 B in 0s (124 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help
Bug#1029594: Fails to authenticate mit o365
Carsten Schoenert wrote on 2/5/23 3:39 AM: > If you need your laptop or your workstation for mission critical > things than Debian unstable/sid isn't the right choice. If you do so > then you will need some knowledge to handle situations like happen > now.I'm not. The broken package has been released to testing already. In an ideal world I would have two separate computers but not everyone has ideal situations. testing release is good for my situation and have now added notifications of important bugs for apt-listbugs config as well, so thank you for mentioning that. However, that's not the default for users. > Debian doesn't have any really resilient statistics as such > statistics bases on completely free choice. Debian doesn't collect > data from users without any confirmation. Then why are you making assumptions on who the majority of users are? Such assertions require evidence, such as statistics. > Most users of Thunderbird are not using M$ products or at least only > using a small set of features of Exchange or Outlook.com. Again, how do you know this? guts or feelings are not valid sources of statistics. >> Further, the actual bug in mozilla is #1814536 (OAuth2 authentication >> | 102.7.1. | Linux - fails) - still Open. This is an even broader >> than just o365 as Google uses OAuth2 as well, etc. That bug was >> reported here in Debian as grave under #1030112 but you closed it as >> a duplicate of this bug. That was perhaps mistaken. > No, it was not. > Having dozen of issues open that are about the same problem is really > not helpful to handle the issue. Okay then, as long as you are certain. > I don't really understand your problem. What is the problem here? I'm just voicing my support for keeping the severity at serious while you keep insisting it should merely be important. > Even right now the the broken package will not migrate to testing. Why do you think that? How do you determine such? Is your system configured correct? It is literally listed in testing on packages.debian.org and available to be upgraded from 102.6. > But it will > also trigger a remove of the version in testing. What do we win? Maybe less bug reports? You seem to like that ;) I'm sure we all do. > My GMail account is working with the current version in testing means > to me that Google doesn't has changed something on their side. > Obviously only MS has changed something. Okay then, that's good. Maybe the report on Mozilla is wrong then, I don't know, I am just putting out there what I've found. > So finally again as written in other answers: If you need to use > Thunderbird in a critical environment you shouldn't use unstable/sid and again as I've said and as you should know, I/we are not, Thunderbird 102.7.1 has already been released to testing. > as long you don't know how to handle the potential breakage of > packages. Debian is providing a stable release for productive use, if > you need newer version of software you can add the backport suite. Most of us should already know that. I too just want to help others not have to spend time fixing things that can be prevented with a good severity label. I have a system with stable, backports, testing, experimental, unstable, and snapshots repos working fine, for now... ;)
Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1
Package: tex-common Version: 6.18 Severity: serious Dear Maintainer, I got this when upgrading texlive today in testing: > Paramétrage de tex-common (6.18) ... > Running mktexlsr. This may take some time... done. > Running mtxrun --generate. This may take some time... done. > Running updmap-sys. This may take some time... done. > Running mktexlsr /var/lib/texmf ... done. > Building format(s) --all. > This may take some time... > fmtutil failed. Output has been stored in > /tmp/fmtutil.RDPxpv93 > Please include this file if you report a bug. > > dpkg: erreur de traitement du paquet tex-common (--configure) : > installed tex-common package post-installation script subprocess returned > error exit status 1 > Des erreurs ont été rencontrées pendant l'exécution : > tex-common Attached is the file, as instructed. Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 Versions of packages tex-common depends on: ii ucf 3.0043 tex-common recommends no packages. Versions of packages tex-common suggests: ii debhelper 13.11.4 Versions of packages texlive-base depends on: ii debconf [debconf-2.0] 1.5.82 ii libpaper-utils 1.1.28+b1 ii sensible-utils 0.0.17+nmu1 ii texlive-binaries 2022.20220321.62855-5 ii ucf3.0043 ii xdg-utils 1.1.3-4.1 Versions of packages texlive-base recommends: ii lmodern 2.005-1 Versions of packages texlive-base suggests: ii evince [postscript-viewer] 43.1-2+b1 ii ghostscript [postscript-viewer] 10.0.0~dfsg-9+b1 ii perl-tk 1:804.036-1+b1 ii xpdf [pdf-viewer]3.04+git20220601-1+b2 pn xzdec Versions of packages texlive-binaries depends on: ii libc6 2.36-8 ii libcairo2 1.16.0-7 ii libfontconfig1 2.14.1-3 ii libfreetype62.12.1+dfsg-4 ii libgcc-s1 12.2.0-14 ii libgraphite2-3 1.3.14-1 ii libharfbuzz0b 6.0.0-1 ii libicu7272.1-3 ii libkpathsea62022.20220321.62855-5 ii libmpfr64.2.0-1 ii libpaper1 1.1.28+b1 ii libpixman-1-0 0.42.2-1 ii libpng16-16 1.6.39-2 ii libptexenc1 2022.20220321.62855-5 ii libstdc++6 12.2.0-14 ii libsynctex2 2022.20220321.62855-5 ii libteckit0 2.5.11+ds1-1+b1 ii libtexlua53-5 2022.20220321.62855-5 ii libtexluajit2 2022.20220321.62855-5 ii libx11-62:1.8.3-3 ii libxaw7 2:1.0.14-1 ii libxi6 2:1.8-1+b1 ii libxmu6 2:1.1.3-3 ii libxpm4 1:3.5.12-1.1 ii libxt6 1:1.2.1-1 ii libzzip-0-130.13.72+dfsg.1-1.1 ii perl5.36.0-7 ii t1utils 1.41-4 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages texlive-binaries recommends: pn dvisvgm ii texlive-base 2022.20221123-1 -- debconf information excluded fmtutil.RDPxpv93.xz Description: application/xz
Bug#1030615: marked as done (opendht: FTBFS on mipsel: /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0')
Your message dated Sun, 05 Feb 2023 19:20:22 + with message-id and subject line Bug#1030615: fixed in opendht 2.4.12-1.2 has caused the Debian Bug report #1030615, regarding opendht: FTBFS on mipsel: /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1030615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opendht Version: 2.4.12-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=opendht&arch=mipsel&ver=2.4.12-1.1&stamp=1675583004&raw=0 [ 91%] Built target perftest [ 94%] Linking CXX executable dhtchat cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtchat.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtchat.dir/dhtchat.cpp.o -o dhtchat ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [ 94%] Built target dhtchat [ 97%] Linking CXX executable dhtnode cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtnode.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtnode.dir/dhtnode.cpp.o -o dhtnode ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0' /usr/bin/ld: /usr/lib/mipsel-linux-gnu/libatomic.so.1: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [tools/CMakeFiles/dhtnode.dir/build.make:113: tools/dhtnode] Error 1 make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:155: tools/CMakeFiles/dhtnode.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [100%] Linking CXX executable durl cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/durl.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/durl.dir/durl.cpp.o -o durl ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [100%] Built target durl make[2]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[1]: *** [Makefile:139: all] Error
Bug#1025985: marked as done (hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra)
Your message dated Sun, 5 Feb 2023 20:28:02 +0100
with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de>
and subject line Closing
has caused the Debian Bug report #1025985,
regarding hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra
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.)
--
1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glosstex
Version: 0.4.dfsg.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
Your package fails to build with:
|Writing index file glosstex.idx
|(/usr/share/texlive/texmf-dist/tex/latex/hypdoc/hypdoc.sty
|(/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty)
|(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
|(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
|(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
|
|! LaTeX Error: File `pdftexcmds.sty' not found.
|
|Type X to quit or to proceed,
|or enter new name. (Default extension: sty)
|
|Enter file name:
|! Emergency stop.
|
|
|l.111 \RequirePackage{pdftexcmds}[2018/09/10]
| ^^M
|No pages of output.
|Transcript written on glosstex.log.
|make[1]: *** [Makefile:83: glosstex.dvi] Error 1
|make[1]: Leaving directory '/<>'
|make: *** [debian/rules:12: install/glosstex] Error 2
|dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess
returned exit status 2
The full build log is available from:
https://buildd.debian.org/status/fetch.php?pkg=glosstex&arch=riscv64&ver=0.4.dfsg.1-4%2Bb1&stamp=1670830203&raw=0
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glosstex_0.4.dfsg.1-4.rbuild.log.gz
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Version: 2022.20230122-1--- End Message ---
Bug#1029460: marked as done (glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found))
Your message dated Sun, 5 Feb 2023 20:28:02 +0100 with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de> and subject line Closing has caused the Debian Bug report #1025985, regarding glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found) 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.) -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:glosstex Version: 0.4.dfsg.1-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules build-arch test -x debian/rules mkdir -p "." /usr/bin/make -C . CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" make[1]: Entering directory '/<>' cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o database.o database.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o error.o error.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o labels.o labels.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o list.o list.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o main.o main.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o version.o version.c cc -Wl,-z,relro database.o error.o labels.o list.o main.o version.o -o glosstex TEXINPUTS=.: latex glosstex.ins This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./glosstex.ins LaTeX2e <2022-06-01> patch level 5 L3 programming layer <2022-08-30> (/usr/share/texlive/texmf-dist/tex/latex/base/docstrip.tex Utility: `docstrip' v2.6a <2020-11-23> English documentation<2020-11-23> ** * This program converts documented macro-files into fast * * loadable files by stripping off (nearly) all comments! * ** * No Configuration file found, using default settings. * (./glosstex.ins Generating file(s) ./glosstex.sty ./glosstex.std ./glosstex.ist ./glosstex.gdf ./glosstex.cfg Processing file glosstex.dtx (package) -> glosstex.sty (std) -> glosstex.std (ist) -> glosstex.ist (gdf) -> glosstex.gdf (cfg) -> glosstex.cfg File glosstex.dtx ended by \endinput. Lines processed: 1768 Comments removed: 1092 Comments passed: 16 Codelines passed: 646 ** * * You will find the documentation in glosstex.dvi. You may remake it * by running latex on glosstex.dtx or invoking `make doc' * * To finish the installation you have to move the following * files (according to TDS): * * glosstex.sty to texmf/tex/latex/glosstex * glosstex.std to texmf/tex/latex/glosstex * glosstex.ist to texmf/makeindex * * and your own .gdf-files to texmf/glosstex. * * The files `glosstex.gdf' and `glosstex.cfg` are meant just for * this document, so you won't want to install them, normally. * * Happy TeXing! ** ) ) ) No pages of output. Transcript written on glosstex.log. make[1]: Leaving directory '/<>' touch debian/stamp-makefile-build CDBS WARNING: DEB_MAKE_CHECK_TARGET unset, not running checks fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_prep dh_installdirs -A dh_installdirs: warning: Compatibility levels before 10 are deprecated (level 9 in use) mkdir -p "." CDBS WARNING: DEB_MAKE_CHECK_TARGET unset, not running checks CDBS WARNING: DEB_MAKE_INSTALL_TARGET unset, skipping default makefile.mk common-inst
Bug#1029438: marked as done (auctex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found))
Your message dated Sun, 5 Feb 2023 20:28:02 +0100 with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de> and subject line Closing has caused the Debian Bug report #1025985, regarding auctex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found) 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.) -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:auctex Version: 12.2-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep /bin/bash: line 1: git: command not found /bin/bash: line 1: git: command not found dh binary-indep --exclude .eperl --with tex dh_update_autotools_config -i -O--exclude=.eperl dh_autoreconf -i -O--exclude=.eperl configure.ac:38: warning: The macro `AC_FD_CC' is obsolete. configure.ac:38: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:26: EMACS_PATH_PREFIX is expanded from... aclocal.m4:36: EMACS_PROG_EMACS is expanded from... configure.ac:38: the top level configure.ac:40: warning: The macro `AC_FD_CC' is obsolete. configure.ac:40: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:100: EMACS_CHECK_VERSION is expanded from... configure.ac:40: the top level configure.ac:44: warning: The macro `AC_FD_CC' is obsolete. configure.ac:44: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:494: VALID_BUILD_DIR is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from... configure.ac:44: the top level configure.ac:44: warning: The macro `AC_FD_CC' is obsolete. configure.ac:44: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:494: VALID_BUILD_DIR is expanded from... lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from... configure.ac:44: the top level configure.ac:60: warning: The macro `AC_FD_CC' is obsolete. configure.ac:60: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:126: EMACS_EXAMINE_INSTALLATION_DIR is expanded from... aclocal.m4:160: EMACS_PATH_LISPDIR is expanded from... configure.ac:60: the top level configure.ac:102: warning: The macro `AC_FD_CC' is obsolete. configure.ac:102: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:102: the top level configure.ac:109: warning: The macro `AC_FD_CC' is obsolete. configure.ac:109: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:109: the top level configure.ac:112: warning: The macro `AC_FD_CC' is obsolete. configure.ac:112: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:112: the top level configure.ac:118: warning: The macro `AC_FD_CC' is obsolete. configure.ac:118: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:118: the top level configure.ac:131: warning: The macro `AC_FD_CC' is obsolete. configure.ac:131: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... configure.ac:131: the top level configure.ac:152: warning: The macro `AC_FD_CC' is obsolete. configure.ac:152: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:26: EMACS_PATH_PREFIX is expanded from... aclocal.m4:185: TEX_PATH_TEXMFDIR is expanded from... configure.ac:152: the
Bug#1029461: marked as done (xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found))
Your message dated Sun, 5 Feb 2023 20:28:02 +0100 with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de> and subject line Closing has caused the Debian Bug report #1025985, regarding xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found) 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.) -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xemacs21-packages Version: 2009.02.17.dfsg.3-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules build-indep chmod +x debian/makevarfile debian/makevarfile "debian/./var_file.pl" \ "MAJVERSION" "21" \ "VERSION" "2009.02.17.dfsg.3" \ "SUBNAME" "" \ "CONF_NAME" "amd64-debian-linux" \ "ARCH" "amd64" \ "HTML_FILE_LOC" "debian/html" \ "TMP_FILE_LOC" "debian/tmp" \ "PREFIX" "usr" \ "TOPDIR" "/<>" [...] Loading /usr/lib/xemacs-21.4.24/lisp/auto-autoloads... Loading /<>/xemacs-packages/edit-utils/auto-autoloads... Loading /<>/xemacs-packages/mail-lib/auto-autoloads... Loading /<>/xemacs-packages/fsf-compat/auto-autoloads... Loading /<>/xemacs-packages/texinfo/auto-autoloads... Loading /<>/xemacs-packages/xemacs-base/auto-autoloads... Compiling /<>/xemacs-packages/auctex/style/frenchb.el... While compiling toplevel forms in file /<>/xemacs-packages/auctex/style/frenchb.el: ** reference to free variable TeX-quote-after-quote ** assignment to free variable TeX-quote-language While compiling the end of the data: ** The following functions are not known to be defined: TeX-add-style-hook, TeX-add-symbols Wrote /<>/xemacs-packages/auctex/style/frenchb.elc Done xemacs21-mule -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list (expand-file-name "mule" lisp-directory) lisp-directory))' -l /<>/package-compile.el -- xemacs-base texinfo fsf-compat mail-lib edit-utils -- -eval '(setq load-path (cons "." (cons "preview" load-path)))' -f batch-byte-compile style/francais.el Loading /usr/lib/xemacs-21.4.24/lisp/auto-autoloads... Loading /<>/xemacs-packages/edit-utils/auto-autoloads... Loading /<>/xemacs-packages/mail-lib/auto-autoloads... Loading /<>/xemacs-packages/fsf-compat/auto-autoloads... Loading /<>/xemacs-packages/texinfo/auto-autoloads... Loading /<>/xemacs-packages/xemacs-base/auto-autoloads... Compiling /<>/xemacs-packages/auctex/style/francais.el... While compiling the end of the data in file /<>/xemacs-packages/auctex/style/francais.el: ** The following functions are not known to be defined: TeX-add-style-hook, TeX-run-style-hooks Wrote /<>/xemacs-packages/auctex/style/francais.elc Done xemacs21-mule -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list (expand-file-name "mule" lisp-directory) lisp-directory))' -l /<>/package-compile.el -- xemacs-base texinfo fsf-compat mail-lib edit-utils -- -eval '(setq load-path (cons "." (cons "preview" load-path)))' -f batch-byte-compile style/MinionPro.el Loading /usr/lib/xemacs-21.4.24/lisp/auto-autoloads... Loading /<>/xemacs-packages/edit-utils/auto-autoloads... Loading /<>/xemacs-packages/mail-lib/auto-autoloads... Loading /<>/xemacs-packages/fsf-compat/auto-autoloads... Loading /<>/xemacs-packages/texinfo/auto-autoloads... Loading /<>/xemacs-packages/xemacs-base/auto-autoloads... Compiling /<>/xemacs-packages/auctex/style/MinionPro.el... While compiling toplevel forms in file /<>/xemacs-packages/auctex/style/MinionPro.el: ** reference to free variable TeX-install-font-lock ** reference to free variable font-latex-match-textual-keywords-local ** assignment to free variable font-latex-match-textual-keywords-local While compiling the end of the data: ** The following functions are not known to be defined: TeX-add-style-hook, TeX-add-symbols, font-latex-match-textual-make, font-latex-match-variable-make Wrote /<>/xemacs-packages/auctex/style/MinionPro.elc Done xemacs21-mule -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list (expand
Bug#1028638: marked as done (libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call)
Your message dated Sun, 05 Feb 2023 19:35:36 + with message-id and subject line Bug#1028638: fixed in libproxy 0.4.18-1.2 has caused the Debian Bug report #1028638, regarding libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call 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.) -- 1028638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gajim Version: 1.6.0-1 Severity: important Gajim 1.6.0-1 crashes while connecting to XMPP server(s). Visually the Gajim window pops up briefly and then disappears again. According to the stack trace below the crash seems related to libproxy.so.1, but I don't have any proxy configured for the account. $ gdb --ex r --args python3 $(command -v gajim) -v [shortened to remove private info, let me know if you need more detail] 01/08/23 11:06:16 (D) gajim.gui.main Window state changed: ICONIFIED: False, WITHDRAWN: False 01/08/23 11:06:16 (I) gajim.c.settings Set settings: app 01/08/23 11:06:16 (I) gajim.c.settings Signal: is_window_visible changed 01/08/23 11:06:16 (D) gajim.c.storage.cache Execution time for _commit: 1 ms 01/08/23 11:06:16 (I) gajim.c.settings Commit 01/08/23 11:06:16 (I) gajim.c.dbus.logindName org.freedesktop.login1 appeared, owned by :1.0 01/08/23 11:06:16 (I) gajim.c.dbus.logindObtained shutdown delay inhibitor 01/08/23 11:06:16 (I) gajim.gui.notification Notifications D-Bus connected 01/08/23 11:06:16 (I) gajim.c.settings Set account settings: *** 01/08/23 11:06:16 (I) gajim.c.settings Signal: last_status changed 01/08/23 11:06:16 (I) gajim.c.settings Set account settings: *** 01/08/23 11:06:16 (I) gajim.c.settings Signal: last_status_msg changed 01/08/23 11:06:16 (I) gajim.client Connect 01/08/23 11:06:16 (I) gajim.client State: 3 01/08/23 11:06:16 (I) gajim.client Signal: state-changed 01/08/23 11:06:16 (I) gajim.gui.css Get .gajim-status-connecting color: rgb(77, 166, 255) 01/08/23 11:06:16 (D) gajim.c.storage.cache Execution time for get_contact: 1 ms 01/08/23 11:06:16 (I) nbxmpp.stream (***) Connect 01/08/23 11:06:16 (I) nbxmpp.stream (***) Set state: StreamState.RESOLVE 01/08/23 11:06:16 (I) nbxmpp.http Request(140734679377472): Created 01/08/23 11:06:16 (I) nbxmpp.http Request(140734679377472): Request sent, method: GET, uri: https://***/.well-known/host-meta [New Thread 0x7fff3fbff6c0 (LWP 8799)] Thread 27 "pool-org.gajim." received signal SIGABRT, Aborted. [Switching to Thread 0x7fff53fff6c0 (LWP 8765)] __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x77d28d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x77cd9ef2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x77cc4472 in __GI_abort () at ./stdlib/abort.c:79 #4 0x73a9d40a in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x73aa861a in __gxx_personality_v0 () at /lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x71c63131 in __libunwind_Unwind_Resume () at /lib/x86_64-linux-gnu/libunwind.so.8 #7 0x7fff51ebd34a in () at /lib/x86_64-linux-gnu/libproxy.so.1 #8 0x7fff51eb3e52 in () at /lib/x86_64-linux-gnu/libproxy.so.1 #9 0x7fff51eb4287 in () at /lib/x86_64-linux-gnu/libproxy.so.1 #10 0x7fff51eb4751 in px_proxy_factory_get_proxies () at /lib/x86_64-linux-gnu/libproxy.so.1 #11 0x7fff51ee761f in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so #12 0x77024793 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x773016da in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x77300d0d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x77d26fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #16 0x77da766c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_
Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1
Am 05.02.2023 um 19:56 teilte Stéphane Glondu mit:
Package: tex-common
Version: 6.18
Severity: serious
Hello,
I got this when upgrading texlive today in testing:
Paramétrage de tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.RDPxpv93
Please include this file if you report a bug.
Today the new texlive-base & texlive-extra did migrate to testing and
hence were upgraded on your system. The texlive-lang did not migrate
yet, this will happen soon. Once texlive-lang-japanese is upgraded,
please repeat the test. Is suspect an incompatibility in these packages,
as I'm not able to reproduce the issue using unstable.
For the records: the error message is:
**
*
* making upLaTeX format
*
**
(/usr/share/texlive/texmf-dist/tex/platex/base/plcore.ltx
! Argument of \platexNILa has an extra }.
\par
l.52 ...ter\expandafter\expandafter{\platexBANNER}
%
?
! Emergency stop.
\par
l.52 ...ter\expandafter\expandafter{\platexBANNER}
%
Hilmar
--
sigfault
Bug#1026962: openjfx: tries to build with -j64 on a host with 2 processors
Source: openjfx Followup-For: Bug #1026962 Could the following build-related scripting be something to do with it? - https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/webkitdirs.pm#L494-499 - https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/build-webkit#L300-305 (perhaps something about the way that numberOfCPUs is being evaluated on s390x hosts isn't matching the expectations of the build script)
Bug#1027965: Fix for the RC bug in vtk
Hi Steven, * Steven Robbins [2023-02-05 10:26]: Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- a build failure in gdcm caused by missing dependency. The fix proposed by Mathieu seems reasonable to me. I assume you mean the proposal to add a libvtk9-qt-dev dependency to libvtk9-dev? Note that libvtk9-dev already has a dependency to libvtk9-qt-dev resulting in a cyclic dependency between both. Those are known to not work well in Debian and should be avoided. The underlying problem here is that the vtk9 cmake files are not separated between libvtk9-dev and libvtk9-qt-dev so the split seems artificial to Debian and both packages should probably be merged into one or the cmake files need rewriting. Cheers Jochen signature.asc Description: PGP signature
Processed: tagging 1019604
Processing commands for cont...@bugs.debian.org: > tags 1019604 + pending Bug #1019604 [src:bsfilter] bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1019604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030480: marked as done (puppetlabs-http-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact compojure:compojure:jar:debian has not been downl
Your message dated Sun, 05 Feb 2023 20:42:40 + with message-id and subject line Bug#1030480: fixed in puppetlabs-http-client-clojure 2.1.0-4 has caused the Debian Bug report #1030480, regarding puppetlabs-http-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact compojure:compojure:jar:debian has not been downloaded from it before. 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.) -- 1030480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetlabs-http-client-clojure Version: 2.1.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > ./dev-resources/gen-pki.sh > > Generating primary self-signed CA > ..++*+...+.+...+*++..++.++...+.+...+.+...+.+..+.+..+++..+..++..+..+..+.+++..+...+...++..+...+.+.++..+...++..+...+...++..++.+.+...+.+...+...+...++.+..+...+...+...++.+.+..+...+..+.+..+..+...+...+..+...+.+.+...+.++.+.+..+..+..+.+.+..+.+..+...+...+..+...+...+...+...+..+...++..+.+...++..+.+.+.+...+...+ > ...+...+.+...++.+*+..+.+..+.+...+..++*..+..+.+...+..+...+..+.+...+..++...++...+..+...+.+..+...+..+.+.+.+.+...+..+...+..+..++.+.+..+..++.+...++.+.+...+..+.+..+...+...+.+...+...+...+...+.+...+...+..+...++...+..+...+..+...+...+.+...+..+.+..+...+..+...+.+..+.++.+.+.+..+...+...+.+..+...+.+...+..++.+.++...+.+..++..++...++..+...+..+...+++...+..+..+.+.+...+...++...+...+...+..+...+...+.+..+..+...+..++...+..++.++...++...++...+ > - > > Generating node cert > > Creating node CSR > > Signing node CSR > Certificate request self-signature ok > subject=C = US, ST = OR, L = Portland, O = "Puppet, Inc", CN = localhost > > Generating alternate self-signed CA > ..+..+..+*...+.+..+...+..+...+...+...+.+.+.+..+++...+..+*.++...+..+.+++.+.+.+..+...+.+...+...+..+.+.+..+.+..+.+..+.+..+...+.+.+.+...+..++..++...+..++.+..+.+..+...+.+.+..+..+..+.+...+...+.+.+.+.+.+..++.+.+.++...+++...++..+...+..+...+.+...+.++...+...+.
Bug#1030488: marked as done (trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact puppetlabs:ring-middleware:jar:debian has
Your message dated Sun, 05 Feb 2023 20:42:40 + with message-id and subject line Bug#1030488: fixed in puppetlabs-http-client-clojure 2.1.0-4 has caused the Debian Bug report #1030488, regarding trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact puppetlabs:ring-middleware:jar:debian has not been downloaded from it before. 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.) -- 1030488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-webserver-jetty9-clojure Version: 4.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not been > downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has > not been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has not > been downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact puppetlabs:ring-middleware:jar:debian has not been downloaded > from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact puppetlabs:ring-middleware:jar:debian has not been downloaded from > it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/03/trapperkeeper-webserver-jetty9-clojure_4.4.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: puppetlabs-http-client-clojure Source-Version: 2.1.0-4 Done: Jérôme Charaoui We believe that the bug you reported is fixed in the latest version of puppetlabs-http-client-clojure, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérôme Charaoui (supplier of updated puppetlabs-http-client-clojure 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: Sun, 05 Feb 2023 14:15:56 -0500 Source: puppetlabs-http-client-clojure Architecture: source Version: 2.1.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Jérôme Charaoui Closes: 1030480 1030488 Changes: puppetlabs-http-client-clojure (2.1.0-4) unstable; urgency=medium . * d/rules: build without tests temporarily (Closes: #1030480, #1030488) * d/control:
Bug#1028163: sshfs-fuse bug
There are a couple of odd things about this bug. First: it doesn't seem like an RC bug because the test manifestly runs fine on buildds -- see https://buildd.debian.org/status/package.php?p=sshfs-fuse I'd suggest to downgrade the bug on this basis. Second: the bug log shows python 3.9.2 is used. That hasn't been the default python since 2021 -- so it's an unusual test environment. -Steve signature.asc Description: This is a digitally signed message part.
Bug#1030510: mariadb: FTBFS on s390x: timeout
After restarting the build there is no longer a timeout, but a crash: main.plugin_auth 'innodb'w1 [ fail ] Found warnings/errors in server log file! Test ended at 2023-02-05 09:41:56 line Attempting backtrace. You can use the following information to find out ^ Found warnings in /<>/builddir/mysql-test/var/1/log/mysqld.1.err ok - found 'core' (0/5) Core generated by '/<>/builddir/sql/mariadbd' Output from gdb follows. The first stack trace is from the failing thread. The following stack traces are from all threads (so the failing one is duplicated). -- [New LWP 460078] [New LWP 460124] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1". Core was generated by `/<>/builddir/sql/mariadbd --defaults-group-su'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x03ff99c48992 in kill () from /lib/s390x-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x3ff9ab6a820 (LWP 460078))] #0 0x03ff99c48992 in kill () from /lib/s390x-linux-gnu/libc.so.6 #1 0x02aa226907c4 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:367 #2 #3 0x02aa22b7c26a in my_read (Filedes=, Buffer=0x3ff9ab6a820 "", Count=4096, MyFlags=) at ./mysys/my_read.c:63 #4 0x02aa22690266 in output_core_info () at ./sql/signal_handler.cc:90 #5 0x02aa22690792 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:351 #6 #7 0x03ff99d0e632 in munmap () from /lib/s390x-linux-gnu/libc.so.6 #8 0x03ff99ca7790 in free () from /lib/s390x-linux-gnu/libc.so.6 #9 0x02aa228bfe6e in aligned_free (ptr=) at ./include/aligned.h:37 #10 pfs_free (ptr=, size=2048000, klass=0x2aa23e47900 ) at ./storage/perfschema/pfs_global.cc:83 #11 pfs_free (klass=0x2aa23e47900 , size=size@entry=2048000, ptr=) at ./storage/perfschema/pfs_global.cc:78 #12 0x02aa228b5fe6 in PFS_thread_allocator::free_array (this=, array=array@entry=0x2aa24cf4d30) at ./storage/perfschema/pfs_buffer_container.cc:715 #13 0x02aa228c25da in PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:506 #14 PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:491 #15 cleanup_instruments () at ./storage/perfschema/pfs_instr.cc:233 #16 0x02aa228d000c in cleanup_performance_schema () at ./storage/perfschema/pfs_server.cc:296 #17 0x02aa228d04f0 in shutdown_performance_schema () at ./storage/perfschema/pfs_server.cc:326 #18 0x02aa2233f912 in mysqld_exit (exit_code=exit_code@entry=0) at ./sql/mysqld.cc:1943 #19 0x02aa2234a4fe in mysqld_main (argc=, argv=) at ./sql/mysqld.cc:6040 #20 0x03ff99c2b84a in ?? () from /lib/s390x-linux-gnu/libc.so.6 #21 0x03ff99c2b932 in __libc_start_main () from /lib/s390x-linux-gnu/libc.so.6 #22 0x02aa2233d378 in _start () A previous restart also had: main.mysql_upgrade 'innodb' w1 [ fail ] Found warnings/errors in server log file! [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1". Core was generated by `/<>/builddir/sql/mariadbd --defaults-group-su'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x03ffaa0c8992 in kill () from /lib/s390x-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x3ffaafea820 (LWP 1668996))] #0 0x03ffaa0c8992 in kill () from /lib/s390x-linux-gnu/libc.so.6 #1 0x02aa26c107c4 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:367 #2 #3 0x02aa270fc26a in my_read (Filedes=, Buffer=0x696c646469722f6d , Count=4096, MyFlags=) at ./mysys/my_read.c:63 #4 0x02aa26c10266 in output_core_info () at ./sql/signal_handler.cc:90 #5 0x02aa26c10792 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:351 #6 #7 0x03ffaa18e632 in munmap () from /lib/s390x-linux-gnu/libc.so.6 #8 0x03ffaa127790 in free () from /lib/s390x-linux-gnu/libc.so.6 #9 0x02aa26e40022 in aligned_free (ptr=) at ./include/aligned.h:37 #10 pfs_free (ptr=, size=2304000, klass=0x2aa283c8f00 ) at ./storage/perfschema/pfs_global.cc:83 #11 pfs_free (ptr=, size=2304000, klass=0x2aa283c8f00 ) at ./storage/perfschema/pfs_global.cc:78 #12 pfs_free_array (klass=0x2aa283c8f00 , n=n@entry=32000, size=size@entry=72, ptr=) at ./storage/perfschema/pfs_global.cc:134 #13 0x02aa26e36680 in PFS_user_allocator::free_array (this=, array=array@entry=0x2aa297ac0a0) at ./storage/perfschema/pfs_buffer_container.cc:875 #14 0x02aa26e53786 in PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:506 #15 PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:491 #16 cleanup_user () at ./storage/perfschema/pfs_user.cc:63 #17 0x02aa26e4ffb8 in cleanup_performance_schema () at ./storage/perfschema/pfs_server.cc:275 #18 0x02aa26e504f0 in shutdown_performance_schema () at ./storage/perfschema/pfs_server.cc:3
Bug#1030574: marked as done (debian-edu-router-config: Missing dependency on procps)
Your message dated Sun, 05 Feb 2023 21:04:26 + with message-id and subject line Bug#1030574: fixed in debian-edu-router 2.12.3 has caused the Debian Bug report #1030574, regarding debian-edu-router-config: Missing dependency on procps 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.) -- 1030574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-edu-router-config Version: 2.12.2 Severity: serious https://piuparts.debian.org/sid/fail/debian-edu-router-config_2.12.2.log ... /var/lib/dpkg/info/debian-edu-router-config.postinst: line 1485: sysctl: command not found dpkg: error processing package debian-edu-router-config (--configure): installed debian-edu-router-config package post-installation script subprocess returned error exit status 127 Processing triggers for libc-bin (2.36-8) ... Errors were encountered while processing: debian-edu-router-config E: Sub-process /usr/bin/dpkg returned an error code (1) --- End Message --- --- Begin Message --- Source: debian-edu-router Source-Version: 2.12.3 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of debian-edu-router, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated debian-edu-router 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: Sun, 05 Feb 2023 21:28:34 +0100 Source: debian-edu-router Architecture: source Version: 2.12.3 Distribution: unstable Urgency: medium Maintainer: Debian Edu Developers Changed-By: Mike Gabriel Closes: 1030574 Changes: debian-edu-router (2.12.3) unstable; urgency=medium . * debian/control: Add to D (d-e-r-c): procps (provides sysctl cmd). (Closes: #1030574). Checksums-Sha1: e5f8760b5617ee52fe6592ffa646114041278a4d 1920 debian-edu-router_2.12.3.dsc 8e3d18bfba6022dd9310d3274196bb55a01d7bed 101964 debian-edu-router_2.12.3.tar.xz c5ab466dbcdae25bef3929511f902fe0fbc23040 6308 debian-edu-router_2.12.3_source.buildinfo Checksums-Sha256: ffc408a385d80903a2ecd90faa307957c6f62c590e9ae93220a17bc0c7e4bcea 1920 debian-edu-router_2.12.3.dsc aed2315105e97a80ad021933f71dfcd784243905f5635be8364c7f2003b4c792 101964 debian-edu-router_2.12.3.tar.xz f049074a0a50cb779626ae313017270ee9e96a2dd0f6e0fbfdf4a9348007d95c 6308 debian-edu-router_2.12.3_source.buildinfo Files: fc95132c067af9db6ba0f950803dc903 1920 admin optional debian-edu-router_2.12.3.dsc c3e9b18a7df0b637550b8826d54c751c 101964 admin optional debian-edu-router_2.12.3.tar.xz bf2a5820c99283309d6ee2263ba8c4d4 6308 admin optional debian-edu-router_2.12.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmPgEf8VHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxE0cQALZDTQHMOc35qeKXDap9DSEUiXyy IY5lR52vMV78/yVBk7QBeX1Pnm51N0xKCH5b5+10WvAvZgIdYhOWQk631AwyfnGP M/OWb+FlF9SZgdib5OTsdtXEeaNqQRIYvngb6qL/CWUbrcC1mjjqSFWPnXFouzdk yQoaE7Yw7i9k1wjQYy6zvZbM2/t2FJn5jFNMTSXcIbfVU3Lb4fbiO/KiTe0LfmLM lJowV93YBRMA2u+UE5+ffxPxU2GiaV4V6nYNlelQbcYXowFdOfzNbrTXaz2LNpzH mMA0+6zWziC1fvDaBssJRvXE9oy71Zj+XVrFqBzfFLa5RHi6hzLDca2Q1Rk4jtZY ZcWzl33+49KSFejApX8wULWUykBmeDFuenH7V/z2imcsU0t0ELwoyVIkWJPiR4tq jM89hllCob/+CGU8iRBHrGvocv/Ybc+13vmoYdN74Vq06hw4O23+oCYNEhBa2sfJ fVk6hdlyrCRI4YiBifwMV1XVqwiGfpAGEj4AUhB3zKaDmyY0FF24VdgMii5RpeKA duK3Xu5uAkuQkVOg75krlxHZPAfR+BcoE+hXpqpjVTiMszbtVPpWbvl33CV3GgQv 4NHwnGRS7Rss1JhOJaCkpwCuGwvk6UKzZJWCcFBQMPAHZ4ghlrA8DwseKXi5N31h tR3mWSJ0V19xHnd7 =YGLN -END PGP SIGNATURE End Message ---
Bug#1030487: python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
clone 1030487 -1 reassign -1 python3-service-identity 18.1.0-7 retitle -1 Missing dependency on python3-six makes package unusable thanks On Sat, Feb 04, 2023 at 08:58:30AM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > ImportError while importing test module > > '/<>/.pybuild/cpython3_3.11/build/tests/test_trustme.py'. > > Hint: make sure your test modules/packages have valid Python names. > > Traceback: > > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > > return _bootstrap._gcd_import(name[level:], package, level) > > tests/test_trustme.py:21: in > > import service_identity.pyopenssl # type: ignore[import] > > /usr/lib/python3/dist-packages/service_identity/__init__.py:7: in > > from . import cryptography, pyopenssl > > /usr/lib/python3/dist-packages/service_identity/pyopenssl.py:9: in > > import six > > E ModuleNotFoundError: No module named 'six' Looks like python3-service-identity should have a dependency on python3-six but it does not. Steps to reproduce: apt install python3-service-identity python3 >>> from service_identity.pyopenssl import verify_hostname ... ModuleNotFoundError: No module named 'six' This is expected to work as documented at https://service-identity.readthedocs.io/en/stable/api.html I will send a fix for this to Salsa shortly. Robie signature.asc Description: PGP signature
Processed: Re: Bug#1030487: python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Processing commands for cont...@bugs.debian.org:
> clone 1030487 -1
Bug #1030487 [src:python-trustme] python-trustme: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Bug 1030487 cloned as bug 1030628
> reassign -1 python3-service-identity 18.1.0-7
Bug #1030628 [src:python-trustme] python-trustme: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Bug reassigned from package 'src:python-trustme' to 'python3-service-identity'.
No longer marked as found in versions python-trustme/0.9.0-1.1.
Ignoring request to alter fixed versions of bug #1030628 to the same values
previously set
Bug #1030628 [python3-service-identity] python-trustme: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit
code 13
Marked as found in versions python-service-identity/18.1.0-7.
> retitle -1 Missing dependency on python3-six makes package unusable
Bug #1030628 [python3-service-identity] python-trustme: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit
code 13
Changed Bug title to 'Missing dependency on python3-six makes package unusable'
from 'python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.11 returned exit code 13'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1030487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030487
1030628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: RFS: libquazip1-qt5/1.4-1 [RC] -- Qt/C++ wrapper over minizip - Version 1 (Qt5)
Processing control commands: > block 1028641 by -1 Bug #1028641 [libquazip1-qt5-dev] libquazip1-qt5-dev: Missing dependencies on "qtbase5-dev, zlib1g-dev" 1028641 was not blocked by any bugs. 1028641 was not blocking any bugs. Added blocking bug(s) of 1028641: 1030629 -- 1028641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028641 1030629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030096: #1030096 dask.distributed autopkgtest fail
I currently have this in a state where it sometimes succeeds and sometimes doesn't: https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/tree/fix1030096 Tests I've seen to fail multiple times (and don't have a fix for): test_balance_expensive_tasks[enough work to steal] https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902376 (Seems to be the most common problem. Using @pytest.mark.flaky to try 3 times doesn't seem to have helped, suggesting that if it fails once it keeps failing in that run. Applying part of upstream pull 7253 seemed to make things worse, but I haven't tried applying the whole thing.) test_popen_timeout https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902745 Tests I've seen to fail once: test_stress_scatter_death https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902040 test_tcp_many_listeners[asyncio] https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3896327
Bug#1028163: sshfs-fuse bug
El 5/2/23 a las 21:54, Steven Robbins escribió: There are a couple of odd things about this bug. First: it doesn't seem like an RC bug because the test manifestly runs fine on buildds -- see https://buildd.debian.org/status/package.php?p=sshfs-fuse The package is trying to access the network. This is considered RC even if it works in the official buildds. Second: the bug log shows python 3.9.2 is used. That hasn't been the default python since 2021 -- so it's an unusual test environment. Maybe I was reporting the failure in bullseye (because packages in stable must build in stable). Here is a recent build log from January in bookworm. Thanks. sshfs-fuse_3.7.3-1_amd64-20230112T160950.844Z.gz Description: application/gzip
