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

Re: Cvs2svn - one repo/module

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-02-04 18:36:56 CET

Arnout Standaert <arnout.standaert@cit.kuleuven.ac.be> writes:

> >>Is there a way to tell cvs2svn to convert the CVS modules in one CVS
> >> repository to separate SVN repositories?
> > Yeah, just convert the subdirs that represent your modules. I mean,
> > on Unix, you could do something like (typing without trying this, so
> > pay attention only to the gist of my idea):
> > $ cd /path/to/cvs/repos
> > $ for module in `ls -1 | grep -v CVSROOT`; do \
> > cvs2svn.py --create -s ${module}-svn-repos ${module}; done
> Thanks for that!
> It works perfectly for most smaller modules. I'm getting errors on
> some (mostly larger) CVS modules, I'm getting "KeyError" errors like
> "250", "115", "Db", "fed", depending on which module I'm trying to
> convert.

Oh... Now that's just wrong. cvs2svn shouldn't be doing that. Are
you using a recent version?

> I know that branches and tags are still a difficult point for cvs2svn,
> so I'm just gonna wait for a 1.0 release. But, on the other hand: I'm
> using CVSNT on a Windows machine as a CVS server. Maybe the CVSNT
> repositories have a slightly different structure, could that be the
> cause of the cvs2svn errors?

CVSNT does allow some things that violate the RCS standard, but again,
not to the point where you should be seeing KeyErrors. If you have a
small repository that you don't mind sharing and which demonstrates
this problem with really recent cvs2svn (like, as of today), I'd love
to see it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 4 18:37:43 2004

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.