On Mon, Nov 7, 2011 at 10:09 AM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> > On Fri, Nov 4, 2011 at 3:26 PM, j s <jbluedelta_at_yahoo.com> wrote:
> > I have apache running and connect to my repo using http. What is the best
> > way to upgrade to latest svn server version? Would gladly appreciate any
> > documentation that helps in upgrading
> >
> > You pretty much just need the new server binaries. You do not need to do
> > anything to your repository. This might be a good opportunity to
> migrate to
> > Subversion Edge, since that gives you a web UI to manage the server and
> get
> > future updates automatically:
> >
> >
> https://ctf.open.collab.net/sf/wiki/do/viewPage/projects.svnedge/wiki/Mig
> > rationPath
> >
> > Since you are using 1.5, you could choose to create a new repository and
> > dump/load your existing repository. This would let you use the new rep-
> > sharing feature which can save some disk space in the repository. It is
> > nothing you need to do right away though. I would recommend upgrading
> > just the server version and then you can always upgrade repositories
> later if
> > you think there is a compelling reason to do so.
> >
>
> I went with the option of moving to Subversion Edge to get to svn 1.7.x. I
> am still running 1.6 svnserve and 1.7 Edge against the same repos until
> everything is relocated. Once I take the 1.6 server down I didn't see
> anything in the Edge UI to run svnadmin upgrade. Do I just do this from the
> command line? Is it needed? Or should I dump load? My last dump load was
> when moving from 1.5.x to 1.6 but it took a LONG time.
>
There is no need to run svnadmin upgrade when moving from 1.6 to 1.7. It
would not even do anything as there are no changes in the repository format.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2011-11-07 16:11:54 CET