On Thu, Jun 17, 2004 at 03:49:57PM -0400, Scott Lawrence wrote:
>
> > > I don't think so: rpm -qa | grep db4
> > > db4-4.2.52-3
> > >
> > > there is a db4-4.1.25-8 further down in the list, but I'm pretty sure
> > > that svn is not using that (because the rpm wouldn't install until I had
> > > the 4.2 version in place).
>
> On Thu, 2004-06-17 at 15:38, Joe Orton wrote:
>
> > Using David's RPMs for systems based on DB 4.1.25, you end up with both
> > DB 4.1.25 and 4.2.52 linked into httpd processes, both using the same
> > symbols. It is totally unsurprising that this combination ends up with
> > random database corruption.
>
> What's the right way to go about that, then? It looks as though trying
> to eliminate that older version entirely is the road to dependancy-hell;
> this is what comes up when I run rpm -e --test for those rpms:
Rebuild the DB 4.2.52 packages passing --with-uniquename to configure
(as I've advised David several times), or just stick to the system
db4/httpd packages in the first place, e.g.:
http://people.redhat.com/jorton/Taroon-svn/
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 17 21:58:25 2004