[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#977319: marked as done (slurm-wlm: reproducible builds: Binaries contain embedded paths from usrmerge systems)

Your message dated Thu, 18 Feb 2021 00:33:25 +0000
with message-id <E1lCXG1-000BCa-Rr@fasolo.debian.org>
and subject line Bug#977319: fixed in slurm-wlm 20.11.3-3
has caused the Debian Bug report #977319,
regarding slurm-wlm: reproducible builds: Binaries contain embedded paths from usrmerge systems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
977319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977319
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: slurm-wlm
Severity: normal
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Several binaries shipped with slurm-wlm include embedded paths to the
"su" and "sleep" commands:

  https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/diffoscope-results/slurm-wlm.html

  200 Could·not·locate·command:·/bin/su
  201 Could·not·locate·command:·/usr/bin/su

The attached patch fixes this in debian/rules by passing variables to
the configure script that specify using the locations in /bin, as this
is the most compatible path.


Thanks for maintaining slurm-wlm!


live well,
  vagrant

From 9358f54ddf5c36f9c83a056464a58455191a6686 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
Date: Sun, 13 Dec 2020 22:15:20 +0000
Subject: [PATCH] debian/rules: Pass SUCMD and SLEEP_CMD to configure.

The path to "su" and "sleep" are embedded in the binaries, which may
be /bin/CMD or /usr/bin/CMD depending on if the running system is a
usrmerge system or not. Consistently use /bin/CMD as this is the most
compatible path.

https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/rules b/debian/rules
index b84d25ab..90060bf0 100755
--- a/debian/rules
+++ b/debian/rules
@@ -26,8 +26,8 @@ override_dh_auto_clean:
 # hardening-no-fortify-functions
 # Notice that -g in CFLAGS is still provided by dpkg-buildflags
 override_dh_auto_configure:
-	dh_auto_configure -- --sysconfdir=/etc/slurm --with-munge --enable-pam --without-rpath --disable-debug --enable-multiple-slurmd --with-pmix=/usr/lib/$(DEB_HOST_MULTIARCH)/pmix2 $(ENABLEDEPRECATED)
-	dh_auto_configure --builddirectory build-emulator -- -sysconfdir=/etc/slurm --with-munge --enable-pam --without-rpath --disable-debug --enable-front-end --enable-multiple-slurmd --with-pmix=/usr/lib/$(DEB_HOST_MULTIARCH)/pmix2 $(ENABLEDEPRECATED)
+	dh_auto_configure -- --sysconfdir=/etc/slurm --with-munge --enable-pam --without-rpath --disable-debug --enable-multiple-slurmd --with-pmix=/usr/lib/$(DEB_HOST_MULTIARCH)/pmix2 $(ENABLEDEPRECATED) SUCMD=/bin/su SLEEP_CMD=/bin/sleep
+	dh_auto_configure --builddirectory build-emulator -- -sysconfdir=/etc/slurm --with-munge --enable-pam --without-rpath --disable-debug --enable-front-end --enable-multiple-slurmd --with-pmix=/usr/lib/$(DEB_HOST_MULTIARCH)/pmix2 $(ENABLEDEPRECATED) SUCMD=/bin/su SLEEP_CMD=/bin/sleep
 override_dh_auto_build:
 	dh_auto_build
 	dh_auto_build --builddirectory build-emulator
-- 
2.20.1

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: slurm-wlm
Source-Version: 20.11.3-3
Done: Gennaro Oliva <oliva.g@na.icar.cnr.it>

We believe that the bug you reported is fixed in the latest version of
slurm-wlm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977319@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gennaro Oliva <oliva.g@na.icar.cnr.it> (supplier of updated slurm-wlm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 17 Feb 2021 21:24:19 +0100
Source: slurm-wlm
Architecture: source
Version: 20.11.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team <debian-hpc@lists.debian.org>
Changed-By: Gennaro Oliva <oliva.g@na.icar.cnr.it>
Closes: 977319
Changes:
 slurm-wlm (20.11.3-3) unstable; urgency=medium
 .
   * Pass SUCMD and SLEEP_CMD to configure (Closes: #977319)
Checksums-Sha1:
 f2254fc40180fa4bbd2a80c69dbc033356ba893d 3767 slurm-wlm_20.11.3-3.dsc
 c8e75d4072704b271a7b7e0e376e925d41f15f32 134080 slurm-wlm_20.11.3-3.debian.tar.xz
 49b36a8d9c66a8af0de4c6526e6ec87d6cb6c679 21886 slurm-wlm_20.11.3-3_amd64.buildinfo
Checksums-Sha256:
 99f8953b68aba9914aeba2d12655127ceea05dd9374a2d0b930e904f02e9838a 3767 slurm-wlm_20.11.3-3.dsc
 dfa2257b501e0e31ebffae2173ed02c6578e6ea0f1cddd4545a595f39262f097 134080 slurm-wlm_20.11.3-3.debian.tar.xz
 1922ebc0df03bf4d3b98b9b0f1dc2389d4443e4131c4ad501d96f2f893fbf958 21886 slurm-wlm_20.11.3-3_amd64.buildinfo
Files:
 c9f8a393e2c6c498a7b082257fcd22cd 3767 admin optional slurm-wlm_20.11.3-3.dsc
 6e0fa5f6afe2c307c77f48231c5e4600 134080 admin optional slurm-wlm_20.11.3-3.debian.tar.xz
 263aac9a8b9884de5ae37c3f14d4d6fd 21886 admin optional slurm-wlm_20.11.3-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJLBAEBCgA1FiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmAtjsUXHG9saXZhLmdA
bmEuaWNhci5jbnIuaXQACgkQffpBrZYZhddW8w//XtDQEv1gnY+TgT5Ozj/8QkHA
wL/2PykNJoyphu3GUxLbnpQFHgR5xLBOueCaMLUZ+8bIawwtW7UE53f/DwivNZK0
WCqqxi0RnA3DIcNu1qkCqOdmx5KrqyIvCeraR6qQDpUWfgl2BVlWJpHe+gGM8uUc
sfHG3czpFLH6fLAT5bxjiQ2SUP1tH6QbB8DrjM8r7T4nNvvyCTaxd0qsPv/9xZL2
LfOhRKm7fsqFxtQLWwv6wEP4AVfQ27zlvUnBOSYCUwDum45oeilDZBydUN4laQsb
Z6yWHTTVSkndrsZgCzQQlt1uFgwvAF8IjZFrd7CTivGH6JzsJF5eVnKspIbbcMey
vo68rf/LeWyU+0LTT6u3DDV/s/aRD3u4nj/+WzcWgUPikydhIiXmEFoVeCirukrn
j2aFftweB+MnDymEUf83ADyMImxuJ90GJGUzWrWmv8cilHPCagarjcOqFLMZLj09
kbC+CVs1ST44e4cPVNvFnoZBVJCmXTWwnizyky+ATLNTrtWqmPuGdiizxX2CNX9N
qNwz9zMh3ENhAECW3SDBGfB1+Gyt/Ed+JcdYAD4bGP2fHp4tn2c6h3mB4xOjbR7I
lCxJf52lPZ53Z7N46AB7kJ30aqAjFz4jyLaRjVDD8Zzt4gy+n50qn7Dh/IEeEPR1
+FjdzVHqY1A+kSshAfg=
=9IbH
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: