cvs2svn.py vs. repository structure

Hello,

After successfully getting subversion to work with apache2, I would like to
migrate an old CVS repository now.
Using cvs2svn.py this generally works, but not with the expected result.
In my CVS repository I have several modules:

var/lib/cvs/vdr
var/lib/cvs/vdr-plugin-teletext
...

After...

cvs2svn.py --create -s -v -s /var/lib/svn /var/lib/cvs

...I get the following svn repository structure:

svn/trunk/CVSROOT
svn/trunk/vdr
svn/trunk/vdr-plugin-teleltext
svn/tags/debian_version_0_0_1-1
svn/tags/debian_version_0_11-3
svn/tags/debian_upstream_0_0_1
svn/tags/debian_upstream_0_11
svn/branches/source-dist/vdr
svn/branches/source-dist/vdr-plugin-teletext
...

What I have expected is something like this:

svn/vdr/trunk
svn/vdr/branch
svn/vdr/tags
svn/vdr-plugin-teletext/trunk
svn/vdr-plugin-teletext/branch
svn/vdr-plugin-teletext/tags
...

I'm pretty sure that I either did something wrong or that I havn't
understood how a svn repository should be stuctured.

Any help would be appreciated!

Thanks,

Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 11 02:16:07 2004