I went to clone a repository from GitHub today and discovered
something interesting:
:: git clone https://github.com/liebke/incanter.git
Cloning into 'incanter'...
remote: Counting objects: 10457, done.
remote: Compressing objects: 100% (3018/3018), done.
error: object 4946e1ba09ba5655202a7a5d81ae106b08411061:contains
zero-padded file modes
fatal: Error in object
fatal: index-pack failed
At first, it surprised me that no one has seen the issue before,
but then I remembered I have transfer.fsckObjects=true in my
config. Turning it off, I was able to clone. Running `git
fsck` I see:
:: git fsck
Checking object directories: 100% (256/256), done.
warning in tree 4946e1ba09ba5655202a7a5d81ae106b08411061: contains
zero-padded file modes
warning in tree 553c5e006e53a8360126f053c3ade3d1d063c2f5: contains
zero-padded file modes
warning in tree 0a2e7f55d7f8e1fa5469e6d83ff20365881eed1a: contains
zero-padded file modes
Checking objects: 100% (10560/10560), done.
So there appears to be several instances of the issue in the
tree. Looking in the archives, I ran across this thread:
http://comments.gmane.org/gmane.comp.version-control.git/143288
In there, Nicolas Pitre says:
> This is going to screw up pack v4 (yes, someday I'll have the
> time to make it real).
I don't know if this is still true, but given that patches are
being sent out about it, I thought it relevant.
Also, searching on the issue, you'll find that a number of
repositories have suffered from this problem, and it appears the
only fix will result in different commit ids. Given all of
that, should Git be updated to cope with zero padded modes? Or
is there no some way of fixing the issue that doesn't involve
changing commit ids?
Thanks!
-John
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html