You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Gareth Walters <ga...@syd.microforte.com.au> on 2003/05/05 06:55:47 UTC

Re: cvs2svn assertion

In that case it doesn;t make sense that it doesn't work..
I don't give configure the path to DB4.1 then it gives an error saying
insufficient DB version
If I do give it the path to DB version 4.1 then it builds and still looks/find
the old version at runtime?

---Gareth


----- Original Message -----
From: "Sander Roobol" <ph...@wanadoo.nl>
To: "Gareth Walters" <ga...@syd.microforte.com.au>
Cc: <de...@subversion.tigris.org>
Sent: Thursday, April 17, 2003 8:04 PM
Subject: Re: cvs2svn assertion


> On Thu, Apr 17, 2003 at 09:27:47AM +1000, Gareth Walters wrote:
> > So with that assertion fixed I now get this...
> >
> >
> >   File "./cvs2svn.py", line 637, in pass4
> >     t_repos = repos.svn_repos_open(ctx.target, ctx.pool)
> > RuntimeError: bad database version: got 3.3.11, should be at least 4.0.14
> >
> >
> > db 3 is installed as well as 4.1 (this is the one that subversion was built
> > against).
> > how do I tell cvs2svn where this installation is?
>
> You can't tell cvs2svn. You have to make sure that you link against db
> 4.x when building subversion and the python bindings.
>
> Sander


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org