From: "André A. Gomes" <andremegafone@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57559@debbugs.gnu.org
Subject: bug#57559: guix pull fails on http status code 503
Date: Sun, 04 Sep 2022 23:27:01 +0300 [thread overview]
Message-ID: <87sfl6nawa.fsf@gmail.com> (raw)
In-Reply-To: <dfcfd3df-9083-c63d-94c8-0d310806cc92@telenet.be> (Maxime Devos's message of "Sat, 3 Sep 2022 19:27:30 +0200")
Maxime Devos <maximedevos@telenet.be> writes:
> 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.
I'm just a user and unfortunately I don't have a deep understanding of
Guix's internals.
Your concrete description seems to resonate with my expectations.
Thanks.
--
André A. Gomes
"You cannot even find the ruins..."
next prev parent reply other threads:[~2022-09-04 20:28 UTC|newest]
Thread overview: 12+ 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 [this message]
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
2024-07-02 16:09 ` André A. Gomes
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=87sfl6nawa.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=57559@debbugs.gnu.org \
--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).