Thanks for the info, but I think this may be a red herring.
For one thing, I was using svn last week without any problems, and our
sysadmin assures me that nothing has been changed in any way either with
svn or BDB in the past 6 months. So the difference between last week and
now can't be explained by changes in the installed svn or BDB software.
To make a *very *long story short, I created a brand-new repository and
populated it from a recent repository dump, and, once again, I was able to
use subversion normally. The error messages I was getting with practically
every svn command went away.
But after a couple of hours of normal svn use, I have now run into another
inexplicable svn failure. I've described this in a separate post ("svn died
for good mid-command...").
On 5/16/06, Ryan Schmidt <email@example.com> wrote:
> On May 16, 2006, at 16:15, kynn at panix.com wrote:
> > % svn co file:///home/jones/svn-repos/MyProject/trunk MyProject
> > svn: Unable to open an ra_local session to URL
> > svn: Unable to open repository ' file:///home/jones/svn-repos/
> > MyProject/trunk'
> > svn: Berkeley DB error while opening environment for filesystem /
> > home/jones/svn-repos/db:
> > DB_VERSION_MISMATCH: Database environment version mismatch
> > svn: bdb: Program version 4.3 doesn't match environment version
> > Could anyone tell me what's going on and/or how to fix it?
> Seems you or someone upgraded the BerkeleyDB libraries on your system
> without following the Subversion BDB upgrade instructions, which are
> Once you get this sorted out you may want to consider switching from
> BDB to FSFS so that you cannot experience similar problems in the
> future. How to do this is described here:
Received on Wed May 17 05:10:50 2006