Re: thousands of errors: "<filename> is not a valid ,v file"

tleonhard wrote:
> When trying to convert my cvs-repository to svn, i get thousands of errors
> containing "<filename> is not a valid ,v file". I read a number of entries
> about this topic, but I can't find anything helpful for me. 
> 
> I use SuSE 8 kernel 2.6.13.11, 
> cvs version 1.12.12, 
> cvs2svn version 2.3.0.
> 
> The corrupted files have one common line:
> "avendor:1.1.1:2003.09.18.05.51.55:@@;"
> What's wrong with this line? What can I do?

I assume that these lines appear in the "symbols" section of the header?

I've never seen anything like this.  I suspect that some deviant
CVS-like system is trying to store extra metadata, but this is
definitely not a valid CVS file according to rcsfile(5).  Is it possible
that this repository has been used under some other version control system?

As to working around the problem, you might try deleting everything
starting with the second colon until the trailing semicolon in these
files; e.g.,

    "avendor:1.1.1:2003.09.18.05.51.55:@@;" -> "avendor:1.1.1;"

Of course you should do this in a copy of your CVS repository, not the
original.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2388305

To unsubscribe from this discussion, e-mail: [[email protected]].