On Wed, Jun 18, 2014 at 9:32 AM, Brisset, Nicolas <
nicolas.brisset_at_airbus.com> wrote:
> Hi,
>
>
>
> We’ve been using svn successfully for years on a server, and now have to
> migrate to a new one. We are hit by the known issue of svn:externals
> containing absolute paths to the repo to be moved, since we started with
> versions <1.5 without support for relative URLs.
>
> We’ve been researching how to properly do this, knowing that we handle
> certified SW on that server, so losing data or corrupting the repo is not
> allowed, and we want to be able to go back in time and checkout an old
> state at any time.
>
>
>
> We’ve experimented the svndumptool (http://svn.borg.ch/svndumptool/)
> referenced for instance in this post:
>
>
> http://stackoverflow.com/questions/204616/how-to-migrate-all-urls-in-svnexternals-properties-across-a-repository
>
> It seems to be the only tool doing what we want, and it apparently works,
> but before doing the change on the production repo we’d like to know what
> experiences there are with this tool, and if it’s safe to use – or if
> there is a better alternative.
>
>
>
>
Don't just take someone else's advice on it - test it with your own data.
Dump your repository, process it with the tool, load it into a test server
& make sure it all works the way you expect.
Even if you get nothing but positive responses here, you should be doing
this because there could be something unique with your data that causes
breakage no one here has experienced.
Received on 2014-06-18 16:02:55 CEST