Re: recovering from "unordered stage entries in index" error
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- May 23, 2015, 02:06 UTC
- Message-ID
- <CACsJy8As8-b6kWHDnmAwAftyPG6X-BmoQdToQywzn9D4dtg2Fg@mail.gmail.com>
- In-Reply-To
- <D377A9280DB18546A2471214D5CBB0E9087568F47B@exchdb01>
On Sat, May 23, 2015 at 1:56 AM, McHenry, Matt <mmchenry@carnegielearning.com> wrote:
> $ git svn fetch > fatal: unordered stage entries in index > write-tree: command returned error: 128
git-svn does not create the index manually. It uses update-index or read-tree to do that. While there's still a chance of bugs in update-index that produces broken index, it's probably read-tree in this case because it assumes good order from the source tree object, which is(?) generated by git-svn. And the write-tree message supports this (the code does read-tree then write-tree).
So maybe you can do "GIT_TRACE=2 git svn fetch" and post the output. I'd expect to see something like "git read-tree <sha1>" before "fatal: unorder...". You can then use git ls-tree <sha1> to examine this tree, try to sort the file list with "LANG=C sort" and compare with the original list.
-- Duy