Debian Bug report logs - #1001872
eiskaltdcpp: reproducible-builds: BuildId differences triggered by RPATH

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@reproducible-builds.org>

To: submit@bugs.debian.org

Subject: eiskaltdcpp: reproducible-builds: BuildId differences triggered by RPATH

Date: Fri, 17 Dec 2021 17:03:46 -0800

[Message part 1 (text/plain, inline)]

Source: eiskaltdcpp
Severity: normal
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid:

  https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/eiskaltdcpp.html

The attached patch to debian/rules passes
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via the CMAKEOPTS variable.  used in
the dh_auto_configure override, which should use a relative path for
RPATH.

With this patch applied, eiskaltdcpp should build reproducibly on
tests.reproducible-builds.org!

Thanks for maintaining eiskaltdcpp!

live well,
  vagrant

[0001-debian-rules-Pass-DCMAKE_BUILD_RPATH_USE_ORIGIN-ON-v.patch (text/x-diff, inline)]

From 0f23fcf76636824aae2490c29699e64f711a60b7 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
Date: Sat, 18 Dec 2021 01:00:06 +0000
Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 CMAKEOPTS variable.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index 0f24cd4..23dfd4b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -30,6 +30,7 @@ CMAKEOPTS = -DUSE_ASPELL=ON \
             -DXMLRPC_DAEMON=OFF \
             -DJSONRPC_DAEMON=ON \
             -DCHECK_GTK_DEPRECATED=OFF \
+            -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \
             -DREPLACE_VERSION="$(DEB_VERSION_UPSTREAM)"
 
 EXCLUDE_FILES = usr/share/eiskaltdcpp/emoticons/*/READ_ME.txt \
-- 
2.34.1

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 1001872-maintonly@bugs.debian.org (full text, mbox, reply):

From: James Addison <jay@jp-hosting.net>

To: undisclosed-recipients:;

Date: Sun, 31 Mar 2024 23:17:33 +0100

Control: severity -1 wishlist

Dear Maintainer,

Currently, Debian's buildd and also the Reproducible Builds team's testing
infrastructure[1] both use a fixed build path when building binary packages.

This means that your package will pass current reproducibility tests; however
we believe that varying the build path still produces undesirable changes in
the binary package output, making it more difficult than necessary for
independent consumers to check the integrity of those packages by rebuilding
them themselves.

As a result, this bugreport will remain open and be re-assigned the 'wishlist'
severity[2].

You can use the 'reprotest' package build utility - either locally, or as
provided in Debian's Salsa continuous integration pipelines - to assist
uncovering reproducibility failures due build-path variance.

For more information about build paths and how they can affect reproducibility,
please refer to: https://reproducible-builds.org/docs/build-path/

Thanks,
James

[1] - https://tests.reproducible-builds.org/debian/reproducible.html

[2] - https://www.debian.org/Bugs/Developer#severities

Message #17 received at 1001872-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1001872-close@bugs.debian.org

Subject: Bug#1001872: fixed in eiskaltdcpp 2.4.2-1.3

Date: Thu, 06 Mar 2025 21:00:36 +0000

[Message part 1 (text/plain, inline)]

Source: eiskaltdcpp
Source-Version: 2.4.2-1.3
Done: Bastian Germann <bage@debian.org>

We believe that the bug you reported is fixed in the latest version of
eiskaltdcpp, 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 1001872@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated eiskaltdcpp 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: Thu, 06 Mar 2025 20:17:55 +0100
Source: eiskaltdcpp
Architecture: source
Version: 2.4.2-1.3
Distribution: unstable
Urgency: medium
Maintainer: Boris Pek <tehnick@debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1001872 1050627 1086098
Changes:
 eiskaltdcpp (2.4.2-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-Depend on libidn-dev. Closes: #1086098
   * Build with lua5.1. Closes: #1050627
   * Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via CMAKEOPTS. Closes: #1001872
Checksums-Sha1:
 00da1715b6f18a24f30c7eb40553b8fc8e98a4bc 2877 eiskaltdcpp_2.4.2-1.3.dsc
 aa3c0a31e0caf845900eecc75143ca27cc1f44fc 13180 eiskaltdcpp_2.4.2-1.3.debian.tar.xz
 fa7e9ce1a64cd8493d7166dfab3a3db3e5ae8891 6256 eiskaltdcpp_2.4.2-1.3_source.buildinfo
Checksums-Sha256:
 16a58dc9072f6a40df88a380e49894e341a2ae0b34ee785ca4c8e2b36cd61cfa 2877 eiskaltdcpp_2.4.2-1.3.dsc
 1811d2cb8950b201ffa04370ecb3618d7967041478de4b06a9ef846cd3dc3497 13180 eiskaltdcpp_2.4.2-1.3.debian.tar.xz
 e024732d53c39ba1e9b66fd0197309ea9ffe0a4d809ac6add10e282408fef735 6256 eiskaltdcpp_2.4.2-1.3_source.buildinfo
Files:
 441d55a37eb2dc8eee8f8daa23caaeb0 2877 net optional eiskaltdcpp_2.4.2-1.3.dsc
 c37d72b57e7688d16b81f45a280526e2 13180 net optional eiskaltdcpp_2.4.2-1.3.debian.tar.xz
 22245f5ddc245db94b511509c035c886 6256 net optional eiskaltdcpp_2.4.2-1.3_source.buildinfo


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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmfJ+ekQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFBnnC/9ZAO90JDSdHpN8/6241MedG9Q3aOz4EVSl
mqUv1VwGlWdB2wTW6TECe/WDh8ipPlfv9OtZATo/30JGs7lpRM2T19bdr2Gx6o2U
b1+WnRGD27Vc1ClfTZRvw4BW7AQK4/is4VoSNKiQM1HavWvrlsoMOVTmkWDlAQR5
RrM+3422gLstytrOGaozsg0P63WyHo03x1LpEyYUGy7O7N8HA2IXE7A8r2vFEqrQ
hdff4QAVD1nmAs1exXI7JBjxHMEPVPDG8Bs+62lhef+tKHcNIeKJbooJFlw1/pw7
c8+StCqIKqjuBDgBhFeipJenvB3X2RZFn5MkIXUfe7XkgVrWYMnj7AXvd82bEMd6
xU19lRLpKHkkcTN/lpEpfgpcJNQy3M910PBW/jsyprNjbM+oDPbY027xT9Dht3wR
6IBwuMXeOmBSHNpwRv3voCLi2SJcIFEAUW9fLkMgPcy43pjtl2/lTr3zN4y5P+vy
yfwNSQ+En/TCz3c6biwY4JdCo7ELeWA=
=bPBj
-----END PGP SIGNATURE-----

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.