From: "Ludovic Courtès" <ludo@gnu.org>
To: Keith Thompson <Keith.S.Thompson@gmail.com>
Cc: 35865@debbugs.gnu.org
Subject: bug#35865: compute-guix-derivation failed to compute the derivation for Guix
Date: Sat, 25 May 2019 19:24:07 +0200 [thread overview]
Message-ID: <877eaeqwg8.fsf@gnu.org> (raw)
In-Reply-To: <CAAHpriOWXe3YDkH-jhQNc77-cirQtauViXtGMwZDdQNhj3Jrhg@mail.gmail.com> (Keith Thompson's message of "Thu, 23 May 2019 01:19:38 -0700")
Hello,
Keith Thompson <Keith.S.Thompson@gmail.com> skribis:
> Computing Guix derivation for 'x86_64-linux'... |@ substituter-started
> /gnu/store/mn3ymm3f2r4xjqf8m9fgmadh6b8p6fvr-glibc-utf8-locales-2.28
> /gnu/store/ncknl03pkmamrxg7q9nxi1rn1qhvwbi9-guix-1.0.1/libexec/guix/substitute
> |guix substitute: error: connect: Connection timed out
[...]
> the outputs of derivation
> `/gnu/store/c4ni4sq1sb9vv5w3a06jnbwy2j0w819k-glibc-utf8-locales-2.28.drv'
> failed (usually happens due to networking issues); try `--fallback' to
> build derivation from source " status: 1] 40e1cf0>)'.
It looks like you experienced a transient network error that prevented
you from downloading ‘glibc-utf8-locales’.
> guix pull: error: You found a bug: the program
This message is confusing: it should report the networking issue above
rather than suggest there’s a bug.
> I have partial output of the successful command (about 1800
> lines). I'm not including it here, but let me know if you want to
> see it. (Ask for a copy of "guix-bug2".)
I don’t think it’s necessary. The main issue from my POV is that the
error message is misleading since it fails to convey the useful piece of
information.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-05-25 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 8:19 bug#35865: compute-guix-derivation failed to compute the derivation for Guix Keith Thompson
2019-05-23 21:10 ` Keith Thompson
2019-05-25 17:24 ` Ludovic Courtès [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=877eaeqwg8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35865@debbugs.gnu.org \
--cc=Keith.S.Thompson@gmail.com \
/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).