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

Re: Could not open the requested SVN filesystem

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-07-21 11:30:28 CEST

On Tuesday 20 July 2004 17:25, Ben Collins-Sussman wrote:
> On Tue, 2004-07-20 at 16:13, Steve wrote:
> > > > I'm more concerned that your binaries are linking to multiple
> > > > versions of bdb at the same time. Can you show us the *full* ldd
> > > > output to these things, not just try to pick out db-4.2?
> >
> > <big snip>
> >
> > Ben, do you(or anyone else) have any thoughts regarding what I
> > posted? I checked my list of installed packagesa little while ago,
> > and noticed that it indicated both bdb4 and bdb42 were installed. I
> > removed both of them, apache2, and svn. Then I went and installed
> > apache2 with db42, and svn again, but I'm still getting the same
> > error.
>
> I'm running out of ideas here. I see nothing suspicious in your 'ldd'
> outputs.

I wonder if the problem is that he wasn't using the right BDB in the first
place. Back around 1.0, IIRC, there were problems when trying to build
with BDB 4.2.52. I believe the configure script (for apr-util) wasn't
correctly picking up the new library yet. Perhaps when Steve built it,
it went unnoticed, and he's been using the older BDB.

If this is the case Steve, rebuilding a version of SVN linked against the
old BDB will bring it back to life. There is a way to do an in-place
upgrade of the backend databases, but you'll need to check Sleepycat's
home page, as I don't recall how to do that offhand. You can also do a
dump & load, making sure that you copy your hook scripts as well.

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 21 11:32:51 2004

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

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