Information and Links
Join the fray by commenting, tracking what others have to say, or linking to it from your blog.
Upgrading Subversion from my own built version to an RPM version
The other day I had to upgrade Subversion to v1.4.6 on an older server that was running Subversion v1.3.1. Seemingly this would be an easy task and I had done it many times before using Dag.weeirs.com packages. On this machine though, I kept getting conflicts when trying to install the RPM's.
Silly me had forgotten that I had compiled my own version of Subversion 1.3.1 way back when and I had compliled my own Trac install, which has since been upgraded to an RPM version also from Dag.weeirs.com.
The solution was simple enough, and I thought I would store it here in case I or anyone else needed the solution at some future point in time.
First, if there are any RPM packages that you previously installed, trying doing 'rpm -e packagename' first. This was the case for one conflicting package that I actually had no use of. Second, my main conflict was that my server was using libraries in /usr/local/lib, and it was using my compiled svn and svnadmin from /usr/local/bin.
The fix was three simple steps:
1 - Edit /etc/ld.so.conf and remove the line linking up the libraries in /usr/local/lib. Save the file and reload the libraries with ldconfig.
2 - Delete svn* in /usr/local/bin. This will delete all svn related binaries.
3 - Delete the libraries in /usr/local/lib that were installed. If you are unsure which ones to delete you can always leave them be, as the server won't load them anymore. I however like a clean machine.
Note that if you use other libraries in /usr/local/lib for other applications, you will NOT want to unlink them in ld.conf. Instead, you will need to remove the svn libs, and all the svn-python libs etc in /usr/local/lib manually.
Once these parts were removed, I was easily able to upgrade my server to Subversion 1.4.6 using the RPM's.
