The mod_dav_svn came from subversion-server-XXX.rpm via apt-get. I also downloaded the srec rpm and built it with the same results. I also then download the source tarball of the latest version and built it from that, all with the same results. The one thing I have not tried is using the rpm that ship on the CDs, I might try those now. --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller poeml@cmdline.net wrote:
On Thu, Jun 03, 2004 at 02:23:48AM -0500, Mobeen Azhar wrote:
I seem to have worked myself into a pickle with subversion on SuSE 9.1
I had subversion and apache working nice and dandy on the machine with SuSE 9.0. Since I upgraded it to 9.1 and db4-2, all components of subversion work fine except the mod_dav_svn piece.
The problem stays the same whether I install using apt-get, or if I download the subversion source tar ball and compile myself.
The problem is that whenever I try to access the subversion repository via a webdav client (such as TortoiseSVN), messages show up in the apache error log to the effect that the module was compiled with db4-1 but is running with db4-2. I have verified that only db4-2 exists on the system.
Doing an ldd on mod_dav_svn.so shows that it is indeed referencing db4-1. [...]
And where does that mod_dav_svn.so come from (rpm -qf, rpm -qi)? 9.1's mod_dav_svn.so is not linked against libdb at all.
Peter