Question

A few years ago, TortoiseSVN 1.4.3 was deployed to our software development team and we are now looking at upgrading the client to the latest 1.6.x version. I had hoped this upgrade would be transparent with the additional features and modifications being client-side. For the most part, this was true except for a very important feature — merging. When I try to merge a feature branch back into truck I get a show-stopping “Merge tracking not supported error.”

Here are some facts worth noting:

1. When the repository was first created (before I was on board), it was created via the TortoiseSVN client itself. We do not have an ‘SVN server daemon’ per se, rather the repository folders/database resides on a share folder that is accessible from our workstation machines via file:///. This was actually an eyeopener for me; I had always thought there was some SVN server daemon we were talking to.

2. We do not have any access to the underlying machine hosting the SVN share other than the ability to read/write to the share itself. I don’t even know what OS the machine is running on. This share server was chosen because its drives are backed up nightly by our IT group.

3. In all honesty, we really don’t need the merge tracking feature although it would be nice to have. For the time being, it would be sufficient to be able to use a 1.6.x TortoiseSVN client on the 1.4.3 repository and have it merge (sans tracking) without error.

How does one upgrade a client-created 1.4.3 repository to a 1.6.x compatible version without access to the underlying machine the repository resides on?

I was hoping the TortoiseSVN client itself had the ability to do this, but that does not appear to be the case.

Will I be forced to copy the entire repositoryover to my local drive, run some SVN commands to upgrade the repository locally and then copy the repository back to the share point? If so, will doing this break any compatibility with the 1.4.3 clients in case we can’t upgrade them all at the same time?

NOTE
The question has been completely reworded in light of some of the answers given.

Answer 1

You will need to do an svnadmin -upgrade to convert the repository format. Just make sure you backup the repository first…just in case.

For the most part 1.4.x clients should be able to talk to a 1.6.x server. Of course the 1.6.x server has features that the 1.4.x clients do not support so those features will be unavailable.

Edit:

It does not really matter that you created the repository via TortoiseSVN. It all happens the same way. You will need to download the Subversion command line tools to be able to use svnadmin. I would definitely copy the repository to your local drive first so you can experiment with the upgrade. Without upgrading that repository you will be forced to forfeit the new features. I think you will be okay upgrading the repository without affecting the existing 1.4.x clients, but it never hurts to test that out before you replace the production copy of the repository on the server.