Yum Repository

Given that a great deal of the content on this site has become how-to’s on updating Red Hat Enterprise Linux & CentOS servers, I’ve decided to make things a bit easier on everyone and supply a repository that can be used to install the newer versions of software that I build with a single command.

As of 8/28/2007 binaries are provided for both 32-bit and 64-bit RHEL & CentOS systems running release 4 or 5.

First things first, all of my binaries are GPG signed. That means that you can be sure that these packages are coming from me, even if you should happen to find them on some other site (if you find a file with “jason” in the name and it isn’t signed, DON’T install it).

In order to validate that the packages came from me, you’ll want to install my public GPG key on your system. You can take care of that with a single command:

rpm --import http://www.jasonlitka.com/media/RPM-GPG-KEY-jlitka

The preferred method of adding my repository to your RHEL or CentOS system is with the Yum package manager. CentOS 4, CentOS 5, and RHEL 5 install yum automatically. If you are using RHEL 4 then you can install yum or add the following to your ‘/etc/sysconfig/rhn/sources’ file and install the sqlite package (i386 – x86_64) to use my repository with ‘up2date’.

# Enable Jason's Utter Ramblings Repo
 yum utterramblings http://www.jasonlitka.com/media/EL4/$ARCH

For those of you using yum, type:

nano -w /etc/yum.repos.d/utterramblings.repo

… and then paste the following into the editor:

[utterramblings]
 name=Jason's Utter Ramblings Repo
 baseurl=http://www.jasonlitka.com/media/EL$releasever/$basearch/
 enabled=1
 gpgcheck=1
 gpgkey=http://www.jasonlitka.com/media/RPM-GPG-KEY-jlitka

NOTE: If the above URL returns a 404 then try hard-coding $releasever to your EL version (‘EL4′ or ‘EL5′) and the $basearch to whatever is appropriate (‘i386′ or ‘x86_64′).

Once you’ve taken care of the above, you’ll be able to easily upgrade to the same packages I build for my own sites with a simple ‘up2date -u’ or ‘yum update’.

There is one caveat to the above statement… If your 64-bit system includes both 32-bit and 64-bit packages by the same name (such as “mysql.i386″ and “mysql.x86_64″ ) then you will experience a problem unless you remove the 32-bit packages from your system.