Geek Answers Handbook

Upgrading a Subversion server from 1.5.5 to 1.6.5 - reset / update / reboot, exact steps?

I'm going to upgrade the SVN server from version 1.5.5 to 1.6.5 - everything is fine with the actual update, but I'm a little confused about updating real repositories.

I read in several places ( here , here ) that it is better to reset and reload repositories rather than using svnadmin upgrade . I suggest that I have to reset, update the server, and then load the reset again - however, should I delete the old files from the repository before downloading? If so, what is the best way to do this?

If before I completely ruined my version control system, someone could give me a quick step by step, it would be very useful!

Cheers, Mark

+6
svn upgrade
source share
3 answers

The Subversion FAQ is often asked step by step :

  • Shut down svnserve, Apache, and anything else that might be available to the repository.
  • svnadmin dump /path/to/repository > dumpfile.txt using version X of svnadmin.
  • mv /path/to/repository /path/to/saved-old-repository
  • Now upgrade to Subversion Y (i.e. create and install Y, replacing X).
  • svnadmin create /path/to/repository using version Y of svnadmin.
  • svnadmin load /path/to/repository < dumpfile.txt , again using version Y of svnadmin.
  • Copy scripts with hooks, etc. from the old repository to the new one.
  • Restart svnserve, Apache, etc.

more on dumping and loading in the Subversion book. I assume that you have studied the subversion 1.6 release notes .

+10
source share

No, you do not need to reset / load before updating, 1.6 was specially designed for easy updating, using only svnadmin upgrade . I did it, it worked, I'm happy.

release notes clearly say there is no need to upload / download repos.

I would make a backup anyway (just in case), and then do the recommended update. Then I will pack the repo files ( svadmin pack ) to speed up future backups and run SVN faster.

+4
source share

If you are going to do this, you will probably want to dump, update, delete and recreate the repo, and then download it again.

I can’t say that I have ever had problems using the update, although you may have a less optimal repo structure.

+1
source share

More articles:


All Articles