Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: britney
In #947852 or #945840 there were testing->unstable autopkgtest regressions in reverse dependencies that blocked testing migration. Fixing them by fixing the broken reverse dependencies in unstable, or even (auto)removal from testing, does not solve the same problem during upgrades or potentially in backports. The reverse dependency might even have been fixed in testing before the breaking change happened in unstable, which is currently completely missed. It would catch more potential problems in stable->nextstable upgrades and backports usage if stable->unstable autopkgtests would be run and required to pass for testing migration similar to the testing->unstable autopkgtests that are already run. If autopkgtest machine speed is an issue, testing this on amd64 should already catch most problems. It is rare that such incompatibilities are specific to other architectures.
