From mboxrd@z Thu Jan 1 00:00:00 1970 From: Katherine Cox-Buday Subject: Re: Getting rid of "source file [...] newer than compiled" messages Date: Wed, 10 Apr 2019 15:20:08 -0500 Message-ID: <87o95dobnr.fsf@gmail.com> References: <875zs2313w.fsf@gmail.com> <87imw21jpk.fsf@elephly.net> <87wokh1zc0.fsf@gmail.com> <87k1g6ncss.fsf@gmail.com> <87r2aeg96d.fsf@elephly.net> <87ftqun8ce.fsf@gmail.com> <87mul2fr1x.fsf@elephly.net> <877ec5n2n0.fsf@gmail.com> <87h8b9f14s.fsf@elephly.net> <87wok2ortk.fsf@gmail.com> <20190410160428.GA4187@jurong> <871s29q155.fsf@gmail.com> <87k1g1erf6.fsf@elephly.net> <87sgupohx9.fsf@gmail.com> <87d0lten4u.fsf@elephly.net> 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]:34459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hEJhc-0006cJ-Oz for help-guix@gnu.org; Wed, 10 Apr 2019 16:20:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hEJhb-00040Q-Sv for help-guix@gnu.org; Wed, 10 Apr 2019 16:20:12 -0400 Received: from mail-it1-x133.google.com ([2607:f8b0:4864:20::133]:37626) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hEJhb-0003z0-KV for help-guix@gnu.org; Wed, 10 Apr 2019 16:20:11 -0400 Received: by mail-it1-x133.google.com with SMTP id u65so5692849itc.2 for ; Wed, 10 Apr 2019 13:20:11 -0700 (PDT) In-Reply-To: <87d0lten4u.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 10 Apr 2019 20:22:25 +0200") 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: Ricardo Wurmus Cc: help-guix@gnu.org Ricardo Wurmus writes: > Maybe. But subsequent calls to =E2=80=9Cguix pull=E2=80=9D should give y= ou new store > items anyway, and those should be fine. That's odd. I have definitely run `guix pull` several times on this machine. > Is there anything special about your setup perhaps? E.g. running the > daemon as some other user than root, using btrfs, etc. The store is mounted on a RAID-6 array with an ext4 filesystem. Maybe the striping is confusing things? Here's the mount point: #+BEGIN_EXAMPLE $ mount |grep gnu /dev/mapper/vg1-volume_2 on /gnu type ext4 (rw,relatime,synoacl,stripe=3D= 32,data=3Dwriteback,jqfmt=3Dvfsv0,usrjquota=3Daquota.user,grpjquota=3Daquot= a.group) #+END_EXAMPLE >> I still hold the opinion that the guix toolchain should be able to heal >> store items, regardless of how they got that way, or whether it should >> be theoretically possible. Do you disagree? > > No, I agree with you. That=E2=80=99s one of the reasons why =E2=80=9Cgui= x gc > --verify=3Drepair,contents=E2=80=9D exists. Hm, does this also look at timestamps? Why didn't this give me any output or fix the issue? --=20 Katherine