Re: repository split

On Jun 26, 2009, at 09:03, Jason Malinowski wrote:

> Agreed, one repository's UUID will have to change, so it can't be 100%
> transparent.

I still say both repositories must be given new UUIDs to indicate
that they are different repositories. Otherwise it would be possible
for a user to, say, take a working copy of projectB from the old
combined repository and "svn switch" it to some place within the new
projectA repository, since the new projectA repository has the same
UUID as the old combined repository. But that wouldn't make sense.

> However, if you're OK making it non-transparent, and force your
> devs to
> re-check out. The trick is to go editing your dump files after you've
> ran them through svndumpfilter but before you import them. If you look
> at a dump file, you will see lines like this:
>
> Node-path: projectA/trunk/file.txt
>
> ...
>
> Node-copyfrom-path: projectA/trunk/someotherfile.txt
>
> In this case, do something like:
>
> cat dumpfile | sed 's|-path: projectA/|-path: |g' > dumpfile2
>
> And then diff the two to make sure you used sed right. ;-)

A subversion dump is a binary file, and editing it with sed is not a
good idea. You should use a tool that has been designed to edit
dumpfiles, like svndumpfilter or svndumptool.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2365830

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-26 21:57:07 CEST