Bug#992028: transition: libidn
On Mon, Aug 30, 2021 at 09:19:07PM +0200, Simon Josefsson wrote:
> Adrian Bunk <bunk@debian.org> writes:
>
> > On Mon, Aug 30, 2021 at 04:03:36PM +0200, Simon Josefsson wrote:
> >>...
> >> Also, there is an arch:all missing build of libidn, is that a real
> >> problem? Should I do a binary upload to correct it? I thought
> >> source-only uploads was sufficient now.
> >
> > There are no packages you could upload, see #993294.
>
> Thanks -- for my learning, is there anywhere I could read about that?
> Is it always required when removing arch:all packages?
That knowledge from observing how the archive and testing migration
software is working right now, in theory what we are seeing is a bug.
dak (archive software) does have automatic cruft removal.
For some time it was too eager to remove cruft, so when the package did
FTBFS on binary-all this often resulted in a round through NEW.
Now it's a bit more cautious, and tends to err on the side of not
removing enough.
britney (testing migration software) used to be a bit too liberal on
letting things migrate, andthere were packages migrating to testing
despite a binary-all FTBFS (sometimes noone notices for months when a
-doc package is missing).
Most likely the release team can force libidn into testing right away,
but that's something they have to tell.
> /Simon
cu
Adrian
Reply to: