From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Getting rid of "source file [...] newer than compiled" messages
Date: Wed, 17 Apr 2019 23:01:02 +0200 [thread overview]
Message-ID: <87zhoo73e9.fsf@gnu.org> (raw)
In-Reply-To: <87k1g1erf6.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 10 Apr 2019 18:49:49 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
>> $ stat /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/hash.go
>> File: ‘/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/hash.go’
>> Size: 77485 Blocks: 152 IO Block: 4096 regular file
>> Device: fc02h/64514d Inode: 137925 Links: 1
>> Access: (0444/-r--r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
>> Access: 2019-04-06 16:56:32.259721626 -0500
>> Modify: 2018-12-25 17:02:43.753150336 -0600
>> Change: 2018-12-25 17:02:43.753150336 -0600
>> Birth: -
>> #+END_EXAMPLE
>>
>> It looks like the scheme file is fractions of a second newer than the
>> compiled file. So, pulling on this thread:
>
> These time stamps are wrong. Everything in /gnu/store should have 0 for
> the mtime.
More precisely the mtime should be 1 (one second after the Epoch).
Also, when using the ‘stat’ command, it’s a good idea to set TZ=UTC to
avoid confusion when looking at the timestamps.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-04-17 21:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 17:55 Getting rid of "source file [...] newer than compiled" messages Katherine Cox-Buday
2019-03-28 21:40 ` Ricardo Wurmus
2019-03-29 1:45 ` Katherine Cox-Buday
2019-03-29 2:46 ` Ricardo Wurmus
2019-03-29 15:21 ` Katherine Cox-Buday
2019-04-06 19:39 ` Katherine Cox-Buday
2019-04-06 20:39 ` Ricardo Wurmus
2019-04-06 21:15 ` Katherine Cox-Buday
2019-04-06 21:24 ` Gábor Boskovits
2019-04-07 3:11 ` Ricardo Wurmus
2019-04-07 17:31 ` Katherine Cox-Buday
2019-04-08 6:43 ` Ricardo Wurmus
2019-04-10 14:31 ` Katherine Cox-Buday
2019-04-10 16:04 ` Andreas Enge
2019-04-10 16:24 ` Katherine Cox-Buday
2019-04-10 16:49 ` Ricardo Wurmus
2019-04-10 18:04 ` Katherine Cox-Buday
2019-04-10 18:22 ` Ricardo Wurmus
2019-04-10 20:20 ` Katherine Cox-Buday
2019-04-11 12:47 ` Giovanni Biscuolo
2019-04-11 14:34 ` Katherine Cox-Buday
2019-04-11 17:16 ` Giovanni Biscuolo
2019-04-17 21:01 ` Ludovic Courtès [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=87zhoo73e9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
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).