Bug#1034688: marked as done (onionshare: flaky autopkgtest)
Your message dated Tue, 02 May 2023 20:49:58 + with message-id and subject line Bug#1034688: fixed in onionshare 2.6-2 has caused the Debian Bug report #1034688, regarding onionshare: flaky autopkgtest 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.) -- 1034688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: onionshare Version: 2.6-1 Severity: serious The autopkgtests from onionshare are flaky and have been failing roughly half the time over the last couple of weeks. https://ci.debian.net/data/autopkgtest/testing/amd64/o/onionshare/32901091/log.gz Give this address and private key to the recipient: http://127.0.0.1:17632 Private key: E2GOT5LTUTP3OAMRCRXO4GSH6VKJEUOXZQUC336SRKAHTTT5OVSA Press Ctrl+C to stop the server Stopped because auto-stop timer ran out Segmentation fault autopkgtest [22:20:10]: test chat_server: ---] autopkgtest [22:20:10]: test chat_server: - - - - - - - - - - results - - - - - - - - - - chat_server FAIL non-zero exit status 139 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: onionshare Source-Version: 2.6-2 Done: Sandro Knauß We believe that the bug you reported is fixed in the latest version of onionshare, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Knauß (supplier of updated onionshare 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: Tue, 02 May 2023 22:27:57 +0200 Source: onionshare Binary: onionshare onionshare-cli Architecture: source all Version: 2.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Sandro Knauß Description: onionshare - Share a file over Tor Hidden Services anonymously and securely onionshare-cli - Share a file over Tor Hidden Services anonymously and securely - Closes: 1034688 Changes: onionshare (2.6-2) unstable; urgency=medium . * The verbose flag makes the chat test not flaky. (Closes: #1034688) Checksums-Sha1: 14b34c6706d7c85c72c6237a9937b2c767b77177 2759 onionshare_2.6-2.dsc 4950d6a3efe79e7a7404714c83adbba50ee0d503 111320 onionshare_2.6-2.debian.tar.xz ea88853e1316f01ddc0fec4f9eddca7a34f71b3e 150760 onionshare-cli_2.6-2_all.deb 52e3ebf477d9963e3e17585e94d3f63a3b457a79 1077512 onionshare_2.6-2_all.deb 9dc71dab6e7331f9ea28ff24dda4ccf4d4d02295 14861 onionshare_2.6-2_amd64.buildinfo Checksums-Sha256: ebae69bbca2fadc8b1ecb4e4f1ebe7ba1e5eeaddc6d2a41fa90017b00eddda1b 2759 onionshare_2.6-2.dsc b56920512ae23f1a1b5b01d72d3e1848d788d3d2098c4429fb5e8eb0361e4b06 111320 onionshare_2.6-2.debian.tar.xz 977c9170e3ca3af7b883515c4f6ad33ccd98a4c6b62f8fda1a260c973658053f 150760 onionshare-cli_2.6-2_all.deb 67941705c3f9c5d397829e2e23d4746991e29a8192b32aeabbb3e86508e7d7d0 1077512 onionshare_2.6-2_all.deb bc047a587efc54345759047a99d9195dab471be8c40e300d461f5bf54796031d 14861 onionshare_2.6-2_amd64.buildinfo Files: 9e60ea1588083deebce58cce4d2216ab 2759 net optional onionshare_2.6-2.dsc ac5cf0a427f4fe47e2238f2b7e281aeb 111320 net optional onionshare_2.6-2.debian.tar.xz 70d841d8c59bb384c84384ef160dc3d7 150760 net optional onionshare-cli_2.6-2_all.deb 8933dd266cb708650bd4222b4501cd81 1077512 net optional onionshare_2.6-2_all.deb 6079d42dd53dd1d17c55232b3a326f13 14861 net optional onionshare_2.6-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmRRc+gRHGhlZmVlQGRl Ymlhbi5vcmcACgkQ462wCFBgVjb7CRAAp4am8obDJ3YECH3OoQJAZ2wWWMkoOpqF 0CkCwGXXamwetyiaro69bPgNRvMD8QHPtAMDXUESofKG5EkxRKPRuc6yoFqUkFLp q0L/5QetqphF2V2DPsmyuoTHHMsVfqXVvy8UE8jncqgIuGKZNLA1cdDSI7tjc/w8 tGPhKR1WFfDSDZMo1VTHbAm9W01DDea5f6vUBX72xAa0hEPikc9wT3KwdZlU5OGN BZo8X8npRtkPdP2XcnYU6Ln9LkaCAq25CV7GCUkPupwlCeGTwjpt6+sKzAzxpcQc D4AKtUu94j1szlKep9Q3LOH8WZWgf8NS2IwzCOSqLt6IoncUP0hZ3ZPpfg74OUcj vujGaFdRApLBBGIcwFrXmkFMtvPyKfeZQLPkklG5UUEDu7qhwsu6/asJn7pLXgAy 6rrQsdUGqss16gKWvahQ/IIQZUVFeFZY+IyIuakNj0mw4aiuS8uaTWZUX4Uq22fY T2mpKpM5kisdeVUL+4fvLVutGiWQdvtVq0j7cQhOznO5ihVpfDhesPjNJY0EFfv1
Bug#1024021: marked as done (netatalk: CVE-2022-45188)
Your message dated Tue, 02 May 2023 19:03:55 + with message-id and subject line Bug#1024021: fixed in netatalk 3.1.15~ds-1 has caused the Debian Bug report #1024021, regarding netatalk: CVE-2022-45188 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.) -- 1024021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netatalk X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for netatalk. CVE-2022-45188[0]: | Netatalk through 3.1.13 has an afp_getappl heap-based buffer overflow | resulting in code execution via a crafted .appl file. This provides | remote root access on some platforms such as FreeBSD (used for | TrueNAS). https://rushbnt.github.io/bug%20analysis/netatalk-0day/ If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-45188 https://www.cve.org/CVERecord?id=CVE-2022-45188 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: netatalk Source-Version: 3.1.15~ds-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of netatalk, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated netatalk 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: Tue, 02 May 2023 20:13:06 +0200 Source: netatalk Architecture: source Version: 3.1.15~ds-1 Distribution: unstable Urgency: high Maintainer: Debian Netatalk team Changed-By: Jonas Smedegaard Closes: 1013308 1024021 1025011 Changes: netatalk (3.1.15~ds-1) unstable; urgency=high . [ upstream ] * new release + fixes CVE-2022-45188 CVE-2022-45188; closes: bug#1024021, thanks to Moritz Mühlenhoff . [ Jonas Smedegaard ] * adopt package, thanks to renewed interest in the Netatalk team; add Daniel Markstedt as uploader; closes: bug#1013308; closes: bug#1025011, thanks to Moritz Mühlenhoff * drop patches obsoleted by upstream changes * unfuzz patches * update copyright info: update coverage * generate documentation from Markdown source; build-depend on cmark-gfm * add patch 202 to avoid privacy leak in documentation * set urgency=high due to fixing CVE issue Checksums-Sha1: 321a6569d19b21f5a54ba67e8d224835fc57f874 2464 netatalk_3.1.15~ds-1.dsc 8e7422000e568e8866a26866d7dc4c32b23f4ffc 866396 netatalk_3.1.15~ds.orig.tar.xz 055565a84326f0c1f900beb1fa45081a97084a9f 42228 netatalk_3.1.15~ds-1.debian.tar.xz a4c7e891e7ddd900f02e69c06364a9bcf58d1d26 16885 netatalk_3.1.15~ds-1_amd64.buildinfo Checksums-Sha256: f0a6b1c6111e302310d9c4698bcdcb1ee2c74ef40854062ec929b67d9b3143f3 2464 netatalk_3.1.15~ds-1.dsc d1241bc697e9648b889440011996a9a6fd455e4556b9325bf8276634901fff95 866396 netatalk_3.1.15~ds.orig.tar.xz 304fcb215120fe452df054519b00e264c670035dd25327ca5e5af146a70d4cfa 42228 netatalk_3.1.15~ds-1.debian.tar.xz 6e8681a43808cba9b82df8216f8b1d9030724d9e2da0408e29ec89cc2d8912b3 16885 netatalk_3.1.15~ds-1_amd64.buildinfo Files: 0e2a37e8079c791d964691075bb8ddb8 2464 net optional netatalk_3.1.15~ds-1.dsc 62dbf3b08744d90291f8757087824a15 866396 net optional netatalk_3.1.15~ds.orig.tar.xz 60b560cbe449450b8e25cd2a95a36e0c 42228 net optional netatalk_3.1.15~ds-1.debian.tar.xz f24a3d74aabc19e501dcacdcf1fcffc6 16885 net optional netatalk_3.1.15~ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmRRWc4ACgkQLHwxRsGg ASElXhAAl+i7SbVObwb+U6X3WR+ZR/OxoN1TyabAm79G/gtqnAbxrj7aOq5UnkNu 30vEosk+bkSj9p43tLmd9L2sUPm1TYZwPmrhzlqfpQ5UK8ilbDAzofsvPuTlwMOx 6fYX1vheMeEAmM2rYElio5YtRy8m5KRKSdaNDoNrn4TeIe2GghhA+JrZ3uv6Rwim X7RzDxWrftij5Q9rUYHXGu3DC74MXnlv3qP4ql95b4UEfUWMA3b8Saps4S7qnnRW zI/RK0UZxkKgqm+3AyS3OcsLl2JBROScVR64ebaDrgRkmcmu5bM0iowLG/B3FWUm
Bug#1025011: marked as done (Keep out of bookworm unless actively maintained)
Your message dated Tue, 02 May 2023 19:03:55 + with message-id and subject line Bug#1025011: fixed in netatalk 3.1.15~ds-1 has caused the Debian Bug report #1025011, regarding Keep out of bookworm unless actively maintained 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.) -- 1025011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netatalk Version: 3.1.13~ds-2 Severity: serious netatalk should not enter bookworm unless it gets adopted and actively maintained. Cheers, Moritz --- End Message --- --- Begin Message --- Source: netatalk Source-Version: 3.1.15~ds-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of netatalk, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated netatalk 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: Tue, 02 May 2023 20:13:06 +0200 Source: netatalk Architecture: source Version: 3.1.15~ds-1 Distribution: unstable Urgency: high Maintainer: Debian Netatalk team Changed-By: Jonas Smedegaard Closes: 1013308 1024021 1025011 Changes: netatalk (3.1.15~ds-1) unstable; urgency=high . [ upstream ] * new release + fixes CVE-2022-45188 CVE-2022-45188; closes: bug#1024021, thanks to Moritz Mühlenhoff . [ Jonas Smedegaard ] * adopt package, thanks to renewed interest in the Netatalk team; add Daniel Markstedt as uploader; closes: bug#1013308; closes: bug#1025011, thanks to Moritz Mühlenhoff * drop patches obsoleted by upstream changes * unfuzz patches * update copyright info: update coverage * generate documentation from Markdown source; build-depend on cmark-gfm * add patch 202 to avoid privacy leak in documentation * set urgency=high due to fixing CVE issue Checksums-Sha1: 321a6569d19b21f5a54ba67e8d224835fc57f874 2464 netatalk_3.1.15~ds-1.dsc 8e7422000e568e8866a26866d7dc4c32b23f4ffc 866396 netatalk_3.1.15~ds.orig.tar.xz 055565a84326f0c1f900beb1fa45081a97084a9f 42228 netatalk_3.1.15~ds-1.debian.tar.xz a4c7e891e7ddd900f02e69c06364a9bcf58d1d26 16885 netatalk_3.1.15~ds-1_amd64.buildinfo Checksums-Sha256: f0a6b1c6111e302310d9c4698bcdcb1ee2c74ef40854062ec929b67d9b3143f3 2464 netatalk_3.1.15~ds-1.dsc d1241bc697e9648b889440011996a9a6fd455e4556b9325bf8276634901fff95 866396 netatalk_3.1.15~ds.orig.tar.xz 304fcb215120fe452df054519b00e264c670035dd25327ca5e5af146a70d4cfa 42228 netatalk_3.1.15~ds-1.debian.tar.xz 6e8681a43808cba9b82df8216f8b1d9030724d9e2da0408e29ec89cc2d8912b3 16885 netatalk_3.1.15~ds-1_amd64.buildinfo Files: 0e2a37e8079c791d964691075bb8ddb8 2464 net optional netatalk_3.1.15~ds-1.dsc 62dbf3b08744d90291f8757087824a15 866396 net optional netatalk_3.1.15~ds.orig.tar.xz 60b560cbe449450b8e25cd2a95a36e0c 42228 net optional netatalk_3.1.15~ds-1.debian.tar.xz f24a3d74aabc19e501dcacdcf1fcffc6 16885 net optional netatalk_3.1.15~ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmRRWc4ACgkQLHwxRsGg ASElXhAAl+i7SbVObwb+U6X3WR+ZR/OxoN1TyabAm79G/gtqnAbxrj7aOq5UnkNu 30vEosk+bkSj9p43tLmd9L2sUPm1TYZwPmrhzlqfpQ5UK8ilbDAzofsvPuTlwMOx 6fYX1vheMeEAmM2rYElio5YtRy8m5KRKSdaNDoNrn4TeIe2GghhA+JrZ3uv6Rwim X7RzDxWrftij5Q9rUYHXGu3DC74MXnlv3qP4ql95b4UEfUWMA3b8Saps4S7qnnRW zI/RK0UZxkKgqm+3AyS3OcsLl2JBROScVR64ebaDrgRkmcmu5bM0iowLG/B3FWUm EwB/td241x3ZZxtfDbNz4vM95gK/1D/rpwfG4hinFbgamFo8rwBCs4hBvo3SmHvG QqLPfxm5s/tVw0I+RJUdfhVV8tSbBhAcVLI5FhXz+gKg9cvSI8r5K2sC8NxnC01c FeAI5vx6DP+B97/RBMXqeuCOrz62ny/rYrs7ULQ3k9pGPc/EqNpwV2ctRsb+HbY0 +4fZ+GnQH/TsrW5Q1wiuj8GV8QuByXA7coHsf+pgq7is0swbSEHbYjmk87o2NcXc 4d1c26UPynmpSz9Vz5IRM6Pop3uKwazUzZaPxYo0ZJrh9ZHUDT3WfkEPDVtCs3z5 6pupLivX0EvJizxJEFUmJJUYBWnH0CtH7HfYpLsgDponZvT2t/E= =cnbo -END PGP SIGNATURE End Message ---
Bug#1035284: marked as done (znc: missing Depends: adduser)
Your message dated Tue, 02 May 2023 18:19:27 + with message-id and subject line Bug#1035284: fixed in znc 1.8.2-3.1 has caused the Debian Bug report #1035284, regarding znc: missing Depends: adduser 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.) -- 1035284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: znc Version: 1.8.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up znc (1.8.2-3+b4) ... /var/lib/dpkg/info/znc.postinst: 7: addgroup: not found dpkg: error processing package znc (--configure): installed znc package post-installation script subprocess returned error exit status 127 Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: znc cheers, Andreas znc_1.8.2-3+b4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: znc Source-Version: 1.8.2-3.1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of znc, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated znc 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, 02 May 2023 19:54:58 +0200 Source: znc Architecture: source Version: 1.8.2-3.1 Distribution: unstable Urgency: medium Maintainer: Patrick Matthäi Changed-By: Andreas Beckmann Closes: 1035284 Changes: znc (1.8.2-3.1) unstable; urgency=medium . * Non-maintainer upload with maintainer approval. * znc: Add dependency on adduser. (Closes: #1035284) Checksums-Sha1: 472b6b6ebe207313eb8d523377e2fd854cda389d 2455 znc_1.8.2-3.1.dsc fb0b45a38f62a81ee3d1cf47497dc15ee4a0420a 511492 znc_1.8.2-3.1.debian.tar.xz 4ef39f9930f29822cfe55450d526510199fb981a 13202 znc_1.8.2-3.1_source.buildinfo Checksums-Sha256: dd054e615bb2181d08a915756fbf5cecb57f0a01693c9f9a88e48dfb2f2a690d 2455 znc_1.8.2-3.1.dsc 58222e17e144863353aa60d45b7b05405deb9a187815b7851ef8bb3112012e4d 511492 znc_1.8.2-3.1.debian.tar.xz b47e8df977122d94c270b4f564abc44b353057152d1316a3d7975d4c76af3450 13202 znc_1.8.2-3.1_source.buildinfo Files: f3b4dd539febf013f986b93bf696eb9d 2455 net optional znc_1.8.2-3.1.dsc 2ef6ca342895cdc295356a34a24acf20 511492 net optional znc_1.8.2-3.1.debian.tar.xz bc7ac8eccde7cd24cd39ebc3d5352635 13202 net optional znc_1.8.2-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmRRT8oQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCL7bD/0ZXjDt6GSy3sI6Jj+UyLE2d5YJWHLlddN9 o0xSvd+DgsecQ31QxbMXTVtdXfmU7c5AQ16oGWa+Sd4XpQ54Kuf/g84CGCL8w0Ag 60nLDvfTo3UdR+8S1vMz+Q3mkRu3BVH+p5DjQN1o1hPKgILa6JyfUfI4CDkYPzjI 09Cl08N63DetmkzdFY3TTt34lhUORyi5CUTejKZE3OCiZegOzz2gZlmc9KvROJxV V0r+uVmIvPiGPm3nuP7nhPkbHqjX0kaRgU74u0AUSnZvve8UvQgiB4DvFoI9mqCh O/bppsLhgWcfZMpAGumVfwwrTRmvoPW1ucjXPpXd582BmzFom3J1fbbmDZmet1ug U7NtnHvf/joVa6TzIJmWgbGDsKFUvmm2bKaBj1ZkrkGkjfCXRQ7jyFo4CJ6xl4pa 0zekU4Y3stdoZbkLqLpGAKoOqbIuu/O5ej7K5jlf1RizooDYqh/RWTiyNJVgcx9d 2BxqECKg7q5eBduQRO1CYkVqviT8GQBUc5MMioirHKoA65dw9DV25tM17nf1E2pa NzBK+vbPBvech2MWJVC5q+yOWFG0SmWT1H95QcTSf/xv1JEVK/MouLxUnEnP3b19 qnqsTyseui+cbe/zu+z7Oy7VdfCL30Kh163PDuLIl4PUtUQEY5FazcUtKFPiUydg s9nteaEZkw== =88EE -END PGP SIGNATURE End Message ---
Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
Andreas Beckmann writes ("Re: Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
> [trying] it manually by installing logrotate and sauce in a chroot
> (without removing sauce again):
Ah!
Thanks for investigating. I think that I ought to fix the
permissions of the logrotate.d and the chown syntax.
I will do some more tests to check about whether that's sufficient or
whether "missingok" is needed too.
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Processed: Re: Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
Processing control commands: > clone -1 -2 Bug #1035361 [sauce] sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755 Bug 1035361 cloned as bug 1035396 > retitle -2 ancient chown syntax Bug #1035396 [sauce] sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755 Changed Bug title to 'ancient chown syntax' from 'sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755'. > severity -2 serious Bug #1035396 [sauce] ancient chown syntax Ignoring request to change severity of Bug 1035396 to the same value. -- 1035361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035361 1035396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
Control: clone -1 -2
Control: retitle -2 ancient chown syntax
Control: severity -2 serious
Andreas Beckmann writes ("Re: Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
> Setting up sauce (0.9.1) ...
> Checking for SAUCE databases in /var/lib/sauce ...
> cdb.site-annoy (no existing data) donechown: warning: '.' should be
> ':': 'mail.mail'
> chown: warning: '.' should be ':': 'mail.mail'
> chown: warning: '.' should be ':': 'mail.mail'
> chown: warning: '.' should be ':': 'mail.mail'
etc.
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)
On Sat, Apr 29, 2023 at 07:44:24PM +0530, Nilesh Patra wrote: > On Tue, Apr 18, 2023 at 03:54:23PM +0200, Andreas Tille wrote: > >2. Remove the package from testing for the moment. The only > > rdepends is currently pan-grazing-incidence which will be > > lowered to suggests once we re-render debian-pan metapackages. > > It is a possible option but it maybe a useful package in itself. > This numba situation has arised due to uploading a new upstream update > of genx during hard freeze (I wonder why this happened). I guess I understand the reason for this: > I think we do have a third alternative: > > > What do you think? > > 3. Cherry-pick the commit[6] for fixing this bug and upload to t-p-u by > asking release team first, or go ahead with a +really scheme whichever > seems better, but it needs to be done quickly. I guess I ended up under-estimating the fix. Even after applying heaps of patches, genx is rendering broken for me, in the sense that the GUI is up but I am observing some concerning warnings/errors in the logs, which means that I need to pick more and more commits to the point that the delta becomes huge for existing package. It probably _genuinely_ needs a new version that Roland uploaded, which had major rework and has fixes for many bugs. I think it is better out of bookworm at the moment. My 2 cents. > > [1] > >
Bug#1002393: mdp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Bump to avoid auto removal while the fixed version ages in unstable. I'm not sure if this needs some additional prodding because tracker only shows one of the bugs as fixed by migration and 2 bugs triggering auto removal.
Bug#1035281: marked as done (firmware-intel-sound: broken symlinks: /lib/firmware/intel/dsp_fw_*.bin -> avs/*/dsp_basefw.bin)
Your message dated Tue, 02 May 2023 16:19:55 + with message-id and subject line Bug#1035281: fixed in firmware-nonfree 20230310-1~exp2 has caused the Debian Bug report #1035281, regarding firmware-intel-sound: broken symlinks: /lib/firmware/intel/dsp_fw_*.bin -> avs/*/dsp_basefw.bin 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.) -- 1035281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-intel-sound Version: 20230310-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks. >From the attached log (scroll to the bottom...): 0m13.1s ERROR: WARN: Broken symlinks: /lib/firmware/intel/dsp_fw_bxtn.bin -> avs/apl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_cnl.bin -> avs/cnl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_glk.bin -> avs/apl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_kbl.bin -> avs/skl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_release.bin -> avs/skl/dsp_basefw.bin (firmware-intel-sound) Severity serious, since that likely means the firmware is missing at the expected location. cheers, Andreas firmware-intel-sound_20230310-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: firmware-nonfree Source-Version: 20230310-1~exp2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of firmware-nonfree, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated firmware-nonfree 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: Tue, 02 May 2023 18:03:22 +0200 Source: firmware-nonfree Architecture: source Version: 20230310-1~exp2 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1035281 Changes: firmware-nonfree (20230310-1~exp2) experimental; urgency=medium . * intel-sound: intel: avs: Add AudioDSP base firmware for SKL-based platforms (Closes: #1035281) * intel-sound: intel: avs: Add AudioDSP base firmware for APL-based platforms (Closes: #1035281) * intel-sound: intel: avs: Add AudioDSP base firmware for CNL-based platforms (Closes: #1035281) Checksums-Sha1: d107c10c0ef13d9b0ac179aec0d681a32c6d964a 4296 firmware-nonfree_20230310-1~exp2.dsc d14a25226c6a662ce126d8e1aa2e6e12e7648aa1 827720 firmware-nonfree_20230310-1~exp2.debian.tar.xz e5ca2818c834908a11533688f7eb3ddac056fd85 6049 firmware-nonfree_20230310-1~exp2_source.buildinfo Checksums-Sha256: ab6ab817b399200b61aca8c2aa67f13f7ebd6cbe914e21a35e153c2b0eeb14ee 4296 firmware-nonfree_20230310-1~exp2.dsc 4328eb292e98c822346f8f8113bbe84c7bc8048d64c47bb095b14a44a4417831 827720 firmware-nonfree_20230310-1~exp2.debian.tar.xz 31c6b49fb6b6ec982939224bf08d7008ff3da30b6921619873184797346bd8fa 6049 firmware-nonfree_20230310-1~exp2_source.buildinfo Files: 15c6a7d41eed9593696b0cb546aea020 4296 non-free-firmware/kernel optional firmware-nonfree_20230310-1~exp2.dsc 6aa510e6f0c38f5759049280115180e7 827720 non-free-firmware/kernel optional firmware-nonfree_20230310-1~exp2.debian.tar.xz 5912566ef295c98fde35e4babbfe53d8 6049 non-free-firmware/kernel optional firmware-nonfree_20230310-1~exp2_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmRRNJFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EYCUP/37emCMqs+XTkZZo9k/OUY1w0B6131rn ATEZ2D1eFMo+uGVO93/nMgL3uBnK+T93xcHxLS0cxNLds9kyELKgiUpLSz/ossge Wej4ypok6MnC7PMtL/CkaQ9LWhzt87gcmsMq0wI8wrmp0TZ+P36URuveUcLqL34j 8kffjRhcLYWgUBj799wpAq3xvGH15Wh85DpoIKbEcMn9K9Q7S9ZPiBwu/1e+Ozb8 amAB8kOnHj8NHVy7TPKbzxsUPa8iR3iKl20pNdSar8kPSChEwAR/KQ0wMIrNk856
Bug#1035389: ruby-aws-sdk-core: The VERSION file is not packaged
Package: ruby-aws-sdk-core
Version: 3.104.3-3+deb11u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Our build pipeline uses Debian Bullseye, which received a point release (11.7)
including an update to your package.
This update now renders this package unusable.
After installing the package ("apt install ruby-aws-sdk-core"), when one tries
to require aws-sdk-core or run the file directly on debian by running:
"ruby /usr/lib/ruby/vendor_ruby/aws-sdk-core.rb", you get the error:
Traceback (most recent call last):
2: from /usr/lib/ruby/vendor_ruby/aws-sdk-core.rb:93:in `'
1: from /usr/lib/ruby/vendor_ruby/aws-sdk-core.rb:95:in `'
/usr/lib/ruby/vendor_ruby/aws-sdk-core.rb:95:in `read': No such file or
directory @ rb_sysopen - /usr/lib/ruby/VERSION (Errno::ENOENT)
This was most likely caused by dropping the fix-version.patch file, now the
following line is executed and generates the aforementioned error:
"CORE_GEM_VERSION = File.read(File.expand_path('../../VERSION',
__FILE__)).strip"
I expect the gem to not throw an error when requiring it.
This can be achieved by correctly packaging the VERSION file that exists in the
repository.
-- System Information:
Debian Release: 11.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-20-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ruby-aws-sdk-core depends on:
ii ruby 1:2.7+2
ii ruby-aws-eventstream 1.1.0-1
ii ruby-aws-partitions 1.354.0-2
ii ruby-aws-sigv41.1.0-3
ii ruby-jmespath 1.4.0-2
ruby-aws-sdk-core recommends no packages.
ruby-aws-sdk-core suggests no packages.
-- no debconf information
Processed: user debian...@lists.debian.org, usertagging 1020977, usertagging 1017619, usertagging 946452 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1020977 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1017619 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 946452 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1029331 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1029331 + librust-snapbox-dev usertag 978322 piuparts Bug #1029331 [librust-snapbox-dev] librust-snapbox-dev has unmet dependencies Added indication that 1029331 affects librust-snapbox-dev, usertag, 978322, and piuparts > affects 978322 + librust-sleef-sys-dev Bug #978322 [src:rust-sleef-sys] rust-sleef-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 Added indication that 978322 affects librust-sleef-sys-dev > usertags 1004596 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 979146 piuparts Usertags were: edos-uninstallable. Usertags are now: piuparts edos-uninstallable. > usertags 996285 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1013423 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1004581 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1031969 piuparts There were no usertags set. Usertags are now: piuparts. > severity 1031969 serious Bug #1031969 [python3.10-venv] python3.10-venv: python3-venv no longer installable since python3-distutils 3.11.2-2 Severity set to 'serious' from 'normal' > found 1031969 3.10.11-1 Bug #1031969 [python3.10-venv] python3.10-venv: python3-venv no longer installable since python3-distutils 3.11.2-2 Marked as found in versions python3.10/3.10.11-1. > found 1030530 3.10.11-1 Bug #1030530 [python3.10] python3.10 should not be in bookworm Marked as found in versions python3.10/3.10.11-1. > usertags 1030530 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1030530 + idle-python3.10 Bug #1030530 [python3.10] python3.10 should not be in bookworm Added indication that 1030530 affects idle-python3.10 > usertags 1004823 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 993015 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1004805 + libaudio-xmmsclient-perl xmms2-plugin-avcodec > xmms2-plugin-flac Bug #1004805 [src:xmms2] xmms2: FTBFS with ffmpeg 5.0 Added indication that 1004805 affects libaudio-xmmsclient-perl, xmms2-plugin-avcodec, and xmms2-plugin-flac > usertags 1006386 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 995050 piuparts There were no usertags set. Usertags are now: piuparts. > affects 995050 + libedasqlite0 Bug #995050 [src:ecere-sdk] ecere-sdk FTBFS with gcc 10 Added indication that 995050 affects libedasqlite0 > usertags 1025731 piuparts Usertags were: edos-uninstallable. Usertags are now: edos-uninstallable piuparts. > usertags 1031686 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 999750 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 984228 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 957514 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1023565 piuparts There were no usertags set. Usertags are now: piuparts. > severity 1023565 serious Bug #1023565 [mopidy-dleyna] mopidy-dleyna: depends on orphaned/removed dleyna Severity set to 'serious' from 'important' > usertags 1017623 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1017547 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1012690 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1004816 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 983991 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1017493 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1004626 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 997203 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 966743 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1015138 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1018277 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1029333 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 966726 piuparts Usertags were: piuparts edos-uninstallable. Usertags are now: piuparts edos-uninstallable. > affects 966726 + htcondor Bug #966726 [src:condor] condor: Unversioned Python removal in sid/bullseye Added indication that 966726 affects htcondor > usertags 1004770 piuparts There were no usertags set. Usertags are now: piuparts. >
Bug#1031909: marked as done (python3-tk: bytecode not removed on upgrade)
Your message dated Tue, 02 May 2023 14:38:42 + with message-id and subject line Bug#1031909: fixed in python3-stdlib-extensions 3.11.2-3 has caused the Debian Bug report #1031909, regarding python3-tk: bytecode not removed on upgrade 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.) -- 1031909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-tk Version: 3.11.2-2 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, The python3-tk package does not remove bytecode on upgrade: Unpacking python3-tk:amd64 (3.11.2-2) over (3.10.8-1) ... dpkg: warning: unable to delete old directory '/usr/lib/python3.10/tkinter': Directory not empty dpkg: warning: unable to delete old directory '/usr/lib/python3.10': Directory not empty On a side note this bug is the same as #1017445 which is the same as #960653 which is the same as #918098. Why does this keep happening? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-tk depends on: ii blt 2.5.3+dfsg-4.1 ii libc6 2.36-8 ii libtcl8.6 8.6.13+dfsg-2 ii libtk8.6 8.6.13-2 ii python3 3.11.1-3 ii tk8.6-blt2.5 2.5.3+dfsg-4.1 python3-tk recommends no packages. Versions of packages python3-tk suggests: pn python3-tk-dbg pn tix -- no debconf information --- End Message --- --- Begin Message --- Source: python3-stdlib-extensions Source-Version: 3.11.2-3 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python3-stdlib-extensions, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python3-stdlib-extensions 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: Tue, 02 May 2023 15:34:18 +0200 Source: python3-stdlib-extensions Architecture: source Version: 3.11.2-3 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 1031909 Changes: python3-stdlib-extensions (3.11.2-3) unstable; urgency=medium . * Remove 3.10 byte code on upgrade. Closes: #1031909. Checksums-Sha1: e35c01a363646d03028da7e76290fec20d26e397 2485 python3-stdlib-extensions_3.11.2-3.dsc b5dfffca81188fdbeba4f291b659d01fa07f7c7b 25964 python3-stdlib-extensions_3.11.2-3.debian.tar.xz b43408c26aba059eb198ffcea82f0b5cc8e2e8f6 8127 python3-stdlib-extensions_3.11.2-3_source.buildinfo Checksums-Sha256: a6ea0ff105c3d34fa2986961826e04bc20efb2ff5af3a04460a528994fbd 2485 python3-stdlib-extensions_3.11.2-3.dsc d1824aed18f046336b96dced598ae33cd67886f22823bf1d155e793ee6296f6e 25964 python3-stdlib-extensions_3.11.2-3.debian.tar.xz 4495dc66bdbe8cb81528006b4e1fdbb0e4fbf07469d00d6bec4afdccbf5ede9e 8127 python3-stdlib-extensions_3.11.2-3_source.buildinfo Files: 5729b8682765e76ec0fde010a1693f56 2485 python optional python3-stdlib-extensions_3.11.2-3.dsc bcb4565dc2c32336b1124ed9ff5db138 25964 python optional python3-stdlib-extensions_3.11.2-3.debian.tar.xz c5113e501eb1c7c91dc3d5d7de9e0e2f 8127 python optional python3-stdlib-extensions_3.11.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmRREwoQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9eIFEADORk/hM7ot7r7EmqQ3MWFaOsdY66iRDTzz CNO+G8PNStJs2tIIsqvHKz4RUpsrjAz1b86V3Ga0Eal1+BnMDrHp2ilH71m0sBNS W84wUzlq5myWzsUCGKHbYEycVTBh3W6N5EGUAcWjRF4IOK3j1Dcrk74I0E4nikgx IVl61G1fhb/0+rPVCM5mGlGfHLDWfsbE0bHdPi/28l/ZQGCv5q6Rsgy+tmN0XLTp W6hAenyGe3HSm9o5UWURaY9I5JnnbrtCkvgP2udMEVUGMlc3LM1gkLOEaa/5xrr6
Bug#1035384: openscap-daemon: hardcoded dependency on no longer available libopenscap8
Package: openscap-daemon Version: 0.1.10-3.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: openscap-daemon : Depends: libopenscap8 but it is not installable libopenscap8 is long gone, but even rebuilding openscap-daemon does not pick up a dependency on a newer version, threrfore that seems to be hardcoded somewhere. Cheers, Andreas
Processed: Re: Bug#1034409: Boot from removable media path fails after changing secure boot validation because MOK Manager is not found
Processing control commands: > severity -1 serious Bug #1034409 [src:grub2] Boot from removable media path fails after changing secure boot validation because MOK Manager is not found Severity set to 'serious' from 'normal' -- 1034409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034674: marked as done (mm3d can not load OBJ files, corrupts IQE & SMD & D3D files on save, depending on locale)
Your message dated Tue, 2 May 2023 15:20:43 +0200 with message-id <92841277-4c5e-9683-ef80-f3e28a144...@iem.at> and subject line mm3d cannot load OBJ files, depending on locale has caused the Debian Bug report #1034674, regarding mm3d can not load OBJ files, corrupts IQE & SMD & D3D files on save, depending on locale 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.) -- 1034674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mm3d Version: 1.3.12-1+b1 Severity: grave Tags: l10n X-Debbugs-Cc: nils+debian-p...@dieweltistgarnichtso.net Dear Maintainer, I tried to open some OBJ files with mm3d, but no 3D model was shown. I figured out that it seems to have something to do with my locale. I think file loading code mistakenly localizes decimal separators. This did not work: LC_NUMERIC=de_DE.UTF-8 mm3d tmp/sydney.obj This did work: LC_NUMERIC=C mm3d tmp/sydney.obj According to this commit message I found, this is fixed in a new upstream version: https://github.com/zturtleman/mm3d/commit/f00fdd5f2a27292a646a23ba34f80be50ab9844c The commit message also warns that mm3d will corrupt IQE & SMD & D3D when saving … for this reason the bug report is marked grave because this could cause data loss! -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-0.bpo.3-amd64 (SMP w/16 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mm3d depends on: ii libc6 2.31-13+deb11u5 ii libgcc-s1 [libgcc1] 10.2.1-6 ii libgl1 1.3.2-1 ii libglu1-mesa [libglu1] 9.0.1-1 ii libqt5core5a5.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5opengl5 5.15.2+dfsg-9 ii libqt5widgets5 5.15.2+dfsg-9 ii libstdc++6 10.2.1-6 Versions of packages mm3d recommends: ii blender 2.83.5+dfsg-5+deb11u1 ii wings3d 2.2.5-1 pn yafray mm3d suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- the version currently in Debian/testing (aka bookworm) is 1.3.13-1, which has this bug already fixed. "bookworm" is now in deep freeze. thanks. OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1034443: python3-brial: uninstallable on arcitectures where sagemath is unavailable
Hell All, I have just made singular independent from brial
Thanks for dealing with that part of the issue.
Otherwise it must be keep in mind that Sage is mostly umbrella software.
That means that the dependency of brian on sage material is odd.
odd as it may be, it seems the dependency of python3-brial
on sagemath is real.
I've prepared a NMU, and intend to open a pre-approval
request with the release team. If you have any objections
to the NMU please tell me ASAP (I do not intend to upload
it until I receive a response from the release team, if you
would preffer to make the upload yourself that is fine too).
diff -Nru brial-1.2.11/debian/changelog brial-1.2.11/debian/changelog
--- brial-1.2.11/debian/changelog 2023-04-03 12:13:10.0 +
+++ brial-1.2.11/debian/changelog 2023-05-02 10:39:34.0 +
@@ -1,3 +1,11 @@
+brial (1.2.11-2.1) bookworm-staging; urgency=medium
+
+ * Non-Maintainer upload.
+ * Limit architectures for python3-brial package to architectures where
+sagemath is available (Closes: #1034443).
+
+ -- Peter Michael Green Tue, 02 May 2023 10:39:34
+
+
brial (1.2.11-2) unstable; urgency=medium
* Team upload.
diff -Nru brial-1.2.11/debian/control brial-1.2.11/debian/control
--- brial-1.2.11/debian/control 2023-04-03 12:11:20.0 +
+++ brial-1.2.11/debian/control 2023-04-08 15:18:38.0 +
@@ -22,7 +22,7 @@
Homepage: https://github.com/BRiAl
Package: python3-brial
-Architecture: any
+Architecture: amd64 arm64 i386 riscv64
Section: python
Depends: python3-sage,
${misc:Depends},
Bug#1035350: postfix: postinst script modifies configuration files despite local changes
On 02/05/2023 15:07, Scott Kitterman wrote: > On Tuesday, May 2, 2023 8:35:12 AM EDT Einhard Leichtfuß wrote: >> On 02/05/2023 00:56, Scott Kitterman wrote: >>> On Monday, May 1, 2023 3:20:19 PM EDT Einhard Leichtfuß wrote: On 01/05/2023 19:47, Scott Kitterman wrote: > On Monday, May 1, 2023 1:01:17 PM EDT Einhard Leichtfuß wrote: >> On 01/05/2023 18:14, Scott Kitterman wrote: >>> On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote: Package: postfix > > ... > In `main.cf`, the following lines were appended: > readme_directory = /usr/share/doc/postfix > html_directory = /usr/share/doc/postfix/html If I understand the postinst script correctly, this modification of `main.cf` should only have happened upon first installation, which this was not. I was unable to reproduce this. So maybe this modification was indeed done earlier. However, even upon initial installation (with pre-existing configuration), this should, in my opinion, not happen. > > ... > >>> Also, note that the message about is about main.cf not being modified. >>> These changes are in master.cf, so I don't understand the concern with >>> the message? >> >> The second modification (readme_directory, html_directory) was to >> `main.cf`. While this modification should only happen for initial >> installations (with pre-existing configuration), the message is >> displayed even then. >> >> Steps to reproduce (assuming postfix is not installed): >> >> $ apt install postfix-doc >> $ echo > /etc/postfix/main.cf >> $ apt install postfix > > To focus in on the main.cf part of this, I believe that's per policy. > > First, it's a change made by postfix-doc, not postifx, so the postfix > package statement that main.cf was not modified by it is correct and > unrelated to the main.cf change. Ah, I did not check the postfix-doc postinst script. It seems that both postfix-doc's and postfix's postinst scripts conditionally run postconf -e readme_directory=/usr/share/doc/postfix html_directory=/usr/share/doc/postfix/html However, postfix's postinst script only does so in the arguably rare case that postfix-doc was installed first. So one might argue that this is still an action performed for postfix-doc falling under Policy 10.7.4. > For the postfix-doc change to main.cf, Policy 10.7.4 is the relevant > portion. Postfix-doc uses the provided interface (postfconf), when > available. It is not clear to me that Policy 10.7.4 overrides Policy 10.7.3 w.r.t. the requirement not to override local changes. While this may very well not be the intention behind these policies, I'd understand them as such that the related package (postfix-doc) must only [be able to] modify the configuration file if it does not contain local changes. I.e., either the provided program (currently postconf) should refuse to modify a locally modified configuration file, or the related package (postfix-doc) should check for local changes itself. I am generally unsure, however, how detection of local modification is supposed to work in practice without using conffiles. I suppose a second configuration file copy that is modified by postinst scripts, but not the local administrator, should work. >>> >>> Preserve local modifications means don't undo specific changes made by the >>> local administrator. It does not mean make no changes to a file that an >>> administrator has made changes to. The use of postconf specifically >>> enables changing the values relevant to postfix-doc without disturbing >>> anything else in the file. I think this is fine. >> >> I agree that preserving local changes does not generally mean not to >> modify locally modified files. (Even though I'd prefer it to mean that.) >> >> However, unless I am mistaken, the postinst scripts do not preserve >> local changes to the readme_directory and html_directory configuration >> settings. >> >> In practice (given postfix-doc is [being] installed), such local changes >> probably either do not happen, or the values are exactly those set by >> the postinst scripts. >> >> That is, in such an unlikely case, the letter of the Policy would be >> violated, I think, but it may still be considered fine in practice. I >> cannot assess that. > > I agree with that analysis. I think it is technically a policy violation, > but > one that is very unlikely to ever be an issue (I think it's fine in practice). > > I still need to do further assessment on the master.cf portion of this bug. > We're approximately a month away from a new Debian release. I am extremely > reluctant to mess with this so close to the release date, so any changes from >
Processed: fixed 1034674 in 1.3.13-1
Processing commands for cont...@bugs.debian.org: > fixed 1034674 1.3.13-1 Bug #1034674 [mm3d] mm3d can not load OBJ files, corrupts IQE & SMD & D3D files on save, depending on locale Marked as fixed in versions mm3d/1.3.13-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1034674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034969: [Pkg-javascript-devel] Bug#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
Quoting Yadd (2023-05-02 08:58:06) > For the record, unblock issue is #1035368 Looks excellent - thanks for your work on this, Yadd! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1035350: postfix: postinst script modifies configuration files despite local changes
On Tuesday, May 2, 2023 8:35:12 AM EDT Einhard Leichtfuß wrote: > On 02/05/2023 00:56, Scott Kitterman wrote: > > On Monday, May 1, 2023 3:20:19 PM EDT Einhard Leichtfuß wrote: > >> On 01/05/2023 19:47, Scott Kitterman wrote: > >>> On Monday, May 1, 2023 1:01:17 PM EDT Einhard Leichtfuß wrote: > On 01/05/2023 18:14, Scott Kitterman wrote: > > On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote: > >> Package: postfix > >>> > >>> ... > >>> > >> In `main.cf`, the following lines were appended: > >>> readme_directory = /usr/share/doc/postfix > >>> html_directory = /usr/share/doc/postfix/html > >> > >> If I understand the postinst script correctly, this modification of > >> `main.cf` should only have happened upon first installation, which > >> this > >> was not. I was unable to reproduce this. So maybe this modification > >> was indeed done earlier. > >> > >> However, even upon initial installation (with pre-existing > >> configuration), this should, in my opinion, not happen. > >>> > >>> ... > >>> > > Also, note that the message about is about main.cf not being modified. > > These changes are in master.cf, so I don't understand the concern with > > the message? > > The second modification (readme_directory, html_directory) was to > `main.cf`. While this modification should only happen for initial > installations (with pre-existing configuration), the message is > displayed even then. > > Steps to reproduce (assuming postfix is not installed): > > $ apt install postfix-doc > $ echo > /etc/postfix/main.cf > $ apt install postfix > >>> > >>> To focus in on the main.cf part of this, I believe that's per policy. > >>> > >>> First, it's a change made by postfix-doc, not postifx, so the postfix > >>> package statement that main.cf was not modified by it is correct and > >>> unrelated to the main.cf change. > >> > >> Ah, I did not check the postfix-doc postinst script. It seems that both > >> postfix-doc's and postfix's postinst scripts conditionally run > >> > >> postconf -e readme_directory=/usr/share/doc/postfix > >> > >> html_directory=/usr/share/doc/postfix/html > >> > >> However, postfix's postinst script only does so in the arguably rare > >> case that postfix-doc was installed first. So one might argue that this > >> is still an action performed for postfix-doc falling under Policy 10.7.4. > >> > >>> For the postfix-doc change to main.cf, Policy 10.7.4 is the relevant > >>> portion. Postfix-doc uses the provided interface (postfconf), when > >>> available. > >> > >> It is not clear to me that Policy 10.7.4 overrides Policy 10.7.3 w.r.t. > >> the requirement not to override local changes. While this may very well > >> not be the intention behind these policies, I'd understand them as such > >> that the related package (postfix-doc) must only [be able to] modify the > >> configuration file if it does not contain local changes. > >> > >> I.e., either the provided program (currently postconf) should refuse to > >> modify a locally modified configuration file, or the related package > >> (postfix-doc) should check for local changes itself. > >> > >> I am generally unsure, however, how detection of local modification is > >> supposed to work in practice without using conffiles. I suppose a > >> second configuration file copy that is modified by postinst scripts, but > >> not the local administrator, should work. > > > > Preserve local modifications means don't undo specific changes made by the > > local administrator. It does not mean make no changes to a file that an > > administrator has made changes to. The use of postconf specifically > > enables changing the values relevant to postfix-doc without disturbing > > anything else in the file. I think this is fine. > > I agree that preserving local changes does not generally mean not to > modify locally modified files. (Even though I'd prefer it to mean that.) > > However, unless I am mistaken, the postinst scripts do not preserve > local changes to the readme_directory and html_directory configuration > settings. > > In practice (given postfix-doc is [being] installed), such local changes > probably either do not happen, or the values are exactly those set by > the postinst scripts. > > That is, in such an unlikely case, the letter of the Policy would be > violated, I think, but it may still be considered fine in practice. I > cannot assess that. I agree with that analysis. I think it is technically a policy violation, but one that is very unlikely to ever be an issue (I think it's fine in practice). I still need to do further assessment on the master.cf portion of this bug. We're approximately a month away from a new Debian release. I am extremely reluctant to mess with this so close to the release date, so any changes from this bug are likely early in the next release cycle.
Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
On 02/05/2023 11.37, Ian Jackson wrote:
Andreas Beckmann writes ("Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
Package: sauce
Version: 0.9.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
...
during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after the package
has been removed (*) or when logrote is run but no logfile exists.
Thanks for the report. I will fix this ASAP.
Usually the solution is to specify 'missingok' in the logrotate
configuration.
I will do some tests but that sounds like a possible approach.
That doesn't look like a solution in this case.
Setting severity to serious since this does not seem limited to being
emitted after package removal but always. The current logrotate version
in sid seems to be more strict.
I looked through the changelog and didn't find anything about missing
logfiles since at least 2015. Are you sure ?
>From the attached log (scroll to the bottom...):
0m17.0s DEBUG: Starting command: ['chroot',
'/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate',
'/etc/logrotate.d/sauce']
0m17.0s DUMP:
warning: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
0m17.0s DEBUG: Command ok: ['chroot',
'/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate',
'/etc/logrotate.d/sauce']
0m17.0s ERROR: FAIL: Logrotate file /etc/logrotate.d/sauce exits with error or
has output with package removed
I have one question. The message here is complaining about the file
permission. I think that mode is probably wrong, but I don't think it
is *dangerous*.
I don't think I ought to change the mode for bookworm.
That code is from logrotate
https://sources.debian.org/src/logrotate/3.21.0-1/config.c/?hl=1057#L1057
but it was already present at least in bullseye (didn't check earlier
releases).
Tryinit it manually by installing logrotate and sauce in a chroot
(without removing sauce again):
bullseye# ls -la /etc/logrotate.d/sauce
-rwxr-xr-x 1 root root 506 Jan 27 2021 /etc/logrotate.d/sauce
bullseye# logrotate /etc/logrotate.d/sauce
bullseye# echo $?
0
installing sauce in bookworm is very noisy:
Setting up sauce (0.9.1) ...
Checking for SAUCE databases in /var/lib/sauce ...
cdb.site-annoy (no existing data) donechown: warning: '.' should be
':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
.
cdb.site-seen (no existing data) donechown: warning: '.' should be
':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
.
cdb.site-list (no existing data) donechown: warning: '.' should be
':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
.
cdb.addr-seen (no existing data) donechown: warning: '.' should be
':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
.
cdb.addr-list (no existing data) donechown: warning: '.' should be
':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
chown: warning: '.' should be ':': 'mail.mail'
.
bookworm# ls -la /etc/logrotate.d/sauce
-rwxr-xr-x 1 root root 506 Jan 27 2021 /etc/logrotate.d/sauce
bookworm# logrotate /etc/logrotate.d/sauce
warning: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
bookworm# echo $?
0
If I understand it correctly, logrotate complains about the executable
permission. (0644 and 0600 should be both ok)
And it will do that every time logrotate runs while the package is
installed, producing some cron email or other notification.
IMO both bugs (logrotate permission and ancient chown syntax) warrant an
update of the package to be included in bookworm.
Andreas
Bug#1035360: marked as done (bookworm RC2 installation leaves luks encrypted system in unbootable state)
Your message dated Tue, 02 May 2023 13:04:15 + with message-id and subject line Bug#1035360: fixed in live-build 1:20230502 has caused the Debian Bug report #1035360, regarding bookworm RC2 installation leaves luks encrypted system in unbootable state 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.) -- 1035360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: grave X-Debbugs-Cc: think...@rumbero.org Hi all, using the xfce4 based RC2 live ISO image[1], on a Thinkpad T480 (16GB RAM/256GB NVME/INTEL GRAPHICS ONLY) installation of Debian in an luks encrypted LVM was performed. Apparently, the required cryptsetup-initramfs packages were removed from the system during the last instalation stages, rendering the resulting system unbootable. Manual intervention was required to fix the issue from a live rescue system, something a novice user will never be able to accomplish. The same issue was already note with the prior RC1 variant of this bookworm live ISO. It can be reliably reproduced. Attached installation logs should be sufficiently verbose about what actually happened underneath. [1] https://cdimage.debian.org/cdimage/bookworm_di_rc2-live/amd64/iso-hybrid/debian-live-bkworm-DI-rc2-amd64-xfce.iso Regards, P.Seelig -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'oldstable-proposed-updates'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-8-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: live-build Source-Version: 1:20230502 Done: Jonathan Carter We believe that the bug you reported is fixed in the latest version of live-build, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated live-build 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: Tue, 02 May 2023 14:30:24 +0200 Source: live-build Architecture: source Version: 1:20230502 Distribution: unstable Urgency: medium Maintainer: Debian Live Changed-By: Jonathan Carter Closes: 1035360 Changes: live-build (1:20230502) unstable; urgency=medium . * Team upload * Add cryptsetup-initramfs to package pool (Closes: #1035360) Checksums-Sha1: 49c9392ce13fcbb68d3fff91823dafef6ed62b40 1848 live-build_20230502.dsc a73d193ed8988207e9d335e18d45185d4634f4af 235104 live-build_20230502.tar.xz 3f59ebaae97c86fc816d02ac1481d1e60f2a1a4c 6114 live-build_20230502_source.buildinfo Checksums-Sha256: 07915ef266f2538814e6d28f0b6574e9f08f686ff1ed86fd13e50eb06d9b9c08 1848 live-build_20230502.dsc d5f178dfd556db74411bd51fb6559372408f3e796ce202e53fc4bbf8d7c31076 235104 live-build_20230502.tar.xz fbe76bf4314c088d31c8e27a357978eba4f678b795e815d35f825a0ece97e14b 6114 live-build_20230502_source.buildinfo Files: 0011b2b372d65a487874b47ca09f2642 1848 misc optional live-build_20230502.dsc 8d4033743d54c26aa9e2b2c651003c44 235104 misc optional live-build_20230502.tar.xz 71c8d935d9b6a35019f3982051c87a0a 6114 misc optional live-build_20230502_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmRRA2IPHGpjY0BkZWJp YW4ub3JnAAoJELAdGnKsjcmhvmcP/jf3/oXf3YRH8Ct8IVlbSxsOIK/PlebOmYQF stuz/FzF6ARiP1vwD0H1Fh2zPySs5iFFkJ44ZuEfyI5qu8Sig4vzXw+snyR1Wjsg Nixx+QtH3irR2dhCqgrjjFqQZEHVfLAtJvpJOtx29CxieKXIBU0WAjASDT4VHFIA ajedKidhnQEfS6xULf6C7zIuT0ahq2uX2AIMFi+e+yJLnCLRV5Hs6eEutGz6U0nv 49zyOJalHlTQBhNNcM03TMUMz+U3T53elsQG1ZdYpPIP+PGDGFVUmLEeMQIerB75 +8tI4voQLb5OSCnOX23xQqPgqbSHRHxGvQhBRrDb50UJNCSU57lYz4c0b7Gy5r9t 6o6D2dQd93rIgW3YXIr6pQuLAyPwuo0IhfTRE6nOlNNINB/tvV30dlS6TtLpaj5W Z0V/o/TQfMzQbk23QY3NUeePdEmGLj+b4BgsK5sf+XLTkLY9IG7ZjdNEanVy1OXZ 6K8WudFvE
Bug#1035350: postfix: postinst script modifies configuration files despite local changes
On 02/05/2023 00:56, Scott Kitterman wrote: > On Monday, May 1, 2023 3:20:19 PM EDT Einhard Leichtfuß wrote: >> On 01/05/2023 19:47, Scott Kitterman wrote: >>> On Monday, May 1, 2023 1:01:17 PM EDT Einhard Leichtfuß wrote: On 01/05/2023 18:14, Scott Kitterman wrote: > On Monday, May 1, 2023 11:06:07 AM EDT Einhard Leichtfuß wrote: >> Package: postfix >>> >>> ... >>> >> In `main.cf`, the following lines were appended: >>> readme_directory = /usr/share/doc/postfix >>> html_directory = /usr/share/doc/postfix/html >> >> If I understand the postinst script correctly, this modification of >> `main.cf` should only have happened upon first installation, which this >> was not. I was unable to reproduce this. So maybe this modification >> was indeed done earlier. >> >> However, even upon initial installation (with pre-existing >> configuration), this should, in my opinion, not happen. >>> >>> ... >>> > Also, note that the message about is about main.cf not being modified. > These changes are in master.cf, so I don't understand the concern with > the message? The second modification (readme_directory, html_directory) was to `main.cf`. While this modification should only happen for initial installations (with pre-existing configuration), the message is displayed even then. Steps to reproduce (assuming postfix is not installed): $ apt install postfix-doc $ echo > /etc/postfix/main.cf $ apt install postfix >>> >>> To focus in on the main.cf part of this, I believe that's per policy. >>> >>> First, it's a change made by postfix-doc, not postifx, so the postfix >>> package statement that main.cf was not modified by it is correct and >>> unrelated to the main.cf change. >> >> Ah, I did not check the postfix-doc postinst script. It seems that both >> postfix-doc's and postfix's postinst scripts conditionally run >> >> postconf -e readme_directory=/usr/share/doc/postfix >> html_directory=/usr/share/doc/postfix/html >> >> However, postfix's postinst script only does so in the arguably rare >> case that postfix-doc was installed first. So one might argue that this >> is still an action performed for postfix-doc falling under Policy 10.7.4. >> >>> For the postfix-doc change to main.cf, Policy 10.7.4 is the relevant >>> portion. Postfix-doc uses the provided interface (postfconf), when >>> available. >> It is not clear to me that Policy 10.7.4 overrides Policy 10.7.3 w.r.t. >> the requirement not to override local changes. While this may very well >> not be the intention behind these policies, I'd understand them as such >> that the related package (postfix-doc) must only [be able to] modify the >> configuration file if it does not contain local changes. >> >> I.e., either the provided program (currently postconf) should refuse to >> modify a locally modified configuration file, or the related package >> (postfix-doc) should check for local changes itself. >> >> I am generally unsure, however, how detection of local modification is >> supposed to work in practice without using conffiles. I suppose a >> second configuration file copy that is modified by postinst scripts, but >> not the local administrator, should work. > > Preserve local modifications means don't undo specific changes made by the > local > administrator. It does not mean make no changes to a file that an > administrator has made changes to. The use of postconf specifically enables > changing the values relevant to postfix-doc without disturbing anything else > in > the file. I think this is fine. I agree that preserving local changes does not generally mean not to modify locally modified files. (Even though I'd prefer it to mean that.) However, unless I am mistaken, the postinst scripts do not preserve local changes to the readme_directory and html_directory configuration settings. In practice (given postfix-doc is [being] installed), such local changes probably either do not happen, or the values are exactly those set by the postinst scripts. That is, in such an unlikely case, the letter of the Policy would be violated, I think, but it may still be considered fine in practice. I cannot assess that. Einhard Leichtfuß
Bug#1031909: marked as done (python3-tk: bytecode not removed on upgrade)
Your message dated Tue, 02 May 2023 12:34:04 + with message-id and subject line Bug#1031909: fixed in python3-stdlib-extensions 3.11.3-2 has caused the Debian Bug report #1031909, regarding python3-tk: bytecode not removed on upgrade 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.) -- 1031909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-tk Version: 3.11.2-2 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, The python3-tk package does not remove bytecode on upgrade: Unpacking python3-tk:amd64 (3.11.2-2) over (3.10.8-1) ... dpkg: warning: unable to delete old directory '/usr/lib/python3.10/tkinter': Directory not empty dpkg: warning: unable to delete old directory '/usr/lib/python3.10': Directory not empty On a side note this bug is the same as #1017445 which is the same as #960653 which is the same as #918098. Why does this keep happening? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-tk depends on: ii blt 2.5.3+dfsg-4.1 ii libc6 2.36-8 ii libtcl8.6 8.6.13+dfsg-2 ii libtk8.6 8.6.13-2 ii python3 3.11.1-3 ii tk8.6-blt2.5 2.5.3+dfsg-4.1 python3-tk recommends no packages. Versions of packages python3-tk suggests: pn python3-tk-dbg pn tix -- no debconf information --- End Message --- --- Begin Message --- Source: python3-stdlib-extensions Source-Version: 3.11.3-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python3-stdlib-extensions, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python3-stdlib-extensions 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: Tue, 02 May 2023 14:15:07 +0200 Source: python3-stdlib-extensions Architecture: source Version: 3.11.3-2 Distribution: experimental Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 1031909 Changes: python3-stdlib-extensions (3.11.3-2) experimental; urgency=medium . * Remove 3.10 byte code on upgrade. Closes: #1031909. Checksums-Sha1: 006a5841b9b69dca8b44ffd1639adf1532770575 2563 python3-stdlib-extensions_3.11.3-2.dsc fb09d2cbc3ca715524f1ebc7e1aa198890ae53fb 26264 python3-stdlib-extensions_3.11.3-2.debian.tar.xz c77e8fdcebc48aa2ce002b0dd0d313e59d679098 8127 python3-stdlib-extensions_3.11.3-2_source.buildinfo Checksums-Sha256: 29fad4480e61eaca2ba3b523626b176e675f1a38969b458cc0c6d82a98db1370 2563 python3-stdlib-extensions_3.11.3-2.dsc 6cbc9f0705a7017e2d4f5d1b58cfb9b4969f5a786fec7a638cdcc1950cd5ad4c 26264 python3-stdlib-extensions_3.11.3-2.debian.tar.xz 6cf7ec428399b1d35ac86820bb831f18a2497ebd6027806011b570b08eaaed7a 8127 python3-stdlib-extensions_3.11.3-2_source.buildinfo Files: 7b265ddf75e45e10929db2fdea3f5b91 2563 python optional python3-stdlib-extensions_3.11.3-2.dsc 54c0561552ba7a3cbb3b5c7dc0c03f23 26264 python optional python3-stdlib-extensions_3.11.3-2.debian.tar.xz b9a0025a8b41c78961740a96a34c4c26 8127 python optional python3-stdlib-extensions_3.11.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmRQ/xEQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9eqvEACHWAyQ1vG9nO2+fpRzZYDS0E9tGo76SgIk iNQxBYnHn8qHc95ZlZsLJr6oB2tezww4mo6zX18SlLougzQ6JCu1n8w0/1qMBohc iyGeOaiQMUz0nO41ym2dem7DyKpaUbzZbdLBpoV6J/VDd3pjI289TZ5gOcn8uy2s KB0Q9DKZGEI4JXnmzE5a8olXQWQwi5nl8cl/W5kWANasxz7U38j7CEwffE5/1xcJ Z7SmuT9rz97huc68P1IRSmrVrHS8wFJPgievHaKxiukoUGAeJv6Uy+eey0U+ZmlS
Bug#1035363: marked as done (torrus-common: fails to install: addgroup with two arguments is an unspecified operation.)
Your message dated Tue, 02 May 2023 12:21:02 + with message-id and subject line Bug#1035363: fixed in torrus 3.00-2 has caused the Debian Bug report #1035363, regarding torrus-common: fails to install: addgroup with two arguments is an unspecified operation. 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.) -- 1035363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: torrus-common Version: 3.00-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up torrus-common (3.00-1.1) ... dpkg: error processing package torrus-common (--configure): installed torrus-common package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: torrus-common Re-running the postinst script with set -x: Setting up torrus-common (3.00-1.1) ... + set -e + dpkg-maintscript-helper rm_conffile /etc/logrotate.d/torrus-common 2.01-3 -- configure + test -L /etc/apache2/conf.d/torrus-apache2.conf + configure_user_group + adduser --quiet --system --no-create-home --home /nonexistent --force-badname --group Debian-torrus + fix_owner_perm + chown Debian-torrus:Debian-torrus /var/lib/torrus /var/log/torrus + chmod g+w /var/log/torrus + chmod g+w /var/lib/torrus/session_data/lock /var/lib/torrus/session_data/store + [ -d /var/cache/torrus ] + rm -rf /var/lib/torrus/db + addgroup www-data Debian-torrus Re-running the last command manually in the chroot without output redirection: # addgroup www-data Debian-torrus addgroup: addgroup with two arguments is an unspecified operation. cheers, Andreas torrus-common_3.00-1.1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: torrus Source-Version: 3.00-2 Done: Marc Haber We believe that the bug you reported is fixed in the latest version of torrus, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated torrus 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, 02 May 2023 13:43:51 +0200 Source: torrus Architecture: source Version: 3.00-2 Distribution: unstable Urgency: medium Maintainer: Torrus maintainers Changed-By: Marc Haber Closes: 1035363 Changes: torrus (3.00-2) unstable; urgency=medium . * use adduser instead of addgroup. Thanks to Andreas Beckmann (Closes: 1035363) * add debian/salsa-ci.yml Checksums-Sha1: 80c3e6dcd135c23ef60c15bed5db9ae2027a77ba 1908 torrus_3.00-2.dsc e24e411d4d1d72aebaef43cd2ba4b62c5dd7550a 18284 torrus_3.00-2.debian.tar.xz 6676e0f7e7765474e020b0a37a85ab91cefaaf9b 5716 torrus_3.00-2_source.buildinfo Checksums-Sha256: 1662fdf1520165c7034ede0a26b9d2f15bbd4faaf78ce547d9de799b727b4acd 1908 torrus_3.00-2.dsc ffc0e8288f2cf725efb1cd55acbe04c994ef64f2dd1bd411b76926c48cd330b5 18284 torrus_3.00-2.debian.tar.xz b30e8432a12145b5f4a6e90ac3d2eb57726efeb202a9b0d7e53ba176b93091fc 5716 torrus_3.00-2_source.buildinfo Files: a6f6205471c0018e2e41f3cc24008939 1908 net optional torrus_3.00-2.dsc 2b2a74d13f7434a94bf18c571f647730 18284 net optional torrus_3.00-2.debian.tar.xz 006a1e21072d1c2b68a542f926193940 5716 net optional torrus_3.00-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmRQ9/gACgkQj3cgEwEy BEIUpA/+Lf/V/nMQKfggEZR1nUVYJ1ls/tgk+EiV9i+G1JOBbeiLppcPN4XAEdfb TuIKoECEgeDk93+zcwpDe4UVa/x/jTVDFjmqoQ2sjmFH8+qaCeb42WRQc+9/26ED WSEl+CYnLMn0fQp+aV4q0l9sIeJf4zk4okxDR180UEG3wUImUsXn7P3lu1v/AZC4 FGhGpvqBapt5TRPWJbNIevv4BULD68KjYfQ9IiGyoEmiMbpzg6n3zm7BiYLGop3s ASVkKJK9UIxRCRjneBS1/TcgBbK0sKyGPX+7Cf/4JIhwE8aUqEpzLGBjonvW1xET za4UamzjhVsb1+ynEsaCY9v5UomSEqhp4izDTIAFGHyU2cgOMuKCZpswHHJ91VxW
Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
Andreas Beckmann writes ("Bug#1035361: sauce: Potentially dangerous mode on
/etc/logrotate.d/sauce: 0755"):
> Package: sauce
> Version: 0.9.1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
...
> during a test with piuparts I noticed your package's logrotate
> configuration causes logrotate to exit with an error after the package
> has been removed (*) or when logrote is run but no logfile exists.
Thanks for the report. I will fix this ASAP.
> Usually the solution is to specify 'missingok' in the logrotate
> configuration.
I will do some tests but that sounds like a possible approach.
> Setting severity to serious since this does not seem limited to being
> emitted after package removal but always. The current logrotate version
> in sid seems to be more strict.
I looked through the changelog and didn't find anything about missing
logfiles since at least 2015. Are you sure ?
> >From the attached log (scroll to the bottom...):
>
> 0m17.0s DEBUG: Starting command: ['chroot',
> '/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate',
> '/etc/logrotate.d/sauce']
> 0m17.0s DUMP:
> warning: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
> 0m17.0s DEBUG: Command ok: ['chroot',
> '/srv/piuparts.debian.org/tmp/tmp6h9n6ntx', '/usr/sbin/logrotate',
> '/etc/logrotate.d/sauce']
> 0m17.0s ERROR: FAIL: Logrotate file /etc/logrotate.d/sauce exits with error
> or has output with package removed
I have one question. The message here is complaining about the file
permission. I think that mode is probably wrong, but I don't think it
is *dangerous*.
I don't think I ought to change the mode for bookworm.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#1034961: marked as done (librust-mio-0.6-dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye)
Your message dated Tue, 02 May 2023 08:23:23 + with message-id and subject line Bug#1034961: fixed in rust-mio-0.6 0.6.23-3 has caused the Debian Bug report #1034961, regarding librust-mio-0.6-dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-mio-0.6-dev Version: 0.6.23-2+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-mio-0.6-dev/0.6.23-2+b1 from Debian bookworm on a minimal Debian bullseye with librust-mio-dev/0.6.23-1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/mio-0.6.23/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-mio-0.6-dev:amd64. | dpkg: considering deconfiguration of librust-mio-dev:amd64, which would be broken by installation of librust-mio-0.6-dev:amd64 ... | dpkg: yes, will deconfigure librust-mio-dev:amd64 (broken by librust-mio-0.6-dev:amd64) | (Reading database ... 5686 files and directories currently installed.) | Preparing to unpack .../librust-mio-0.6-dev_0.6.23-2+b1_amd64.deb ... | De-configuring librust-mio-dev:amd64 (0.6.23-1) ... | Unpacking librust-mio-0.6-dev:amd64 (0.6.23-2+b1) ... | dpkg: error processing archive ./librust-mio-0.6-dev_0.6.23-2+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/mio-0.6.23/.cargo-checksum.json', which is also in package librust-mio-dev:amd64 0.6.23-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./librust-mio-0.6-dev_0.6.23-2+b1_amd64.deb Please ensure that librust-mio-0.6-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: rust-mio-0.6 Source-Version: 0.6.23-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-mio-0.6, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-mio-0.6 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, 02 May 2023 05:39:37 + Source: rust-mio-0.6 Architecture: source Version: 0.6.23-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1034961 Changes: rust-mio-0.6 (0.6.23-3) unstable; urgency=medium . * Team upload. * Declare breaks+replaces on physical package instead of virtual one (Closes: #1034961) Checksums-Sha1: 1efacd46eb970d2952e2e931a5a6795d290c1d71 2714 rust-mio-0.6_0.6.23-3.dsc 7936ccb724c0b55b093cd336eeb5bc2ed9bc0a74 3572 rust-mio-0.6_0.6.23-3.debian.tar.xz 8df7cc905c99721ed3aa4371be324c981212b307 8393 rust-mio-0.6_0.6.23-3_source.buildinfo Checksums-Sha256: 78dcd15b5bee9ee65620c953cbe187add5c8ddb76a4ad6c4493caab73bf9ea17 2714 rust-mio-0.6_0.6.23-3.dsc c8efedc5aeb7d7884e9f9b57b2028fa31f85e756184985c0c067cb800732c4b5 3572 rust-mio-0.6_0.6.23-3.debian.tar.xz 662def1490eb05a4a0492f19c298851cffc50d7f7afe75976ec98c2c81f1b727 8393 rust-mio-0.6_0.6.23-3_source.buildinfo Files: a0ecb52ee7c11b40d901497e8cb7e6f2 2714 rust optional rust-mio-0.6_0.6.23-3.dsc 7abfa4c707af1b432773300ae8699a55 3572 rust optional rust-mio-0.6_0.6.23-3.debian.tar.xz 3b2d38f308eb75c736c4f19e50573966 8393 rust optional rust-mio-0.6_0.6.23-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRQpWYUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xu0AA/+LRjQKQubJ1qn6hjSDBC2yNmNjip2 l/cHPHYVQ10BUUk0WSNaBNy/F8Fqc8XrOxLiKZQudnUV3UX8XFJKAgNKUR2ePnkj +R5pVaPkuN6e4ajg2XsKrDxSMOJ4EpizIiccbPiRLfOZJMhoX46eDq6PwCT3pxlT nCFfnf6iciL4gkjm0yJTAkW8S69NOw44mRjD5v9jkdkssI1W/1tIqmlFdjuB4Hlv rCnZUXLUi2zT9woKnbWzrLf6O3OMng7hjDFpVQqg9fOk2G3JHbzgp0cCXNKELWVg AiNGzMULeIuzwYJcpV0En1jgaMseEjvpP69OWuIhX33twuUjRvO/6McXQxeTVXGe
Bug#1035371: libwebp: CVE-2023-1999
Source: libwebp Version: 1.2.4-0.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libwebp. There is unfortunately no public reference accessible, [1] has no details, [2] is restricted. it might be related to [3] and [4]. CVE-2023-1999[0]: | Double-free in libwebp If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-1999 https://www.cve.org/CVERecord?id=CVE-2023-1999 [1] https://www.mozilla.org/en-US/security/advisories/mfsa2023-13/#CVE-2023-1999 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1819244 [3] https://bugs.chromium.org/p/webp/issues/detail?id=603 [4] https://chromium.googlesource.com/webm/libwebp/+/a486d800b60d0af4cc0836bf7ed8f21e12974129 Can you find more on the issue? Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1034949: marked as done (librust-env-logger-0.7-dev: missing Breaks+Replaces for librust-env-logger-dev when upgrading from bullseye)
Your message dated Tue, 02 May 2023 07:34:20 + with message-id and subject line Bug#1034949: fixed in rust-env-logger-0.7 0.7.1-4 has caused the Debian Bug report #1034949, regarding librust-env-logger-0.7-dev: missing Breaks+Replaces for librust-env-logger-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-env-logger-0.7-dev Version: 0.7.1-3+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-env-logger-0.7-dev/0.7.1-3+b1 from Debian bookworm on a minimal Debian bullseye with librust-env-logger-dev/0.7.1-2 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/env_logger-0.7.1/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-env-logger-0.7-dev:amd64. | dpkg: considering deconfiguration of librust-env-logger-dev:amd64, which would be broken by installation of librust-env-logger-0.7-dev:amd64 ... | dpkg: yes, will deconfigure librust-env-logger-dev:amd64 (broken by librust-env-logger-0.7-dev:amd64) | (Reading database ... 4793 files and directories currently installed.) | Preparing to unpack .../librust-env-logger-0.7-dev_0.7.1-3+b1_amd64.deb ... | De-configuring librust-env-logger-dev:amd64 (0.7.1-2) ... | Unpacking librust-env-logger-0.7-dev:amd64 (0.7.1-3+b1) ... | dpkg: error processing archive ./librust-env-logger-0.7-dev_0.7.1-3+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/env_logger-0.7.1/.cargo-checksum.json', which is also in package librust-env-logger-dev:amd64 0.7.1-2 | Errors were encountered while processing: | ./librust-env-logger-0.7-dev_0.7.1-3+b1_amd64.deb Please ensure that librust-env-logger-0.7-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: rust-env-logger-0.7 Source-Version: 0.7.1-4 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-env-logger-0.7, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-env-logger-0.7 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, 02 May 2023 07:01:45 + Source: rust-env-logger-0.7 Architecture: source Version: 0.7.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1034949 Changes: rust-env-logger-0.7 (0.7.1-4) unstable; urgency=medium . * Team upload. * Declare breaks+replaces against physical package, rather than virtual one (Closes: #1034949) Checksums-Sha1: cb3b47d18f6ac0b2b595c1909da9dbb9693b534d 3084 rust-env-logger-0.7_0.7.1-4.dsc 112e5cdc196a98f20612e5af910d0225971b287b 3748 rust-env-logger-0.7_0.7.1-4.debian.tar.xz 811493899a5a43f3b2c85b4dcac2bc6982d018a1 9023 rust-env-logger-0.7_0.7.1-4_source.buildinfo Checksums-Sha256: 08b133f6d95af1d398827d257d4029649e6f4ea99153567672518d9ec2d8ea12 3084 rust-env-logger-0.7_0.7.1-4.dsc aabe741057b2358ff372901d9c6802b593077252bfb681e40d78a70164cddaa4 3748 rust-env-logger-0.7_0.7.1-4.debian.tar.xz 87b3c097d8073eec8197d3cc12c2c484362c867580301d94ee60b9836c8beec9 9023 rust-env-logger-0.7_0.7.1-4_source.buildinfo Files: cc653098f517d34a4cd6b53d359d7692 3084 rust optional rust-env-logger-0.7_0.7.1-4.dsc a833845271f0e85e160298ea6c39b36b 3748 rust optional rust-env-logger-0.7_0.7.1-4.debian.tar.xz d452b25bb1042983485e8a74fd3bcced 9023 rust optional rust-env-logger-0.7_0.7.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRQt9UUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtRaA/7BVxkPwDS6W2s+ZVoBUkUKkReZL1I 8aF0SjPzsaXcyDWPjSQ0cYa5amz6GHHHwDPAO9TukWd4q96Cj/yNLGCIVsHQehAl jCs2POBe6bv1YipJxgyhQw5VjirsqacrCdaF4gLvwntLea7rFWyNeadSBPKegX0G NUYyXfBJYLXBoujXb4uxwZzXT8RL2Yo0cgci+fnsm1L9Gy8atPr76opwGTwhEHbz
Bug#1034948: marked as done (librust-digest-0.9-dev: missing Breaks+Replaces for librust-digest-dev when upgrading from bullseye)
Your message dated Tue, 02 May 2023 07:34:13 + with message-id and subject line Bug#1034948: fixed in rust-digest-0.9 0.9.0-3 has caused the Debian Bug report #1034948, regarding librust-digest-0.9-dev: missing Breaks+Replaces for librust-digest-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-digest-0.9-dev Version: 0.9.0-2 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-digest-0.9-dev/0.9.0-2 from Debian bookworm on a minimal Debian bullseye with librust-digest-dev/0.9.0-1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/digest-0.9.0/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-digest-0.9-dev:amd64. | dpkg: considering deconfiguration of librust-digest-dev:amd64, which would be broken by installation of librust-digest-0.9-dev:amd64 ... | dpkg: yes, will deconfigure librust-digest-dev:amd64 (broken by librust-digest-0.9-dev:amd64) | (Reading database ... 4778 files and directories currently installed.) | Preparing to unpack .../librust-digest-0.9-dev_0.9.0-2_amd64.deb ... | De-configuring librust-digest-dev:amd64 (0.9.0-1) ... | Unpacking librust-digest-0.9-dev:amd64 (0.9.0-2) ... | dpkg: error processing archive ./librust-digest-0.9-dev_0.9.0-2_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/digest-0.9.0/.cargo-checksum.json', which is also in package librust-digest-dev:amd64 0.9.0-1 | Errors were encountered while processing: | ./librust-digest-0.9-dev_0.9.0-2_amd64.deb Please ensure that librust-digest-0.9-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: rust-digest-0.9 Source-Version: 0.9.0-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-digest-0.9, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-digest-0.9 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, 02 May 2023 07:14:02 + Source: rust-digest-0.9 Architecture: source Version: 0.9.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1034948 Changes: rust-digest-0.9 (0.9.0-3) unstable; urgency=medium . * Team upload. * Declare breaks+replaces against physical package instead of virtual one (Closes: #1034948) Checksums-Sha1: a014f93f99fe2c24b925589a26f442f560125176 rust-digest-0.9_0.9.0-3.dsc 704b9c2978cd47408681b6f918da74765bc0ac49 3120 rust-digest-0.9_0.9.0-3.debian.tar.xz 81fef1eab8941adf638f9259f31274351aa0a356 7366 rust-digest-0.9_0.9.0-3_source.buildinfo Checksums-Sha256: 641b1849a4059eaf4580ebf2fc1ec2626c08045609c511b07027e2cf5b9114fc rust-digest-0.9_0.9.0-3.dsc 80cd97a27e01c6e3a056c8b7fc56e3cce0c1960f0d0d1c2fe7df3954f4c38e33 3120 rust-digest-0.9_0.9.0-3.debian.tar.xz a706f6bf1a30e2c8aca0737bf78721d1308cfa70c7cf57f84ed37113ad4c7e40 7366 rust-digest-0.9_0.9.0-3_source.buildinfo Files: 1f2d8b3457f9fe1447d2ca6f1209de8f rust optional rust-digest-0.9_0.9.0-3.dsc 8595787145389457f923f65c791721ad 3120 rust optional rust-digest-0.9_0.9.0-3.debian.tar.xz d7946614b9070256eedf7116ec81705e 7366 rust optional rust-digest-0.9_0.9.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRQuUAUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuQLg/+Mul7WXoC9H9cdBPlGK4sD+Ns068C TiU9lMpOpcXzQljk6yyoXnTxmQdl5rIWBh4GEjHXt2k5S0R0jGJ0B0eCZrcTjxXx y1vnbXM8BrgUXjVh7XOCKoZot4fesTUCe2KEBZ3wWDhmwJFOGXmtVSjEQL+oiSZt LZmSlOKY650bBr/ok0rl0cUOoDaGqXn2ypNLZOVaiAR4tNT5av9n+Q4A283d5w5C 0ZJMaVaYbWvD/M+XgNA4A7OGoRFHopU2PJznWVwxKgZWvBJjpPe69kGiQaP42eDz 08jty+P+PtOvwQJ0qHgCMOTjC8/2G+gRt//RClJ37if9wAR7k9ItM2DE/Sb3nVFE
Bug#1034999: marked as done (librust-sha3-0.9-dev: missing Breaks+Replaces for librust-sha3-dev when upgrading from bullseye)
Your message dated Tue, 02 May 2023 07:22:09 + with message-id and subject line Bug#1034999: fixed in rust-sha3-0.9 0.9.1-2 has caused the Debian Bug report #1034999, regarding librust-sha3-0.9-dev: missing Breaks+Replaces for librust-sha3-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-sha3-0.9-dev Version: 0.9.1-1+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-sha3-0.9-dev/0.9.1-1+b1 from Debian bookworm on a minimal Debian bullseye with librust-sha3-dev/0.9.1-1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/sha3-0.9.1/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-sha3-0.9-dev:amd64. | dpkg: considering deconfiguration of librust-sha3-dev:amd64, which would be broken by installation of librust-sha3-0.9-dev:amd64 ... | dpkg: yes, will deconfigure librust-sha3-dev:amd64 (broken by librust-sha3-0.9-dev:amd64) | (Reading database ... 4873 files and directories currently installed.) | Preparing to unpack .../librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb ... | De-configuring librust-sha3-dev:amd64 (0.9.1-1) ... | Unpacking librust-sha3-0.9-dev:amd64 (0.9.1-1+b1) ... | dpkg: error processing archive ./librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/sha3-0.9.1/.cargo-checksum.json', which is also in package librust-sha3-dev:amd64 0.9.1-1 | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) | Errors were encountered while processing: | ./librust-sha3-0.9-dev_0.9.1-1+b1_amd64.deb Please ensure that librust-sha3-0.9-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: rust-sha3-0.9 Source-Version: 0.9.1-2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-sha3-0.9, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-sha3-0.9 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, 02 May 2023 06:30:56 + Source: rust-sha3-0.9 Architecture: source Version: 0.9.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1034999 Changes: rust-sha3-0.9 (0.9.1-2) unstable; urgency=medium . * Team upload. * Declare breaks+replaces against physical package instead of virtual one (Closes: #1034999) * Remove dev feature from dev-dependency on digest and disable tests that depend on it so the rest of the autopkgtest can run. * Bump hex-literal dev-dependency to 0.3 Checksums-Sha1: 1b429b0f9649afe374f754d52183184781c94e29 2578 rust-sha3-0.9_0.9.1-2.dsc c3dc73fe18512cc3b0764e7eb32446f9190521f1 3536 rust-sha3-0.9_0.9.1-2.debian.tar.xz 0edac8815c22d73c24c7eaa6eee79e503b97319b 7610 rust-sha3-0.9_0.9.1-2_source.buildinfo Checksums-Sha256: a01f0370f18a5f985d1aa0c982641f39b1abd9ff1c5d326933cb3572bd474c75 2578 rust-sha3-0.9_0.9.1-2.dsc 3c09ff71ea37577a3c22588bf7cb56617e01d1c6da9c2aa0ab4bde9956fc9959 3536 rust-sha3-0.9_0.9.1-2.debian.tar.xz 886b6548818683c7c60ce76a48782d66cd5b88da81bf1f8ab4030ea6a65b7e0f 7610 rust-sha3-0.9_0.9.1-2_source.buildinfo Files: fcc303c0e647272943df0e278a079f4b 2578 rust optional rust-sha3-0.9_0.9.1-2.dsc 550f0b821ee77ab04f7c014ffe2587b0 3536 rust optional rust-sha3-0.9_0.9.1-2.debian.tar.xz 4179adccf31c861b29f664a0d1df3557 7610 rust optional rust-sha3-0.9_0.9.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRQtCQUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtiKhAAjThrWFVlDi0z8CxeqxM0grrCoU+s nvDVYmnmjs827DTC4l5sxixHjpd/1rWANFErcOTtp488sBsKa+JLyldiSyBns08d 178bAWrhPZCqhLjyLxCu0SyPAlrNZFjQIoPMYxpkPMzEhL8JybOJ+WGmwsCIXwBf
Bug#1034969: marked as done (terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye)
Your message dated Tue, 02 May 2023 07:03:55 + with message-id and subject line Bug#1034969: fixed in node-terser 5.16.5-2 has caused the Debian Bug report #1034969, regarding terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: terser Version: 5.16.4-1 Severity: serious Justification: dpkg unpack error Attempting to unpack terser/5.16.4-1 from Debian bookworm on a minimal Debian bullseye with uglifyjs.terser/4.1.2-8 installed, causes an unpack error from dpkg due to /usr/share/nodejs/terser/bin/uglifyjs being contained in both packages. | Selecting previously unselected package terser. | dpkg: considering deconfiguration of uglifyjs.terser, which would be broken by installation of terser ... | dpkg: yes, will deconfigure uglifyjs.terser (broken by terser) | (Reading database ... 4922 files and directories currently installed.) | Preparing to unpack ./terser_5.16.4-1_all.deb ... | De-configuring uglifyjs.terser (4.1.2-8) ... | Unpacking terser (5.16.4-1) ... | dpkg: error processing archive ./terser_5.16.4-1_all.deb (--unpack): | trying to overwrite '/usr/share/nodejs/terser/bin/uglifyjs', which is also in package uglifyjs.terser 4.1.2-8 | Errors were encountered while processing: | ./terser_5.16.4-1_all.deb Please ensure that terser has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: node-terser Source-Version: 5.16.5-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-terser, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-terser 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: Tue, 02 May 2023 06:52:23 +0400 Source: node-terser Architecture: source Version: 5.16.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1034969 Changes: node-terser (5.16.5-2) unstable; urgency=medium . * Team upload * Duplicate Breaks field with Replaces (Closes: #1034969) Checksums-Sha1: 4f4eb21c75ea4b5cceb463baef4fc848b6d2ba1c 2477 node-terser_5.16.5-2.dsc b2f1f6a96d2b24b9fdbd3a9529058dfeb2ad24fa 14080 node-terser_5.16.5-2.debian.tar.xz Checksums-Sha256: 6917cf41335baf42e4d14713b1e58c438df8b707039c2de735d53a2e3f0ed3e6 2477 node-terser_5.16.5-2.dsc b239f53ca06cc93f79d09c3e0457e38a03d70e74c1473a1ea0557ace59eacfef 14080 node-terser_5.16.5-2.debian.tar.xz Files: 7bb5cb84f984a38fbccc2f9a8dc62d46 2477 javascript optional node-terser_5.16.5-2.dsc dc3aac2072970753f873014927c650d4 14080 javascript optional node-terser_5.16.5-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmRQsKQACgkQ9tdMp8mZ 7ulZSg/8DTlZ7bV7GJuaDxxJ8rC4ZR9dahVOj1R2SB1piM/mh9zr2hDlCduGXQTY s3xfssvdHb6EkZxylLmT8qwXSjan/tTqGZnkRo7u3S8BIA7xuBOuT0ycbfZ+mJed LLkoKuw0+wMli8v7lrWjuFV96ZufTLYRCGDeP6MVdtZZsjfIz1FqP+0E8FfOUfBg W8euPX5iQ6bdhlgYiJb/gmfISvZSNUpzQbdXCDgRpD/ppFLH8CycJtrVN9AiMWaK v1DD7CDCZogTvCXYYT3atmsmwBcgVMu5D3Ul7RAwng42lukT7/aimYf02W7hqugD /AyNzqseX+iBfHvfwz+PXNPecyVowveb3idRcVLVPVmH1OpcG047rt6qrjw+6oGK G94LC9paC/j0XftGtk+sS8DqLWwVeYXYj+aEAwSZpSNGxyJCqPeSxh4D4Y9aMXwH ktAill7QPacJhqQdYDZdv26qt6tUFsUZ1IM7KC/Wg1hNv4ys2FPBwi6RUPWHqSCD 5nx24sk/9GYILzEA6w5BD9M9A4EDhbFzyxdD+khwV76DVJVbKIntrLBOXMrtVWaz pXsJXLJVHmp0sS+xRMGzVG/eWrCvuP4DJMqr2oVUcjqN2S4R1dikHb/Z/wMIcXPo zGHVbvaNwCgGRoEM4dlYTWrX69yDMGpfB43S6Uh/YwJQjUrxnns= =m/Cz -END PGP SIGNATURE End Message ---
Bug#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
On 5/2/23 08:25, Jonas Smedegaard wrote: Quoting Yadd (2023-05-02 04:58:47) a previous "unblock" was missing here: unstable version is 5.16.5-1 while testing version is 5.16.4-1. What do you want to do, fix only this bug with a 5.16.5-really-5.16.4-1 or a full update ? It is a bugfix release, and as such I would consider it relevant for stable, but I get exhausted just thinking about the need for "defending" changes against the release team: If you do it, you can desice if you want to try get all of it in or only a (arguably too) minimal patch. Thanks! - Jonas For the record, unblock issue is #1035368
Bug#1034994: marked as done (librust-semver-0.9-dev: missing Breaks+Replaces for librust-semver-dev when upgrading from bullseye)
Your message dated Tue, 02 May 2023 06:48:51 + with message-id and subject line Bug#1034994: fixed in rust-semver-0.9 0.9.0-4 has caused the Debian Bug report #1034994, regarding librust-semver-0.9-dev: missing Breaks+Replaces for librust-semver-dev when upgrading from bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-semver-0.9-dev Version: 0.9.0-3+b1 Severity: serious Justification: dpkg unpack error Attempting to unpack librust-semver-0.9-dev/0.9.0-3+b1 from Debian bookworm on a minimal Debian bullseye with librust-semver-dev/0.9.0-1+b1 installed, causes an unpack error from dpkg due to /usr/share/cargo/registry/semver-0.9.0/.cargo-checksum.json being contained in both packages. | Selecting previously unselected package librust-semver-0.9-dev:amd64. | dpkg: considering deconfiguration of librust-semver-dev:amd64, which would be broken by installation of librust-semver-0.9-dev:amd64 ... | dpkg: yes, will deconfigure librust-semver-dev:amd64 (broken by librust-semver-0.9-dev:amd64) | (Reading database ... 4714 files and directories currently installed.) | Preparing to unpack .../librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb ... | De-configuring librust-semver-dev:amd64 (0.9.0-1+b1) ... | Unpacking librust-semver-0.9-dev:amd64 (0.9.0-3+b1) ... | dpkg: error processing archive ./librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb (--unpack): | trying to overwrite '/usr/share/cargo/registry/semver-0.9.0/.cargo-checksum.json', which is also in package librust-semver-dev:amd64 0.9.0-1+b1 | Errors were encountered while processing: | ./librust-semver-0.9-dev_0.9.0-3+b1_amd64.deb Please ensure that librust-semver-0.9-dev has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: rust-semver-0.9 Source-Version: 0.9.0-4 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-semver-0.9, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-semver-0.9 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, 02 May 2023 05:56:10 + Source: rust-semver-0.9 Architecture: source Version: 0.9.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1034994 Changes: rust-semver-0.9 (0.9.0-4) unstable; urgency=medium . * Team upload. * Declare breaks+replaces against physical package instead of virtual one (Closes: #1034994) * Fix autopkgtest + Remove dev-dependency on crates-index and disable "regression" test so that the rest of the tests can run. + Remove dev-dependency on tempfile, it was only used by the "regression" test. + Do not fail the tests due to compiler warnings. Checksums-Sha1: 559b9c4807a99bac20253be158381e1bbea28707 2404 rust-semver-0.9_0.9.0-4.dsc 3a5c402aaf020d193faf275c77eb1cea05b9bafb 3796 rust-semver-0.9_0.9.0-4.debian.tar.xz cc2bd22d7b13da84717f2bc64d1a0daf03342e59 7297 rust-semver-0.9_0.9.0-4_source.buildinfo Checksums-Sha256: 2b935a52ebd33eccc5355420227b5aa8af399dbacfffc07dd4edf5c6fbf6b929 2404 rust-semver-0.9_0.9.0-4.dsc df746fcb29f5f33b6cae1328b674caa057eca9456d17194a2f7fa35da6a7049a 3796 rust-semver-0.9_0.9.0-4.debian.tar.xz a1337fb6308e4415a3f858f7fa3fbee7b3c97e2cbdd356f2fd12d302f8ae34d3 7297 rust-semver-0.9_0.9.0-4_source.buildinfo Files: 755f9fe44bcb101701659c03622e1922 2404 rust optional rust-semver-0.9_0.9.0-4.dsc bfeaabe50adbc367b8376a697821d272 3796 rust optional rust-semver-0.9_0.9.0-4.debian.tar.xz b2d121b9f6ecf67208ffe8d15d1985a0 7297 rust optional rust-semver-0.9_0.9.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmRQrVUUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvRzRAAgMOjHxRvDPJSUBY2TriO36C/LZnU I4ccNThZPHd26crYwPcVV2ffdNuQZCpKdAgDcVvJ12+o+59/juceV0/BRgKkjjQV
Processed: Bug#1034969 marked as pending in node-terser
Processing control commands: > tag -1 pending Bug #1034969 [terser] terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye Added tag(s) pending. -- 1034969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034969: marked as pending in node-terser
Control: tag -1 pending Hello, Bug #1034969 in node-terser 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/js-team/node-terser/-/commit/d1c07253a2d17c302c76c53f24eb31331b6a1959 Duplicate Breaks field with Replaces Closes: #1034969 (this message was generated automatically) -- Greetings https://bugs.debian.org/1034969
