From: "Ludovic Courtès" <ludo@gnu.org>
To: o.rojon@posteo.net
Cc: 41715@debbugs.gnu.org
Subject: bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix
Date: Fri, 05 Jun 2020 18:29:21 +0200 [thread overview]
Message-ID: <87mu5h1noe.fsf@gnu.org> (raw)
In-Reply-To: <6a6c6f638f0a33ec39b9e70843090299@posteo.net> (o. rojon's message of "Fri, 05 Jun 2020 10:26:00 +0200")
Hi,
o.rojon@posteo.net skribis:
> Just to follow up: a roll-back does NOT solve the issue.
>
> What I have tried:
> 1) roll-back via guix system roll-back (to the generation that was
> created upon system installation)
> 2) roll-back via guix package --roll-back (same)
> 3) (1) + (2) combined
> 4) boot into the generation created upon system installation.
>
> In none of these cases was I able to run 'guix pull'.
Thanks for testing this.
Note that, if “which guix” returns ~/.config/guix/current/bin/guix, then
none of the rollbacks above can have any effect. What could make a
difference (but again, that would seem weird to me) is:
guix pull --roll-back
Are you passing extra options to guix-daemon, such as
‘--cache-failures’? Or did you enable offloading?
It could also be that a transient failure is causing a silent build
failure somewhere, as Jakub suggests.
Thanks,
Ludo’.
PS: Please keep the bug address Cc’d.
next prev parent reply other threads:[~2020-06-05 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 19:12 bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix o.rojon
2020-06-04 20:00 ` Ludovic Courtès
2020-06-05 5:54 ` o.rojon
2020-06-05 8:26 ` o.rojon
2020-06-05 16:29 ` Ludovic Courtès [this message]
2020-06-06 0:57 ` o.rojon
2020-06-07 19:47 ` Ludovic Courtès
2020-06-08 14:55 ` o.rojon
2020-06-09 14:30 ` Ludovic Courtès
2020-06-12 5:54 ` o.rojon
2020-06-12 14:12 ` Ludovic Courtès
2020-07-21 18:11 ` Olivier
2020-07-22 10:12 ` Ludovic Courtès
2020-06-04 22:15 ` Jakub Kądziołka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu5h1noe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41715@debbugs.gnu.org \
--cc=o.rojon@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.