Subject: Re: bug#30602: guix pull failures at and after 0458ab53f6ab58c42f379b8e7d55d130df4232e3

From: [email-masked] (Ludovic Courtès)
Date: Mon, 26 Feb 2018 18:31:10 +0100

Hi again,

Alex ter Weele <[email-masked]> 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’.