--- Begin Message ---
|
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.
--- End Message ---
--- Begin Message ---
|
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.
--- End Message ---