Source: gcc-10-doc Version: 10.1.0-1 Severity: serious Control: close -1 10.2.0-1 Tags: sid bullseye User: [email protected] 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:gcc-10-doc in its current version in unstable has been trying to migrate for 61 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. Packages in main should be build on buildd, and our migration tooling prevents packages from migrating if they contain maintainer built binaries. However, packages in non-free are not built by default, and if they are not, the binaries need to be uploaded manually. I'll try to build the binary package and upload myself soon. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html [2] https://qa.debian.org/excuses.php?package=gcc-10-doc
signature.asc
Description: OpenPGP digital signature
