Submodules borked
0xhaggis opened this issue · comments
The theos submodule is broken in master. To reproduce: clone a new copy of the repo, then do git submodule update --init. You'll see:
Submodule 'GRMustache' (https://github.com/groue/GRMustache.git) registered for path 'GRMustache'
Submodule 'OpenSSL-for-iPhone' (https://github.com/x2on/OpenSSL-for-iPhone.git) registered for path 'OpenSSL-for-iPhone'
Submodule 'layout/var/www/iSpy/static/DataTables' (https://github.com/DataTables/DataTables.git) registered for path 'layout/var/www/iSpy/static/DataTables'
Submodule 'layout/var/www/iSpy/static/bootstrap-progressbar' (https://github.com/minddust/bootstrap-progressbar.git) registered for path 'layout/var/www/iSpy/static/bootstrap-progressbar'
Submodule 'layout/var/www/iSpy/static/font-awesome' (https://github.com/FortAwesome/Font-Awesome.git) registered for path 'layout/var/www/iSpy/static/font-awesome'
Submodule 'layout/var/www/iSpy/static/jQuery-contextMenu' (https://github.com/medialize/jQuery-contextMenu.git) registered for path 'layout/var/www/iSpy/static/jQuery-contextMenu'
error: invalid key (newline): submodule.theos
theosfork.url
error: invalid key (newline): submodule.theos
theosfork.url
No url found for submodule path 'theos' in .gitmodules
If you remove the following line from .gitmodules and retry, the submodule initialization will proceed but barf at the end. Remove these lines:
[submodule "theosfork"]
path = theos
url = https://github.com/moloch--/theos
The new error is:
Cloning into 'theos'...
remote: Reusing existing pack: 4101, done.
remote: Counting objects: 10, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 4111 (delta 1), reused 6 (delta 0)
Receiving objects: 100% (4111/4111), 913.27 KiB | 540.00 KiB/s, done.
Resolving deltas: 100% (2058/2058), done.
Checking connectivity... done.
fatal: reference is not a tree: 5ebf6be26aa92206b4f00494fac988729ef7b07c
Unable to checkout '5ebf6be26aa92206b4f00494fac988729ef7b07c' in submodule path 'theos'
You need to purge your local cache, you still have a cached module of the old tree which is why the commit is not found (git can be frustrating!)
Nope, this is a fresh pull of master.