From: Ricardo Wurmus <rekado@elephly.net>
To: Brant Gardner <brantcgardner@brantware.com>
Cc: 28144@debbugs.gnu.org
Subject: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date: Mon, 28 Jan 2019 19:57:45 +0100 [thread overview]
Message-ID: <87h8dsr4nq.fsf@elephly.net> (raw)
In-Reply-To: <ce4c4b43-7f04-47fe-9246-cefc9ea7a1ce@www.fastmail.com>
Brant Gardner <brantcgardner@brantware.com> writes:
> I get this very reproducibly with 'guix pull', starting last
> week. This is on a pretty simple installation of GuixSD, no extra
> parameters or unusual environment. Is there anything I gather that
> would help?
>
> Note: This only seems to happen for the non-root user executing 'guix
> pull' - so far it has not show for root.
That’s because every user has their own version of Guix. The root
user’s copy of Guix differs from that of your other user account.
Could you please tell us what “guix describe” and/or “guix --version”
say? This would help us figure out if we can do something to prevent
this.
You can get out of this problem by using a different variant of Guix to
run “guix pull”, e.g. ~/.config/guix/current-1-link/bin/guix pull.
--
Ricardo
next prev parent reply other threads:[~2019-01-28 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 0:20 bug#28144: info-dir ERROR: no code for module (guix build utils) Christopher Baines
2017-08-22 8:41 ` Ludovic Courtès
2017-08-22 9:59 ` Christopher Baines
2017-08-22 10:41 ` Ludovic Courtès
2017-08-22 11:02 ` Christopher Baines
2017-11-13 10:03 ` Ludovic Courtès
2019-01-28 13:00 ` Brant Gardner
2019-01-28 18:57 ` Ricardo Wurmus [this message]
2019-01-28 22:04 ` Brant Gardner
2019-01-29 21:14 ` swedebugia
2019-01-29 21:17 ` swedebugia
2019-02-01 19:59 ` Brant Gardner
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=87h8dsr4nq.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=28144@debbugs.gnu.org \
--cc=brantcgardner@brantware.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).