[cvsnt] Upgrade from CVSNT 2.0.51d to CVSNT 2.5.03 2382 - InvalidRCS Flags
glen.starrett at march-hare.com
Thu May 22 18:26:28 BST 2008
Sean Bertinotti wrote:
> I have done a trace when checking out the module and I've identified the
> file, it was not the file I thought it was.
That happens... it's why I asked you to verify :)
> I have opened that file in
> the repository and it's all garbaged, no CVS header info. It was a
> compiled file that shouldn't have been in there.
That's very odd, but there could be a few explanations (e.g. extracting
the file directly into the repository, bad transfer from one machine to
another, or just a plain 'ol bug at some point). Binary files should be
just fine -- no problems at all -- but they should *all* have the RCS
header information at the top of the RCS file.
> Question is how do I
> remove it, so that the checkout can carry on and I can clean up the
> repository, can I just delete it in the repository? If so then I can
> manually do this for each module until all non needed "corrupt" files
> get removed. Yes?
Yes, you can do that. You might also try using rlog, it may be easier
to work with (e.g. go until it bombs, then check that file or the next
in line). It sounds like the files you're finding are very corrupt, so
there shouldn't be any marginal cases (rlog/log catches most issues with
RCS files, but I don't know if it'll get them all).
Technical Account Manager, North America
March Hare Software, LLC
More information about the cvsnt