Subject: Re: bug#27042: test-package.sh fails on aarch64

From: [email-masked] (Ludovic Courtès)
Date: Mon, 10 Jul 2017 11:05:35 +0200

Hi Efraim,

Efraim Flashner <[email-masked]> skribis:

> ./pre-inst-env: 78: exec: guile: not found
>
> guix package -i guile
> ./pre-inst-env guile -c '(use-modules (guix scripts offload))'
>
> guile: warning: failed to install locale
> Backtrace:
> In ice-9/eval.scm:
>    721:20 19 (primitive-eval (use-modules (guix scripts offload)))
> In ice-9/psyntax.scm:
>   1234:36 18 (expand-top-sequence ((use-modules (guix scripts #))) _ ?)
>   1181:24 17 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
>    284:10 16 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) ?)
> In ice-9/boot-9.scm:
>   3369:20 15 (process-use-modules _)
>    230:17 14 (map1 (((guix scripts offload))))
>   3370:31 13 (_ ((guix scripts offload)))
>   2792:17 12 (resolve-interface (guix scripts offload) #:select _ # _ ?)
>   2718:10 11 (_ (guix scripts offload) _ _ #:ensure _)
>   2986:16 10 (try-module-autoload _ _)
>    2316:4  9 (save-module-excursion #<procedure 7b635d0 at ice-9/boo?>)
>   3006:22  8 (_)
> In unknown file:
>            7 (primitive-load-path "guix/scripts/offload" #<procedure?>)
> In guix/scripts/offload.scm:
>      19:0  6 (_)
> In ice-9/boot-9.scm:
>    2866:4  5 (define-module* _ #:filename _ #:pure _ #:version _ # _ ?)
>   2075:24  4 (call-with-deferred-observers #<procedure 7a21190 at ic?>)
>   2879:24  3 (_)
>    230:17  2 (map1 (((ssh key)) ((ssh auth)) ((ssh session)) ((?)) ?))
>    2795:6  1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ ?)
> In unknown file:
>            0 (scm-error misc-error #f "~A ~S" ("no code for modu?" ?) ?)
>
> ERROR: In procedure scm-error:
> ERROR: no code for module (ssh key)

So something is wrong with this environment.  I’m not sure what, but
the fact that Guile and Guile-SSH are sometimes available, sometimes
not, suggests some flakiness.  :-)

It seems that sometimes you used ‘guix environment guix’, sometimes not,
which probably caused some confusion.

Anyway I’m willing to close this bug as “not a bug” because it really
looks like an environment issue and not an aarch64-specific problem.
Fine with you?

Thanks for taking the time to investigate!

Ludo’.