GNU bug report logs - #56845
unclear error message: No route to host

Previous Next

Package: guix;

Reported by: Csepp <raingloom <at> riseup.net>

Date: Sat, 30 Jul 2022 18:38:01 UTC

Severity: normal

To reply to this bug, email your comments to 56845 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#56845; Package guix. (Sat, 30 Jul 2022 18:38:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Csepp <raingloom <at> riseup.net>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sat, 30 Jul 2022 18:38:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Csepp <raingloom <at> riseup.net>
To: Bug reports GNU Guix <bug-guix <at> gnu.org>
Subject: unclear error message: No route to host
Date: Sat, 30 Jul 2022 20:33:23 +0200
```
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.

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.




Information forwarded to bug-guix <at> gnu.org:
bug#56845; Package guix. (Fri, 05 Aug 2022 15:05:01 GMT) Full text and rfc822 format available.

Message #8 received at 56845 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Csepp <raingloom <at> riseup.net>
Cc: 56845 <at> debbugs.gnu.org
Subject: Re: bug#56845: unclear error message: No route to host
Date: Fri, 05 Aug 2022 17:04:31 +0200
Hi,

Csepp <raingloom <at> 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’.




This bug report was last modified 1 year and 265 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.