From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 44257@debbugs.gnu.org, drkrider@gmail.com
Subject: bug#44257: guix boot stop
Date: Wed, 28 Oct 2020 18:31:42 +0100 [thread overview]
Message-ID: <87zh46xnnl.fsf@nckx> (raw)
In-Reply-To: <20201028162431.GB12095@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Well, since this is the Internet...
Leo Famulari 写道:
> The timestamps are reset to "zero" (the first date possible on
> Unix
> systems) as part of Guix's efforts to build everything
> reproducibly.
The manual does claim as much (in (guix)Binary Installation) but
it's never been true:
$ stat -c %Y /gnu/store/arbitrary.file
1
0 is a valid value:
$ touch -d @0 /tmp/foo
$ stat -c %Y /tmp/foo
0
But (IIRC) it's a dangerous one to use in practice as too much
code assumes it never occurs in the wild, and use it to mean
something special for internal use. IIRRC GNU make was (once?)
one such culprit.
I shall patch the manual and make this an actionable bug after
all.
Thanks,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-28 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 14:23 bug#44257: guix boot stop Douglas Linford
2020-10-27 16:25 ` Julien Lepiller
2020-10-27 18:13 ` Douglas Linford
2020-10-28 14:21 ` Ludovic Courtès
2020-10-28 14:55 ` Douglas Linford
2020-10-28 16:24 ` Leo Famulari
2020-10-28 16:32 ` Douglas Linford
2020-10-28 16:45 ` Leo Famulari
2020-10-28 17:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-10-28 18:00 ` Leo Famulari
2020-10-28 18:28 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-28 16:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-28 16:45 ` Douglas Linford
2020-10-28 17:11 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-28 17:43 ` Julien Lepiller
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=87zh46xnnl.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=44257@debbugs.gnu.org \
--cc=drkrider@gmail.com \
--cc=leo@famulari.name \
--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 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).