Migrate form reprotest to debrebuild?
I've been discussing with @jspricke about the how to improve the reprotest job, and this issue is meant to continue our discussion and involve other fellows in the loop. The main question is if it we should rely on debrebuild instead of reprotest to verify the reproducibility in Salsa CI.
reprotest has some limitations, as described in #351 (comment 542573). Additionally, with the buildd move to unshare, reprotest is needing to include support for it (sbuild+unshare?). So given the current status of the virtualization backends, it is indeed worth to consider moving to a better supported tool.
One of my questions/concerns is about the way how the reproducibility is verified. reprotest runs a control build and a test build that includes variations. I was willing to get rid of the control build (See: #118). From my understanding, it is more valuable from the reproducibility check PoV to test if some variations in the build environment still produce the same result from the main build jobs. Is that (still) accurate? We could still run two different jobs, one that just tries to reproduce the same build environment, and the other that includes different variations. But I was happy to save some CPU time...
Any thoughts?