Hi Adrian, On 1/4/26 10:43, Adrian Bunk wrote:
A maintainer task relevant to the Release Team not currently covered by our infrastructure are test rebuilds for transitions. Providing this as an optional step in the Salsa CI would be very useful for maintainers.
I assume you mean as a pre-upload check again. I feel you'd be implementing something that debusine is designed to also do (albeit maybe not automated (yet)).
britney2 should still be aware of what to test, otherwise it doesn't know how to interpret results from elsewhere. The simplest design is rather trivial to implement, but the difficulty is to design it such that we don't loose smooth-updates completely. We wouldn't need an extra services to provide the information here. (Well, I imagine proper (archive integrated) bikesheds could help as a means to avoid smooth-updates without the pain. I.e. have a bikeshed for each ongoing transition, such that they can be disentangled while still going on in parallel. But again, that's not salsa.)
Maybe what we could be doing is also test binNMU's and block *their* migration if autopkgtest failures are discovered. At least it would make issues somewhat visible, but transferring that information to transition overviews is probably needed in that case.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
