Guix pull fails building package cache

  • Done
  • quality assurance status badge
Details
3 participants
  • André A. Gomes
  • Leo Famulari
  • Tobias Geerinckx-Rice
Owner
unassigned
Submitted by
André A. Gomes
Severity
normal
A
A
André A. Gomes wrote on 19 Dec 2021 00:32
(address . bug-guix@gnu.org)
87tuf54hgh.fsf@gmail.com
Hi,

I got the following error after issuing guix pull.

Toggle snippet (5 lines)
building package cache...
/builder for `/gnu/store/6z0pny4mqnhrakqxs1yca5lnxjd1xszr-guix-package-cache.drv' failed to produce output path `/gnu/store/9spwrk8l40kpi110q47ckay0znmjzbdb-guix-package-cache'
build of /gnu/store/6z0pny4mqnhrakqxs1yca5lnxjd1xszr-guix-package-cache.drv failed

And the log says:

Toggle snippet (6 lines)
(repl-version 0 1 1)
Generating package cache for '/gnu/store/c68ygnsa87mqzfnrnkp798qi3jdsixh0-profile'...
(exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (lttng-ust)) (value #f))


--
André A. Gomes
"Free Thought, Free World"
L
L
Leo Famulari wrote on 19 Dec 2021 01:18
(name . André A. Gomes)(address . andremegafone@gmail.com)(address . 52650@debbugs.gnu.org)
Yb56cYSU33yeMev/@jasmine.lan
On Sat, Dec 18, 2021 at 11:32:46PM +0000, Andr� A. Gomes wrote:
Toggle quote (16 lines)
> I got the following error after issuing guix pull.
>
> --8<---------------cut here---------------start------------->8---
> building package cache...
> /builder for `/gnu/store/6z0pny4mqnhrakqxs1yca5lnxjd1xszr-guix-package-cache.drv' failed to produce output path `/gnu/store/9spwrk8l40kpi110q47ckay0znmjzbdb-guix-package-cache'
> build of /gnu/store/6z0pny4mqnhrakqxs1yca5lnxjd1xszr-guix-package-cache.drv failed
> --8<---------------cut here---------------end--------------->8---
>
> And the log says:
>
> --8<---------------cut here---------------start------------->8---
> (repl-version 0 1 1)
> Generating package cache for '/gnu/store/c68ygnsa87mqzfnrnkp798qi3jdsixh0-profile'...
> (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (lttng-ust)) (value #f))
> --8<---------------cut here---------------end--------------->8---

I'm using Guix on x86_64-linux.

While using commit 94836b215630ad0f4a7c06b8e4284d923ac1197f, I pulled to
current --- commit b3a0db7a0e5fa7186c090647cfd5666e2b9287ff.

I didn't have any problems doing `guix install hello` afterwards.

Are you using some 3rd-party channels that might need to be adjusted?
A
A
André A. Gomes wrote on 19 Dec 2021 10:48
(name . Leo Famulari)(address . leo@famulari.name)(address . 52650@debbugs.gnu.org)
87pmpt3oxx.fsf@gmail.com
Leo Famulari <leo@famulari.name> writes:

Toggle quote (22 lines)
> On Sat, Dec 18, 2021 at 11:32:46PM +0000, André A. Gomes wrote:
>> I got the following error after issuing guix pull.
>>
>> --8<---------------cut here---------------start------------->8---
>> building package cache...
>> /builder for
>> `/gnu/store/6z0pny4mqnhrakqxs1yca5lnxjd1xszr-guix-package-cache.drv'
>> failed to produce output path
>> `/gnu/store/9spwrk8l40kpi110q47ckay0znmjzbdb-guix-package-cache'
>> build of /gnu/store/6z0pny4mqnhrakqxs1yca5lnxjd1xszr-guix-package-cache.drv failed
>> --8<---------------cut here---------------end--------------->8---
>>
>> And the log says:
>>
>> --8<---------------cut here---------------start------------->8---
>> (repl-version 0 1 1)
>> Generating package cache for '/gnu/store/c68ygnsa87mqzfnrnkp798qi3jdsixh0-profile'...
>> (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (lttng-ust)) (value #f))
>> --8<---------------cut here---------------end--------------->8---
>
> Are you using some 3rd-party channels that might need to be adjusted?

Oh, right!

How can I close this bug report? Thank you.


--
André A. Gomes
"Free Thought, Free World"
T
T
Tobias Geerinckx-Rice wrote on 19 Dec 2021 12:26
(name . André A. Gomes)(address . andremegafone@gmail.com)(address . 52650-done@debbugs.gnu.org)
871r28zvcp.fsf@nckx
André,

André A. Gomes ???
Toggle quote (2 lines)
> How can I close this bug report? Thank you.

When replying, change the NNNNN@debbugs.gnu.org address to
NNNNN-done@debbugs.gnu.org (or -close, but IME we don't rely on
the subtle distinction?).

I've done so here.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYb8Xhw0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW159doBAK7y/Qp9n/SE6AmFcMwdJaU1fKw6Yf/4M8P4XUrj
aWthAQCAj5+w2Cvkt+HPg6ENh6rgmzxxnBGABgJcAoMG5/FKDA==
=krle
-----END PGP SIGNATURE-----

Closed
L
L
Leo Famulari wrote on 19 Dec 2021 17:55
(name . André A. Gomes)(address . andremegafone@gmail.com)(address . 52650-done@debbugs.gnu.org)
Yb9kHInC42tVeKR+@jasmine.lan
On Sun, Dec 19, 2021 at 09:48:42AM +0000, Andr� A. Gomes wrote:
Toggle quote (4 lines)
> > Are you using some 3rd-party channels that might need to be adjusted?
>
> Oh, right!

Glad to hear you've solved the problem!

Toggle quote (3 lines)
>
> How can I close this bug report? Thank you.

Like I'm doing now, by sending a message to
<$bugnumber-done@debbugs.gnu.org>. That is, by appending "-done" to the
bug's email address.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 52650@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 52650
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch