On Tue, Jul 28, 2009 at 7:27 PM, Dan Stromberg<dstromberglists_at_gmail.com> wrote:
> On Tue, Jul 28, 2009 at 4:05 PM, Hari Kodungallur<hkodungallur_at_gmail.com> wrote:
>>> >> We have 3 subversion repositories on a single subversion server, and
>>> >> we want to move them to a new subversion server.
>>> >>
>>> >> This seems simple enough - until you start to consider all the
>>> >> absolute external references (in branches and tags)
>> I forgot about another method (that I have never used -- because I have
>> never needed to) that you could try. Assuming you have access to the
>> repository (server side), you can dump the repository and then I believe the
>> SvnDumpTool has an option (transform-prop) to fix up the externals. Please
>> try it out and see if it works for you.
>>
>
> Oh, interesting.
>
> I've copied the data using svnadmin dump | ssh svnadmin load, but
> SvnDumpTool sounds pretty interesting. Why does SvnDumpTool have such
> a low version number though? Does the author not trust it yet? I
> don't want to take any unnecessary risks with these files.
Modifying the dump seems to be the right way to go. This way you'll be
able to fix all revisions of the repository. Using svn/svnmucc will
keep all old revisions useless, because they cannot be checked out
after the move.
Modifying the dump does not destroy the original repo, You can load it
to another place during tests.
The dump is binary, but readable and possible to understand (and the
format is well documented). Just don't modify the eols in the dump.
You can probably find out all you need to change using grep, and then
(when you've analysed you old usage of externals) fix it using sed.
/$
/$
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376490
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-29 10:49:21 CEST