I see no SVN version 1.6 RPM in RPMForge. It's the first place I looked
before trying to build it by hand.
root_at_sunfire60# rpm -i rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm
root_at_sunfire60# yum list > /tmp/foo
root_at_sunfire60# grep -i '^svn' /tmp/foo | grep 1.6
root_at_sunfire60# grep -i '^subversion' /tmp/foo | grep 1.6
root_at_sunfire60# rpm -e rpmforge-release
root_at_sunfire60# rpm -i rpmforge-release-0.5.1-1.el5.rf.i386.rpm
root_at_sunfire60# yum list > /tmp/foo
root_at_sunfire60# grep -i '^svn' /tmp/foo | grep 1.6
root_at_sunfire60# grep -i '^subversion' /tmp/foo | grep 1.6
root_at_sunfire60#
MJB
On 11/23/2010 10:12 PM, Nico Kadel-Garcia wrote:
> On Tue, Nov 23, 2010 at 7:16 PM, Michael J. Bauer
> <mjbauer_at_eecs.tufts.edu> wrote:
>> I am attempting to build SVN on a RHEL 5.4 system. There are two versions
>> of SQLite on the system:
> Use the SRPM or the RPM from RPMforge. I've had some involvement with
> that: previous contributors included the squlite-amalgmation tarball,
> which is used at compile time to provide statically loaded libraries
> and brings it successfully into RHEL 5.x compatibilyy.
>
> RHEL 5's version is perilously out of date for both security and
> performance reasons: I strongly recommend the RPMforge
> subversion-1.6.13 toolsuite. It's one issue is that RPMforge doesn't
> publish i386 packages in the same repository as x86_64 packages, and
> RHEL does, so you have to play yum configuration games to avoid
> loading the subversion-1.4.2-1.i386.rpm from RHEL, and the
> subversion-1.6.13-[release].x86_64.rpm from RPMforge and causing
> chaos.
Received on 2010-11-24 18:11:32 CET