Re: corrupted repository (was Re: the 0.24 release?)

On Thu, Jun 12, 2003 at 10:28:05AM +0200, Timothee Besset wrote:
> I dunno if that's related, but I've seen similar things happen to my
> repository after 0.23 upgrade. It was because of db version mismatch. I
> used to have a 'default' build of httpd (which was probably using db 4
> then), and svn 0.22 built against db 4.1
>
> When I switched to 0.23 with the same setup, things started to go bad. I
> was not aware of the db 4 in httpd / db 4.1 in mod_dav_svn till then. I
> rebuilt everything making sure httpd and svn where using db 4.1, and the
> problems went away.

I don't believe this was the case with my corruption. I've been using
the Debian packages on all my systems. Remote access to the
repositories (the only way they are accessed) is via mod_dav_svn and
Apache2. The apache version install installed on the server is Debian's
apache2-mpm-worker v2.0.46-2. While I haven't specifically checked the
linking of the binary files, the Depends for the package are:

   libapr0 (>= 2.0.46), libc6 (>= 2.3.1-1), libdb4.1, libexpat1 (>=
   1.95.6), libgdbmg1, libssl0.9.7, zlib1g (>= 1:1.1.4), apache2-common
   (= 2.0.46-2)
   
As you can see, it's dependant on libdb4.1 (Debian's BDB v4.1 package).

(little more investigation)

The system does have libdb4.0 installed on it though, and there is a
somewhat round-a-bout dependancy from apache2-mpm-worker to libdb4.0 (so
I may be wrong):

   apache2-mpm-worker
   - apache2-common
    - openssl
     - perl
      - libdb4.0

So, is this the root of the problem?

-- 
Jamin W. Collins
This is the typical unix way of doing things: you string together lots
of very specific tools to accomplish larger tasks. -- Vineet Kumar
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org