Git子模块检出错误:"致命:引用不是树"

时间:2015-05-20 11:40:15

标签: git git-submodules

供参考,请参阅问题https://github.com/drmeister/clasp/issues/98

要重现,请执行以下操作:

git clone git://github.com/drmeister/clasp claspcl
cd claspcl
git checkout tags/0.3-test-3
git submodule update --init

结果是:

git submodule update --init
Submodule 'updatedAsdf' (https://github.com/drmeister/asdf.git) registered for path 'src/lisp/kernel/asdf'
Submodule 'src/lisp/kernel/contrib/sicl' (https://github.com/drmeister/SICL.git) registered for path 'src/lisp/kernel/contrib/sicl'
Submodule 'src/mps' (https://github.com/Ravenbrook/mps-temporary) registered for path 'src/mps'
Cloning into 'src/lisp/kernel/asdf'...
remote: Counting objects: 13416, done.
remote: Total 13416 (delta 0), reused 0 (delta 0), pack-reused 13416
Receiving objects: 100% (13416/13416), 5.34 MiB | 838.00 KiB/s, done.
Resolving deltas: 100% (9935/9935), done.
Checking connectivity... done.
Submodule path 'src/lisp/kernel/asdf': checked out 'dcd692a8f9f6a5cb86133123e1c433a9afb4e7e9'
Cloning into 'src/lisp/kernel/contrib/sicl'...
remote: Counting objects: 49356, done.
remote: Total 49356 (delta 0), reused 0 (delta 0), pack-reused 49356
Receiving objects: 100% (49356/49356), 8.49 MiB | 298.00 KiB/s, done.
Resolving deltas: 100% (37020/37020), done.
Checking connectivity... done.
fatal: reference is not a tree: 280c12ab49223c64c6f914944287a7d049cf4dd0
Cloning into 'src/mps'...
remote: Counting objects: 25250, done.
remote: Total 25250 (delta 0), reused 0 (delta 0), pack-reused 25250
Receiving objects: 100% (25250/25250), 86.87 MiB | 831.00 KiB/s, done.
Resolving deltas: 100% (15851/15851), done.
Checking connectivity... done.
Submodule path 'src/mps': checked out '3e6640e7eeb5d086adec18e6227a84da59898e1c'
Unable to checkout '280c12ab49223c64c6f914944287a7d049cf4dd0' in submodule path 'src/lisp/kernel/contrib/sicl'

如您所见,复制配方不会触及sicl子模块。所以,我最好的猜测是clasp Git存储库在其中的某个地方有280c12ab49223c64c6f914944287a7d049cf4dd0的虚假引用。 #git上的人似乎也认为这是合情合理的。如您所见,复制配方不会触及sicl子模块。那么,如何最好地解决这个问题呢? clasp Git存储库需要什么样的手术?

注意:如果没有git checkout tags/0.3-test-3步骤,问题就不会显示出来。所以问题可能出在那个特定的分支,这里fixnum.

1 个答案:

答案 0 :(得分:1)

我按照你的指示,能够重现问题 它不是你做的,对象280c12ab49223c64c6f914944287a7d049cf4dd0 已损坏,你无法做任何事情来解决它。

我需要做一个解决方法并获取主人的内容:

git show 280c12ab49223c64c6f914944287a7d049cf4dd0
(will display bad object)
cd sicl
git checkout clos
git branch -d master
git fetch --all --prune
git checkout master
git fsck

完成上述步骤后,git show 280c12ab49223c64c6f914944287a7d049cf4dd0仍然显示坏对象(因为它在原始存储库中存在问题)

但更奇怪的是git fsck没有发现任何错误,我会在今天晚些时候进行调查。

目前,解决方法将允许您继续工作。