[p4] RCS Parse errors - RCS expected EOF
robert at vizim.com
Thu Aug 14 14:23:05 PDT 2008
Perforce does not use rcs executables - it reads and writes the formats
directly. This is for performance and reliability reasons I imagine. Note
also that recent releases do things like use the changelist number for
versions - this to enhance performance in things like obliterate.
Have you checked with od or equivalent?
Perforce suppport have utilities to validate RCS archive files which might
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Wholly Mindless
> Sent: 14 August 2008 18:01
> To: perforce-user at perforce.com
> Subject: Re: [p4] RCS Parse errors - RCS expected EOF
> Despite it looking like there was not a terminating linefeed,
> it made no difference adding it.
> I figured I'd see if the server's installation of RCS could
> digest the file and I find that RCS isn't even installed on
> the server. (I'd been using cygwin's rcs)
> On Wed, Aug 13, 2008 at 5:51 PM, Ivey, William
> <william_ivey at bmc.com> wrote:
> > Just a long shot, but if this is on Unix, is the last
> character in the
> > file a linefeed? Some file operations will fail if a "text"
> > file doesn't end with a linefeed. It's not consistent across all
> > tools, though, and it usually doesn't cause an error, just
> causes the
> > last line to be dropped. (Why this would be reported as a
> problem in
> > the middle of the file, I don't know.)
More information about the perforce-user