From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: help-guix@gnu.org
Subject: Re: Getting rid of "source file [...] newer than compiled" messages
Date: Thu, 11 Apr 2019 09:34:34 -0500 [thread overview]
Message-ID: <87k1g0obk5.fsf@gmail.com> (raw)
In-Reply-To: <87mukwaetg.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Thu, 11 Apr 2019 14:47:55 +0200")
Giovanni Biscuolo <g@xelera.eu> writes:
> synoacl? I cannot find that mount option: are you on a Synology NAS?
Yes.
> AFAIK stripe=32 should not have any impact on mtime, nor data=writeback
>
> I'm using Guix on Debian and my store is in a LV too:
>
> /dev/mapper/vg01-gnu on /gnu type ext4 (rw,relatime)
Hm, OK. That was my best guess.
> I vaguely recall once I had one problem with source scm files newer than
> compiled when using ./pre-inst-env (for sure I did something wrong
> hacking, not directly touching /gnu/store anyway) but "guix gc
> --verify=repair" fixed that for me
This was my expectation too! I am perplexed as to why it doesn't.
> Ricardo also asked you about the daemon: how is it started on your
> machine?
Synology's distro remains on upstart which is what I'm using to start
the daemon:
#+BEGIN_EXAMPLE
$ ps -fC guix-daemon
UID PID PPID C STIME TTY TIME CMD
root 27071 1 0 Apr06 ? 00:00:00 guix-daemon --build-users-group=guixbuild
#+END_EXAMPLE
> HTH! Gio'
Thank you!
--
Katherine
next prev parent reply other threads:[~2019-04-11 14:34 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 [this message]
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=87k1g0obk5.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=g@xelera.eu \
--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).