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

cvs2svn failing on "non-CVS" files

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Wed, 12 Sep 2012 18:30:06 -0400

I'm helping upgrade a 12 year old CVS repository to use modern source
control, and have run into a bit of a surprise. Running either cvs2svn
or cvs2git, I'm finding a couple of old CVS files that were hand
edited, 6 hears, and cause cvs2svn to fail with this kind of error.

Processed 5345 files
Pass 1 complete.
Error summary:
ERROR: '/var/www/cvs/module/badfile,v' is not a valid ,v file

This is with cvs2svn 2.3.0, Subversion 1.6.12 on Ubuntu or Subversion
1.6.11 on RHEL. I've also tested with Subvesion 1.7.4 on RHEL, same
problem. My problem is that the CVS files check out OK with plain CVS,
and my clients really want to keep the history intact in their

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?
Received on 2012-09-13 00:30:43 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.