How do I Upgrade to Subversion 1.5 On CentOS 5? [closed]

Question

My development server (CentOS 5) is running Subversion 1.4.2, and I wish to upgrade it to 1.5. I have read in various blogs and documents scattered around the web that this may be done by using RPMForge. I have followed the instructions found on CentOS Wiki, including installing yum-priorities and setting my priorities as indicated (1 and 2 for core repo sources, and 20 for RPMForge).

However, when I attempt to run:

$ yum info subversion

the version number given to me is still 1.4.2, with a status of Installed. My other option at this point is compiling from source, but I would like to find a package-managed solution for ease of future upgrades.

Any thoughts?

Answer 1

What you are trying to do is to replace a "core" package (one which is contained in the CentOS repository) with a newer package from a "3rd party" repository (RPMForge), which is what the priorities plugin is designed to prevent.

The RPMForge repository contains both additional packages not found in CentOS, as well as newer versions of core packages. Unfortunately, yum is pretty stupid and will always update a package to the latest version it can find in any repository. So running "yum update" with RPMforge enabled will update half of your system with the latest (bleeding edge, possibly unstable and less well supported) packages from RPMForge.

Therefore, the recommended way to use repos like RPMForge is to use them only together with a yum plugin like "priorites", which prevents packages from "high" priority repos to overwrite those from "low" priority repos (the name of the "priority" parameter is very misleading). This way you can savely install additional packages (that are not in core) from RPMForge, which is what most people want.

Now to your original question ...

If you want to replace a core package, things get a little tricky. Basically, you have two options:

1. Uninstall the priority plugin, and disable the RPMForge repository by default (set enabled = 0 in /etc/yum.repos.d/rpmforge.repo). You can then selectively enable it on the command line:

   yum --enablerepo=rpmforge install subversion
   

   will install the latest subversion and dependencies from RPMForge.

   The problem with this approach is that if there is an update to the subversion package in RPMForge, you will not see it when the repo is disabled. To keep subversion up to date, you have to remember to run

   yum --enablerepo=rpmforge update subversion
   

   from time to time.

2. The second possibility is to use the priorites plugin, but manually "mask" the core subversion package (add exclude=subversion to the [base] and [update] sections in /etc/yum.repos.d/CentOS-Base.repo).

   Now yum will behave as if there is no package named "subversion" in the core repository and happily install the latest version from RPMForge. Plus, you will always get the latest subversion updates when running yum update.

Answer 2

1.- if you are using yum-priorities disable this in the file /etc/yum/pluginconf.d/priorities.conf

2.- check the version of subversion

  $ rpm -qa|grep subversion
    subversion-1.4.2-4.el5_3.1
    subversion-1.4.2-4.el5_3.1 

3.- search the last version of the subversion from rpmforge repository

$ yum --enablerepo=rpmforge check-update subversion
subversion.x86_64      1.6.6-0.1.el5.rf         rpmforge

4.- now proced to upgrade subversion with rpmforge repository

$ yum shell
>erase mod_dav_svn-1.4.2-4.el5_3.1
>erase subversion-1.4.2-4.el5_3.1
>install mod_dav_svn-1.6.6-0.1.el5.rf
>install subversion-1.6.6-0.1.el5.rf.x86_64
>run

that's all it works for me im running centos 5.4

Answer 3

Thanks Matt - we also have the only distro of SVN 1.7 on SVN.

You may also want to try uberSVN.

Answer 4

If you install RPMForge's repos, you should then be able to get a newer package - this isn't working for you?

You should see rpmforge.list in /etc/apt/sources.list.d with a line like:

repomd http://apt.sw.be redhat/el$(VERSION)/en/$(ARCH)/dag

I just tested on a clean CentOS 5 install, and yum check-update shows

subversion.i386                          1.5.2-0.1.el5.rf       rpmforge
subversion-perl.i386                     1.5.2-0.1.el5.rf       rpmforge

So check your sources list and run check-update again.

Edit: Whoops, lost part of my answer. Added it back above.