GNU bug report logs - #44382
Updating the guix package triggers a full Git clone of guix.git

Previous Next

To reply to this bug, email your comments to 44382 AT debbugs.gnu.org.

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

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

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: Updating the guix package triggers a full Git clone of guix.git
Date: Sun, 1 Nov 2020 19:50:49 -0500

While building the package of Guix itself [0], I noticed that Savannah
can't serve cheap "shallow clones" of the commits that these packages
are based on, so users will end up doing full clones (260M on
disk):

------
building /gnu/store/ma04vkl42jyr9p2nw5yzlzw61r5s2h3p-guix-1.1.0-31.1c6d985-checkout.drv...
guile: warning: failed to install locale
environment variable `PATH' set to `/gnu/store/378zjf2kgajcfd7mfr98jn5xyc5wa3qv-gzip-1.10/bin:/gnu/store/sf3rbvb6iqcphgm1afbplcs72hsywg25-tar-1.32/bin'
Initialized empty Git repository in /gnu/store/nwf2579gigc9xhnd7i82lpmja854l9fb-guix-1.1.0-31.1c6d985-checkout/.git/
error: Server does not allow request for unadvertised object 1c6d98533153bc8e0e36236e7fbcf1eb5e178d26
Failed to do a shallow fetch; retrying a full fetch...
------

I'm reaching out to the Savannah admins to ask them about this, and if
it has any unduly negative affects on the Savannah infrastructure.

Maybe these commits should be tagged?

[0]
That is, while building (@@ (gnu packages package-management) guix)

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

From: Leo Famulari <leo <at> famulari.name>
To: 44382 <at> debbugs.gnu.org
Subject: Re: Updating the guix package triggers a full Git clone of guix.git
Date: Sun, 1 Nov 2020 20:39:36 -0500

I poked around a bit and found that Savannah can serve shallow clones of
random commits, but does not allow shallow *fetching*, except for
special things such as Git tags. We fetch instead of clone.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: 44382 <at> debbugs.gnu.org
Subject: Re: bug#44382: Updating the guix package triggers a full Git clone
 of guix.git
Date: Tue, 03 Nov 2020 22:48:25 +0100

Hi,

Leo Famulari <leo <at> famulari.name> skribis:

> I poked around a bit and found that Savannah can serve shallow clones of
> random commits, but does not allow shallow *fetching*, except for
> special things such as Git tags. We fetch instead of clone.

Weird, what’s the difference between fetch and clone technically?  I
believe commit 329dabe13bf98b899b907b45565434c5140804f5 moved to “fetch”
precisely so we could do shallow clones.

Ludo’.

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

From: Leo Famulari <leo <at> famulari.name>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 44382 <at> debbugs.gnu.org
Subject: Re: bug#44382: Updating the guix package triggers a full Git clone
 of guix.git
Date: Thu, 5 Nov 2020 12:11:06 -0500

On Tue, Nov 03, 2020 at 10:48:25PM +0100, Ludovic Courtès wrote:
> Weird, what’s the difference between fetch and clone technically?  I
> believe commit 329dabe13bf98b899b907b45565434c5140804f5 moved to “fetch”
> precisely so we could do shallow clones.

I don't know. It's definitely weird.

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Leo Famulari <leo <at> famulari.name>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 44382 <at> debbugs.gnu.org
Subject: Re: bug#44382: Updating the guix package triggers a full Git clone
 of guix.git
Date: Sun, 29 Nov 2020 22:24:18 -0500

Hello,

Leo Famulari <leo <at> famulari.name> writes:

> On Tue, Nov 03, 2020 at 10:48:25PM +0100, Ludovic Courtès wrote:
>> Weird, what’s the difference between fetch and clone technically?  I
>> believe commit 329dabe13bf98b899b907b45565434c5140804f5 moved to “fetch”
>> precisely so we could do shallow clones.
>
> I don't know. It's definitely weird.

I had researched this before and the option the git server is missing is
uploadpack.allowAnySHA1InWant [0].  Unfortunately last I check in
#savannah their machine (vcs0) is using an older Trisquel stuck with git
v2.11.0, one patch version before when the above feature was introduced
(v2.11.1)!  If I understood correctly, they have a new VM vcs2 but it
needs to be completely setup before they can switch.

Maxim

[0]  https://github.com/git/git/commit/f8edeaa05d8623a9f6dad408237496c51101aad8

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

From: Leo Famulari <leo <at> famulari.name>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 44382 <at> debbugs.gnu.org
Subject: Re: bug#44382: Updating the guix package triggers a full Git clone
 of guix.git
Date: Wed, 29 Dec 2021 17:45:19 -0500

On Sun, Nov 29, 2020 at 10:24:18PM -0500, Maxim Cournoyer wrote:
> I had researched this before and the option the git server is missing is
> uploadpack.allowAnySHA1InWant [0].  Unfortunately last I check in
> #savannah their machine (vcs0) is using an older Trisquel stuck with git
> v2.11.0, one patch version before when the above feature was introduced
> (v2.11.1)!  If I understood correctly, they have a new VM vcs2 but it
> needs to be completely setup before they can switch.

Savannah is now using Git version 2.17.1. I wonder if we can have this
option enabled now? I checked and the problem described by this bug
still exists.

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Leo Famulari <leo <at> famulari.name>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 44382 <at> debbugs.gnu.org
Subject: Re: bug#44382: Updating the guix package triggers a full Git clone
 of guix.git
Date: Sat, 01 Jan 2022 23:59:26 -0500

Hi Leo,

Leo Famulari <leo <at> famulari.name> writes:

> On Sun, Nov 29, 2020 at 10:24:18PM -0500, Maxim Cournoyer wrote:
>> I had researched this before and the option the git server is missing is
>> uploadpack.allowAnySHA1InWant [0].  Unfortunately last I check in
>> #savannah their machine (vcs0) is using an older Trisquel stuck with git
>> v2.11.0, one patch version before when the above feature was introduced
>> (v2.11.1)!  If I understood correctly, they have a new VM vcs2 but it
>> needs to be completely setup before they can switch.
>
> Savannah is now using Git version 2.17.1. I wonder if we can have this
> option enabled now? I checked and the problem described by this bug
> still exists.

You'd want to check in #savannah, I think.  It'd help reduce bandwidth
and hasten 'guix pull' a bit if it were now possible, I think.

Thanks!

Maxim

Previous Next

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