GNU bug report logs - #38446
Guix pull broken (502 error)

Previous Next

Package: guix;

Reported by: Clément Lassieur <clement <at> lassieur.org>

Date: Sun, 1 Dec 2019 18:16:02 UTC

Severity: serious

Done: Clément Lassieur <clement <at> lassieur.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38446 in the body.
You can then email your comments to 38446 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Sun, 01 Dec 2019 18:16:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Clément Lassieur <clement <at> lassieur.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sun, 01 Dec 2019 18:16:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Clément Lassieur <clement <at> lassieur.org>
To: bug-guix <at> gnu.org
Subject: Guix pull broken
Date: Sun, 01 Dec 2019 19:15:22 +0100
https://git.savannah.gnu.org/cgit/guix.git/log/ returns 502 error.

Reproducible 9 times out of 10.




Severity set to 'serious' from 'normal' Request was from clement <at> lassieur.org (Clément Lassieur) to control <at> debbugs.gnu.org. (Sun, 01 Dec 2019 18:17:02 GMT) Full text and rfc822 format available.

Changed bug title to 'Guix pull broken (502 error)' from 'Guix pull broken' Request was from clement <at> lassieur.org (Clément Lassieur) to control <at> debbugs.gnu.org. (Sun, 01 Dec 2019 18:19:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Sun, 01 Dec 2019 18:20:02 GMT) Full text and rfc822 format available.

Message #12 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: clement <at> lassieur.org (Clément Lassieur)
To: 38446 <at> debbugs.gnu.org
Subject: Re: bug#38446: Guix pull broken
Date: Sun, 01 Dec 2019 19:19:22 +0100
Clément Lassieur <clement <at> lassieur.org> writes:

> https://git.savannah.gnu.org/cgit/guix.git/log/ returns 502 error.
>
> Reproducible 9 times out of 10.

Since at least yesterday.




Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Mon, 02 Dec 2019 18:10:02 GMT) Full text and rfc822 format available.

Message #15 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 38446 <at> debbugs.gnu.org
Subject: Re: bug#38446: Guix pull broken
Date: Mon, 2 Dec 2019 19:09:14 +0100
Hi,

On Sun, 1 Dec 2019 at 19:20, Clément Lassieur <clement <at> lassieur.org> wrote:
>
> Clément Lassieur <clement <at> lassieur.org> writes:
>
> > https://git.savannah.gnu.org/cgit/guix.git/log/ returns 502 error.
> >
> > Reproducible 9 times out of 10.
>
> Since at least yesterday.

I have issues too.




Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Mon, 02 Dec 2019 20:34:02 GMT) Full text and rfc822 format available.

Message #18 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: Amin Bandali <bandali <at> gnu.org>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 38446 <at> debbugs.gnu.org,
 Clément Lassieur <clement <at> lassieur.org>
Subject: Re: bug#38446: Guix pull broken
Date: Mon, 02 Dec 2019 15:33:50 -0500
[Message part 1 (text/plain, inline)]
Hi folks,

The reason for these errors is that various parts of GNU Savannah have
been under a sizable botnet attack for a few days now.  Savannah hackers
and FSF sysadmins have been working on it mitigating the attack, but it
is an ongoing effort.

In the mean time, I suggest using "member checkouts" (i.e. ssh) for
accessing the repositories.  You need to a Savannah account for this,
but to my knowledge you don't have to be a member of that project to
just pull from its repositories using ssh.  Another option would be
using the git:// protocol, which I recommend against, as it's insecure
and prone to MITM attacks.

See
    https://savannah.gnu.org/git/?group=guix
and
    https://savannah.gnu.org/maintenance/UsingGit/
for more details.

Hope this helps.

-- 
Amin Bandali
Free Software Activist | GNU Maintainer & Webmaster
GPG: BE62 7373 8E61 6D6D 1B3A  08E8 A21A 0202 4881 6103
https://bandali.eu.org
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Mon, 02 Dec 2019 23:16:02 GMT) Full text and rfc822 format available.

Message #21 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: Clément Lassieur <clement <at> lassieur.org>
To: Amin Bandali <bandali <at> gnu.org>
Cc: 38446 <at> debbugs.gnu.org, zimoun <zimon.toutoune <at> gmail.com>
Subject: Re: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 00:15:36 +0100
Hi Amin,

Thank you for this nice reply.

Would it be possible to have an *official* backup Git repository hosted
somewhere else (like Github, or whatever), where we could redirect users
when they encounter issues?

Clément

Amin Bandali <bandali <at> gnu.org> writes:

