Kenneth Porter wrote:
> --On Thursday, January 06, 2005 1:35 PM -0500 "Martin J. Stumpf"
> <email@example.com> wrote:
> Why would you need to check out the repo? Just grab
> swig-1.3.21-6.src.rpm, build it, force-upgrade it (I believe only
> subversion-1.0.2 depends on it, but check to be safe by attempting
> upgrading without "-force" first), and then build and install
> subversion-1.1.1-1.1.src.rpm from the FC3 repo.
> swig can be found here:
> Subversion is here:
Thanks but I am more confused now. I don't REALLY want to build the
packages. I am running FC2 not FC3. I didn't think that I could get rpms
from the FC3 updates because of other possible links that I don't have.
I just want to upgrade to 1.1.1 or 1.1.2 from rpms or even a build from
a tarball. I have many other clients that are FC2 so that is why I was
trying to rebuild a binary rpm. After 6 hours of messing with this (I
had already tried editing the spec file and that didn't work because I
need all the dependencies available to build a new rpm). The tigris
website downloads section doesn't even mention FC2 under Redhat it just
takes you to the summer site which has only whitebox. I don't even know
what whitebox is but it was the only place I could find src rpms.
I tried to rpm -Uv the subversion rpm you pointed me to and I get the
error: Failed dependencies:
liblber-2.2.so.7()(64bit) is needed by subversion-1.1.1-1.1
libldap-2.2.so.7()(64bit) is needed by subversion-1.1.1-1.1
libswigpy.so.0()(64bit) is needed by subversion-1.1.1-1.1
subversion = 1.0.9-1 is needed by (installed)
subversion = 1.0.9-1 is needed by (installed) mod_dav_svn-1.0.9-1
So, do I go get those lib's from FC3? They don't exist on my complete
install of FC2.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jan 6 21:16:20 2005