all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Jochen Luig <jochen.luig@gmail.com>, 54900@debbugs.gnu.org
Subject: bug#54900: Bug encountered when running `guix pull`
Date: Wed, 13 Apr 2022 13:04:26 +0200	[thread overview]
Message-ID: <35631d9589dcac428788a0349159d8fd1616a942.camel@telenet.be> (raw)
In-Reply-To: <CAPzt=uTRnqQLehXptB69m=9YUwnPAfa=DTEmD8iZNZUa5hydEA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Jochen Luig schreef op wo 13-04-2022 om 04:56 [+0200]:
> guix substitute: warning: while fetching
> https://ci.guix.gnu.org/nar/lzip/mzz11jzk3ag1nzzzdg83kmgysm5faijd-texlive-babel-fixed-59745
> : server is somewhat slow
> guix substitute: warning: try `--no-substitutes' if the problem
> persists
> guix substitute: error: connect*: Connection timed out
>           16 (primitive-load
> "/gnu/store/ghf5nvs7mwv0w99737ilgja4hfdm2l7s-compute-guix-
> derivation")

Probably network problems, just retry, and maybe pass --fallback to
"guix pull".

Anyway, this is not a bug and hence shouldn't be reported as such, but
error reporting in "guix pull" is complicated™.  FWIW, the v2 patch at
<https://issues.guix.gnu.org/50238> would avoid the here unnecessary
backtrace and make it clearer that it's just some network problems,
though it's not perfect (the ‘please report a bug’ remains).

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2022-04-13 11:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  2:56 bug#54900: Bug encountered when running `guix pull` Jochen Luig
2022-04-13 11:04 ` 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

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

  git send-email \
    --in-reply-to=35631d9589dcac428788a0349159d8fd1616a942.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54900@debbugs.gnu.org \
    --cc=jochen.luig@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 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.