From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: Getting rid of "source file [...] newer than compiled" messages Date: Sat, 6 Apr 2019 23:24:58 +0200 Message-ID: References: <87ef6q3muf.fsf@gmail.com> <87lg0y1xut.fsf@elephly.net> <875zs2313w.fsf@gmail.com> <87imw21jpk.fsf@elephly.net> <87wokh1zc0.fsf@gmail.com> <87k1g6ncss.fsf@gmail.com> <87r2aeg96d.fsf@elephly.net> <87ftqun8ce.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hCsoL-0004ZX-JJ for help-guix@gnu.org; Sat, 06 Apr 2019 17:25:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hCsoJ-0007ov-M2 for help-guix@gnu.org; Sat, 06 Apr 2019 17:25:13 -0400 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]:33988) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hCsoJ-0007nt-6f for help-guix@gnu.org; Sat, 06 Apr 2019 17:25:11 -0400 Received: by mail-ed1-x52d.google.com with SMTP id x14so8425689eds.1 for ; Sat, 06 Apr 2019 14:25:11 -0700 (PDT) In-Reply-To: <87ftqun8ce.fsf@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Katherine Cox-Buday Cc: help-guix Hello Katherine, Katherine Cox-Buday ezt =C3=ADrta (id=C5=91pont= : 2019. =C3=A1pr. 6., Szo, 23:16): > > Ricardo Wurmus 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