From: Gary Johnson <lambdatronic@gmail.com>
To: help-guix@gnu.org
Subject: Re: Error with guix pull
Date: Sat, 16 Dec 2017 15:50:12 -0500 [thread overview]
Message-ID: <87lgi2l7nf.fsf@gmail.com> (raw)
In-Reply-To: <87d13jopml.fsf@gnu.org>
I tried running "guix pull" again after I got your message, but I
actually got a different error that time. (Unfortunately, I didn't take
the time to save it.) Anyway, I ran "guix pull" again today, and this
time it worked, so I guess the problem has been resolved.
Thanks,
Gary
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Gary,
>
> Gary Johnson <lambdatronic@gmail.com> skribis:
>
>> I tried running "guix pull" today, and at the end of the compilation
>> phase, I was presented with this error:
>>
>> --8<-------------------------------------------------------------->8--------
>> copying and compiling to '/gnu/store/29nci1d7zykwriwhnpxqivilbi6cr8wc-guix-latest' with Guile 2.2.3...
>> loading... 26.1% of 656 filesrandom seed for tests: 1513007529
>> compiling... 100.0% of 656 files
>> Backtrace:
>> Exception thrown while printing backtrace:
>> In procedure public-lookup: Module named (system repl debug) does not exist
>> --8<-------------------------------------------------------------->8--------
>
> This is a bug that apparently manifests itself randomly when building
> with Guile 2.2.3, as was the case here. (I suspect it has to do with
> thread-safety in the presence of autoloaded modules.)
>
> We’ve switched back to using 2.2.2 in ‘guix pull’ to address
> <https://bugs.gnu.org/29570>. Can you try running ‘guix pull’ again?
>
> Thanks in advance,
> Ludo’.
prev parent reply other threads:[~2017-12-16 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 16:14 Error with guix pull Gary Johnson
2017-12-12 16:52 ` Ludovic Courtès
2017-12-16 20:50 ` Gary Johnson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgi2l7nf.fsf@gmail.com \
--to=lambdatronic@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.