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

Re: Upgrading a very old SVN version

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 13 Dec 2017 14:27:10 -0500

On Wed, Dec 13, 2017 at 11:01 AM, Joanne Giammo <jgiammo_at_kwi.com> wrote:

> My company had been working with a very old version of SVN – 1.3.2 from
> 2006
> They are planning to upgrade to the latest version – currently 1.9.7
> I realize that an upgrade from 1.3.2 to 1.9.7 is a serious jump.
> - Are there any know issues doing an upgrade such as this?
> - Is this full upgrade recommended or should the upgrade be done in
> stages until we reach 1.9.7?
> - We don’t want to lose the check-in history of all the files.
Subversion has good compatibility so I recommend doing this in stages.

1. Upgrade your server to 1.9.7 but have it just serve the same
repositories as before

You do not have to upgrade your repositories and the server should work
with them fine. This gives you time to make sure everything is OK with the
new version and you have all of the right binaries and it is configured
correctly etc.

2. When it is convenient, you can upgrade your repositories using a dump
and load (and you can do this one at a time)

- Subversion 1.5 introduced merge tracking and it required your repository
to be upgrade to enable the feature. So even though you have installed
1.9.7, you will not be able to start using merge tracking until you upgrade
the repository format
- Many Subversion releases offer improvements in how the repository data is
stored. Usually, it is just using less disk space but also sometimes it
offers performance improvements just by how the data is stored

Going through a dump/load process will allow you to upgrade to the latest

Step 1 is very safe and easy and you are unlikely to encounter problems.
Step 2 is more of an unknown. There are various bugs that existed in older
versions that allowed some data to be stored in repository in format that
was in violation of what was intended. Newer versions of Subversion detect
and enforce those rules better. If you have any of this data you might get
errors when loading the repository to the new format. If you do, you can
search the archives of this list to find answers on how to proceed.

Mark Phippard
Received on 2017-12-13 20:27:16 CET

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