I just checked the db4 rpms installed and it turns out the SVN server has
db4-4.0.14-20, which has got me a little worried since it seems kinda old.
I installed everything from the Redhat 9 RPMs available from tigris.org, and
all dependencies were met.
How can I know what version of db4 the RPMs from tigris.org are linked
against? Is it perhaps possible to simply upgrade the db4 rpm (or install
db4 4.2 alongside the current rpm) and have the installed svn automatically
pick up the new db4? Or is building everything from source the only way to
> -----Original Message-----
> From: John Szakmeister [mailto:firstname.lastname@example.org]
> Sent: 20 February 2004 02:32 PM
> To: email@example.com
> Cc: Stuart Robertson
> Subject: Re: Stone-dead repository
> > Our server configuration is as follows:
> > - RedHat Linux 9.3
> > - Subversion-0.37.0-1
> > - subversion-tools-0.37.0-1
> > - apr-0.9.5-0.2
> > - neon-0.24.4-1
> > - httpd-2.0.48-3
> > - 256MB RAM
> What version of db4? If it's 4.1, then you need to seriously consider
> Subversion compiled with db 4.2. I've seen more and more problems with
> popping up on the list.
> > Interestingly enough, when we retried the documentation commit after
> > restoring the backup, the commit succeeded, so the problem doesn't
> > to be a consistent one.
> Well, it would be consistent with the db 4.1 reports I've been seeing on
> list. The problems seem to happen somewhat randomly, and there have been
> several instances where everything ran fine, until months down the road
> db 4.1 finally did something strange and corrupted the repository. If
> 4.1, spend sometime and recompile everything using 4.2. You won't regret
> > Any pointers/recommendations for a good incremental backup strategy will
> > most appreciated.
> I'm afraid that I can't help you much here. The repositories I have are
> small enough that I dump them every night, put them into a tarball, and
> backed up on tape and shipped to another server. Someone else on this
> might have a better suggestion for doing this with larger projects.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Feb 20 13:49:37 2004