From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Jesse Gibbons" <jgibbons2357@gmail.com>
Cc: 53710@debbugs.gnu.org
Subject: bug#53710: "guix pull" doesn't have nice error messages in case of network errors
Date: Wed, 02 Mar 2022 14:14:58 +0100 [thread overview]
Message-ID: <126927a6292208ac84e74afa1a7dab31d4a5968e.camel@telenet.be> (raw)
In-Reply-To: <87r17k38la.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Ludovic Courtès schreef op wo 02-03-2022 om 12:19 [+0100]:
> > ./guix/serialization.scm:80:6: In procedure get-bytevector-n*:
> > ERROR:
> > 1. &nar-error:
> > file: #f
> > port: #<input-output: file 10>
> > guix pull: error: You found a bug: the program
> > '/gnu/store/rx23w5k5nys4a2hjwcy4lampkhnslj3m-compute-guix-
> > derivation'
> > failed to compute the derivation for Guix (version:
> > "787b13a5d9df8f0cc7170de1b80cead68b516c66"; system: "x86_64-linux";
> > host version: "90a41fe388102d448b3f91a070e38a7680d2d568"; pull-
> > version: 1).
> > Please report the COMPLETE output above by email to
> > <bug-guix@gnu.org>.
>
> Thanks for reporting the issue. Unfortunately, I suspect it was
> “just”
> a transient issue (probably a networking issue while downloading
> substitutes for guile-ssh, which we see in the backtrace). It’s
> unfortunate that it crashed like that.
Even if it's ‘only’ a networking issue, shouldn't it be reported
better? When "guix package -u" fails due to networking errors, the
error messages are much clearer. Why not the same for "guix pull"?
Perhaps the issue should be reopened?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-02 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 19:50 bug#53710: guix pull fails Jesse Gibbons
2022-03-02 11:19 ` Ludovic Courtès
2022-03-02 13:14 ` Maxime Devos [this message]
2022-03-02 16:31 ` bug#53710: "guix pull" doesn't have nice error messages in case of network errors Jesse Gibbons
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=126927a6292208ac84e74afa1a7dab31d4a5968e.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53710@debbugs.gnu.org \
--cc=jgibbons2357@gmail.com \
--cc=ludo@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 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.