Currently FC1 includes subversion 0.32, while subversion is up to
1.04! Packages are available for FC1 at the referenced URL.
Subversion 1.0 has a different database schema to 0.32, so an upgrade
would break any existing repositories using the 0.32 packages. FC2
includes Subversion 1.0.
Unfortunately, FC2 seems to have its own problems, which are not
prompting me to upgrade. I take it there's no way to migrate the older
Reopening, as I don't believe this issue is resolved.
I include this response from Ben Collins-Sussman (email@example.com)
Of course there's a way to upgrade the database schema. 0.32 is
*alpha* software. Nobody should be using it anymore.
Here's a HOWTO:
Just make sure the 1.0.4 RPM includes a static binary of the 0.32
'svnadmin', so users can use it to dump their data and load with the
new 1.0.4 svnadmin. This is what Debian does, I believe.
Forcing people to upgrade to FC2, a release that is apparently highly
questionable, is not an acceptable solution, IMHO.
Of course, but the fact is that an "up2date" from 0.32 to 1.0 would
break databases without manual intervention, and that just isn't
acceptable packaging policy. If you don't want to use 0.32 on FC1,
use the third-party packages you reference.
This decision does not force you to do anything. If you want a
Fedora-packaged Subversion 1.0 package, use FC2; if you don't, you
have the choice of using 0.32 packages included in FC1, or any
third-party or self-built 1.0 packages.