On 2021-02-21, Andreas Metzler wrote: > On 2021-02-21 Vagrant Cascadian <vagr...@reproducible-builds.org> wrote: >> The paths to various binaries are embedded in /usr/bin/lynx, which >> differs on a usrmerge vs. non-usrmerge system. ... >> Patch attached which passes variables to configure to use the >> non-usrmerge locations, as usrmerge installations typically have >> compatibility symlinks, but not vice-versa. > >> This does not resolve all reproducibility issues (e.g. when /bin/sh >> points to bash), but should reduce some of the noise when comparing the >> differences. > [...] > > Hello, > > Reluctantly applied.
Thanks for applying. > I don't get the point of trying to do reproducible builds on systems > that differ significantly (usrmerge or not), it feels like make-work. I get that, for sure. The current reproducible builds test infrastructure is geared towards finding issues so that we can fix them; some of the issues may seem to be nuanced corner-cases. In the case of usrmerge, both usrmerge and non-usrmerge systems exist in the wild; having fewer variables that affect the build makes it significantly easier to reproduce a build and more resilient. Bugs triggered by building in a usrmerge environment have actually resulted in functionally broken packages in several cases, too, so it does seem to me important to find them early. live well, vagrant
signature.asc
Description: PGP signature
