On 2022-08-05, Francesco P. Lovergine wrote: > On Sun, Jul 17, 2022 at 01:52:46PM +0100, Simon McVittie wrote: >>On Fri, 19 Feb 2021 at 14:38:09 -0800, Vagrant Cascadian wrote: >>> The configure script sets the BASH variable to /bin/sh when run on a >>> usrmerge system, resulting in the pwupdate script differing between >>> builds: >>> >>> >>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/ypserv.html >>> >>> ./usr/lib/yp/pwupdate >>> >>> #!/bin/bash >>> vs. >>> #!/bin/sh >> >>In general, the Debian technical committee resolution >>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#110 recommends >>treating this class of bug as release-critical for Debian 12. >> >>However, without knowing anything about the specifics of this package, >>I'm unsure whether this specific bug is RC or not: will the pwupdate >>script still work correctly with a purely POSIX shell like dash? If it >>does not, then the severity of this bug should be raised to serious. >> >>Regardless of whether this is RC or not, it would be great to have it fixed >>for Debian 12. Vagrant's patch looks appropriate. >> >>Thanks, >> smcv > > The patch looks good enough to fix the pwupdate generation. In any case, the > script seems currently POSIX compliant, so using /bin/bash or /bin/sh looks > indifferent.
Given that it's the BASH variable, I figured using /bin/bash would make more sense and allow consistent builds. Oddly, it appears to be build reproducibly currently even though no source changes happened between bullseye and bookworm (both currently version 4.1-2): https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ypserv.html So something changed back in March ... the toolchain? The reproducible builds infrastructure? hrm. live well, vagrant
signature.asc
Description: PGP signature
