[p4] RCS Parse errors - RCS expected EOF

Wholly Mindless whollymindless at gmail.com
Wed Aug 13 16:20:58 PDT 2008


OK, I'd rather not explain HOW I got in this mess but I would like to
fix what I can to get OUT of this mess.  So, my db.'s are clean and
have good history but many of my ,v files are out of whack.  I'm
having some real issues trying to translate the error messages I'm
getting from perforce when it tries to retrieve revsions of some
files.

I have one ,v file that has 90+ revisions in it.  If I pull it out and
drop it in an RCS folder I seem to be able to check out any version I
like.   Perforce's db history lines up by time and revision number so
I am confident I'm starting with the right file - however that same
file under perforce returns messages like:

Date 2008/08/13 16:35:13:
Operation: user-annotate
RCS parse error at line 1066!
RCS expected EOF!

and

Date 2008/08/13 17:04:39:
Operation: user-print
Librarian checkout depot/filename.c failed.
RCS parse error at line 1066!
RCS expected EOF!

At least it's consistent!  The p4d console shows the same messages so
it's not really helpful.  Looking at the ,v file, I see nothing
interesting about line 1066, it is in the middle of the newest revision.

Is there some way to get more detail on why/what is going bad here? Is
there any way to validate that the ,v file is properly formatted
(beyond visual inspection)?  Is there a way to turn up logging (or a
log file I've not found yet) that would show more information?

Any hints would be appreciated.

Wholly



More information about the perforce-user mailing list