Your message dated Tue, 19 Jan 2021 20:38:24 +0000 with message-id <e1l1xlg-000iom...@fasolo.debian.org> and subject line Bug#973789: fixed in parsinsert 1.04-10 has caused the Debian Bug report #973789, regarding src:parsinsert: fails to migrate to testing for too long: FTBFS on armel, armhf, mips64el and ppc64el 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.) -- 973789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: parsinsert Version: 1.04-7 Severity: serious Control: close -1 1.04-9 Tags: sid bullseye User: release.debian....@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:parsinsert in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html [2] https://qa.debian.org/excuses.php?package=parsinsert
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Source: parsinsert Source-Version: 1.04-10 Done: Étienne Mollier <etienne.moll...@mailoo.org> We believe that the bug you reported is fixed in the latest version of parsinsert, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier <etienne.moll...@mailoo.org> (supplier of updated parsinsert 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, 19 Jan 2021 19:36:40 +0100 Source: parsinsert Architecture: source Version: 1.04-10 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team <debian-med-packag...@lists.alioth.debian.org> Changed-By: Étienne Mollier <etienne.moll...@mailoo.org> Closes: 973789 976929 Changes: parsinsert (1.04-10) unstable; urgency=medium . * Team upload. * Remove unused CFLAGS from 020_hardening.patch; makefile less confusing. * d/rules: reduce CXXFLAGS to optimization level -O1 on armel, armhf, ppc64el, mips64el and riscv64, which otherwise would output incorrect results. (Closes: #973789, #976929) * Standards-Version: 4.5.1 (routine-update) Checksums-Sha1: ce556eecbc586505d367f9b44db1ae591544f113 2103 parsinsert_1.04-10.dsc 5bb5e7408dad199763cc8b32ac16643523147d72 2827616 parsinsert_1.04-10.debian.tar.xz 5c435498b3865e366c9f18f3610d4ae6a73de74a 6244 parsinsert_1.04-10_amd64.buildinfo Checksums-Sha256: b832a9bd157644d4f4af6f6e87813df380e4bdcd14b80ff10aac161f9f245830 2103 parsinsert_1.04-10.dsc 278830d3e00e5046f20526c9cfd2d9df8c24783f35ea887a4f98f2f71ad10074 2827616 parsinsert_1.04-10.debian.tar.xz a6b6495cba0bd05b07e8a73b2eead49bc16c2db2de763abdaeed7c40c2a964c1 6244 parsinsert_1.04-10_amd64.buildinfo Files: 0d6c6601587714cf15d16c7433d9aecc 2103 science optional parsinsert_1.04-10.dsc b8031a6e036b026bea7d959af116c0b8 2827616 science optional parsinsert_1.04-10.debian.tar.xz 23d7ba128effdd62d8312b26ae7cab39 6244 science optional parsinsert_1.04-10_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmAHOFQUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafHgfg//aoKkVqTp7y5kFzv68Tt6Ej87WuF5 7t7lPH2KwDN1gGLdfZx2/3BU4WADkusDRlJ9epe9+XSl7g9ml7m4cobWr9k+TllL zDCWPEN+gSloKuChoXaH8XkSmFSTFrCtP/KyL3yQXs0/UbK/VVmG0qtE+oZMB9xD Uy8Yf2E2Ry1MaWQobRgNZAKyVhHJgeJlYoqtAvjatlxUgQTGh+3JACEpbAZ+FVtT j7Ae+fRPmUyiZ7C8fQUtXgNj3o6wkcJ5tSjLGd7pUDdtAI96R3R4CPkupY05h8aO NhpUCBehKHfYMSLPlH83kthMDzDBZNs//KSf8euhlNNhW0qTErR/GcJ0zYfPVbd0 7pAedhcooTZS7vlZL8HQsH3UbXYtBY0uLgjHPVPJmReDWfNDfYdHii0BI62OCkCY Ykw0K/EgwnQdwnAMOCVKfrVXcNNXT95/yKj8H9A+7oMBtg7nG79siooQlijQSn3W B0ldr4JwnvL+uV/p2WdxzvrJhowleW2/DS5q6K5OJnCpDptI3TFUjWCnLrM8m1/d 4ls1HiSKJr2zQV6BWIQPoYepNMITpxOOUseD5ZmjPRZcdhqCsErZQHOPUDkrjWT+ 7eyGZvwbSBZIB8IvypJVh8stTLJv8z824pXPjGwH9mz+51cqbiLAFOm9U072jFwS Az920BHnD9DGdb0= =o4Ku -----END PGP SIGNATURE-----
--- End Message ---
