Okay, my upgrade woes continue. If you just tuned in: I'm upgrading my
svn server from 0.15.0 to 0.29 because I want to start using Web::svn.
In the process, I upgraded Apache 2.0.43 to 2.0.47. I'm now getting
"bad database version: got 3.1.17, should be at least 4.0.14" when I
try to browse to my repository using a web browser.
I tried grabbing the latest BerkeleyDB (4.1..25), but that wasn't the
problem, because when I tried building, I didn't get past ./configure -
-with-berkeley-db=/usr/local/BerkeleyDB.4.1, because it complained it
couldn't find the correct db version. ./configure --with-berkeley-db=/
usr/local/BerkeleyDB.4.0 worked. I remade subversion just in case,
removed my newly created repository, created it again with the newly
built svnadmin, loaded the database dump, and restarted Apache.
Same error:
<?xml version="1.0" encoding="utf-8"?>
<D:error xmlns:D="DAV:" xmlns:m="http://apache.org/dav/xmlns" xmlns:C=
"svn:">
<C:error/>
<m:human-readable errcode="160000">
bad database version: got 3.1.17, should be at least 4.0.14
</m:human-readable>
</D:error>
Using objdump on mod_dav_svn.so, I see that it dynamically links
against libsvn_repos-1.so.0, libsvn_fs-1.so.0, libsvn_delta-1.so.0,
libsvn_subr-1.so.0, libz.so.1, and libc.so.6 - no mention of any of the
DB libs. I assume that's because they're statically linked.
But in that case, the problem can't be that I have the 3.1.17 version
of BerkeleyDB somewhere in my lib path, and I specifically add the full
path to ./configure.
Here's my full command line again:
./configure --with-aspx --with-zlib --with-berkeley-db=/usr/local/
BerleleyDB.4.0; make; make install
Hints are very welcome as my repository is now broken.
Thanks,
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 15 23:37:02 2003