[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Error: guix build xonsh ; guix pull --commit=572ee05c31
From: |
Ludovic Courtès |
Subject: |
Re: Error: guix build xonsh ; guix pull --commit=572ee05c31 |
Date: |
Tue, 08 Jan 2019 23:52:48 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hi,
zimoun <address@hidden> skribis:
> I naively try from the Build section in the manual:
>
> guix build \
> --cores=0 --max-jobs=10 \
> --quiet --keep-going \
> `guix package -A | cut -f1,2 address@hidden
>
> and it does not seem "keep-going" because it quickly fails on xonsh
> with the message:
>
> guix build: error: build failed: build of
> `/gnu/store/06m5xywkfwza30ngh9lazzaq0vrmwyzr-xonsh-0.6.2.drv' failed
What makes you think it did not keep going? When using --keep-going
you’ll still get an error at the end if one or more builds failed.
> Then, I simply try: `git pull --commit=572ee05c31`.
> It also fails with the backtrace below. Is it expected?
[...]
> In guix/channels.scm:
> 394:36 6 (channel-instances->manifest (#<<channel-instance> cha?>))
> 310:28 5 (channel-instance-derivations (#<<channel-instance> ch?>))
> In ice-9/eval.scm:
> 619:8 4 (_ #(#(#(#<directory (build-self) 1834d20>) "/gnu?" ?) ?))
> 626:19 3 (_ #(#(#(#<directory (build-self) 1834d20>) "/gnu?" ?) ?))
> 155:9 2 (_ #(#(#(#<directory (build-self) 1834d20>) "/gnu?" ?) ?))
> 223:20 1 (proc #(#(#(#<directory (build-self) 1834d20>) "/?" ?) ?))
> In unknown file:
> 0 (%resolve-variable (7 . %guix-register-program) #<direc?>)
> ERROR: In procedure %resolve-variable:
> error: %guix-register-program: unbound variable
This is simply because commit 572ee05c3134cf9408ba463c97fdbacb9a98f714
dates back to 2016 at a time where ‘guix pull’ and related files where
not “future-proof”, so we just cannot roll back this far I’m afraid.
Again the changes to ‘guix pull’ made shortly before 0.15 should fix the
issue and allow us to go back further in future history, if you see what
I mean. :-)
Ludo’.