Groups | Search | Server Info | Login | Register
Groups > linux.debian.maint.hams > #11427
| From | "Chris Lamb" <lamby@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.maint.hams |
| Subject | Bug#1136297: pycayennelpp: please make the build reproducible |
| Date | 2026-05-11 18:40 +0200 |
| Message-ID | <MTBPH-4oac-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Source: pycayennelpp
Version: 2.4.0-3
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
pycayennelpp could not be built reproducibly.
This is because the testsuite bumps the modification time of the
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@debian.org / chris-lamb.co.uk
`-
Back to linux.debian.maint.hams | Previous | Next | Find similar
Bug#1136297: pycayennelpp: please make the build reproducible "Chris Lamb" <lamby@debian.org> - 2026-05-11 18:40 +0200
csiph-web