From: ludo@gnu.org (Ludovic Courtès)
To: Alex ter Weele <alex.ter.weele@gmail.com>
Cc: 30602@debbugs.gnu.org
Subject: bug#30602: guix pull failures at and after 0458ab53f6ab58c42f379b8e7d55d130df4232e3
Date: Mon, 26 Feb 2018 18:31:10 +0100 [thread overview]
Message-ID: <87lgffvesh.fsf@gnu.org> (raw)
In-Reply-To: <87efl9it32.fsf@librem.i-did-not-set--mail-host-address--so-tickle-me> (Alex ter Weele's message of "Sat, 24 Feb 2018 22:36:17 -0600")
Hi again,
Alex ter Weele <alex.ter.weele@gmail.com> skribis:
> The following derivation will be built:
> /gnu/store/ciawm53ygcvs7gfpb54wpzb4kkgnag9i-guix-latest.drv
> copying and compiling to '/gnu/store/r82flrikwwd6ir0qlbc8ssm1n1m2z9dw-guix-latest' with Guile 2.2.3...
> loading... 25.9% of 667 filesrandom seed for tests: 1519531629
> compiling... 100.0% of 667 files
> Backtrace:
> Exception thrown while printing backtrace:
> In procedure public-lookup: Module named (system repl debug) does not exist
Looking more closely, (system repl debug) is used in one place, (guix ui),
where it’s an #:autoload.
Here the (guix ui) code is failing to load that module, and thus failing
to provide a good backtrace and error message.
However I’m unclear whether the error is on the client side (the ‘guix
pull’ process), or whether it’s on the build side (in the guile process
that builds the derivation.)
Can you paste the output of:
cat $(guix build --log-file /gnu/store/ciawm53ygcvs7gfpb54wpzb4kkgnag9i-guix-latest.drv)
?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-02-26 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 4:36 bug#30602: guix pull failures at and after 0458ab53f6ab58c42f379b8e7d55d130df4232e3 Alex ter Weele
2018-02-25 16:32 ` bug#30602: Status: " Alex ter Weele
2018-02-26 15:04 ` bug#30602: " Ludovic Courtès
2018-02-26 17:31 ` Ludovic Courtès [this message]
2018-02-27 12:07 ` Alex ter Weele
2018-07-29 15:26 ` 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=87lgffvesh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30602@debbugs.gnu.org \
--cc=alex.ter.weele@gmail.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).