On Feb 13, 2008, at 10:49, John Mcgrath wrote:
> Hi All,
>
> I just wanted to ask the experts if the following is a safe idea or
> a little risky –
>
>
>
> I am currently running svn 1.3.2 for my project. The repository is
> the FSFS type.
>
>
>
> Everything runs on Linux.
>
>
>
> If I were simple to change the svn install path to change from the
> 1.3.2 install to the 1.4.7 install,
>
> And re-start svnserve, Would this be enough to ‘upgrade’ everyone
> immediately?
>
You're saying everyone is logging into a single Linux machine and
using the svn binaries on that machine? Then this upgrade plan would
work, and I don't see anything risky about it. Well, you might want
to shut down svnserve, then switch the svn install path, then bring
svnserve back up.
If users also have svn installed on local machines, they should
upgrade as well. Though there's no rush to do so; any Subversion 1.x
client can talk to any Subversion 1.x server.
The one catch is that Subversion 1.4 introduces a new working copy
format. Any existing old-format working copies that a 1.4 client
encounters will be automatically and silently upgraded to the new 1.4
format. This means that once you've touched any given working copy
with a 1.4 client, an older client will no longer be able to use it.
If you use various different client programs to access the same
working copy, they should all be upgraded to 1.4 versions at the same
time.
> I would only do this when the repository is not being accessed. Do
> you forsee any issues with doing this,
>
> Or is the recommended method to dump and reload the full repository?
>
The dump and load is not necessary, but might bring a small
performance improvement if you did it. 1.4 made some changes to the
delta algorithm.
> Also, is FSFS the best DB to use?
>
FSFS is easier to set up and maintain that BDB. I use and recommend
FSFS.
People on occasion encounter problems (including, occasionally,
repository corruption) with both types, BDB and FSFS, possibly due to
some misconfiguration, possibly due to some as-yet-undiscovered bug,
so a good backup strategy is essential to your Subversion deployment
regardless what type of repository database you use.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-13 21:05:36 CET