Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

intrigeri intrigeri at debian.org
Sun Jun 7 08:11:16 BST 2020


Hi,

gregor herrmann (2020-05-22):
> On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote:
>
>> So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to
>> ask (presumably the release team) for libparse-debianchangelog-perl to
>> lose its "key package" status, so the autoremoval machinery can remove
>> it from testing due to this very RC bug.
>
> Unless we go directly for an RM;RoM bug, then it will be removed from
> testing when it's gone from unstable.

Indeed. This would be my preferred option: it's simpler for everyone
involved, it communicates the maintenance status more clearly, and it
avoids confusion that could lead to new reverse-dependencies to
be uploaded.

I did not dare proposing this course of action so far because the
notes from our BoF at DebConf19 are a bit ambiguous about whether we
decided to remove the package from sid, in addition to removing it
from testing.

If another team member +1's the package removal, I'll happily proceed.

Cheers!



More information about the pkg-perl-maintainers mailing list