On 2019-11-19, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0] we noticed that > intel-gpu-tools could not be built reproducibly. > > This is because it embedded the path to the test directory in the > binary. As we don't even build the tests (according to a comments, > they FTBFS...) my attached patch is almost-certainly harmless. > > Patch attached.
That patch no longer applies due to changes in upstream, but I've attached a new patch that passes a relative source directory from debian/rules, leveraging the upstream changes. Would the maintainers be amendable to an NMU for this fix? I would love to see this land in time for the bookworm freeze... It looks like there is or will be a transition for: https://release.debian.org/transitions/html/auto-procps.html Which might necessitate a bit of delay... live well, vagrant
From 9300b7973cec79f4d33d48f676b7e491ea6d2a8b Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian <vagr...@reproducible-builds.org> Date: Thu, 1 Dec 2022 21:20:56 +0000 Subject: [PATCH] debian/rules: Pass relative source directory for reproducible builds. (Closes: #945105) --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index ef422d80..a0dfcccd 100755 --- a/debian/rules +++ b/debian/rules @@ -17,7 +17,7 @@ override_dh_clean: # FIXME: building debugger causes FTBFS override_dh_auto_configure: dh_auto_configure -- \ - -Dtests=disabled + -Dtests=disabled -Dsrcdir=. # Disable test suite: override_dh_auto_test: -- 2.38.1
signature.asc
Description: PGP signature
