On Feb 2, 2006, at 01:07, Hans Fangohr wrote:
> Presumably after an upgrade of packages (using fink update-all) on
> the svn-server, I get the following error (both when executing this
> on the server in checked out directory and when executed in a
> checked out directory or a remote client):
>
> svn status -u
> svn: Berkeley DB error for filesystem /Users/svn/fangohr/teaching/
> admin/db while opening environment:
> DB_VERSION_MISMATCH: Database environment version mismatch
> svn: bdb: Program version 4.3 doesn't match environment version
>
> After some googling and searching I find that the most common
> explanation is that I have accidentally upgraded the Berkeley data
> base (bdb) from 4.2 to 4.3, and therefore there is a version mismatch.
>
> There are a number of things that make me suspicious thought
> whether this is the right conclusion (although I don't have any
> firm evidence on either of these):
>
> -- I had run a fink update-all on the server not soo long ago (max 14
> days ago)
>
> -- I might have switched from stable to unstable (which should
> result in
> svn-ssl 1.2.3-12 or 1.2.3-13 being installed). I have therefore
> switched back to stable and re-installed the 1.2.3-12. However, I
> stil get the error message shown above.
>
> -- As far as I can see, svn brings its own bdb code (so there is no
> separate package) and I can't recall any upgrade of svn itself.
>
> I hope I have set the scene without boring people too much.
>
> To get the repository back in a useful state I think I need to find
> the right version of svn (which brings the right version of the
> bdb, correct?)
Subversion requires BDB. Subversion does not include BDB. At least,
the Subversion source distribution does not, and the Subversion build
process on Mac OS X using DarwinPorts does not. (It uses
DarwinPorts's BDB port.) I assume Fink works in a similar way.
To upgrade to BDB 4.3 you need to follow these instructions:
http://subversion.tigris.org/faq.html#bdb43-upgrade
Unfortunately you'll see that it requires you to still have your old
BDB 4.2 Subversion binaries, which you probably no longer have.
You'll probably have to downgrade back to the previous version of BDB
and recompile Subversion against that again, then perform the first
part of the upgrade, then upgrade back to the new version of the
software, then perform the next part.
If you have a current repository dumpfile you could skip all this and
reimport it into a new empty repository.
After you restore access to your repository, you may want to convert
it to FSFS so that you don't run into BDB oddities in the future.
http://subversion.tigris.org/faq.html#bdb-fsfs-convert
> I have tried to find out what berkely database version my
> repository requires, but I don't know how to. The error message
> seems to suggest that the installed version of the database is 4.3
> but it doesn't agree with the repository? (Or is it the other way
> round?)
>
> I have located the DB_CONFIG file but can't read it. Can anyone
> enlighten me on this? I attach the file below.
Find out what version of BDB your repository was using here:
http://subversion.tigris.org/faq.html#divining-bdb-version
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 2 13:25:31 2006