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

problem splitting a repository

From: Jim Alateras <jima_at_bigpond.net.au>
Date: 2006-02-03 06:24:45 CET

Hi,

I am new to subversion and need to some help to reorg my repository.

Currently, I have the following layout

repo/
   /branches
   /tags
   /trunk
     /project1
     /project2
     /project3

but want to move to the following layout

repo/
   /project1
     /branches
     /tags
     /trunk
   /project2
     /branches
     /tags
     /trunk
   /project3
     /branches
     /tags
     /trunk

After reading the redbook and looking over the mail archives I tried the
following

1. 'svnadmin dump repo' > repo.backup.svn to back up the current repository

2. I then created a new repository using 'svnadmin create repo-new'

3. I then executed 'svnadmin create repo-new/projectX' for each project
(I'm not sure about this step. Can someone pls confirm).

4. I then used svndumpfilter to extract a project from the repository
'cat repo.backup.svn | svndumpfilter include trunk/project1 >
project1-backup'

5. Next I use 'sed' to modify the Node-path elements. The sed search and
replace string i use is 's/trunk\/project1/project1\/trunk/g'. (I'm also
not sure about this step as well).

6. Finally I try and load it into the new repository using 'svnadmin
load repo-new < project1-backup' but that fails with the following error

<<< Started new transaction, based on original revision 378
svnadmin: File not found: transaction '377-1', path 'project1/trunk'
      * adding path : project1/trunk ...

Any ideas?

cheers
</jima>

        

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 3 06:26:32 2006

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.