On 20/07/07, Robert Denton <firstname.lastname@example.org> wrote:
> 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.
In fact you don't even need to do a dump/load cycle. The repo format
is compatible. However, I believe you will benefit from better
compression if you do.
> 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
> 3. Update the client to TSVN 1.4.4 even though the server is not 1.4.4.
1.3.x is not recommended, not because of compatibility issues but
because there have been a lot of improvements and bug fixes since
You do not need to keep the client and server in step at all.
Compatibility is guaranteed throughout the 1.x.x lifetime. So the best
option is to use TSVN 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.
The manual is correct. The client only knows the URL, not where the
server is physically located, so there is no need to switch.
> 2. Delete their WC and do a fresh checkout?
If you do have problems, you can always fall back to this, but I don't
anticipate anything. It is easier than you think :)
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Jul 21 01:12:15 2007