bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#64745: [guix-past] channel derivation broken after recent u-boot upd


From: Maxim Cournoyer
Subject: bug#64745: [guix-past] channel derivation broken after recent u-boot update
Date: Fri, 21 Jul 2023 11:35:46 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)

Hi Ludovic,

Thanks a lot for the prompt resolution.

Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> It appears that the Guix-Past channel now fails to build like so:
>>
>> substitute: ^Msubstitute: ESC[Kupdating substitutes from
>> 'https://ci.guix.gnu.org'...  0.0%^Msubstitute: ESC[Kupdating
>> substitutes from 'https://ci.guix.gnu.org'... 100.0%
>> substitute: ^Msubstitute: ESC[Kupdating substitutes from
>> 'https://bordeaux.guix.gnu.org'...  0.0%^Msubstitute: ESC[Kupdating
>> substitutes from 'https://bordeaux.guix.gnu.org'... 100.0%
>> @ build-started
>> /gnu/store/5gxx0xnrncdg5rsi00j4bvy4frxpd466-guix-past.drv -
>> x86_64-linux
>> /var/log/guix/drvs/5g//xx0xnrncdg5rsi00j4bvy4frxpd466-guix-past.drv
>> 4536
>> (repl-version 0 1 1)
>> (exception unbound-variable (value #f) (value "Unbound variable:
>> ~S") (value (crust-pine64-plus)) (value #f))
>> builder for
>> `/gnu/store/5gxx0xnrncdg5rsi00j4bvy4frxpd466-guix-past.drv' failed
>> to produce output path
>> `/gnu/store/hwfy6kbh8q7v9ljam99gfzaz46lf3i8z-guix-past'
>> @ build-failed
>> /gnu/store/5gxx0xnrncdg5rsi00j4bvy4frxpd466-guix-past.drv - 1
>> builder for
>> `/gnu/store/5gxx0xnrncdg5rsi00j4bvy4frxpd466-guix-past.drv' failed
>> to produce output path
>> `/gnu/store/hwfy6kbh8q7v9ljam99gfzaz46lf3i8z-guix-past'
>>
>> I suspect it's caused by the commit
>> ed5dc3a25d858a394bb7db937a51d866c3cdc6ed ("gnu: u-boot: Add crust
>> firmware to pinebook, pine64_plus and pine64-lts."), although I don't
>> understand why.
>
> This can be reproduced like so:
>
> $ guix time-machine --commit=a4038c4f783b05040cfdb262d9f4c0119b612371 -- repl 
> <(echo '(use-modules (gnu packages firmware))')
> Backtrace:
> In ice-9/boot-9.scm:
>    222:29 19 (map1 (((gnu packages acl)) ((gnu packages admin)) ((gnu 
> packages assembly)) ((gnu packages attr)) ((gnu packages autotools)) ((gnu 
> packages backup)) ((gnu # #)) # …))
>    222:29 18 (map1 (((gnu packages admin)) ((gnu packages assembly)) ((gnu 
> packages attr)) ((gnu packages autotools)) ((gnu packages backup)) ((gnu 
> packages base)) ((gnu # #)) # …))
>    222:29 17 (map1 (((gnu packages assembly)) ((gnu packages attr)) ((gnu 
> packages autotools)) ((gnu packages backup)) ((gnu packages base)) ((gnu 
> packages bash)) ((gnu # #)) # …))
>    222:29 16 (map1 (((gnu packages attr)) ((gnu packages autotools)) ((gnu 
> packages backup)) ((gnu packages base)) ((gnu packages bash)) ((gnu packages 
> bison)) ((gnu # #)) ((…)) …))
>    222:29 15 (map1 (((gnu packages autotools)) ((gnu packages backup)) ((gnu 
> packages base)) ((gnu packages bash)) ((gnu packages bison)) ((gnu packages 
> bootloaders)) ((gnu …)) …))
>    222:29 14 (map1 (((gnu packages backup)) ((gnu packages base)) ((gnu 
> packages bash)) ((gnu packages bison)) ((gnu packages bootloaders)) ((gnu 
> packages build-tools)) ((# …)) …))
>    222:29 13 (map1 (((gnu packages base)) ((gnu packages bash)) ((gnu 
> packages bison)) ((gnu packages bootloaders)) ((gnu packages build-tools)) 
> ((gnu packages check)) ((gnu …)) …))
>    222:29 12 (map1 (((gnu packages bash)) ((gnu packages bison)) ((gnu 
> packages bootloaders)) ((gnu packages build-tools)) ((gnu packages check)) 
> ((gnu packages cluster)) ((…)) …))
>    222:29 11 (map1 (((gnu packages bison)) ((gnu packages bootloaders)) ((gnu 
> packages build-tools)) ((gnu packages check)) ((gnu packages cluster)) ((gnu 
> packages cmake)) ((…)) …))
>    222:17 10 (map1 (((gnu packages bootloaders)) ((gnu packages build-tools)) 
> ((gnu packages check)) ((gnu packages cluster)) ((gnu packages cmake)) ((gnu 
> packages #)) ((gnu …)) …))
>   3327:17  9 (resolve-interface (gnu packages bootloaders) #:select _ #:hide 
> _ #:prefix _ #:renamer _ #:version _)
> In ice-9/threads.scm:
>     390:8  8 (_ _)
> In ice-9/boot-9.scm:
>   3253:13  7 (_)
> In ice-9/threads.scm:
>     390:8  6 (_ _)
> In ice-9/boot-9.scm:
>   3544:20  5 (_)
>    2836:4  4 (save-module-excursion #<procedure 7f15e679c150 at 
> ice-9/boot-9.scm:3545:21 ()>)
>   3564:26  3 (_)
> In unknown file:
>            2 (primitive-load-path "gnu/packages/bootloaders" #<procedure 
> 7f15e68a0c00 at ice-9/boot-9.scm:3551:37 ()>)
> In gnu/packages/bootloaders.scm:
>   1061:31  1 (_)
> In ice-9/boot-9.scm:
>   1685:16  0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> error: crust-pine64-plus: unbound variable
>
> This is the dreaded “circular top-level references” case: to load
> firmware.scm, you need to (indirectly) load bootloaders.scm

I suspected it had to do with top level cycles, but how did you work out
the indirect dependencies of firmware.scm on bootloaders.scm ?  I simply
thought "firmware doesn't pull the bootloaders module directly, so we
should be good".

Is there some trick (Guile traces?) to print which modules are getting
pulled or something useful to know?

-- 
Thanks,
Maxim





reply via email to

[Prev in Thread] Current Thread [Next in Thread]