Re: Migrating to svn

Lacoste, Dana (TSG Software San Diego) wrote:
> I don't know if someone can help me, but I'm trying to migrate from another SCM to svn.
>
> I keep running into issues:
>
> The original SCM was, well, extremely large. massive. So we're running a tool to extract data in it to the svn dump format. Fine (the dump format looks fine enough) but I can't seem to get it to LOAD.
>
> Example:
>
> Dump branch A into svn-brancha.dump (content is in branches/branchA)
> Dump branch B into svn-branchb.dump (content is in branches/branchB)
>
> svnadmin load branch A : no problem.
>
> svnadmin load branch B : fails immediately, unable to create "branches"

You probably want to make branch B only contain the branchB directory
and load it with the --parent-dir option so it doesn't try to create
"branches" again.

> Seriously? svn load won't load a dump file that references files that already exist? Or am I misunderstanding?

I think your bigger problem will be that it will have to renumber the
revisions from your 2nd run, putting them out of time sequence - and it
probably won't know about things with a common history.

> I can't make a single dump file that contains branchA _and_ branchB because it's too large: it runs out of memory.
>
> I'm kind of stumped here: I can make dump files (using the scripts on tigris to migrate to svn) but I can't figure out how I can possibly make this work if I can't svnadmin load into a subdirectory of an existing directory.....

Add memory? Or write a script that checks out revisions one at a time
and commits to svn.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2419659
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].