Package: release.debian.org Severity: normal Usertags: britney Consider the following situation:
test-src migrated after its amd64 and i386 binaries appeared. It also has architecture-independent binaries that miraculously only showed up after migration was complete (maybe someone hinted through the package too early). When this occurs, you might expect the arch:all binaries to migrate normally or to get information from britney why that couldn't happen. Instead, britney2 outputs the empty list in its excuses. This occurs because ExcuseFinder._should_upgrade_srcarch explicitly skips all architecture-independent binaries. If there are no other changes to the source which would cause excuses output, britney says nothing. If the package were binNMU'd, though, britney would migrate everything including the arch:all package if it passed checks. This behavior instability might be undesirable. The code which skips arch:all packages dates all the way back to britney2's original import[1], so it's not clear if it's still load-bearing. I've been researching the reason for the explicit ignore, but I've come up empty. For my part, I removed the descendant of the code[2] and only hit #1064427 when running britney2-tests against it. This may also relate to bugs like #909555, but without a reproduction case I wouldn't hold my breath on that. Should britney be given the ability to test arch:all packages in ExcuseFinder by removing the block of code? If not, should it at least give a REJECTED_CANNOT_DETERMINE_IF_PERMANENT output to help an archive admin figure out what's going on? I've attached a patch to britney2-tests which adds a test case to demonstrate this situation. Thanks, Dalton
0001-New-arch-all-binary-on-migrated-source.patch
Description: Binary data
