unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Todor Kondić" <tk.code@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Pull errors with git error 502
Date: Fri, 06 Dec 2019 19:32:20 +0100	[thread overview]
Message-ID: <878snpmhjt.fsf@nckx> (raw)
In-Reply-To: <m0V5yCtYH98qkhmBt7dwzY8HDDNaVY-jOSpXGP_TCtfR9pSehXQfrIsCL-TWrqBDJ-EzSNSDMoNjKPbEuSxxSd5ydIewLHbPcr8WO1C6zSg=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

Todor,

Todor Kondić 写道:
> A simple `guix pull'
>
> outputs the following,
>
> Updating channel 'eci-pkg-menu' from Git repository at 
> 'https://git-r3lab.uni.lu/eci/eci-pkg-menu.git'...
> 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
>
>
> and dies.

This is a known issue.  Savannah (which hosts the guix git 
repository used by ‘guix pull’) has been under attack for a 
week[0].  If you have or create a Savannah account, you can clone 
over SSH to bypass the overloaded HTTP proxies although guix pull 
--url= doesn't support that directly.

If that's not possible, retrying ‘guix pull’ a few times tends to 
succeed after a few times.

Guix will probably host a git mirror in future to mitigate attacks 
like these, assuming nobody attacks us directly.  We're a lot more 
vulnerable than Savannah.

Kind regards,

T G-R

[0]: 
https://lists.gnu.org/r/savannah-hackers-public/2019-12/msg00003.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-12-06 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 18:18 Pull errors with git error 502 Todor Kondić
2019-12-06 18:32 ` Tobias Geerinckx-Rice [this message]
2019-12-06 18:34 ` zimoun

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=878snpmhjt.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=tk.code@protonmail.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.
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).