From: Ricardo Wurmus <rekado@elephly.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Getting rid of "source file [...] newer than compiled" messages
Date: Mon, 08 Apr 2019 08:43:15 +0200 [thread overview]
Message-ID: <87h8b9f14s.fsf@elephly.net> (raw)
In-Reply-To: <877ec5n2n0.fsf@gmail.com>
Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Oh, well, that’s definitely not right. Guix does not download
>> individual files when fetching packages — it downloads archives that
>> definitely do contain the .go files. So the question is… where did they
>> go once “guix pull” finished?
>
> Yeah, I don't know! Mostly I'm trying to dig into this edge-case of
> trying to get malformed packages back into a known state. I imagine that
> will come up from time to time on users' machines, for various reasons.
>
>> Does “guix gc --verify=repair,contents” (run as root) really not tell
>> you anything useful?
[no repair output]
Hmm.
You said that there are no .go files, yet Guile keeps saying that the
source file
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/hash.scm
is newer than the compiled
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/hash.go
Does the second file really not exist while the first one does?
--
Ricardo
next prev parent reply other threads:[~2019-04-08 6:43 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 [this message]
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
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=87h8b9f14s.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=cox.katherine.e@gmail.com \
--cc=help-guix@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.
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).