From: Wil deBeest <bovid-19@4tii.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: "Wamm K. D." <jaft.r@outlook.com>, help-guix@gnu.org
Subject: Re: Guix Halts After "updating substitutes from …"
Date: Wed, 25 May 2022 10:39:20 +0200 [thread overview]
Message-ID: <15B5E55F-84BF-4BED-A0CD-1EC2B2317A43@4tii.de> (raw)
In-Reply-To: <87r14i8qkm@nckx>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
Thank you!
I've been having the same problem and had no idea what caused it.
Wouldn't adding a timeout make sense? Either with a sensible default time and options to change or disable it or just configuration options that would be documented in the "channels" section?
If timeouts aren't an option, a message like "could not reach substitute server [server-name] ([time/unit])"* would already be much more be helpful than the current state for those of us who are not (yet) that familiar with guix.
I regularly feel like guix errors could give more useful information. Is this due to design decisions or something that just hasn't been considered or worked on?
* Optionally with additional information like "Press 'Control C' to abort" and "You can temporarily disable this substitute server by adding '--substitute-urls=[server-name] to the command that got you here.'"
> On 25. May 2022, at 01:21, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
> Wamm K. D. 写道:
>>> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
>>
>> I haven't let it run for longer than an hour but it just sits there and
>> doesn't progress any further. When I run ~guix upgrade~, it halts,
>> similarly, after listing which programs it's going to upgrade.
>>
>> Anyone, possibly, know what this is (or, at least, how I might get
>> around it)?
>
> Sure: <https://lists.gnu.org/archive/html/guix-devel/2022-05/msg00243.html>
>
> Use ‘--substitute-urls=https://ci.guix.gnu.org’ (i.e., remove bordeaux from the default list) until it's resolved.
>
> Kind regards,
>
> T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/octet-stream, Size: 247 bytes --]
-----BEGIN PGP SIGNATURE-----
iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYo1oeQ0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15e88BAOpitl1J/FQfSzFOoY3ZeoRLFVHOxF2b0QDHe4XX
YCTTAP95n8tVgKtgAPdXGaP/m64rrYOVrp4M45ApMofHBFxXCQ==
=4zQl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2022-05-25 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:55 Guix Halts After "updating substitutes from …" Wamm K. D.
2022-05-24 23:19 ` Tobias Geerinckx-Rice
2022-05-24 23:50 ` Wamm K. D.
2022-05-25 8:39 ` Wil deBeest [this message]
2022-05-24 23:22 ` raingloom
2022-05-25 0:10 ` Wamm K. D.
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=15B5E55F-84BF-4BED-A0CD-1EC2B2317A43@4tii.de \
--to=bovid-19@4tii.de \
--cc=help-guix@gnu.org \
--cc=jaft.r@outlook.com \
--cc=me@tobias.gr \
/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.
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).