From: Maxime Devos <maximedevos@telenet.be>
To: "André A. Gomes" <andremegafone@gmail.com>, 57559@debbugs.gnu.org
Subject: bug#57559: guix pull fails on http status code 503
Date: Sat, 3 Sep 2022 19:27:30 +0200 [thread overview]
Message-ID: <dfcfd3df-9083-c63d-94c8-0d310806cc92@telenet.be> (raw)
In-Reply-To: <87wnakn1oq.fsf@gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1452 bytes --]
On 03-09-2022 13:21, André A. Gomes wrote:
> Hi Guix,
>
> --8<---------------cut here---------------start------------->8---
> $ guix pull
> Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'...
> guix pull: error: Git error: unexpected http status code: 503
> --8<---------------cut here---------------end--------------->8---
>
> It seems reasonable that if a certain channel isn't available, it should
> be possible to ignore it and proceed.
>
> Thanks.
More concretely:
* if all channels are available --> ok, keep status quo
* if no channels are available --> error, keep status quo
* if some but not all channels are available, and there is at least
one updated channel --> log the missing channels, and update the
channels that _are_ available (but don't 'ignore' the missing
channels by removing them!).
* if some but not all channels are available, and none of the
available channels were updated --> bail out, no progress was made
and this might be due to lack of connectivity instead of lack of
updates.
?
Technically, your message can be interpreted as: if I only have a single
channel, the Guix channel, and it isn't available, it should be possible
to ignore it and proceed. (Proceed with what? It's the only channel,
what is there to proceed with.) To actually implement this, we need to
be precise.
Greetings,
Maxime
[-- Attachment #1.1.1.2: Type: text/html, Size: 2024 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-03 17:28 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 [this message]
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
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=dfcfd3df-9083-c63d-94c8-0d310806cc92@telenet.be \
--to=maximedevos@telenet.be \
--cc=57559@debbugs.gnu.org \
--cc=andremegafone@gmail.com \
/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).