How would one implement this in the common Salsa CI pipeline?
There is an old issue for this [0], but unless someone provides an MR its unlikely to get implemented.
Occasional rebuild campaigns like this don't catch regression in a timely manner. Having a build-twice job in the Salsa CI pipeline would help to catch regressions quickly, but it doesn't cover all packages. Better would be a QA service for all uploads to the archive similar to reproducible builds or piuparts to ensure non-policy compliant clean targets are caught quickly.
[0] https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/193 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1