Bug#993125: src:pcp: fails to migrate to testing for too long: RC bug
Hi Petter, Thanks for reaching out. On 21-11-2021 11:11, Petter Reinholdtsen wrote: 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. According to https://tracker.debian.org/pkg/pcp >, the auto-removal is not cancelled when this issue is fixed in unstable: * Migration status for pcp (5.2.6-1 to 5.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression * Issues preventing migration: * Removal request by auto-removals * Trying to remove package, not update it * Additional info: * Updating pcp fixes old bugs: #993125 * Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcp.html * 11 days old (needed 10 days) * Not considered What more is a package maintainer supposed to do to get the package to migrate to testing? This is one of the imperfections of the autoremoval process [1]. I'm pretty sure that pinging this bug was the right thing to do as it *should* reset the timer for autoremovals a bit and the removal hint should be gone for some days and the package should migrate. I'll keep an eye on it. If the autoremoval hint is still there tomorrow, I'll force it a bit. Paul [1] The case being a package where the autoremoval counter reached zero, so the autoremoval scripts starts generating remove hints, but the removal doesn't happen because, in this case, a new reverse dependency showed up which has its own timer (which isn't expired yet). OpenPGP_signature Description: OpenPGP digital signature
Bug#993125: src:pcp: fails to migrate to testing for too long: RC bug
[Paul Gevers] > 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. According to https://tracker.debian.org/pkg/pcp >, the auto-removal is not cancelled when this issue is fixed in unstable: * Migration status for pcp (5.2.6-1 to 5.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression * Issues preventing migration: * Removal request by auto-removals * Trying to remove package, not update it * Additional info: * Updating pcp fixes old bugs: #993125 * Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcp.html * 11 days old (needed 10 days) * Not considered What more is a package maintainer supposed to do to get the package to migrate to testing? -- Happy hacking Petter Reinholdtsen
Bug#993125: src:pcp: fails to migrate to testing for too long: RC bug
Source: pcp Version: 5.2.6-1 Severity: serious Control: close -1 5.3.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 990223 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:pcp has been trying to migrate for 77 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 bookworm, 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/msg5.html [2] https://qa.debian.org/excuses.php?package=pcp OpenPGP_signature Description: OpenPGP digital signature
