Source: corosync
Version: 2.4.4-3
Severity: normal
Tags: patch
User: m...@linux.it
Usertags: usrmerge
Dear Maintainer,
The package currently fails to build reproducibly on a merged-usr vs
non-merged system. This is caused by looking up the full path of
bash via PATH and embedding it in a shipped file.
The problem can be easily fixed by explicitly telling configure
which path to use via the BASHPATH variable.
Please see attached debdiff.
Regards,
Andreas Henriksson
diff -Nru corosync-2.4.4/debian/changelog corosync-2.4.4/debian/changelog
--- corosync-2.4.4/debian/changelog 2018-04-22 16:47:13.000000000 +0200
+++ corosync-2.4.4/debian/changelog 2018-12-01 21:53:13.000000000 +0100
@@ -1,3 +1,11 @@
+corosync (2.4.4-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Pass BASHPATH=/bin/bash to configure
+ - fixes reproducible build on merged-usr vs non-merged
+
+ -- Andreas Henriksson <andr...@fatal.se> Sat, 01 Dec 2018 21:53:13 +0100
+
corosync (2.4.4-3) unstable; urgency=high
* High urgency because 2.4.4 still hasn't reached testing yet.
diff -Nru corosync-2.4.4/debian/rules corosync-2.4.4/debian/rules
--- corosync-2.4.4/debian/rules 2018-04-22 16:46:21.000000000 +0200
+++ corosync-2.4.4/debian/rules 2018-12-01 21:53:11.000000000 +0100
@@ -36,6 +36,7 @@
override_dh_auto_configure:
dh_auto_configure -- \
+ BASHPATH=/bin/bash \
--with-initconfigdir=/etc/default \
--with-logdir=/var/log/corosync \
--enable-dbus \
