From: "André A. Gomes" <andremegafone@gmail.com>
To: 57559@debbugs.gnu.org
Subject: bug#57559: guix pull fails on http status code 503
Date: Tue, 02 Jul 2024 19:09:16 +0300 [thread overview]
Message-ID: <87msmzixn7.fsf@gmail.com> (raw)
In-Reply-To: <87wnakn1oq.fsf@gmail.com> ("André A. Gomes"'s message of "Sat, 03 Sep 2022 14:21:25 +0300")
André A. Gomes <andremegafone@gmail.com> writes:
> Hi Guix,
>
> $ guix pull
> Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'...
> guix pull: error: Git error: unexpected http status code: 503
>
> It seems reasonable that if a certain channel isn't available, it should
> be possible to ignore it and proceed.
Hi Guix,
In the same spirit as the report above, invoking guix pull replied:
--8<---------------cut here---------------start------------->8---
Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'...
Updating channel 'aadcg' from Git repository at 'https://github.com/aadcg/aadcg-guix-channel'...
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
guix pull: error: Git error: unexpected http status code: 502
--8<---------------cut here---------------end--------------->8---
I'd would be helpful to see which channel failed and continue the
operation with the channels that are operational.
Thanks.
--
André A. Gomes
"You cannot even find the ruins..."
prev parent reply other threads:[~2024-07-02 16:11 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
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 [this message]
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=87msmzixn7.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=57559@debbugs.gnu.org \
/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).