On Thu, Sep 13, 2012 at 5:32 AM, Andreas Tscharner
<andreas.tschar...@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:
1.100
1.99
1.98
* Things had to be restructured at 1.97
Problems with layout
1.97
1.96
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...
Ouch.
