unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: control@debbugs.gnu.org, 57527@debbugs.gnu.org,
	53802@debbugs.gnu.org, 56466@debbugs.gnu.org
Subject: bug#57527: compute-guix-derivation has an error
Date: Thu, 1 Sep 2022 19:07:48 +0200	[thread overview]
Message-ID: <59cb7f24-d9c8-5394-cdbd-605d5addd03a@telenet.be> (raw)
In-Reply-To: <4a7379ce-40b6-0a56-648c-8160cd1cf1b6@uu.nl>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 741 bytes --]

severity 57527 important
merge 47764 57527
severity 53802 important
merge 47764 53802
severity 56466 important
merge 47764 56466
thanks

Found a few apparent duplicates (they are all about a &nar-error, 
read-int and process-stderror).

On second thought, I don't think the patch I referred to #56466 will 
help here, though it could hardly harm here.

For now, you can try working-around by retrying "guix pull".

There are two hypotheses on the cause in

  * https://issues.guix.gnu.org/57527#1
  * and https://issues.guix.gnu.org/47764

The second seems most plausible to me, and the first seems the simplest 
to test (and even if it's not the cause, it would still add some 
robustness).

Greetings,
Maxime.


[-- Attachment #1.1.1.2: Type: text/html, Size: 1249 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 931 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      parent reply	other threads:[~2022-09-01 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 15:00 bug#57527: compute-guix-derivation has an error Toorn, H.W.P. van den (Henk) via Bug reports for GNU Guix
2022-09-01 16:39 ` Maxime Devos
2022-09-01 17:38   ` zimoun
2022-09-01 17:07 ` Maxime Devos [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59cb7f24-d9c8-5394-cdbd-605d5addd03a@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53802@debbugs.gnu.org \
    --cc=56466@debbugs.gnu.org \
    --cc=57527@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).