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: Tue, 06 Sep 2022 15:09:48 +0200 [thread overview]
Message-ID: <86wnagzm1v.fsf@gmail.com> (raw)
In-Reply-To: <745d4a98-fe62-338d-7a26-d5248413ff5f@telenet.be>
Hi Maxime,
On Mon, 05 Sep 2022 at 22:20, Maxime Devos <maximedevos@telenet.be> wrote:
> On 05-09-2022 10:21, zimoun wrote:
>> On sam., 03 sept. 2022 at 19:27, Maxime Devos<maximedevos@telenet.be> wrote:
>>
>>> * 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!).
>> What do you mean by «but don't 'ignore' the missing channels by removing
>> them!»? Do you mean keep the last revision locally known for this
>> channel?
>
> I'm not sure what you're asking, because of the negatives.
[...]
> (It's not unlike double negatives! I first thought of the latter
> interpretation but on second thought you might have meant the former.)
IIUC, you have hard time to parse the double-negative you wrote earlier
in this thread. :-)
> With "but don't ignore [...] by [...]", I meant that, yes.
>
> If you meant "don't ignore [...] by [...]", then no, with 'ignoring by
> removing', I meant, literally removing them. More concretely, a
> situation like this:
>
> * In the channels.scm, two channels are declared: guix and guix-foo.
> * User does "guix pull"; Guix downloads the source code of guix and
> guix-foo.
> * Downloading guix failed (503). As such, Guix decided to ignore the
> guix channel, by removing it from the list of channels to build.
> (The in-memory list I mean, I don't mean modifying the channels.smc
> file)
> * Guix tries building the guix-foo channel and installing it, without
> the guix channel.
> * This cannot work (the guix-foo channel uses modules from guix for
> basic stuff like G-exps, packages, coreutils, ..., and it was the
> removed guix channel that had things build-aux/build-self.scm which
> is required for pulling).
The initial report by André is about:
--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---
So the situation is more likely: Guix from Savannah is reachable and
guix-foo is not.
For sure, we can discuss the case when Guix is unavailable. However,
the 'guix channel is special; see all conditionals using ’guix-channel?’.
Well, %default-guix-channel is somehow a corner use-case when the
regular use-case seems about a failure of additional channels.
Cheers,
simon
next prev parent reply other threads:[~2022-09-06 14:52 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 [this message]
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=86wnagzm1v.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).