Re: Removing more packages from unstable
Le Tue, Aug 20, 2024 at 07:28:52AM +0200, Helmut Grohne a écrit :
>
> please allow me to open a can of worms. Package removal from unstable.
Hi all,
I think that package removal from Unstable, total or partial (for
instance, 32-bit architectures) should be an automated self-sevice
system for leaf packages. And it should be permitted to batch-request
transitive leaf package removals where B becomes leaf after A is
removed.
As of today, removing a package involves mailing the BTS and therefore
not knowing if the message arrived until the acklonledgement is
received, and not knowing when the acknowledgement will be sent. Then
the waiting time for the action is undetermined. Then the
acknowledgement message for removal can arrive together with a couple
hundred emails like mass-bug-fillings (like GCC updates) and autoremoval
warnings, with the risk of of deleting the important information together
with the batch.
So as of today, it is much less work to keep a package rotting than
removing it.
Maybe interface for the self-service system could be a simple text file
in a Salsa repository writeable to all DDs. This would provide obvious
accountability, and allow filters and monitoring to be implemented if
needed.
Have a nice day,
Charles
Reply to: