Control: reopen -1 Control: severity -1 serious On Fri, 24 Jun 2022 at 13:12:07 +0000, Debian Bug Tracking System forwarded: > * d/rules: specify PATH for build so unmerged usr paths are discovered > first (Closes: #915850).
Sorry, this does not solve the problem. More precisely, it solves the problem as originally reported (for cp, rm, lvcreate, etc.), but also causes the opposite problem for tools that are canonically in /usr/bin (rsync, ssh, logger, du, perl). (It also seems to have interfered with the generation of an automatic dependency on perl:any.) You can see this in: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/rsnapshot.html where the first build (b1) was done on an unmerged-/usr system, and the second build (b2) on a merged-/usr system for comparison. 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 to serious. The problem scenario with 1.4.2-1 was: - build the package on a system where both /bin/cp and /usr/bin/cp exist (merged-/usr) - install and run the package on a system where only /bin/cp exists (non-merged-/usr) - result: the feature that runs cp will not work and the problem scenario with 1.4.4-2 is similar, but with /bin and /usr/bin reversed: - build the package on a system where both /bin/perl and /usr/bin/perl exist (merged-/usr) - install and run the package on a system where only /usr/bin/perl exists (non-merged-/usr) - result: the feature that runs perl will not work Please upload a fixed package before the Debian 12 freeze. Reverting the PATH change, and applying Andreas' patch instead, looks appropriate. Thanks, smcv
