From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Cl=C3=A9ment?= Lassieur <clement@lassieur.org>
Subject: bug#38446: Guix pull broken
Date: Tue, 03 Dec 2019 00:15:36 +0100
Message-ID: <87k17e9v53.fsf@lassieur.org>
References: <87pnh7nc91.fsf@lassieur.org> <87fti3nc2d.fsf@lassieur.org>
 <CAJ3okZ09J=xvfK2yLn+GrDmLKnepzd5ZF29Vqrd=JKLka0KiBw@mail.gmail.com>
 <87fti2eac1.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:60954)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ibuvE-0004To-3p
 for bug-guix@gnu.org; Mon, 02 Dec 2019 18:16:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ibuvC-0001Hk-Kh
 for bug-guix@gnu.org; Mon, 02 Dec 2019 18:16:04 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:33118)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1ibuvC-0001HO-GP
 for bug-guix@gnu.org; Mon, 02 Dec 2019 18:16:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.38446.B38446.157532855215337@debbugs.gnu.org>
In-reply-to: <87fti2eac1.fsf@gnu.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Amin Bandali <bandali@gnu.org>
Cc: 38446@debbugs.gnu.org

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=C3=A9ment

Amin Bandali <bandali@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=3Dguix
> and
>     https://savannah.gnu.org/maintenance/UsingGit/
> for more details.
>
> Hope this helps.