Alexis Huxley <ahuxley@gmx.net> writes:
> Hi ..
>
> Up to now, come upgrade time, I've simply exported my version X repository,
> compiled and installed version Y, and reimported. I've done this because
> I've not really been using properties and I've not had any 'history' I
> care to keep.
>
> But now this is no longer the case: I want to keep my repository's properties
> and history, and I want to upgrade, but I'm a bit behind:
>
> leda$ svn --version
> Subversion Client, version 0.14.0 (dev build)
> compiled Aug 4 2002, 19:11:33
>
> Okay, I know I have to do dump/restore cycles with specific versions of
> SVN. Is the sequence of SVN versions I need to "pass through" documented
> somewhere? I couldn't find it on the web pages.
You may be in luck. I don't think that the repository dump format has
changed since revision 2634, and 0.14.0 is 2667! The filesystem
schema itself changed in 0.14.2, so the dump/load is required. But
you shouldn't have to bother with intermediate dump/load stages. Just
dump your repository with your current 'svnadmin dump', build a new
subversion, then use the new svnadmin to create and load your new
repos. After testing that everything looks alright, you can discard
the old repos. Don't forget to copy over any hook scripts or custom
DB_CONFIG edits to the new repos, too.
> Also, I know that compiling any SVN version is best done with
> specific versions of Apache2/APR/neon, are the required versions of
> these documented somewhere?
See the INSTALL file (in the new version of Subversion that you plan
to build of course).
> PS If there'll be a new version this week, then I'll wait till *next*
> weekend to do the upgrade :-)
We're gonna try to get 0.16 out the door next Tuesday.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 23 15:57:36 2002