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

Re: Upgrade SVN server 1.3.2 to 1.6 with Apache

From: Andrey Repin <anrdaemon_at_freemail.ru>
Date: Tue, 7 Apr 2009 03:33:44 +0400

Greetings, Bradley Wagner!

>>> I'm wondering what I have to upgrade a SVN 1.3.2 server to the latest
>>> 1.6 when running with apache's SVN modules.
>>> Am I going to have to recompile apache to use these new binaries? Are these
>>> modules dynamically loaded and easily replaceable?
>> You have answer in your question. Apache modules could be easily replaced.
>> They are shared libraries.
>> However, true question is, what the version of Apache server you're using?
>> If it's not Apache 2.2, you'll need to upgrade Apache server too.
>> And for SVN database upgrade, you better "svnadmin dump" your repository(es)
>> using current server installation, then prepare an upgrade, make test
>> repository, check that it working fine, then restore your actual repos.

> Thanks for the response. I'm using Apache 2.2.2 so that shouldn't be a problem.

Aside from the fact, that the latest Apache is 2.2.11 >.>
Not that i'm huge fan of bleeding edge versions, but Apache in fact mostly
released on security fixes... go figure.

> Still not sure about the modules. From what I can tell the SVN
> binaries don't come up with Apache modules.

Of course. They are SVN modules, so they are coming with SVN...
If you are running something other than Windows system, you most likely going
to compile them for yourself.

> Maybe the ones that come with 2.2.2 will work fine with SVN 1.6.

> The svn docu seems to indicate that I don't have to do the svndump and
> re-import thing when upgrading to 1.6.

Yes, but with such ancient software like you have, it's always better to take
safest possible approach.
Database format has been changed at least two times between your version and
1.6 branch. I don't think these changes was made to scare users... and I sure
know you'll need to re-import your repository from the ground to make best
advantage of the new database format.

> I'll of course back up the repositories regardless.

That's the zero step in any operations - make sure you have fresh and
functional backup. I'd also make sure it is actually functional... i.e.
restore from a backup to separate folder and see if it works... before going
anywhere. Commands like svnadmin, svnlook works directly with repository
folders on disk, so you don't even need to join your repository to the
managing server.

> Apparently the repositories don't get upgraded automatically on upgrade and
> you have to use "svnadmin upgrade" to manually upgrade the repositories to a
> 1.6 format.

There's a big difference in what you can get from simple upgrade and from
complete rebuild of a repository.

Depends on the complexity of your commits, you could save up to 20% of disk

 Andrey Repin (anrdaemon_at_freemail.ru) 07.04.2009, <3:23>
Sorry for my terrible english...
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-07 01:36:51 CEST

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