From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: 55758@debbugs.gnu.org
Subject: [bug#55758] reproducible builds: keyutils: avoid embedding timestamp
Date: Sat, 04 Jun 2022 10:39:40 +0200 [thread overview]
Message-ID: <87sfokg6ur.fsf@gnu.org> (raw)
In-Reply-To: <877d60au45.fsf@contorta> (Vagrant Cascadian's message of "Wed, 01 Jun 2022 15:36:58 -0700")
Hi,
Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
> Alternately, one could hard-code a specific timestamp (e.g. 2012-04-18),
> or patch it to use the SOURCE_DATE_EPOCH environment variable (which
> might at least be acceptible to submit upstream), although since
> SOURCE_DATE_EPOCH is always 0 in guix, this seems a bit silly to me. :)
Yup. :-)
> From 36888e9dc33188115142ecde9d31eb3884004940 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@reproducible-builds.org>
> Date: Wed, 1 Jun 2022 09:24:00 -0700
> Subject: [PATCH 3/4] gnu: keyutils: Avoid embedding build timestamp.
>
> * gnu/packages/crypto.scm (keyutils)[arguments]: Add
> 'avoid-embedding-timestamp phase.
LGTM, thanks!
Ludo’.
next prev parent reply other threads:[~2022-06-04 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 22:36 [bug#55758] reproducible builds: keyutils: avoid embedding timestamp Vagrant Cascadian
2022-06-04 8:39 ` Ludovic Courtès [this message]
2022-06-06 5:26 ` bug#55758: " Vagrant Cascadian
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=87sfokg6ur.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55758@debbugs.gnu.org \
--cc=vagrant@reproducible-builds.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).