Source: argus Version: 2:5.0.2-1 Tags: patch User: [email protected] Usertags: ftcbfs
argus checks for presence of /var/lib/dbus/machine-id during build and changes its build depending on its presence or absence. This is bad for reproducibility as the build environment needs to replicate that presence or absence, but cannot know it. It also is bad for cross building as AC_CHECK_FILE makes the build fail hard. I propose forcing a test result here. On Debian buildds, the file tends to be absent. Once forced, the build no longer depends on the build environment in this regard and cross builds work again. I'm attaching a patch for your convenience. Helmut
diff --minimal -Nru argus-5.0.2/debian/changelog argus-5.0.2/debian/changelog --- argus-5.0.2/debian/changelog 2025-04-07 19:36:34.000000000 +0200 +++ argus-5.0.2/debian/changelog 2025-04-22 20:37:28.000000000 +0200 @@ -1,3 +1,10 @@ +argus (2:5.0.2-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Don't check for /var/lib/dbus/machine-id during build. (Closes: #-1) + + -- Helmut Grohne <[email protected]> Tue, 22 Apr 2025 20:37:28 +0200 + argus (2:5.0.2-1) unstable; urgency=low * New upstream version diff --minimal -Nru argus-5.0.2/debian/rules argus-5.0.2/debian/rules --- argus-5.0.2/debian/rules 2025-04-07 19:36:34.000000000 +0200 +++ argus-5.0.2/debian/rules 2025-04-22 20:37:25.000000000 +0200 @@ -7,6 +7,10 @@ DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/default.mk +# This file may or may not exist in the build environment and influences the +# build result. On Debian buildds it tends to be missing. +export ac_cv_file__var_lib_dbus_machine_id=no + %: dh ${@}
