Like #1064428, copying things here that we discussed on IRC... Sorry if I was unclear. The title is indeed incorrect if the binary takeover is arch:all.
I think the behavior is alright. If that's true, it should probably be tested for, because it might be unexpected and broken by future changes. To reiterate what happens now: If a binNMU occurs on a source, but a different source is taking over one or more of the binaries from the binNMU'd source: * If the taking-over source is okayed to migrate, the takeover occurs. The binNMU is blocked due to "newerintesting". * If the taking-over source is not okay to migrate... - If all of the binaries being taken over are arch-independent, the binNMU is allowed to migrate. (the arch-indep binaries are not changed on a binNMU, but even if they were in a hypothentical situation, I don't believe this behavior would change) - If any binary being taken over is arch-dependent, britney declares the binary from the taking-over source "cruft" in the taken-over source's verdict. If cruft is allowed, the binNMU migrates. If cruft is not allowed, the binNMU is blocked. I hope this helps. Thanks for taking a look!
