octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hg repo corruption -- anyone have a backup?


From: John W. Eaton
Subject: Re: hg repo corruption -- anyone have a backup?
Date: Fri, 31 Aug 2012 03:59:31 -0400

On 30-Aug-2012, Judd Storrs wrote:

| I have a way old one:
| 
| $ hg log | head
| changeset:   10952:18b0af0bbd6b
| tag:         tip
| user:        Ben Abbott <address@hidden>
| date:        Wed Sep 08 08:17:48 2010 -0400
| summary:     image.m: Fix axis limits for single dimension images, add demo.
| 
| $ hg verify
| checking changesets
| checking manifests
| crosschecking files in changesets and manifests
| checking files
| 7772 files, 10953 changesets, 76766 total revisions

Thanks for checking.  I also had one from February 2010 that was
clean.

I'm also able to generate an archive that is clean up to this changeset:

  changeset:   13329:80f7564a3849
  user:        John W. Eaton <address@hidden>
  date:        Wed Oct 12 12:18:27 2011 -0400
  summary:     handle class objects in num2cell

from the current archive that seems to have problems.  The next
changeset is

  changeset:   13330:583c15dd487b
  parent:      -1:000000000000
  user:        Jacob Dawid <address@hidden>
  date:        Tue Apr 05 00:12:18 2011 +0200
  summary:     Initial commit.

and this is where things start to go bad for me.  Note the strange
parent ID.  Is that correct?  I thought the gui branch was a clone of
Octave with the gui directory added?  Is that not correct?

I can get to a clean archive by doing

  hg clone /screwed/up/archive/octave
  cd octave
  hg strip 583c15dd487b

but then after

  hg pull -r 583c15dd487b /screwed/up/archive/octave

I see the following verify failure:

  checking changesets
  checking manifests
  crosschecking files in changesets and manifests
  checking files
  warning: orphan revlog 'data/gui/Quint.pro.i'
  warning: orphan revlog 'data/gui/README.i'
  8858 files, 14597 changesets, 94927 total revisions
  2 warnings encountered!

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]