Malcolm Rowe wrote:
> Hello all,
>
> I've just upgraded my Slackware-based system from BDB 4.2.52 to 4.4.20.
> That broke my existing svn installation (since the old libraries went
> away), so I've just recompiled 1.3.0.
>
Subversion 1.3.x does not supprt BDB-4.4. That support is currently only
on trunk (although a backport is planned).
> Anyway, all the tests pass except for fs-base-test #2, which fails with:
> svn_tests: Berkeley DB error for filesystem test-repo-open-berkeley while opening environment:
> Invalid argument
> svn_tests: bdb: DB_REGISTER limits each process to a single open DB_ENV handle
> FAIL: lt-fs-base-test 2: open an existing Berkeley DB filesystem
>
Also, it's entirely impossible that you got an error mentioning
DB_REGISTER from the 1.3.0 tarball.
So, which version of SVN are you actually using?
> I don't know (or plan to learn) BDB and fs_base, but is this expected
> behaviour for 1.3.0? I notice that the test seems to pass on trunk, so
> I'm guessing that this is something Brane fixed with his BDB-4.4 patch
> (though it didn't change the test). Does SVN 1.3.0 work with BDB 4.4?
>
>
> Hmm, now I'm wondering whether we support 'new' versions of BDB. If we
> didn't, I would have expected that we'd have a list of allowed versions,
> like we do with Neon.
>
I suppose we should tweak configure to accept only blessed versions of
BDB, yes; because the BDB API is prone to ABI changes between minor
releases.
> Either way, I'm thinking that we should have something in the 1.3.0
> release notes.
>
Possibly. AFAIK we do mention BDB version related things in CHANGES.
That should be enough.
Anyway, we can't retroactively change the 1.3.0 release notes.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 2 15:45:39 2006