Hi Petter, Thanks for reaching out.
On 21-11-2021 11:11, Petter Reinholdtsen wrote:
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.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 <URL: 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?
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
