On Fri, Feb 05, 2021 at 07:55:50AM +0100, Rafael Laboissière wrote: >... > If I > understand correctly, the right way to cope with the issue is to contact > individually the maintainers of each architecture with FTBFS and ask them to > upload a correctly built binary package. This will have to be done for each > new release of the package. >...
This was never the correct action, and since the start of the bullseye release cycle, binaries that were not built on the buildds are blocked from entering testing.[1] The only problem for testing migration are stale old binaries on an architecture, if a package never built on a release architecture or after removal of the stale binaries FTBFS on some architectures are not a problem for testing migration. > Best, > > Rafael cu Adrian [1] packages in contrib and non-free are exceptions
