[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Problem accessing local repo

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-29 20:42:44 CEST

On Thu, 2004-07-29 at 13:23, Art Haas wrote:
> Hi.
> Subversion has been working well for me for months, but my latest update
> and build now gives the following error when trying to access a repo
> kept on my machine:
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///mnt/src/svnrepo/pythoncad/trunk'
> svn: Berkeley DB error while opening environment for filesystem
> /mnt/src/svnrepo/db:
> Invalid argument

This is issue 1968. Would you post a tarball of your repository for us
to examine?

> Any known code issues from a day or two ago that cause Berkeley DB to
> get messed up?

No, see issue 1968. We've not touched BDB code in ages and ages.

> My latest build also used Debian's 'libdb-4.2' package instead of my own
> built DB-4.2 libraries. The 'libdb-4.2' libraries are configured so that
> the 'db.h' header file redefines various calls by appending a number to
> the call, and my older (home-built) library was not configured to do
> that. As that change should just effect building and run-time linkage, I
> don't see how that could affect the reading of existing Berkeley DB
> files.

Somehow your new version of BDb is incompatible with whatever data
format the old BDB was writing to disk. Max Bowsher might get a better
idea by looking at your repository.

> Suggestions welcomed. Should I switch over to the 1.1.x branch, as the
> trunk is in flux? An svn rebuild looks to be necessary at some point.

This has nothing to do with svn's code; everything to do with your
change of BDB library. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 29 20:44:13 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.