Bug#1002360: zope.exceptions: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Source: zope.exceptions Version: 4.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:237: python3.10 setup.py config > running config > I: pybuild base:237: python3.9 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:237: /usr/bin/python3.10 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope > copying src/zope/__init__.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope > creating > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/__init__.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/exceptionformatter.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/interfaces.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/log.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions > creating > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions/tests > copying src/zope/exceptions/tests/__init__.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions/tests > copying src/zope/exceptions/tests/test_log.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions/tests > copying src/zope/exceptions/tests/test_exceptionformatter.py -> > /<>/.pybuild/cpython3_3.10_zope.exceptions/build/zope/exceptions/tests > running egg_info > writing src/zope.exceptions.egg-info/PKG-INFO > writing dependency_links to src/zope.exceptions.egg-info/dependency_links.txt > writing namespace_packages to > src/zope.exceptions.egg-info/namespace_packages.txt > writing requirements to src/zope.exceptions.egg-info/requires.txt > writing top-level names to src/zope.exceptions.egg-info/top_level.txt > reading manifest file 'src/zope.exceptions.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE.txt' > writing manifest file 'src/zope.exceptions.egg-info/SOURCES.txt' > I: pybuild base:237: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope > copying src/zope/__init__.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope > creating > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/__init__.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/exceptionformatter.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/interfaces.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions > copying src/zope/exceptions/log.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions > creating > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions/tests > copying src/zope/exceptions/tests/__init__.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions/tests > copying src/zope/exceptions/tests/test_log.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions/tests > copying src/zope/exceptions/tests/test_exceptionformatter.py -> > /<>/.pybuild/cpython3_3.9_zope.exceptions/build/zope/exceptions/tests > running egg_info > writing src/zope.exceptions.egg-info/PKG-INFO > writing dependency_links to src/zope.exceptions.egg-info/dependency_links.txt > writing namespace_packages to > src/zope.exceptions.egg-info/namespace_packages.txt > writing requirements to src/zope.exceptions.egg-info/requires.txt > writing top-level names to src/zope.exceptions.egg-info/top_level.txt > reading manifest file 'src/zope.exceptions.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE.txt' > writing manifest file 'src/zope.exceptions.egg-info/SOURCES.txt' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:237: python3.10 setup.py test > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > writing src/zope.exceptions.egg-info/PKG-INFO > writing dependency_links to src/zope.exceptions.egg-info/dependency_links.txt > writing namespace_packages to > src/zope.exceptions.egg-info/namespace_packages.txt > writing requirements to src/zope.exceptions.egg-info/requires.txt > writing top-level names to src/zop
Bug#568176: memtest86+: multiboot image is broken
Hi, I'm working on a new build for debian experimental with version 5.31b work done for now about memtest86+ package is here: https://salsa.debian.org/debian/memtest86plus/-/commits/debian/experimental for now multiboot patch is disabled, I don't have knowledge about assembly and the boot part except a little something done years ago that I hardly remember anything about, I don't have enough time recently to read up and study the parts. For some tests I can try to adapt the patch from coreboot that is the most recent I found: https://review.coreboot.org/plugins/gitiles/memtest86plus/+/8cc1aeb540a02d9600491ca5fa799b7c8f25c363 but I don't know if adapt and make it applicable and build working is enough to have multiboot correct and don't cause bugs (from an ubuntu issue on launchpad seems that ubuntu binaries have more issue that same upstream version and major of source changes is multiboot patch, so can be a cause of issue, I'm not sure) Is there anyone with enough knowledge about it that want help me get the correct multiboot part for 5.31b for experimental please? OpenPGP_signature Description: OpenPGP digital signature
Wir bitten um Ihre aktive Zustimmung
Miles & More Wir bitten um Ihre aktive Zustimmung Der Bundesgerichtshof (BGH) hat am 27. April 2021 entschieden, dass eine Klausel in Allgemeinen Geschäftsbedingungen unwirksam ist, nach der Schweigen auf ein Änderungsangebot als Zustimmung verstanden wird (die sogenannte Zustimmungsfiktion). Das Urteil wirkt sich auch auf Ihre von der Deutschen Kreditbank AG ausgegebene Lufthansa Miles & More Credit Card aus. Wie in unserer Nachricht in Ihrem Postfach angekündigt, bitten wir Sie deshalb um Ihre Zustimmung zu den aktuellen Preisen und Bedingungen Ihrer Lufthansa Miles & More Credit Card und zu der Änderung der Ziffer 25 der Allgemeinen Geschäftsbedingungen für die Lufthansa Miles & More Credit Card Nur so können wir Ihnen weiterhin Ihre vertraute und leistungsstarke Lufthansa Miles & More Credit Card anbieten sowie unsere bestehende Geschäftsbeziehung in bekannter Weise und auf einer rechtlich gültigen Grundlage fortführen. Die Vertragsbedingungen haben wir Ihnen hier verlinkt und auch in Ihrem Online-Kartenkonto im Postfach unter „Vertragsinformationen“ eingestellt. Ggf. geltende Sonderkonditionen für Mitarbeitende stehen ausschließlich im Online-Kartenkonto bereit. Was müssen Sie jetzt tun? Bitte bestätigen Sie durch nur einen Klick auf den nachfolgenden Button, dass Sie unseren Vertragsbedingungen zustimmen. Diese sind dann ab 15. Februar 2022 gültig. Ja, ich bin einverstanden Wichtig für Sie zu wissen: Unsere Konditionen bleiben gleich. Die aktuellen Preise und Bedingungen entsprechen unverändert dem Ihnen zuletzt mitgeteilten Stand. In Folge des BGH-Urteils möchten wir nur die Art und Weise ändern, wie wir mit Ihnen zukünftig Vertragsanpassungen vereinbaren. Ihre Zustimmung gilt für alle Ihre Lufthansa Miles & More-Credit Cards. You can also choose more convenient or secure ways to sign in, like using your Google or GitHub account or configuring two-factor authentication (2FA). https://www.digitalocean.com/docs/accounts/profile/#sign-in-method
Bug#965855: marked as done (unadf: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Wed, 22 Dec 2021 17:25:17 + with message-id and subject line Bug#965855: fixed in unadf 0.7.11a-5 has caused the Debian Bug report #965855, regarding unadf: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unadf Version: 0.7.11a-4 Severity: normal Usertags: compat-5-6-removal Hi, The package unadf uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: unadf Source-Version: 0.7.11a-5 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of unadf, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated unadf 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: Wed, 22 Dec 2021 18:05:25 +0100 Source: unadf Architecture: source Version: 0.7.11a-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Stephen Kitt Closes: 965855 Changes: unadf (0.7.11a-5) unstable; urgency=medium . * QA upload. * Upgrade to debhelper compatibility level 13. Closes: #965855. * Remove remote monitoring from the FAQ. * Enable all hardening options. * Update debian/watch to point at the current repository. * Set “Rules-Requires-Root: no”. * Standards-Version 4.6.0, no further change required. Checksums-Sha1: 8b55c0e6866b5ffc7e6ddfe46cf501b54de3dc4b 1741 unadf_0.7.11a-5.dsc 31a316e4e200dcbdc947c6f626b618bdaf946789 18464 unadf_0.7.11a-5.debian.tar.xz b6d7f5e3f9462764f72c71a2fb84a503b418f33a 6380 unadf_0.7.11a-5_source.buildinfo Checksums-Sha256: 97f3ab43bd33214bd512994c7e7436a48c5588208968d723c475a8558e4c85a0 1741 unadf_0.7.11a-5.dsc 4c117cc82cd12d6449ecb78fe9860371b18525013040e5fd40a6e6fd58e50422 18464 unadf_0.7.11a-5.debian.tar.xz c15456e7e002292ab03f12a611a7a5ed340d5cbd96c12a1b3b31ba0cd5e00540 6380 unadf_0.7.11a-5_source.buildinfo Files: 289ae512e3f2794ce2f4b65d2f3f69cb 1741 utils optional unadf_0.7.11a-5.dsc 086b30767c0bd2af51121e58fb19605c 18464 utils optional unadf_0.7.11a-5.debian.tar.xz 174d564d5016b92eea4dc65a95288dc9 6380 utils optional unadf_0.7.11a-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHDWt0RHHNraXR0QGRl Ymlhbi5vcmcACgkQgNMC9Yhtg5wSrQ/+L03C80g3Dc+NS1fJUONPHrCbPiHiEA9y GS+dnSVlfTBOrWdF972abzzf7n2KYHBZm0tnBrov9hxC1NJA4BTs+dzOOpcUbKh+ v+s8069LmuBEubrHu6wa//zBkDhmVB6JblC1CWMe3BjmLYvUh4XaTlKHjgmiqhlU jgj0LJjtkd3KnEsaCr3EUTxKo6FrGQmb+pIi80Ikkl4kptqVsDQRDY1SbP3onW1f LR10n7qeakW19djbaxr5FdvZKr2UBRgN8CQH2HleNBie7t1ljSA22OULPF3cYQY/ Vqx9cgp4sLdL574qaEZvX0lQ7m5oaTGhGmzqGXpKi4s62HVMyeiQ+Ouz8Cec1H2S 5BkirBS5lw8ZZ5GMW6hOUoWaxRP8v2/XzgWIU7b0MLedHBGGDGcB7X/GQBXtZOI7 n3i9MDN9y8lJuUypIVaG+xavOAgopjxpFHoQuyl6zslyQeqK4KhpHoXETFKBC43M RHtcaJqxZBI5+/kbPfY2hONKzZ+j6sshRJHAy1dV/bA89U4r3cCA7YfrueSKYuNk 9aEnt9K4aekINznnSzFun09nKP29qtp6+NrfB5hQtyXBIyS7vlDSraMObDwJaq2l 0
Processed: closing 915167
Processing commands for cont...@bugs.debian.org: > close 915167 Bug #915167 [src:unadf] unadf FTCBFS: does not pass cross tools to make Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 915167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 915167 in unadf/0.7.11a-5
Processing commands for cont...@bugs.debian.org: > fixed 915167 unadf/0.7.11a-5 Bug #915167 [src:unadf] unadf FTCBFS: does not pass cross tools to make The source unadf and version 0.7.11a-5 do not appear to match any binary packages Marked as fixed in versions unadf/0.7.11a-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 915167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of unadf_0.7.11a-5_source.changes
unadf_0.7.11a-5_source.changes uploaded successfully to localhost along with the files: unadf_0.7.11a-5.dsc unadf_0.7.11a-5.debian.tar.xz unadf_0.7.11a-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
unadf_0.7.11a-5_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Dec 2021 18:05:25 +0100 Source: unadf Architecture: source Version: 0.7.11a-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Stephen Kitt Closes: 965855 Changes: unadf (0.7.11a-5) unstable; urgency=medium . * QA upload. * Upgrade to debhelper compatibility level 13. Closes: #965855. * Remove remote monitoring from the FAQ. * Enable all hardening options. * Update debian/watch to point at the current repository. * Set “Rules-Requires-Root: no”. * Standards-Version 4.6.0, no further change required. Checksums-Sha1: 8b55c0e6866b5ffc7e6ddfe46cf501b54de3dc4b 1741 unadf_0.7.11a-5.dsc 31a316e4e200dcbdc947c6f626b618bdaf946789 18464 unadf_0.7.11a-5.debian.tar.xz b6d7f5e3f9462764f72c71a2fb84a503b418f33a 6380 unadf_0.7.11a-5_source.buildinfo Checksums-Sha256: 97f3ab43bd33214bd512994c7e7436a48c5588208968d723c475a8558e4c85a0 1741 unadf_0.7.11a-5.dsc 4c117cc82cd12d6449ecb78fe9860371b18525013040e5fd40a6e6fd58e50422 18464 unadf_0.7.11a-5.debian.tar.xz c15456e7e002292ab03f12a611a7a5ed340d5cbd96c12a1b3b31ba0cd5e00540 6380 unadf_0.7.11a-5_source.buildinfo Files: 289ae512e3f2794ce2f4b65d2f3f69cb 1741 utils optional unadf_0.7.11a-5.dsc 086b30767c0bd2af51121e58fb19605c 18464 utils optional unadf_0.7.11a-5.debian.tar.xz 174d564d5016b92eea4dc65a95288dc9 6380 utils optional unadf_0.7.11a-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHDWt0RHHNraXR0QGRl Ymlhbi5vcmcACgkQgNMC9Yhtg5wSrQ/+L03C80g3Dc+NS1fJUONPHrCbPiHiEA9y GS+dnSVlfTBOrWdF972abzzf7n2KYHBZm0tnBrov9hxC1NJA4BTs+dzOOpcUbKh+ v+s8069LmuBEubrHu6wa//zBkDhmVB6JblC1CWMe3BjmLYvUh4XaTlKHjgmiqhlU jgj0LJjtkd3KnEsaCr3EUTxKo6FrGQmb+pIi80Ikkl4kptqVsDQRDY1SbP3onW1f LR10n7qeakW19djbaxr5FdvZKr2UBRgN8CQH2HleNBie7t1ljSA22OULPF3cYQY/ Vqx9cgp4sLdL574qaEZvX0lQ7m5oaTGhGmzqGXpKi4s62HVMyeiQ+Ouz8Cec1H2S 5BkirBS5lw8ZZ5GMW6hOUoWaxRP8v2/XzgWIU7b0MLedHBGGDGcB7X/GQBXtZOI7 n3i9MDN9y8lJuUypIVaG+xavOAgopjxpFHoQuyl6zslyQeqK4KhpHoXETFKBC43M RHtcaJqxZBI5+/kbPfY2hONKzZ+j6sshRJHAy1dV/bA89U4r3cCA7YfrueSKYuNk 9aEnt9K4aekINznnSzFun09nKP29qtp6+NrfB5hQtyXBIyS7vlDSraMObDwJaq2l 0WoZvVE9Yv1zYyhz1AlJDU5iWh4C0MzP76TtHcjJoHWARjjiCWDYMbl+chnpdM6v uH4/KGXlwJA= =cdOy -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of brandy_1.20.1-2_source.changes
brandy_1.20.1-2_source.changes uploaded successfully to localhost along with the files: brandy_1.20.1-2.dsc brandy_1.20.1-2.debian.tar.xz brandy_1.20.1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
brandy_1.20.1-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Dec 2021 19:05:50 +0100 Source: brandy Architecture: source Version: 1.20.1-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Stephen Kitt Closes: 965442 Changes: brandy (1.20.1-2) unstable; urgency=medium . * QA upload. * Orphan the package (see #990610). * Upgrade to debhelper compatibility level 13. Closes: #965442. * Enable all hardening options. * Set “Rules-Requires-Root: no”. * Switch to a machine-readable debian/copyright. * Drop the obsolete dpkg-dev build-dependency. * Standards-Version 4.6.0, no further change required. Checksums-Sha1: 98d9b5e0bb9fe74d24d6d8caae01517227607b0b 1761 brandy_1.20.1-2.dsc 0ecfbe2d3acce4a7959201e7b1416dc6a8566b67 5380 brandy_1.20.1-2.debian.tar.xz 1ec9f62b7a6ded6c902ef47b523a3b1f2b3b7e4b 9853 brandy_1.20.1-2_source.buildinfo Checksums-Sha256: 92b0fec856a6352ce6c45e30226bdbbcae5b64503889b2b2320a74002022890f 1761 brandy_1.20.1-2.dsc 32ddb19e1a95cb5ca33aa0cd16b6f77c429860b03274e9f076e5a479ba4c7861 5380 brandy_1.20.1-2.debian.tar.xz f82da6cccbe885c17e714ed81b6b9ec84e3976b0d3b9238046d7e7e4466db5ad 9853 brandy_1.20.1-2_source.buildinfo Files: 514f7470e12c2877d62f0c632ce2d8df 1761 interpreters optional brandy_1.20.1-2.dsc fec71d2719a291be894f926805771af8 5380 interpreters optional brandy_1.20.1-2.debian.tar.xz bd645a08bd1cc61533f3ba1da3847882 9853 interpreters optional brandy_1.20.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHDaQURHHNraXR0QGRl Ymlhbi5vcmcACgkQgNMC9Yhtg5zyBw//ZAd2suaYA3Y8EwZ9KYksheZDX/hJjmWW M7odGlcwZOhae3JenmU24+DXMZlhwGyqX1XsHNXTe29fo5FjGwoyNLVbgzGcs7AX pca2roxRDncDq7q7Ttlock47H7xQXQGjTck2n0YgcWWSLko66av873rKtkiNgWqv CxF5VH815QFDwhjhkbqRg76k9oOl73MniWky3X+p4YOr8YKxtpYecT4uW08dhIRW ubHtRJg+nwaAEPxsuuY2GmVQNCBa1ra8UjyweytJR/6/jpnIs1w2foT22oWmO0WC AL4PWpUXyTFxfretkPKdb/i9D1zKWiNeo5x8NoetQ4FwI0FHDDl6MxPTQP8F+m1R sDsLsQjd69+d3vKu9QSf60e/zYqEek7sVKbKa2TvlDxJ1GMpSog9lGGXR7adkB9j ZlOGZRhl9rQKVMkZeMuKTQealrhdDXO3Ys6NTCxZL4TAgKHpi8zvT5zxijuG9t1d yMyQ9ab5UJ4bQCr/0hRjwTR5A2r3x/st8gUBU4rZBWRvwwnyDQcQiDVk7CMvQFjY e1IvX+8/GGSFAIvarCnNkzbKcEwpJsERlotw1F+MaYolzziIrgSIwEqCoEPFpvhO PYs7cvcfHw2zziFJ8Xtbv3XIxFK9xJ1kAP8U+P0xnD/4WTLsKnwwcY1bNUBjimYZ W0PL1JBu7yQ= =u+b7 -END PGP SIGNATURE- Thank you for your contribution to Debian.
toxic is marked for autoremoval from testing
toxic 0.11.1-3 is marked for autoremoval from testing on 2022-01-27 It (build-)depends on packages with these RC bugs: 1001711: libtoxcore2: Stack-based buffer overflow vulnerability in UDP packet handling in Toxcore (CVE-2021-44847) https://bugs.debian.org/1001711 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
