From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Timestamps in ...-autoloads.el files
Date: Sat, 14 Nov 2015 23:39:03 +0300 [thread overview]
Message-ID: <87fv08l3iw.fsf@gmail.com> (raw)
In-Reply-To: <87r3jsvd1a.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 14 Nov 2015 16:03:29 +0100")
Ludovic Courtès (2015-11-14 18:03 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Ludovic Courtès (2015-11-03 16:27 +0300) wrote:
>
> [...]
>
>>>> + ;; Avoid non-determinism related to generated timestamps.
>>>> + (setenv "SOURCE_DATE_EPOCH" "1")
>>>> +
>>>> ;; The trick is to #:allow-other-keys everywhere, so that each procedure in
>>>> ;; PHASES can pick the keyword arguments it's interested in.
>>>> (every (match-lambda
>>>
>>> Yes, as simple as this.
>>
>> Great, thanks! I see that you used (setenv "SOURCE_DATE_EPOCH" "0") in
>> 'tk-update' commit, so I also changed the value to "0".
>
> Oh, good point. I don’t know if it matters much (for Python it seems to
> make no difference), but I think “1” is the safest choice because the
> mtime on files in the store is set to 1, not 0. I’ll fix that in
> ‘tk-update’.
I see, thanks for explaining.
>>>>> Could you also submit it upstream, Cc’ing guix-devel and
>>>>> reproducible-builds@lists.alioth.debian.org? Hopefully that is
>>>>> acceptable. (I searched a bit but didn’t find a similar patch by the
>>>>> Debian Reproducible team, but patch-tracker.debian.org is unreachable.)
>>>>
>>>> I'm afraid it's a too hard task for me, sorry. I wouldn't like to mail
>>>> to so many places.
>>>
>>> Or email only emacs-devel if you prefer.
>>>
>>> An experienced Emacs hacker like you shouldn’t have to be afraid of that.
>>
>> After fighting with myself for all these days, I must admit I'm not
>> brave enough for this task yet, sorry.
>
> You’re not the one to be sorry. It tells more about the weaknesses of
> the Emacs developer community than about yours.
Oh, no, no; it's totally me. I have problems with communicating with
people.
> I’ll post it if you don’t mind.
Yes, please, it would be a great relief for me, thank you!
>> From a99fb41a7b84dd28c1a5b3f53cf14ca3c43785e7 Mon Sep 17 00:00:00 2001
>> From: Alex Kost <alezost@gmail.com>
>> Date: Sat, 14 Nov 2015 14:04:43 +0300
>> Subject: [PATCH 1/2] build-system/gnu: Set 'SOURCE_DATE_EPOCH'.
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: 8bit
>>
>> Suggested by Ludovic Courtès <ludo@gnu.org>.
>>
>> * guix/build/gnu-build-system.scm (gnu-build): Set SOURCE_DATE_EPOCH for
>> deterministic builds.
>
> [...]
>
>> + ;; Avoid non-determinism related to generated timestamps.
>> + (setenv "SOURCE_DATE_EPOCH" "0")
>
> OK with that set to 1.
Fixed and pushed, thanks.
--
Alex
next prev parent reply other threads:[~2015-11-14 20:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 23:09 Challenge substitute servers! Ludovic Courtès
2015-10-20 0:17 ` Daniel Pimentel
2015-10-20 14:38 ` [PATCHES] emacs: Changes for 'guix challenge' Alex Kost
2015-10-20 14:58 ` Ludovic Courtès
2015-10-20 17:40 ` Timestamps in ...-autoloads.el files Alex Kost
2015-10-20 19:38 ` Ludovic Courtès
2015-10-21 13:05 ` Alex Kost
2015-10-21 16:55 ` Ludovic Courtès
2015-11-02 16:50 ` Alex Kost
2015-11-03 13:27 ` Ludovic Courtès
2015-11-14 11:32 ` Alex Kost
2015-11-14 15:03 ` Ludovic Courtès
2015-11-14 20:39 ` Alex Kost [this message]
2016-05-11 14:53 ` Alex Kost
2016-05-16 12:45 ` Ludovic Courtès
2016-05-16 20:52 ` Alex Kost
2016-05-17 9:12 ` Ludovic Courtès
2016-05-19 16:29 ` Alex Kost
2016-05-20 12:02 ` Ludovic Courtès
2016-05-20 13:38 ` Leo Famulari
2016-05-21 10:49 ` Alex Kost
2016-05-21 21:02 ` Ludovic Courtès
2016-05-24 9:07 ` Alex Kost
2016-05-20 21:14 ` Alex Kost
2016-05-19 8:12 ` Alex Kost
2016-05-19 12:56 ` Ludovic Courtès
2016-05-21 10:31 ` Alex Kost
2016-05-21 21:01 ` Ludovic Courtès
2016-05-24 9:00 ` Alex Kost
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=87fv08l3iw.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).