[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: More info (svn/apache playing together!)

From: bruce <bedouglas_at_earthlink.net>
Date: 2004-09-08 19:02:11 CEST

ok...

for what it's worth.. here's what seems to work for me in getting svn/apache
to play together... this is simply to provide anonymous access as a test.
it's left as an exercise to the reader to implement the access control for
users/directories/files!!!

Target system is a linux RH8.0 system.

Key RPMS are:
apr-0.9.5-0.2.i386.rpm
apr-devel-0.9.5-0.2.i386.rpm
apr-util-0.9.5-0.1.i386.rpm
apr-util-devel-0.9.5-0.1.i386.rpm
db4-4.2.52-3.1.i386.rpm
db4-devel-4.2.52-3.1.i386.rpm
httpd-2.0.50-5.i386.rpm
httpd-devel-2.0.50-5.i386.rpm
httpd-suexec-2.0.50-5.i386.rpm
mod_dav_svn-1.0.6-3.i386.rpm
mod_python-3.1.3-1.i386.rpm
mod_ssl-2.0.49-1.1.i386.rpm
neon-0.24.7-1.i386.rpm
perl-5.8.3-18.i386.rpm
php-4.2.2-8.0.5.i386.rpm
subversion-1.0.6-1.rh80.i386.rpm
subversion-devel-1.0.6-1.rh80.i386.rpm
subversion-perl-1.0.6-1.rh80.i386.rpm
subversion-python-1.0.6-1.rh80.i386.rpm
subversion-server-1.0.6-1.rh80.i386.rpm
subversion-tools-1.0.6-1.rh80.i386.rpm

(The RPMs were found at
http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fed
ora/RPMS/)

I've included the above RPMs as they were what were initially installed on
the box.

After running through issues, it was decided to go ahead and use the
subversion src tar file, as it gave a more up to date version of
neon/apr/apr-util/svn apps.. The same thought process was used for the
BerkeleyDB.

In using/building from the source files, we also removed the RPMs for the
DB/Subversion apps...

Required Src Files:
db-4.2.52.NC.tar.gz
subversion-1.1.0-rc2.tar.gz

This got the system to a point where we could actually build/install the
required apps for SVN/Apache to work together.

Steps:
Install RPMS:
rpm -ivh -force --nodeps httpd-2.0.50-5.i386.rpm
rpm -ivh -force --nodeps httpd-devel-2.0.50-5.i386.rpm
rpm -ivh -force --nodeps httpd-suexec-2.0.50-5.i386.rpm
rpm -ivh -force --nodeps mod_python-3.1.3-1.i386.rpm
rpm -ivh -force --nodeps mod_ssl-2.0.49-1.1.i386.rpm
rpm -ivh -force --nodeps perl-5.8.3-18.i386.rpm
rpm -ivh -force --nodeps php-4.2.2-8.0.5.i386.rpm

The default output dirs were used for the most part.

Libs: ->/usr/lib
        /etc/httpd/modules

Installing Source

Berkeley DB
./configure (no options were used)

Subversion
./configure --with-apxs=/usr/sbin/apxs --with-berkeley-db=/usr/local/Berke
leyDB.4.2 --with-dbm=db4 --with-gdbm=no

Berkeley libs from the /usr/local/BerkeleyDB.4.2/lib dir to the /usr/lib dir
Subversion libs were copied from the /usr/local/lib dir to the /usr/lib dir
APR libs were copied from the /usr/local/apr/lib dir to the /usr/lib dir

At this point, the system was able to load all the required files/libs and
the httpd started successfully.

Creating the SVN dirs:
A test SVN root was created with a test dir:
 /svnroot
   /test

Creating the repository was done by:
 svnadmin create /svnroot/test

Changing permissions for the repository:
 chown -R apache:apache /svnroot (your httpd owner might be different)
 (This ensures that the httpd daemon/process can
  read/write/access the repository)

The subversion.conf file was modified to be:
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so

<Location /svn>
   DAV svn
   #SVNParentPath /svnroot
   SVNPath /svnroot/test
</Location>

to access the repository through http/apache
 svn list http://192.168.x.x/svn

which successfully generated a blank dir listing!!

ISSUES:
The primary issues that seemed to occur had to do with correctly pointing
apps to the correct libs. Until you have sufficient skill at configuring
apps, using non default/standard file locations, it's probably less problems
to stick with the defaults.

feel free to add/comment on this process...

at some time, it would probably be a good thing to put together a doc, that
describes how to accomplish this from using the source files for
everything...!!

regards,

-bruce

-----Original Message-----
From: Eetu Huisman [mailto:eh@iki.fi]
Sent: Wednesday, September 08, 2004 7:34 AM
To: users@subversion.tigris.org
Subject: More info

Ok, I've managed to locate the root of my problems. From the Apache
error log:

[Wed Sep 08 16:14:55 2004] [error] [client 192.168.1.230] (20014)Error
string not specified yet: Bad database version: compiled with 4.1.25,
running against 4.0.14

So it is a Berkeley DB problem. It seems that for some reason or the
other, Apache is linked against the old version of db4. What exactly are
my options here? I wouldn't want to recompile Apache (and by looking at
Apache spec-file and ./configure, I doubt that it would even help, they
don't provide a way to change the db4 version to link against) and there
isn't a db-compat-devel -package available anywhere.

If anyone has any idea a) why Apache is linked againt db4.0 and b) how
to fix this mess while trying to keep everything under the control of
RPM, I'd appreciate it.

Has anyone had any luck with the RPM's provided @
http://people.redhat.com/jorton/Taroon-svn/? I'd imagine that there is
simply no way to get them working with Apache without (somehow, not sure
how) recompiling Apache with db-4.1.

Eetu Huisman

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 8 19:02:15 2004

This is an archived mail posted to the Subversion Users mailing list.