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

Re: Berkeley DB error

From: Karikalan Kumaresan <karikalan78_at_gmail.com>
Date: 2007-06-06 22:58:03 CEST

Hi, I have tried installing subversion-1.4.3-1.i386.rpm, but it is asking
for too many dependencies which I could not find online. Please suggest
where I can get the dependencies.

Alternatively, I tried installing subversion using "yum install subversion"
and it always installs SVN 1.1 not 1.4. I am a bit stuck there.

Any help or suggestion would be greatly appreciated.


On 6/4/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
> On Jun 2, 2007, at 13:59, Karikalan Kumaresan wrote:
> > I want to setup the SVN server in Linux FC 3. I have installed
> > subversion using "yum install subversion". I am getting the
> > following error when I try to do "svnadmin create <repository path>",
> >
> > svn: Berkeley DB error while creating environment for filesystem
> > test1/db:
> > Invalid argument
> > svn: bdb: Berkeley DB library configured to support only DB_PRIVATE
> > environments
> >
> > I tried to browse for this issue, nothing was helpful so. Can you
> > please help me out in resolving this issue.
> I'm not familiar with that particular error message, but I can tell
> you this: Subversion has not used Berkeley DB as the default format
> for new repositories since Subversion 1.2.0. If you're getting that
> message, then that means you must have an older version of
> Subversion, and I strongly recommend you upgrade to the latest, which
> is 1.4.3 currently. When you create a repository, it will use the
> FSFS storage mechanism by default, which does not need or use
> Berkeley DB, thus you can't run into any Berkeley DB errors.
> If you really want to use a Berkeley DB-based repository for some
> reason, then perhaps someone else can help you with that particular
> message.
Received on Wed Jun 6 22:58:34 2007

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.