Subversion problem using Fedora Core 2

I'm trying to create a new subversion repository but there's a problem with the Berkeley DB:

svnadmin create /home/svnroot/project_name

svn: Berkeley DB error while creating environment for filesystem /home/svnroot/project_name/db:

Invalid argument

I've seen that there may be problems with /lib/tls and renamed that directory but it didn't make a difference.

I've managed to create a new subversion repository on a standalone Fedora Core 2 box so I assume the problem is related to the UML kernel.

Any suggestions?

Thanks,

Xavier

4 Replies

Whoops, my original reply was incorrect; I have erased it. I thought that you were asking about the RedHat 9 problems with subversion. Can't help you with Fedora, sorry :(

I've looked at the thread you mentioned before but as I started with Fedora Core 1, db4 was already at 4.1. Now it's at 4.2 so I'll need to rebuild newer rpms for db4 to test.

Do you have your modified spec files available somewhere so I could see what you've modified and use that to perform similar changes to rebuild rpms for db 4.2?

@brittanysoft:

I've looked at the thread you mentioned before but as I started with Fedora Core 1, db4 was already at 4.1. Now it's at 4.2 so I'll need to rebuild newer rpms for db4 to test.

Do you have your modified spec files available somewhere so I could see what you've modified and use that to perform similar changes to rebuild rpms for db 4.2?

I don't seem to have the spec files or the SRPMS … which leads me to believe that I didn't have to change the spec files, that I just had to rebuild the RPM from the SRPM on the Linode system. As a first step, I think you should try that …

OK, I managed to find a workaround.

First, I tried to regenerate the DB4 rpms from the Fedora developement branch (db4-4.2.52-5 was the version the last time I tried). I disabled the nptl stuff but it didn't change anything, i.e. subversion didn't work.

Then I compiled the original DB4 tarball from sleepycat.com with all the default options (configure, make, make install) and once that was installed in /usr/lib, I created links from the /lib and /usr/lib directories to the /usr/local/… libraries and now Subversion seems to be working fine.

I'll now transfer an existing repository to the machine and I'll post again if the fix above doesn't work when I start really using subversion on my server.

BTW, this is using the 2.4.26-linode30-1um kernel.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct