[Gnu-arch-users] Re: Corrupt pristine tree

[Greek0]

On Thu, 11 Mar 2004 13:38:44 -0700
"C. R. Oldham" <address@hidden> wrote:

> I upgraded my Linux box and moved my home directory onto a new disk. 
> I also upgraded to ext3.  Now on my trees I get
> 
> corrupt pristine (failed inode signature validation)
> 
> Whenever I try to commit.  The message recommends "You should remove
> this pristine from your tree."  How do I do that?  Why do I get this
> message?

In the root of your working directory do:
$ rm -rf {arch}/++pristine-trees
Done.

You get this message, because tla thinks, that the pristine tree got
corrupted. Tla checks this by looking, if inode numbers or device
numbers or change time or filesize of any file in the pristine tree
changed. If any of these values changed, it's very likely that the file
content changed too, which would cause problems when creating the
changeset. So inode signature validation is just a very fast way to make
sure that the files in the pristine trees haven't changed.

Since you have copied your working tree to a new partition inode numbers
and device numbers changed, so tla (incorrectly) believes, that your
pristine tree got corrupted.

Greetings,
Greek0