Working directory has unknown parent

Matt Mackall mpm at selenic.com
Thu Jan 7 12:35:06 CST 2010


On Thu, 2010-01-07 at 16:40 +0000, Hubert Matthews wrote:
> One of my repositories has got itself in a state that I believe is the
> same as Issue 1933 on the bug list
> (http://mercurial.selenic.com/bts/issue1933).  I'm using 1.4.1 on a local
> ext3-formatted disk running Fedora Core 11.  The working directory and the
> contents of the .hg directory tree are present and seem sensible.
> 
> $ uname -a
> Linux maisy.oxyware.net 2.6.30.10-105.fc11.i686.PAE #1 SMP Thu Dec 24
> 16:41:17 UTC 2009 i686 i686 i386 GNU/Linux
> 
> $ rpm -q mercurial
> mercurial-1.4-1.fc11.i586
> 
> $ hg verify
> checking changesets
> checking manifests
> crosschecking files in changesets and manifests
> checking files
> 0 files, 0 changesets, 0 total revisions

Those numbers are revealing.

> The smoking gun appears to be the changelog.
> 
> $ hg debugindex .hg/store/00changelog.i    # thanks to Jim Hague!

Everything points to this file not even being read.

> Note the nodeid of the last entry is the same hash as the hg status error
> message.
> 
> Is there a fix for this?  Fortunately it's a small test repository that is
> of no commercial value so if it is doomed then I won't cry too much. It
> also means that I'm happy enough to forward the contents to anyone that
> wants to see and it's small (69KB tgz).

You can send me a copy.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial mailing list