On Thu, 17 Jun 2004, Joe Orton wrote:
> On Thu, Jun 17, 2004 at 01:19:11PM -0400, Scott Lawrence wrote:
> > On Thu, 2004-06-17 at 12:31, Ben Collins-Sussman wrote:
> > > On Thu, 2004-06-17 at 11:20, Scott Lawrence wrote:
> > >
> > > > Transmitting file data .........................svn: Commit failed (details follow):
> > > > svn:
> > > > Berkeley DB error while committing Berkeley DB transaction for filesystem /scm/rep/sipXtackLib/db:
> > > > Invalid argument
> > >
> > > This looks like a BDB 4.1 bug we've seen before, whereby a table's type
> > > gets mysteriously changed. Is that what you're using? If so, we
> > > recommend rebuilding apache's apr-util to use BDB 4.2 ASAP.
> > 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).
> 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.
I agree with this assesment if you are not using my HTTPD RPMs. If you
ARE using my HTTPD RPMs then I think something else is wrong. I've been
using my HTTPD RPMs for a long time and have never run into any corruption
problems (of course this doesn't PROVE anything, just a data point).
To rephrase: Don't use the RedHat HTTPD RPMs with my Subversion RPMs, I
think that will definitely cause problems because the RedHat RPMs are
normally compiled with a different version of DB for Fedora 1 and
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jun 18 05:56:37 2004