unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Getting rid of "source file [...] newer than compiled" messages
Date: Sat, 6 Apr 2019 23:24:58 +0200	[thread overview]
Message-ID: <CAE4v=piO=a8g+usrgYyNp_pLVU1c_wbzZMeCpevNuTSLk=iOnw@mail.gmail.com> (raw)
In-Reply-To: <87ftqun8ce.fsf@gmail.com>

Hello Katherine,

Katherine Cox-Buday <cox.katherine.e@gmail.com> ezt írta (időpont:
2019. ápr. 6., Szo, 23:16):
>
> Ricardo Wurmus <rekado@elephly.net> writes:
>
> > This is really odd and I cannot reproduce this.  I wonder if this might
> > be related to some unusual file system choices or settings that cause
> > Guile to think that the source files are more recent.
>
> I have accepted that I have somehow gotten myself into a dark corner of
> Guix! I was expecting there to be a Guix command that would basically
> get any package back into a good state. I was kind of surprised that
> `guix build --check` or `guix build --repair` didn't help me out. My
> expectation was that maybe this would check the hash of the store with
> upstream and rebuild or redownload a substitute.
>

I believe you might be looking looking for guix gc --verify, and
suboptions thereof.
https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-gc.html

Does that help?

> > Can you show us the mtime of these files?  In my case both the scm and
> > the go files all have their mtime as 1970-01-01 01:00:01.000000000
> > +0100.
>
> One interesting point might be that there are no `.go` files. I would
> argue Guile's error message here could use some care, but even a better
> error message won't get me to a better spot :)
>
> Thanks again for the time, Ricardo.
>
> --
> Katherine
>

Best regards,
g_bor

  reply	other threads:[~2019-04-06 21:25 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 [this message]
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

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='CAE4v=piO=a8g+usrgYyNp_pLVU1c_wbzZMeCpevNuTSLk=iOnw@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --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).