Control: severity -1 serious On Fri, 18 Dec 2020 at 16:23:25 -0800, Vagrant Cascadian wrote: > The problem with hard-coding at build time is unfortunately it produces > packages that only work with systems with the same path locations, and > at least on Debian systems, both usrmerge and non-usrmerge systems exist > in the real world.
> On 2020-12-18, Keith Winstein wrote: > > I am curious -- why is it important that builds be identical between > > usrmerge systems and non-usrmerge systems? > > Because /usr/sbin/iptables is only present on usrmerge systems, if you > hard-code the paths, then it will only work on usrmerge systems. There > are typically compatibility symlinks /sbin -> /usr/sbin, so hard-coding > the other way around is ... less bad... :) 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 /sbin/iptables and /usr/sbin/iptables exist (merged-/usr) - install and run the package on a system where only /sbin/iptables exists (non-merged-/usr) - result: the feature that runs iptables will not work or the equivalent for ip. Please upload a fixed package before the Debian 12 freeze. Vagrant's patch looks appropriate. Thanks, smcv
