Source: libcbor Version: 0.8.0-2 Severity: serious Control: close -1 0.10.2-1 Tags: sid trixie pending User: release.debian....@packages.debian.org Usertags: out-of-sync Control: block -1 by 1052004
Dear maintainer(s),The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:libcbor has been trying to migrate for 31 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 trixie, so it doesn't affect (old-)stable.
Your package is only blocked because the arch:all binary package(s) aren't built on a buildd (bug 1052004). Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/3 (normally 15 in bugs like this, but because of bug 1052004), closing this bug. Please let me know if I should delay or cancel that upload.
Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html [2] https://qa.debian.org/excuses.php?package=libcbor
OpenPGP_signature.asc
Description: OpenPGP digital signature
