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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

intrigeri-4
Hi,

[hidden email] (2019-07-26):
> Therefore, at the pkg-perl BoF today at DebConf, after pondering other
> options such as orphaning this package, we decided that we don't want
> this package to be included in Bullseye (at least, maintained under
> the Perl team umbrella) unless someone else steps up and becomes its
> upstream maintainer. [...]

> libparse-debianchangelog-perl has quite a few reverse-dependencies, [...]

10 months later, we've reached the point when there's 1 single
reverse dependency left in sid: customdeb, whose maintainer promptly
agreed it can be removed at the same time as libparse-debianchangelog-perl.
All other previous reverse dependencies were ported to something else
(most often libdpkg-perl) and nobody volunteered to adopt it upstream.

Thanks a lot to everyone who participated in making this happen :)

In testing there's another reverse-dependency: aptitude, which has
been ported away from libparse-debianchangelog-perl in 0.8.13-1.

So, once aptitude >= 0.8.13-1 has migrated to testing, I think it'll
be time to ensure libparse-debianchangelog-perl itself is removed from
testing, which was the goal of the whole operation.

But:

> Note that libparse-debianchangelog-perl is on the list of key
> packages┬╣ so this RC bug won't trigger the autoremoval machinery for
> it, nor for any of its reverse dependencies.
>
> [1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi

libparse-debianchangelog-perl is on the list of key packages because
it's installed on many machines ("popcon"). This will prevent the
autoremoval machinery from removing it from testing.

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.

Cheers!

Reply | Threaded
Open this post in threaded view
|

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

intrigeri-4
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!

Reply | Threaded
Open this post in threaded view
|

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

intrigeri-4
Hi,

Axel Beckert (2020-06-07):
> Since Guillem cleared up this and even provided a patch for aptitude
> (which is applied and in testing for a week or two), I changed my
> opinion on this topic completely.
>
>> If another team member +1's the package removal, I'll happily proceed.
>
> Seconded. :-)

Thanks!

ROM bug filed: #962521