From: Zenaan Harkness <zen@cashpoolcomps.com>
To: arch <gnu-arch-users@gnu.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1099109410.17184.17.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Sat, 30 Oct 2004 14:10:10 +1000
Subject: [Gnu-arch-users] corrupt pristine
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 1532
Lines: 42
Can we simply delete a currupt (inodes due to old machine dying => new
disk) pristines tree, and all will continue to work as expected (no
revlib here)?

Error as follows on attempt to commit:
---
corrupt pristine (failed inode signature validation)
    archive: parth@cashpoolcomps.com--cpcParthArchive04
    revision: cpc--parthDev--5.0--patch-17
    directory
/home/parth/workingDir50OldMachine/{arch}/++pristine-trees/unlocked/cpc/cpc--parthDev/cpc--parthDev--5.0/parth@cashpoolcomps.com--cpcParthArchive04/cpc--parthDev--5.0--patch-17
You should remove this pristine from your tree.

---
Now, the really baffling thing for me (since I don't understand it) is
that we got the same error, when we renamed the old working dir tree to
a backup name, then tried to checkout (get) a new working tree ???

That seems bizarre to me, since I never got such an error before. Why
should he (my workmate) not be able to checkout a new working tree? That
seems like a serious bug to me.

Now, when _I_ do a get of his archive (tla get $parthat tmpwd) it works
just fine. What gives?

Finally, to test further, we tar-ed up the working directory into a
backup file, deleted the actual directory, and now we _could_ tla get a
working tree of that archive.

Can anyone explain this seemingly very strange behaviour?

tia
zen


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/