Git Submodules. Pulling into a new clone of the super-project

Question

OK. So I thought I had this licked ... but now ....

I have a project which includes one small library from GitHub as a submodule. In the original version of that super-project the submodule is working as expected.

However, I just cloned the superproject, did what I thought I should : "git submodule init", got the directory of the submodule to appear, but it's empty.

If I now try to do

git submodule update

I get

fatal: Needed a single revision Unable to find current revision in submodule path 'external_libraries/BEACHhtml'

If I try

git submodule foreach git pull

I get

Entering 'external_libraries/BEACHhtml' fatal: Where do you want to fetch from today? Stopping at 'external_libraries/BEACHhtml'; script returned non-zero status.

In my .git/config, I have this :

[submodule "external_libraries/BEACHhtml"] url = [email protected]:interstar/BEACHhtml.git

In my .gitmodules I have this :

[submodule "external_libraries/BEACHhtml"] path = external_libraries/BEACHhtml url = [email protected]:interstar/BEACHhtml.git

Anyone got an idea what's missing?

Robert · Accepted Answer · 2020-05-20 07:20:19Z

196

It seems that now (in 2019) installing latest GIT client could solve the problem according to comments below. This should be the best solution for now.

I have the same problem as you. This is a bug in git: http://git.661346.n2.nabble.com/BUG-git-submodule-update-is-not-fail-safe-td7574168.html

In short, for your problem, try:

# rm -rf external_libraries/BEACHhtml # git submodule update

It seems there is something wrong with the previous checkout folder, remove it, and update again solves the problem.

edited May 20, 2020 at 7:20

Robert

1818 bronze badges

answered Dec 20, 2011 at 9:31

Han He

3,4613 gold badges26 silver badges26 bronze badges

Sign up to request clarification or add additional context in comments.

12 Comments

Mihai Timar Over a year ago

for me it was a hanged git-fetch that was keeping the folder locked

Tobu Over a year ago

I had to remove both the submodule worktree (ext/blah) and the matching folder below the GIT_DIR (.git/modules/ext/blah).

Maverik Over a year ago

In my particular case git submodule update kept failing on my CI server because it wanted somebody to accept the RSA keys (ci server normally uses https connection and this was the first time a submodule had pulled in ssh connection). Hope it saves somebody an hour of head scratching!

Paulo Neves Over a year ago

In 2016 this bug still goes on :(

william.taylor.09 Over a year ago

2017 checking in, still present.

|

Ilya Serbis · Accepted Answer · 2017-07-26 10:57:39Z

Solved by deleting 2 directories and refetching submodule:

Go to external_libraries/BEACHhtml and look into .git file. It's content should be something like gitdir: ../../.git/modules/external_libraries/BEACHhtml
Delete both external_libraries/BEACHhtml and .git/modules/external_libraries/BEACHhtml directories.

From now on git submodule update runs without errors.

you may need to run git submodule init before git submodule update so that the submodule is re-initialized, then this will work.

epatel · Accepted Answer · 2013-07-04 12:54:34Z

I had this problem (flaky network so I got dropped submodule checkout like this) and I solved it by making this script (named it git-submodule-fix so I could run it as git submodule-fix)

#!/bin/bash for arg do echo $arg find . -name "`basename $arg`" | grep "$arg\$" | xargs rm -fr done

If you get this i.e. from a git submodule update

fatal: Needed a single revision Unable to find current revision in submodule path 'some/submodule/path'

do

git submodule-fix some/submodule/path git submodule update

vehsakul · Accepted Answer · 2019-07-17 20:44:42Z

1

If you are reading in 2019 or later, just update the git client. Worked for me.

answered Jul 17, 2019 at 20:44

vehsakul

1,1881 gold badge11 silver badges19 bronze badges

Comments

loscil · Accepted Answer · 2021-11-18 21:37:05Z

I ran into this in 2021 when I got into a detached HEAD state between commits from the sub-module repo's source and it's version in the 'calling' main repo.

this answer helped --> How do I fix a Git detached head?

And I verified this strategy with new changes to the sub-module repo

$ cd <into the sub-module dir within the calling/main repo>
$ git pull --> the sub-module repo brings in any changes from it's source
$ cd <back into the calling/main repo>
$ git status --> should show new changes to be committed for the sub-module repo

Adam Dymitruk · Accepted Answer · 2011-09-30 04:46:40Z

use a diff tool to compare the original clone that's working and this one. Also, what does git submodule output. Ensure you are pointing to the same branch in each repo before you do.

I'm suspecting that you've switched to a branch or older revision where the submodule was not defined.

hope this helps

David Lukac · Accepted Answer · 2013-03-04 09:55:18Z

I had the same issue with a submodule on a project. When I tried to clone the submodule separately it worked well.

I've tried all of the answers above, but without success (git submodule update, ..., removing the submodule folders, ...).

The issue disappeared after update of git (from Git-1.7.11-preview20120710) to latest version (to Git-1.8.1.2-preview20130201) at the time. Strangely my colleagues had even older version, worked without any issues, but they were on Mac. I'm on Win7 64bit.

Collectives™ on Stack Overflow

Git Submodules. Pulling into a new clone of the super-project

7 Answers 7

12 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

12 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Linked

Related