[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: cvs2svn failing on "non-CVS" files

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 14 Sep 2012 06:51:21 -0400

On Thu, Sep 13, 2012 at 5:32 AM, Andreas Tscharner
<Andreas.Tscharner_at_metromec.ch> wrote:
>> /data/cvs/tusk/ocw/tmpl/Attic/header,v
>> Processed 5345 files
>> Pass 1 complete.
>> ==============================================================
>> =============
>> Error summary:
>> ERROR: '/var/www/cvs/module/badfile,v' is not a valid ,v file
>> Has anyone had fun and experience with CVS files that work in CVS, but
>> break cvs2svn? Are there any particular pointers? Any guidelines on
>> repairing such mangled files?
> We have had similar errors when we changed. The only solution I had was to remove these files from the CVS repo and finally re-add them in the svn repo. Of course this works only if there are only a few files (it was 6 in our case)

Found it!!!!

Someone put comments in among the numerical names of revisions in the
beginning of the file, so it looked like this:

           * Things had to be restructured at 1.97
           Problems with layout

Once I stripped out the commentary in the weird location, everything
seems to work. I have developer with the code verifying their CVS
branches. I'm unsure whether someone manually edited the files 6 years
back, or there's some way to store such comments there gracefully, but
clipping that commentary seems to resolve the cvs2svn conversion.

> The actual cause in our case was: CVSNT (!) has saved these files (they were all binary) with a '0' somewhere in the file what the converter didn't like...

Received on 2012-09-14 12:52:01 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.