From lamby at debian.org Mon May 4 18:25:54 2026 From: lamby at debian.org (Chris Lamb) Date: Mon, 04 May 2026 10:25:54 -0700 Subject: Bug#1135692: dkimpy: please make the build reproducible Message-ID: <177791540162.2151.2592120319902720868@1aa6728684b5> Source: dkimpy Version: 1.1.8-2 Severity: wishlist Tags: patch User: reproducible-builds at lists.alioth.debian.org Usertags: nocheck X-Debbugs-Cc: reproducible-bugs at lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that dkimpy could not be built reproducibly. This is because the testsuite bumps the modification time of the /dkim/tests/ directory to the current time (which later gets clamped back to SOURCE_DATE_EPOCH), so if the tests are skipped via nocheck, then this directory will retain its original, upstream timestamp. Instead of saving upstream's original timestamp and restoring that later, I've attached a patch to always set the mtime of this directory to SOURCE_DATE_EPOCH regardless of whether the tests are run or not. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` lamby at debian.org / chris-lamb.co.uk `- -------------- next part -------------- --- a/debian/rules 2026-05-04 10:17:20.879056947 -0700 --- b/debian/rules 2026-05-04 10:23:07.588586989 -0700 @@ -7,6 +7,7 @@ override_dh_auto_build: execute_before_dh_auto_install: + touch -d@$(SOURCE_DATE_EPOCH) $(CURDIR)/dkim/tests/ python3 $(CURDIR)/setup.py install --install-layout=deb \ --root $(CURDIR)/debian/python3-dkim