GNU bug report logs - #42420
git-fetch origins produce same store output when set recursive is set to true or false

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: pkill9 <pkill9 <at> runbox.com>
Subject: bug#42420: closed (Re: bug#42420: git-fetch origins produce same
 store output when set recursive is set to true or false)
Date: Sat, 28 Nov 2020 17:05:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#42420: git-fetch origins produce same store output when set recursive is set to true or false

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 42420 <at> debbugs.gnu.org.

-- 
42420: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42420
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Leo Famulari <leo <at> famulari.name>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 42420-done <at> debbugs.gnu.org, pkill9 <pkill9 <at> runbox.com>,
 Marius Bakke <marius <at> gnu.org>
Subject: Re: bug#42420: git-fetch origins produce same store output when set
 recursive is set to true or false
Date: Sat, 28 Nov 2020 12:04:16 -0500

On Sat, Nov 28, 2020 at 12:23:28AM -0500, Maxim Cournoyer wrote:
> Is there an action to do here, or should we simply close it?

If we have a good idea for how to improve the situation, we should use
it. Otherwise, we can close the bug. It's something that confuses a lot
of people the first time but, once you learn what's happening, it's easy
to avoid in the future.

[Message part 3 (message/rfc822, inline)]

From: pkill9 <pkill9 <at> runbox.com>
To: bug-guix <at> gnu.org
Subject: git-fetch origins produce same store output when set recursive is
 set to true or false
Date: Sat, 18 Jul 2020 23:19:09 +0100

I built a source that uses git-fetch - by default (recursive? #f) - and
the package failed to build, then I remembered it uses submodules, so I
set (recursive? #t) but it failed with the same error. The problem is
that the store path of the source is the same for both, so it didn't
try to rebuild the git checkout with submodules checked out.

After garbage collecting the source so it rebuilds it, I can build the
package.

Previous Next

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