> Hi folks,
>
> The reason for these errors is that various parts of GNU Savannah have
> been under a sizable botnet attack for a few days now.  Savannah hackers
> and FSF sysadmins have been working on it mitigating the attack, but it
> is an ongoing effort.
>
> In the mean time, I suggest using "member checkouts" (i.e. ssh) for
> accessing the repositories.  You need to a Savannah account for this,
> but to my knowledge you don't have to be a member of that project to
> just pull from its repositories using ssh.  Another option would be
> using the git:// protocol, which I recommend against, as it's insecure
> and prone to MITM attacks.
>
> See
>     https://savannah.gnu.org/git/?group=guix
> and
>     https://savannah.gnu.org/maintenance/UsingGit/
> for more details.
>
> Hope this helps.




Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Mon, 02 Dec 2019 23:23:02 GMT) Full text and rfc822 format available.

Message #24 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 38446 <at> debbugs.gnu.org, Clément Lassieur
 <clement <at> lassieur.org>
Subject: Re: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 00:22:39 +0100
[Message part 1 (text/plain, inline)]
Clément Lassieur 写道:
> Would it be possible to have an *official* backup Git repository 
> hosted
> somewhere else (like Github, or whatever), where we could 
> redirect users
> when they encounter issues?

Coming soon ;-)

Kind regards,

T G-R
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Mon, 02 Dec 2019 23:28:02 GMT) Full text and rfc822 format available.

Message #27 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 38446 <at> debbugs.gnu.org, Amin Bandali <bandali <at> gnu.org>
Subject: Re: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 00:27:45 +0100
Hi Clément,

> Would it be possible to have an *official* backup Git repository hosted
> somewhere else (like Github, or whatever), where we could redirect users
> when they encounter issues?

For the time being you can do

  git clone https://guix.gnu.org/git/guix

which is a read-only copy of my clone of the repository.  I’d like to
make it automatically sync up with the repo on Savannah, but I ran out
of time.

~~ Ricardo





Reply sent to Clément Lassieur <clement <at> lassieur.org>:
You have taken responsibility. (Mon, 02 Dec 2019 23:34:02 GMT) Full text and rfc822 format available.

Notification sent to Clément Lassieur <clement <at> lassieur.org>:
bug acknowledged by developer. (Mon, 02 Dec 2019 23:34:02 GMT) Full text and rfc822 format available.

Message #32 received at 38446-done <at> debbugs.gnu.org (full text, mbox):

From: Clément Lassieur <clement <at> lassieur.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 38446-done <at> debbugs.gnu.org, Amin Bandali <bandali <at> gnu.org>
Subject: Re: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 00:32:54 +0100
Hi Ricardo,

Ricardo Wurmus <rekado <at> elephly.net> writes:

> For the time being you can do
>
>   git clone https://guix.gnu.org/git/guix
>
> which is a read-only copy of my clone of the repository.  I’d like to
> make it automatically sync up with the repo on Savannah, but I ran out
> of time.

Great!  Thank you very much,
Clément

PS: I'm closing the bug, since it doesn't really depend on us and we
have a workaround.




Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Mon, 02 Dec 2019 23:56:01 GMT) Full text and rfc822 format available.

Message #35 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 38446 <at> debbugs.gnu.org, Ricardo Wurmus <rekado <at> elephly.net>
Subject: Re: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 00:55:36 +0100
[Message part 1 (text/plain, inline)]
Ricardo,

Ricardo Wurmus 写道:
> For the time being you can do
>
>   git clone https://guix.gnu.org/git/guix
>
> which is a read-only copy of my clone of the repository.  I’d 
> like to
> make it automatically sync up with the repo on Savannah, but I 
> ran out
> of time.

Did you use --mirror to do this?

It should be trivial to finish but I don't want to step on your 
toes.

Kind regards,

T G-R
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#38446; Package guix. (Tue, 03 Dec 2019 02:14:02 GMT) Full text and rfc822 format available.

Message #38 received at 38446 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: 38446 <at> debbugs.gnu.org
Subject: Re: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 03:12:51 +0100
Tobias Geerinckx-Rice <me <at> tobias.gr> writes:

> Ricardo,
>
> Ricardo Wurmus 写道:
>> For the time being you can do
>>
>>   git clone https://guix.gnu.org/git/guix
>>
>> which is a read-only copy of my clone of the repository.  I’d like
>> to
>> make it automatically sync up with the repo on Savannah, but I ran
>> out
>> of time.
>
> Did you use --mirror to do this?

No, I didn’t know about “--mirror”.  I only did this on berlin:

   cd /srv/git
   git init --bare guix

Then I set up git serving over HTTP with some changes to maintenance.git
(not pushed yet but changed on berlin).

Then I pushed to it from my laptop:

   git remote add berlin ssh://berlin.guixsd.org:/srv/git/guix
   git push berlin

~~ Ricardo





bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 31 Dec 2019 12:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 5 years and 230 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.