Re: Subversion upgraded to Berkeley DB 4.0.14

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> There are no known interop issues with Apache, even when httpd is
> using a different dbm or different release of Berkeley, so if you run
> into a problem, please report it right away.

Really? Well, I have problems using shared svn apache modules. This is
not specific to db4, I have the same problem with db3. In my setup I
have

$ ldd /usr/local/apache/bin/httpd | grep db
        libdb2.so.2 => /usr/lib/libdb2.so.2 (0x400a7000)
$ ldd /usr/local/apache/modules/libmod_dav_svn.so | grep db
        libdb-4.0.so => /usr/local/subversion/lib/libdb-4.0.so (0x40199000)

and a checkout command fails

$ svn co http://localhost:8888/repo -d svn

apr_error: #20014, src_err 0 : <Error string not specified yet>
  The OPTIONS status was 500, but expected 200.

The error appears to be generated by the db version check in
check_already_open()

(gdb) c
Continuing.

Breakpoint 1, check_already_open (fs=0x81457c0)
    at ../svn/subversion/libsvn_fs/fs.c:56
56 db_version (&major, &minor, &patch);
(gdb) n
57 if ((major < SVN_FS_WANT_DB_MAJOR)
(gdb) p major
$1 = 2
(gdb) p minor
$2 = 7

I work round this by forcing httpd to use db4 at runtime as follows

$ LD_PRELOAD=/usr/local/subversion/lib/libdb-4.0.so /usr/local/apache/bin/apachectl start

When apache is run like this the checkout command works fine.

-- 
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org