Tree has duplicate entries after commit

[half-ogre]

We've had at least two reports from GHfW users that after making a simple commit, they can't push due to a duplicate entries error, confirmed by fsck. It looks like it's probably due to casing differences in the history. I can't point you to the repositories, because they are both private on GitHub (and I can't manage to create a repo that repros myself). If a GitHubber looks at this, I can point them to the repositories to easily see the error. I can also put together a code sample that causes the bug if that's helpful.

[nulltoken]

More information:

https://www.google.com/search?q=%22contains+duplicate+file+entries%22

[nulltoken]

Ok. Using libgit2 I've successfully been able to reproduce the issue and create a git_tree with duplicate entries

$ git ls-tree be67
100644 blob a8233120f6ad708f843d861ce2b7228ec4e3dec6    duplicate
100644 blob 45b983be36b73c0788dc9cbcb76cbb80fc7bb057    duplicate
100644 blob a71586c1dfe8a71c6cbf6c129f404c5642ff31bd    duplicate

[nulltoken]

cf. libgit2/libgit2#1056

[nulltoken]

@half-ogre The latest libgit2 binaries have been embedded in the tip of vNext and should embed the fix preventing the creation of a Commit from a conflicted index.

Closing this now.