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

Migration Question

From: Robert Denton <robert_at_headsprout.com>
Date: 2007-07-21 00:30:46 CEST

Hi folks,

My question concerns how I should handle TortoiseSVN installations in my company, given a current migration that is occurring:

I am in the process of migrating a subversion 1.3 repository on a windows server to a subverion 1.4.3 repository on a linux server. Members of the subversion mailing list assure me that this should not be a painful process as long as I use the svnadmin dump and load commands wisely.

We are currently using TSVN 1.3 on all of our windows clients. But once the repository is on a subversion 1.4.3 server, which of the following do the members of this mailing list recommend:

1. Leave our clients at 1.3, leaving it to the discretion of the user if they want to upgrade
2. Update the client to TSVN 1.4.3 to match the version of the subversion server
3. Update the client to TSVN 1.4.4 even though the server is not 1.4.4.

Further, should I be concerned about specific compatibility issues, or are the clients and servers more or less mix and match?

Another question concerns how to point the clients working copies to the new server. I will be keeping the URL exactly the same, and making a change to our local DNS in order to keep all of the externals definitions the same. However, it _is_ the same repository, but on a different server. Should I:

1. Use the Relocate feature to update the WC, even though the url will not change? The Tortoise manual says: "The relocate command is only used if the URL of the repository root has changed." So I am left in doubt.
2. Delete their WC and do a fresh checkout?

I am appreciative of any and all advice regarding these issues. Thanks!

Robert
Received on Sat Jul 21 00:29:46 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.