top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

How to upgrade SVN from 1.7 to 1.9?

+1 vote
1,113 views
How to upgrade SVN from 1.7 to 1.9?
posted Jun 8, 2016 by Mandeep Sehgal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

If you are using a particular SVN distribution take a look at the docs of that distribution.

If you are building SVN yourself, see (https://subversion.apache.org/docs/release-notes/1.9.html ): "[...] Subversion 1.9 servers can read and write to repositories created by earlier versions. To upgrade an existing server installation, just install the newest libraries and binaries on top of the older ones."

Don't forget to backup your repositories and server files before the upgrade though, to be sure that you have a backup at hand, if something goes wrong.

For your clients it's more or less the same (note that you don't need to have clients and servers running the same version --- you can also upgrade the client to 1.9 and keep the server at 1.7.8 or the other way around). Make sure their working directories are not locked (aka: run svn cleanup), upgrade the client to 1.9 and then upgrade the working directories (svn upgrade http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.upgrade.html ).

answer Jun 8, 2016 by Amit Mishra
Similar Questions
+1 vote

I recently upgraded my Subversion client from version 1.7.5 to 1.8.3 and from that time on I experience hangs when executing multiple 'svn log' commands in a short amount of time. The "hanging" svn process consumes all CPU cycles it gets but never finishes.

I can reproduce the problem using the following shell script (on Windows using Cygwin):

#!/bin/bash
ROOT="http://example.com/svn/trunk"
for DIR in $(svn ls "${ROOT}" | head -n 4); do
 svn log -v -l 5 "${ROOT}/${DIR}" 2>&1 | head -n 100 > /dev/null
done

In my environment I need at least 4 svn processes to achieve the faulty behavior. The hang only occurs if the output is truncated using the head command (but it can be redirected to a normal file instead of /dev/null which then contains the expected log messages).

+1 vote

I am running subversion 1.4.2 server with apache 2.2.14 on Linux machine. Now I want to upgrade to subversion 1.8.8 with apache 2.2.25 . Please guide me how to upgrade?

0 votes

I'm trying to figure out how to migrate our existing SVN 1.3.1 repository to another server. It's on a Jumpbox with TRAC.

I followed the instructions and have setup svnsync, but since it's pre 1.4 it's setting at revision 0 and not migrating.

I then setup subgit as a way to get it and them migrate it back to the new server, but subgit says it translated 2541 revisions, but there's nothing in the git repository as far as I can tell.

I even tried using the Revision Control Turmkey Linux box with svn 1.6.17, but it gives me the same problems and I can't seem to get it upgraded to 1.8.9 to use svnrdump.

Does anyone have a suggestion on how to migrate svn 1.3.1 to 1.8.9 without console access?

0 votes

I have svn server running on Windows XP as service (using svnserve.exe). Everything was working fine until I switched server from 1.7 to 1.8. From that moment, every few days, SVN server would freeze eating up all cpu it can (50% on dual core system). Note that I upgraded repository after upgrading svn software.

+1 vote

We have a custom tunnel protocol with repository URLs of the form:

 svn+foo_bar://

After upgrading from svn 1.7.x to 1.8.1, these URLs are considered invalid, giving an error of:

svn: E170000: Illegal repository URL

This occurs on an 'svn up' or an 'svn checkout'. Changing the tunnel protocol name to 'foobar' (i.e. drop the underscore) appears to work properly, both 'svn up' and 'svn checkout' work fine.

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...