From: Maxime Devos <maximedevos@telenet.be>
To: 56893@debbugs.gnu.org
Subject: bug#56893: rust-vergen inserts build timestamps, possible irreproducibility source
Date: Tue, 2 Aug 2022 19:14:54 +0200 [thread overview]
Message-ID: <6db9b36d-3411-5473-68a5-56df714e2c1c@telenet.be> (raw)
In-Reply-To: <c93dc305-6988-95c0-6d8f-4e5e2c733dcb@telenet.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 852 bytes --]
The following phase works around the issue for me (for antioxidant) --
this makes "guix build --check" pass (at least for antioxidant):
> + ;; TODO: SOURCE_DATE_EPOCH support would be nice. Also maybe
> better fit for a snippet?
> + ;;
> + ;; Make the rust-vergen reproducible and avoid causing
> irreproducibility
> + ;; in dependents.
> + ("rust-vergen"
> + ,#~((add-after 'unpack 'remove-timestamp-irreproducibility
> + (lambda _
> + (substitute* (find-files "." "\\.rs$")
> + (("^extern crate chrono;") "extern crate chrono; use
> chrono::Utc; use chrono::TimeZone;")
> + (("^use chrono::Utc;") "use chrono::Utc; use
> chrono::TimeZone;")
Should also work for cargo-build-system, but untested.
Greetings,
Maxime
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-08-02 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 16:57 bug#56893: rust-vergen inserts build timestamps, possible irreproducibility source Maxime Devos
2022-08-02 17:14 ` Maxime Devos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6db9b36d-3411-5473-68a5-56df714e2c1c@telenet.be \
--to=maximedevos@telenet.be \
--cc=56893@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).