On Oct 21, 2009, at 03:15, Nicolas.Castagne_at_imag.fr wrote:
> Here are the BDB versions used by the various piece of software at
> hand :
> mod_dav_svn.so ---> bdb 4.4
> ldd /usr/lib/apache2/modules/mod_dav_svn.so libdb-4.4.so
> svn exe ---> bdb 4.2
> ldd /usr/bin/svn libdb-4.2.so
> svnadmin exe ---> bdb 4.2
> ldd /usr/bin/svnadmin libdb-4.2.so
> Also, the repositories are "built" using BDB version is 4.4 (following
> http://subversion.tigris.org/faq.html#divining-bdb-version). This is
> rather logical since the repositories have been accessed/commited
> apache only.
> I guess that svn simply needs an update on the server.
> Much simpler than I expected! I need newer binaries instead of older.
> A question is:
> Do you think that the **latest** svn version could "svnadmin
> recover" the
> repositories that use BDB version 4.4 ?
> If yes, I just update globally my linux distrib.
> If not, I will try using the package manager to get a version of
> and svn binaries linked against libdb-4.4.
I'm not really sure. I haven't dealt with BDB repositories personally.
I have a feeling that the FAQ entry
is talking about going from BDB 4.2 or earlier to BDB 4.3 or later.
It's not clear to me whether it's still needed when going from BDB 4.4
to something later. Note that's the only time you'd need to recover,
aside from if your repository isn't working; if you just want to
upgrade to a later Subversion, but keep BerkeleyDB at version 4.4,
there should be no problem.
If you do want to upgrade BDB too, then I would say just give it a
try. Back up your repository first, of course, in case it doesn't
work, then upgrade Subversion and BDB and see if you can access the
repository. If not, try recover.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-22 04:46:57 CEST