info-cvs
[Top][All Lists]
Advanced

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

Re: Strange error: EOF in value...


From: Donald Sharp
Subject: Re: Strange error: EOF in value...
Date: Mon, 4 Jun 2001 17:08:02 -0400
User-agent: Mutt/1.2.4i

I'm attaching a script that will find the damaged version for you.

donald
On Mon, Jun 04, 2001 at 04:03:34PM -0400, Larry Jones wrote:
> Dennis Jones writes:
> > 
> > cvs [server aborted]: EOF in value in RCS file
> > /vol/cvs/Projects/GenServr/SelectVehicle.dfm,v
> > 
> > What is the meaning of this error, and what do I have to do in the
> > repository file(s) to correct it?
> 
> Your repository has been corrupted -- the RCS file ends in the middle of
> what CVS thinks is the value associated with some keyword.  The file may
> be truncated, or there could be come corruption in the middle that
> causes the quotes (which are actually @'s in RCS files) to get out of
> sync.  Fixing it is tricky -- you pretty much have to manually edit the
> RCS file.  You'll need an intimate knowledge of the RCS file format and
> either some way to get older revisions of the file or a willingness to
> lose them.
> 
> You can probably locate the damaged section of the file by checking out
> different revisions, using a binary search along the revision tree to
> locate the damaged node.  For example, if you can check out revision
> 1.1, then you know the trunk is OK and the damage must be on a branch.
> 
> The most often reported cause of this type of damage is bugs in network
> filesystem code.  If your repository is network mounted, I strongly
> suggest you stop that immediately and switch to a locally mounted
> repository on a server machine.
> 
> -Larry Jones
> 
> Let's pretend I already feel terrible about it, and that you
> don't need to rub it in any more. -- Calvin
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs

Attachment: check_cvs.pl
Description: Perl program


reply via email to

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