I'm not sure if Reinhard received the mail below (don't see him in to/cc). But IOW, Reinhard, you absolutely need to file a RM bug here.
-- Hi Reinhard, On Sat, 11 Oct 2025 06:38:55 -0400 Reinhard Tartler <[email protected]> wrote: > On 2025-10-10 16:28, Mathias Gibbens wrote: > > Thanks for taking care of that, although I think we'll need a > > separate RM bug for [armel armhf i386] before it will be able to > > migrate to testing. > > You might be right. However, that's not my reading of > https://wiki.debian.org/ftpmaster_Removals: > > | The release team can remove source packages - and *all* binaries built > from them - from testing. Per-architecture removals from testing are not > handled by the Release Managers directly, but rather as a result of the > package's state in unstable propagating to testing. What this is meant to say is that the Release Team doesn't handle per architecture removals; testing follows unstable. So per architecture removals need to be done there. > My understanding / assumption is that at some point in the future, > the "auto-decruft" mechanism (cf.> > https://people.debian.org/~nthykier/blog/2015/introducing-dak-auto- decruft.html) > should kick in and remove the remaining msgp binaries with the > version 1.2.5-1+b4 from unstable. After that, britney removes them > from testing and allows the migration. Auto-decruft doesn't handle architecture specific removals (I assume patches are welcome). You'll need to file a RM bug against ftp.debian.org (option 3 seems about right) per source package of which binaries need to be removed. Paul
