From: Philip Beadling <phil@beadling.co.uk>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Jacob Hrbek <kreyren@rixotstudio.cz>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Make guix use alternative substitute if one is down
Date: Sat, 1 Oct 2022 18:34:04 +0000 [thread overview]
Message-ID: <LO0P123MB3898F73899C853C6EED0F4E7F9599@LO0P123MB3898.GBRP123.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87bkqvcwl1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Excellent - thanks for letting us know Ludo', this is really useful.
________________________________
From: Ludovic Courtès <ludo@gnu.org>
Sent: Saturday, 1 October 2022, 18:55
To: Philip Beadling <phil@beadling.co.uk>
Cc: Jacob Hrbek <kreyren@rixotstudio.cz>; guix-devel@gnu.org <guix-devel@gnu.org>
Subject: Re: Make guix use alternative substitute if one is down
Hi,
Philip Beadling <phil@beadling.co.uk> skribis:
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%guix substitute: warning: ci.guix.gnu.org<http://ci.guix.gnu.org>: connection failed: No route to host
> substitute:
> 20,6 MB will be downloaded
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%
> guix substitute: error: connect*: No route to host
> substitution of /gnu/store/c0wd1i6yknmiyp89626mfr9db74dayry-libmng-2.0.3
The good news is that the ci.guix.gnu.org outage gave an incentive to
finally fix this bug:
https://issues.guix.gnu.org/58017
Ludo’.
[-- Attachment #2: Type: text/html, Size: 2065 bytes --]
next prev parent reply other threads:[~2022-10-01 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 13:09 Make guix use alternative substitute if one is down Jacob Hrbek
2022-09-21 15:40 ` Philip Beadling
2022-10-01 16:55 ` Ludovic Courtès
2022-10-01 18:34 ` Philip Beadling [this message]
2022-09-21 20:40 ` zimoun
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=LO0P123MB3898F73899C853C6EED0F4E7F9599@LO0P123MB3898.GBRP123.PROD.OUTLOOK.COM \
--to=phil@beadling.co.uk \
--cc=guix-devel@gnu.org \
--cc=kreyren@rixotstudio.cz \
--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.