From: zimoun <zimon.toutoune@gmail.com>
To: "Maxime Devos" <maximedevos@telenet.be>,
"André A. Gomes" <andremegafone@gmail.com>,
57559@debbugs.gnu.org
Subject: bug#57559: guix pull fails on http status code 503
Date: Thu, 08 Sep 2022 09:25:29 +0200 [thread overview]
Message-ID: <86k06exr86.fsf@gmail.com> (raw)
In-Reply-To: <e0db8bcd-e622-84a7-5488-bcebc9cebc51@telenet.be>
Hi Maxime,
On Thu, 08 Sep 2022 at 02:55, Maxime Devos <maximedevos@telenet.be> wrote:
>> Well, %default-guix-channel is somehow a corner use-case when the
>> regular use-case seems about a failure of additional channels.
>
> The ‘Guix is unavailable’ was just a simple example. For the example,
> you can replace it, with, say nonguix. Automatically removing the
> additional channels upon 503 is undesirable I'd think, though the error
> messages will be different.
My point is that ’Guix is unavailable’ is special and it appears to me
expected to raise an error. Other said,
1. if %default-guix-channel (or its mirrors) is unreachable,
then stop the pull; as it is currently done.
2. if an extra channel is unreachable,
then keep the last local revision of this channel
and try the others.
For sure, #2 can break the whole pull if something in the Guix channel
changed *and* the channel depends on this something. But we cannot do
more than raise an error.
Cheers,
simon
next prev parent reply other threads:[~2022-09-08 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 11:21 bug#57559: guix pull fails on http status code 503 André A. Gomes
2022-09-03 17:27 ` Maxime Devos
2022-09-04 20:27 ` André A. Gomes
2022-09-05 8:21 ` zimoun
2022-09-05 20:20 ` Maxime Devos
2022-09-06 13:09 ` zimoun
2022-09-08 0:55 ` Maxime Devos
2022-09-08 7:25 ` zimoun [this message]
2022-09-08 9:23 ` Maxime Devos
2022-09-08 11:11 ` zimoun
2022-09-08 11:29 ` Maxime Devos
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=86k06exr86.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=57559@debbugs.gnu.org \
--cc=andremegafone@gmail.com \
--cc=maximedevos@telenet.be \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).