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

Upgrade Options for SVN 1.5

From: Rob Hubbard <rob.hubbard_at_softel.co.uk>
Date: Fri, 21 Nov 2008 10:48:04 -0000

Hello,

The notes on the changes in SVN 1.5.x at
  "Working Copy and Repository Format Changes"
 
<http://subversion.tigris.org/svn_1.5_releasenotes.html#wc-and-repos-for
mat-change>
mention a new <svnadmin> subcommand <upgrade>.

Therefore, when upgrading to SVN 1.5.x,
an SVN administrator now has more options than before.

As before, he can:
  * upgrade just the server software to SVN 1.5, or
  * upgrade the repositories as well as the server software

The benefits of the latter are illustrated quite nicely in the table
  "New Feature Compatibility Table"
 
<http://subversion.tigris.org/svn_1.5_releasenotes.html#new-feature-comp
atibility-table>

[See also
  "Blocking Merge-Unaware Clients"
 
<http://svnbook.red-bean.com/en/1.5/svn.branchmerge.advanced.html#svn.br
anchmerge.advanced.pre1.5clients>
 
<http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#sv
n.branchmerge.advanced.pre1.5clients>
regarding how ensure that clients don't mess things up.]

However, now there are the repository upgrade options
  (1) upgrade the repositories by performing a dump/load cycle
  (2) upgrade the repositories using <svnadmin upgrade>
    (a) optionally followed by <fsfs-reshard.py>
    (b) optionally followed by <svn-populate-node-origins-index.exe>

It's not completely clear to me what the best route to take is.
(2) seems a lot easier and requires a little less planning than (1),
and looks like it's probably quicker:

  The routine for (1) would seem to be:

    - take server offline
    - backup repositories

    - dump each repository (using the old version)
    - upgrade software
    - delete or move old repositories
    - create new (empty) repository "place-holders"
    - load each repository

    - deploy the "start-commit" hook
    - bring server back online

  and for (2) it would be

    - take server offline
    - backup repositories

    - upgrade software
    - svnadmin upgrade each repository
      - fsfs-reshard each repository
      - perhaps svn-populate-node-origins-index on each repository

    - deploy the "start-commit" hook
    - bring server back online

Is (2)+(a) [+(b)] essentially equivalent to (1)?

I suppose what I'm asking is this: are there any features of SVN 1.5
that will not be fully functional except by route (1)?

Thanks,
Rob.

________________________________________________________________
This message has been independently scanned for the Softel Group and cleared of containing viruses and other malicious data.

Powering Television Beyond the Video (TM)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-21 11:48:28 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.