RE: getting svn and apache to work !!!!!

as far as i can tell... this shouldn't be the case..

i rebuilt the svn/subversion apps from source... although, i'm not sure how
to actually point to the 4.2.52 version of the berkeley db... i have the .so
files on my system.... however, i also see the earlier .so files in the same
dir..

is there a way to point to a specific lib within the .configure
attributes...

i used the following .configure attributes when building the subversion
apps/libs...

./configure --with-apxs=/usr/sbin/apxs --with-berkeley-db=/usr/lib
--with-dbm=db4 --with-gdbm=no

if there is a way to actually specify the correct /usr/lib/libdb-4.2.so then
this might solve the issue...

a greater issue would simply be to remove the older berkeley db stuff that
seems to be in the dir. however, when i try to remove the older apps/libs
using 'rpm' i run into rpm hell, given the dependency issues...

any thoughts/comments/etc...

-bruce

-----Original Message-----
From: Guido Anzuoni [mailto:guido.anzuoni@kyneste.com]
Sent: Tuesday, September 07, 2004 7:51 AM
To: bedouglas@earthlink.net; users@subversion.tigris.org
Subject: R: getting svn and apache to work !!!!!

Well,
I think that the problem is not in the configuration, but in the repository:
......
Python/2.3.3 DAV/2 SVN/1.1.0-rc2 configured -- resuming normal operations
[Tue Sep 07 07:53:08 2004] [error] [client 192.168.1.52] (20014)Error string
not specified yet: Bad database version: compiled with 4.0.14, running
against 4.2.52
[Tue Sep 07 07:53:08 2004] [error] [client 192.168.1.52] Could not fetch
resource information. [500, #0]
[Tue Sep 07 07:53:08 2004] [error] [client 192.168.1.52] Could not open the
requested SVN filesystem [500, #160000]
[Tue Sep 07 07:53:08 2004] [error] [client 192.168.1.52] Could not open the
requested SVN filesystem [500, #160000]
.........

Seems like you created the repository with subversion linked with Berkeley
DB 4.0.14 and
now you are accessing the repos with subversion linked with Berkeley DB
4.2.52.

If you have the old subversion try to dump the repository, create a new
repository using
the new subversion and load the dump into.

Keep backup !!

Guido.

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