unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Getting rid of "source file [...] newer than compiled" messages
Date: Fri, 29 Mar 2019 10:21:03 -0500	[thread overview]
Message-ID: <87wokh1zc0.fsf@gmail.com> (raw)
In-Reply-To: <87imw21jpk.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 29 Mar 2019 03:46:15 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

> Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
>
>> I'm not using Guix from a source checkout. I've issued `guix pull` (both
>> under the root account and as my user account) a few times with no
>> change.
>
> Hmm, this should never leave you with an uncompiled Guix.  Can you tell
> us more about the environment in which this happens?  (e.g. the output
> of “env” will be fine.)

Here is an example. When I run `guix help` I receive:

#+BEGIN_EXAMPLE
    ;;; note: source file /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/hash.scm
    ;;;       newer than compiled /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/hash.go
    ;;; note: source file /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/common.scm
    ;;;       newer than compiled /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/common.go
    ;;; note: source file /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/package-config.scm
    ;;;       newer than compiled /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/package-config.go
    ;;; note: source file /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/utils.scm
    ;;;       newer than compiled /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/utils.go
#+END_EXAMPLE

`env` reports:

#+BEGIN_EXAMPLE
    GUIX_LOCPATH=/var/services/homes/me/.guix-profile/lib/locale
    TERM=xterm-256color
    SHELL=/bin/sh
    SSH_CLIENT=[redacted ip] 41856 22
    SSH_TTY=/dev/pts/9
    LC_ALL=en_US.utf8
    USER=me
    GUIX_PROFILE=/var/services/homes/me/.guix-profile
    PAGER=more
    MAIL=/var/mail/me
    PATH=/var/services/homes/me/.guix-profile/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin
    PWD=/var/services/homes/me
    LANG=en_US.utf8
    SHLVL=1
    HOME=/var/services/homes/me
    TERMINFO=/usr/share/terminfo
    LOGNAME=me
    SSH_CONNECTION=[redacted ip] 41856 [redacted ip] 22
    PGDATA=/var/services/pgsql
    XDG_RUNTIME_DIR=/var/services/homes/me/.local/run
    GIT_EXEC_PATH=/var/services/homes/me/.guix-profile/bin
    _=/bin/env
#+END_EXAMPLE

>> `guix` is symlinked from `/usr/local/bin/guix` to
>> `/var/guix/profiles/per-user/root/current-guix/bin/guix` which points to
>> the latest profile (which is updated when running `guix pull` as root.
>
> When using “guix pull” it will install into the current user’s
> ~/.config/guix/current/.  Are you only using Guix as the root user?

No, I always use my user account, but root contains the symlinks for the
daemon and CLI. The symlink for `/usr/local/bin/guix` is there from
installation per step (6) of the manual[1]. I tried running `guix pull`
as root because running it under my user account wasn't doing anything.

Thank you for troubleshooting this with me.

[1] - https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html#Binary-Installation

-- 
Katherine

  reply	other threads:[~2019-03-29 15:21 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 [this message]
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
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=87wokh1zc0.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).