Working directory has unknown parent

Hubert Matthews hubert at oxyware.com
Thu Jan 7 10:40:57 CST 2010


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

$ hg status
abort: working directory has unknown parent '436dcc9b0b14'!

The smoking gun appears to be the changelog.

$ hg debugindex .hg/store/00changelog.i    # thanks to Jim Hague!
   rev    offset  length   base linkrev nodeid       p1           p2
     0         0     132      0       0 ef12c2048319 000000000000
000000000000
     1       132     114      0       1 00b8cfc76ddc ef12c2048319
000000000000
     2       246     127      2       2 db7592aba6d8 00b8cfc76ddc
000000000000
     3       373     107      2       3 0974438f17fd db7592aba6d8
000000000000
     4       480     116      4       4 4858eac93876 0974438f17fd
000000000000
     5       596     100      4       5 e0a1d30817d7 4858eac93876
000000000000
     6       696     117      6       6 b9d2bda0713b e0a1d30817d7
000000000000
     7       813     104      6       7 1e5fd101763e b9d2bda0713b
000000000000
     8       917     122      8       8 90005467c504 1e5fd101763e
000000000000
     9      1039     124      8       9 3b4a8f78edc0 90005467c504
000000000000
    10      1163     116     10      10 367d5afc2546 3b4a8f78edc0
000000000000
    11      1279     109     10      11 4fb1c1333fb9 367d5afc2546
000000000000
    12      1388     115     12      12 3b22a62cf22c 4fb1c1333fb9
000000000000
    13      1503      97     12      13 9c80d444376a 3b22a62cf22c
000000000000
    14      1600     126     14      14 45efdefc8838 9c80d444376a
000000000000
    15      1726     124     14      15 2462d4fe8be7 45efdefc8838
000000000000
    16      1850     127     16      16 93914b6f19ff 2462d4fe8be7
000000000000
    17      1977     105     16      17 46a89e7f3462 93914b6f19ff
000000000000
    18      2082     132     18      18 8a55938433b1 46a89e7f3462
000000000000
    19      2214     115     19      19 f2b9e54d6d28 8a55938433b1
000000000000
    20      2329     118     19      20 4e9164292826 f2b9e54d6d28
000000000000
    21      2447     130     21      21 fa6ab12e3a83 4e9164292826
000000000000
    22      2577     130     21      22 d5ba011cd721 fa6ab12e3a83
000000000000
    23      2707     139     23      23 a10fb8380cec d5ba011cd721
000000000000
    24      2846     153     23      24 53718d4c277d a10fb8380cec
000000000000
    25      2999     148     25      25 5823f7cd0d8d 53718d4c277d
000000000000
    26      3147     120     25      26 52082bed7a5f 5823f7cd0d8d
000000000000
    27      3267     130     27      27 436dcc9b0b14 52082bed7a5f
000000000000

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).

-- 
Hubert Matthews         http://www.oxyware.com/
Software Consultant     hubert at oxyware.com




More information about the Mercurial mailing list