Jack Repenning points out:
There are cases where cvs2svn aborts due to surprises in the ,v files.
In some cases, I don't think this is the right behavior; it would be
better to ignore the anomaly and press on, with a warning at the end.
Here are the two such cases I've spotted:
L106, "branch XXX already has name YYY, cannot also have name ZZZ"
L157, "XXX is not a valid tag or branch name"
The second problem may be partially addressed by r8168's resolution of issue
#1524. But there are probably other instances where cvs2svn exits when it could
just warn, ignore, and move on instead. Since conversions take so long, this
will often be a preferable behavior.
Regarding the first problem, Jack threw out this idea:
The mult-named branch thing is similar, though I haven't (yet)
encountered it in [my repository]: cvs allows it, it's clear
enough that it's a problem for SVN, but a notice at the end seems
sufficient. In this case, I imagine I'd simply copy the branch
to the additional name (as a manual finishing-up process). Maybe
I'd rename the one you chose with the other name, 'cause that's
the one I really want. ... But anyway, the conversion would be
over, most people could get back to work, and there would be no
data lost.
Improvement
Major
SVN-1623 cvs2svn.py barfs on mono's cvs repo