Mike Quinn writes:
>
> configuration is a CVS database in an NFS or locally-mounted repository (I can
> reproduce it either way),
If you've been working with an NFS-mounted repository, it's entirely
possible that it's already corrupted and 1.11.2 is just noticing it
where earlier versions didn't.
> we added a branch tag, and at that point most of our CVS database became corrupt
> (checkouts, updates, diffs all complain about the format of the files).
It would be helpful to know exactly what error message(s) you get.
> Both
> cvs tag and cvs rtag will reproduce the problem. Nothing special - just
>
> cvs tag -b -r <branch> <newbranch> or the rtag equivalent
>
> I've restored our database from a backup, and if I add a tag, I can duplicate
> the problem. Everything looks fine if you check out the HEAD of the tree, but
> if you try to check out any branch tag, you will get corruption problems.
Have you tried checking out a branch *without* adding a new tag? My
guess is you'll have exactly the same problem. Donald Sharp posted a
perl script a while back to check a repository for corruption -- I
suggest you get it and run it:
<http://mail.gnu.org/pipermail/info-cvs/2001-June/015932.html>
-Larry Jones
I won't eat any cereal that doesn't turn the milk purple. -- Calvin
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
