I could use some advice on the RIGHT way (versus, I am sure, any number of
WRONG ways) to upgrade Subversion to the latest version (1.3.2) on Fedora
Core 2.
For any number of sad and sorry reasons, I am stuck with FC2 on this
particular machine. It came with Subversion 1.0.9 installed, and I would
like to upgrade.
I tried "yum update subversion" and got a list of actions ending with
"subversion is installed and the latest version. No action to take.".
Tried "yum upgrade subversion" and got a list of actions ending with "No
Upgrades available for subversion". "svn --version" showed that the
installed version stayed at 1.0.9.
I then went looking for RPMs for version 1.3.2 and couldn't find anything
for anything earlier than Fedora Core 3.
So, OK, I figured I may as well download the source tarball and build and
install from that. But first, I figured I'd better uninstall the
currently-installed version; So, I said "rpm -e subversion" and got:
error: Failed dependencies:
libsvn_client-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_delta-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_delta-1.so.0 is needed by (installed) mod_dav_svn-1.0.9-1
libsvn_diff-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_fs-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_fs-1.so.0 is needed by (installed) mod_dav_svn-1.0.9-1
libsvn_ra-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_repos-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_repos-1.so.0 is needed by (installed) mod_dav_svn-1.0.9-1
libsvn_subr-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
libsvn_subr-1.so.0 is needed by (installed) mod_dav_svn-1.0.9-1
libsvn_wc-1.so.0 is needed by (installed) subversion-perl-1.0.2-1
subversion = 1.0.9-1 is needed by (installed) mod_dav_svn-1.0.9-1
subversion = 1.0.9-1 is needed by (installed) subversion-devel-1.0.9-1
If I can get a clean uninstall of the current subversion installation, I
won't feel too uncomfortable about just doing a configure / make / make
install on the source tarball, outside of the RPM environment.
Or, I could just leave the current installation alone in /usr/bin/svn, and
build the new version in its default installation locations like
/usr/local/bin/svn. But, then I'd have to make sure that everyone's path
shows /usr/local/bin first, which is likely to break the first time anyone
decides to play with their path in their local .bashrc file.
So, what is the consensus of the BEST way to get subversion upgraded
correctly on FC2?
Eric Poole
Burgoyne, Nolet & Poole, Inc.
Londonderry, NH, USA
Providing software development consulting and services
to government and industry since 1979.
Phone: 603-437-1811 ext 21
E-mail: eric@bnpconsulting.com
On the Web: http://www.bnpconsulting.com
Skype: EricPooleNH
========================================
NOTE TO CORRESPONDENTS: Email on the Internet has become a bit less than
100 percent reliable, due to spammers. If you email me and don't get a
response in a reasonable time, please re-send. Also, please do what you
can to combat spammers, including supporting any anti-spam legislation and
NEVER buying anything from a spammer.
========================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 23 02:35:17 2006