Huh... BDB...?

After upgrading from debian etch to debian lenny, I tried my first
subversion checkin today, and got the following message:

svn: Commit failed (details follow):
svn: Berkeley DB error for filesystem '/usr/local/svn/db' while opening environment:

svn: DB_VERSION_MISMATCH: Database environment version mismatch
svn: bdb: Program version 4.6 doesn't match environment version 4.4

The thing is... I've never intentionally created a BDB repo. By the
time I created my first subversion repo I was well aware of the BDB
compatibility and upgrade issues, so I've always gone with FSFS.

So, this means something has been doing the upgrade for me. And the
most probable culprit seems to be an apt-get dist-upgrade from one
release of debian to the next.

The dates of the files in the subvesion archive, are from March 11 2007,
which is when I upgraded from sarge to etch, so it didn't happen during
the most recent upgrade.

No bug reports or Changelog entries on Subversion in debian mentions
this (mis)feature (ie. changing an FSFS repo to BDB), and no immediate
google matches, which makes me doubt my theory, but...

Has anyone else seen their FSFS repo become a BDB repo, on debian?

Anyway... what's done, is done. Now I need to figure out how to convert
my existing BDB repo (still in BDB 4.4...?) to FSFS.

How can I find out exactly what version of BDB a repo is using? Is the
setting in db/DB_CONFIG to be trusted? And if it is in 4.4, is there
some kind of utility that can extract it, and change it into something
that can become an FSFS repo?

Ie. will my svnadmin that requires BDB 4.6 be able to dump a BDB 4.4
repo? And can I trust the results if it does?

The quest continues...

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1208296

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-22 18:39:30 CET