all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: 56845@debbugs.gnu.org
Subject: bug#56845: unclear error message: No route to host
Date: Fri, 05 Aug 2022 17:04:31 +0200	[thread overview]
Message-ID: <87edxug29s.fsf@gnu.org> (raw)
In-Reply-To: <87edy2wiow.fsf@riseup.net> (Csepp's message of "Sat, 30 Jul 2022 20:33:23 +0200")

Hi,

Csepp <raingloom@riseup.net> skribis:

> guix pull -v3 --cores=1      
> guix pull: error: failed to load '/home/raingloom/.config/guix/channels.scm': No route to host
> ```
>
> My channels.scm mentions at least 3 hosts by name and indirectly uses
> ci.guix.gnu.org via channel-with-substitutes-available.

‘channel-with-substitutes-available’ failed due to a networking issue,
which is where “No route to host” comes from (it means that
ci.guix.gnu.org could not be reached from your machine).

> It's quite possible this is more a Guile issue, but then again, Guix
> should give a clear stack trace about which function the error
> originates from.

Yeah, ‘load*’ should better discriminate on the type of issues: issues
such as “File not found” (where displaying a stack trace would be
wrong), and issues caused by actually running the code.  Right now it
loads the file at once (meaning open + read + eval), so it doesn’t have
a sufficiently detailed vision.

Ludo’.




      reply	other threads:[~2022-08-05 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 18:33 bug#56845: unclear error message: No route to host Csepp
2022-08-05 15:04 ` 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

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

  git send-email \
    --in-reply-to=87edxug29s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=56845@debbugs.gnu.org \
    --cc=raingloom@riseup.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.