On Friday 20 February 2004 07:49, Stuart Robertson wrote:
> I just checked the db4 rpms installed and it turns out the SVN server has
> db4-4.0.14-20, which has got me a little worried since it seems kinda old.
Hmm... no what I would have suspected. I don't have RH9, so I can't say what
it should be in real-life.
> I installed everything from the Redhat 9 RPMs available from tigris.org,
> and all dependencies were met.
>
> How can I know what version of db4 the RPMs from tigris.org are linked
> against? Is it perhaps possible to simply upgrade the db4 rpm (or install
> db4 4.2 alongside the current rpm) and have the installed svn automatically
> pick up the new db4? Or is building everything from source the only way to
> go?
You can use ldd /path/to/mod_dav_svn.so to see which libraries it's pulling
in. And you can run ldd `which svn` to see what libraries the command line
tool is using.
Unfortunately, it isn't a matter of just installing an RPM. To upgrade you
would need to rebuild Apache and Subversion in order for them to use the new
db library. You also would need to upgrade each of your repositories. You
can upgrade them in place (with httpd off), I found it easier to dump the
repositories (and save off the hook scripts, etc.), and then install
everything and reload them.
However, I haven't seen any problems with 4.0. In fact, we're still using
that at my work place (I just haven't had the time to go and rebuild it all).
Check to make sure that they're not linked against db 4.1. If everything
looks square, can you try to reproduce the problem. If you can narrow it
down to something that I can reproduce, I can at least try and track down the
problem.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 14:38:48 2004