Control: severity -1 serious On Fri, 01 Jan 2021 at 17:25:27 -0800, Vagrant Cascadian wrote: > Various files embed paths to "modinfo" and "sh" differently on a > non-usrmerge vs. usrmerge system. > > > https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/diffoscope-results/lirc.html > > /usr/lib/x86_64-linux-gnu/python3.9/site-packages/lirc/config.py > MODINFO·=·"/sbin/modinfo" > vs. > MODINFO·=·"/usr/sbin/modinfo" > > /usr/include/lirc/config.h > #define·SH_PATH·"/bin/sh" > vs. > #define·SH_PATH·"/usr/bin/sh"
This will be a practical problem as soon as Debian starts using merged-/usr on official buildds, and 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, so I'm raising the severity of this bug. The problem scenario is: - build the package on a system where both /bin/sh and /usr/bin/sh exist (merged-/usr) - install and run the package on a system where only /bin/sh exists (non-merged-/usr) - result: the feature that runs sh will not work and the same for modinfo. > The attached patches fix this by patching configure.ac to accept the > MODINFO variable, and passing the SH_PATH and MODINFO variables to > configure. Please upload a fixed package before the Debian 12 freeze. Vagrant's patch looks appropriate. Thanks, smcv
