Subversion on a linode

@asult:

I tried to install subversion on Redhat(9) linode, but I was able to run it as I got an error from berkeley db.

It was mentioned in the documentation of subversion that the needed berkeley db does not work with some modified kernels on redhat. I tried the different kernels and nothing worked.

When I tried fedora with the 2.6 linode kernel, subversion worked. But mysql stopped working on the combination.

Does anybody know how to get both subversion and mysqk working ?

Thanks,

asult

Hi there. I also had troubles getting subversion to work on my Linode, which runs RedHat 9. I solved this problem by compiling my own version of db4 which works on RedHat 9 with subversion. I can't remember what exactly I had to do to get it to work - I might have had to mess with the spec file a bit; it's been a while, but I do know that these RPMs work.

I have made the RPMs available at:

http://www.ischo.com/db4/db4-4.0.14-20.i386.rpm

http://www.ischo.com/db4/db4-devel-4.0.14-20.i386.rpm

http://www.ischo.com/db4/db4-utils-4.0.14-20.i386.rpm

You can download these and use rpm -Uvh to upgrade to them. Should fix your problem.

You should test your MySQL after upgrading to those RPMs as well, as I do not run MySQL and can't guarantee that they work with it. But I think they should …

Best wishes,

Bryan

Bryan,

Thank you very much, both subversion and Mysql are now working.

Really appreciate it. :)

asult

@bji:

I have made the RPMs available at:

http://www.ischo.com/db4/db4-4.0.14-20.i386.rpm

http://www.ischo.com/db4/db4-devel-4.0.14-20.i386.rpm

http://www.ischo.com/db4/db4-utils-4.0.14-20.i386.rpm

Small bit of advice …

When distributing RPMs that are not with the distro shipped with, it is suggested that these RPMs be tagged with a different version naming scheme. Essentially all you have to do is add your initials to the %define release statement.

Example:

db4-4.0.14-20.i386.rpm

becomes …

db4-4.0.14-20bji.i386.rpm

This way, when someone wants to upgrade the distribution or something, they can easily do "rpm -qa | grep bji" to see which non-standard RPMs might be problematic.

Bill Clinton

@Bill Clinton:

@bji:

I have made the RPMs available at:

http://www.ischo.com/db4/db4-4.0.14-20.i386.rpm

http://www.ischo.com/db4/db4-devel-4.0.14-20.i386.rpm

http://www.ischo.com/db4/db4-utils-4.0.14-20.i386.rpm

Small bit of advice …

When distributing RPMs that are not with the distro shipped with, it is suggested that these RPMs be tagged with a different version naming scheme. Essentially all you have to do is add your initials to the %define release statement.

Example:

db4-4.0.14-20.i386.rpm

becomes …

db4-4.0.14-20bji.i386.rpm

This way, when someone wants to upgrade the distribution or something, they can easily do "rpm -qa | grep bji" to see which non-standard RPMs might be problematic.

Bill Clinton

Thank you for the good advice. I will do this in future even for my own RPMs, so that I can better keep track of which ones I have built myself.