From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: James Smith <jsubuntuxp@disroot.org>, 44039@debbugs.gnu.org
Subject: [bug#44039] [PATCH] gnu: Add slade.
Date: Wed, 28 Oct 2020 15:54:31 +0100 [thread overview]
Message-ID: <87y2jq1jvc.fsf@gnu.org> (raw)
In-Reply-To: <87zh4lanh9.fsf@nckx> (Tobias Geerinckx-Rice's message of "Fri, 16 Oct 2020 23:07:46 +0200")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> The following made multiple builds on one machine identical, but was
> not consistent between file systems, probably due to readdir order:
>
> + (add-before 'build 'reset-slade.pk3-timestamps
> + ;; This appears sufficient to make slade.pk3 reproducible.
> + (lambda _
> + (invoke "find" "../source/dist/res" "-exec" "touch"
> + "--no-dereference" "-t" "197001010000.00" "{}" "+")))
It’s surprising that this is necessary because the ‘unpack’ phase copies
the source directory preserving the mtime of files and since those files
are in the store, their mtime is 1:
;; Preserve timestamps (set to the Epoch) on the copied tree so that
;; things work deterministically.
(copy-recursively source "."
#:keep-mtime? #t)
Thoughts?
Anyhow, we can probably push v2.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-10-28 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 18:43 [bug#44039] [PATCH] gnu: Add slade James Smith
2020-10-16 21:07 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-16 21:14 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-17 0:41 ` James Smith
2020-10-28 14:54 ` Ludovic Courtès [this message]
2020-10-29 2:49 ` James Smith
2020-10-29 23:39 ` Ludovic Courtès
2020-10-30 9:38 ` Tobias Geerinckx-Rice via Guix-patches via
2020-10-31 10:01 ` Ludovic Courtès
2021-05-15 20:52 ` James Smith
2021-09-18 17:47 ` [bug#44039] [PATCH v3] " James Smith via Guix-patches via
2021-09-22 14:21 ` bug#44039: [PATCH] " Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2jq1jvc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44039@debbugs.gnu.org \
--cc=jsubuntuxp@disroot.org \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.