1. Enable the EPEL repository by following the instructions http://fedoraproject.org/wiki/EPEL/FAQ. As of Spring 2014, EPEL is enabled with:

   rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm

2. Fix error in /etc/yum.repos.d/epel.repo. In the [epel] section uncomment the baseurl line.
3. If behind a proxy,

   vi /etc/yum.conf
   proxy=http://proxyfqdn:proxyport

4. Troubleshoot with URLGRABBER_DEBUG=1 yum check-update
5. Follow the instructions found on the Fedora page which are currently:

   yum install rabbitvcs*

RHEL/CentOS 5 users have a couple options for installing RabbitVCS. You can install from our tarball archive, or directly from our Subversion repository. We're working on getting RabbitVCS packaged for CentOS 5 (via rpmforge).

NOTE: Our standard nautilus extension does not work with CentOS5/RHEL5, but we have a simpler, compatible extension (using the same dialogs) that does work.

1. Add the RPMForge Repositories. Instructions are at http://wiki.centos.org/AdditionalResources/Repositories/RPMForge

2. Install Packages:

yum install pygtk2 subversion subversion-devel gcc gcc-c++ neon-devel python-devel pygtk2-devel eel2 eel2-devel python-configobj nautilus-devel meld libX11-devel

3. Download nautilus-python bindings at http://ftp.gnome.org/pub/GNOME/sources/nautilus-python

• Make sure you get v0.5.0, NOT v0.5.1
• Build/install with: ./configure ; make; su -c 'make install'

5. Download and build the pysvn extension source kit. You'll need one built to work for subversion 1.4. Version 1.6.3 works well.

• http://pysvn.barrys-emacs.org/
• Uncompress the pysvn tar.gz file then run the following commands:

cd Source
python setup.py backport
python setup.py configure
make
mkdir /usr/lib/python2.4/site-packages/pysvn
cp pysvn/__init__.py /usr/lib/python2.4/site-packages/pysvn
cp pysvn/_pysvn_2_4.so /usr/lib/python2.4/site-packages/pysvn

6. Download the tarball and from the top folder type:

sudo python setup.py install

Once that is done working, look in the clients folder and read the README file for each client/plugin to learn how they are installed.

Installing from trunk or from a branch is relatively straight-forward. First, install the dependencies listed above, then follow our developer installation instructions.