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

Re: cvs2svn - Try #2

From: <cmpilato_at_collab.net>
Date: 2003-07-29 20:31:34 CEST

David Summers <david@summersoft.fay.ar.us> writes:

> I've now written a script (slighly tested) which should work to convert
> CVS repositories with the above propery to "proper" CVS repositories where
> the username doesn't have a space in it. I'll send it in a separate
> message in a bit for people who are interested.

Nice! If you plan to support this script, though, and you have a
website that you anticipate being around for a file, perhaps you could
just post your script on that website for all to grab, and we could
reference your URL in the Subversion cvs2svn docs.

> * deleting path :
> branches/ModCom_with_stl_alloc/source/lib/fslib_com/Project/fslib_com.dsw
> ...svn: Filesystem has no item
> svn: file not found: transaction `20d', path
> `branches/ModCom_with_stl_alloc/source/lib/fslib_com/Project/fslib_com.dsw'
>
>
> We have done a couple of branches (probably less than 5) in CVS and the
> branches we have probably don't have more than 2 or three changes on them
> so I don't think we've got a complicated repository at all. We've
> probably got less than 30 tags.

Yep, you aren't the first person to see this problem. Karl and I are
looking into right now, in fact.

> Any suggestions? What can I do to help debug this? I've still got all
> the cvs2svn conversion files.

If you can pare your repository down to something smaller that still
produces the bug, and post a tarball of such somewhere, Karl and/or I
would be happy to grab it and add it to our list of repositories that
need a-fixin'.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 29 20:32:50 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.