* Andreas Metzler <ametz...@bebt.de> [241231 06:59]: > On 2024-12-29 Helmut Grohne <hel...@subdivi.de> wrote: > > On Sun, Dec 29, 2024 at 01:08:49PM +0100, Ansgar 🐱 wrote: > [...] > >> I would also like to do something similar to unstable; maybe start with > >> packages uploaded before some arbitrary date that are also not included > >> in any of oldstable/stable/testing. These can cause problems like > >> wasting time to investigate cruft removals, build failures, ... > > >> Does that seem reasonable as well? > > > I earlier proposed unstable removals and am now operating a > > semi-automatic unstable auto remover. Its semantics are as follows. > > > Consider packages that have an rc bug in unstable that hasn't been > > interacted with within one year and where the package in question is not > > part of stable nor testing and is not a key package. For each of those > > packages file an important removal suggestion bug. Reassign such bugs to > > ftp.d.o as RM/RoQA bugs to ftp after a month of idleness. This seems to > > work out quite well and I removed more than 100 source packages this > > way. > > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=helmutg%40debian.org&tag=sidremove > > Feedback welcome. > [...] > > Good morning, > > I think this needs a mechanism fo excempt packages which are kept > out of testing *intentionally* with a dummy rc bug (like firefox's > #817954).
Thats this usertag: https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=helm...@debian.org&tag=sidremove-ignore C.