Centos – I think I’ve resolved dependency, rpm doesn’t

centosepelrpm

I have upgraded EPEL repo in order to install Remi repository in order to upgrade PHP to 3.5.4 in order to upgrade civicrm (on a CentOS 6.7 VPS running one production site and its dev site).

repolist:

repo id          repo name                                         status
base             CentOS-6 - Base                                    6,575
epel             Extra Packages for Enterprise Linux 6 - x86_64     12,126
extras           CentOS-6 - extras                                  52
updates          CentOS-6 - Updates                                 1,472
repolist: 20,225

but rpm -Uvh remi-release-6.rpm gives

warning: remi-release-6.rpm: Header V3 DSA/SHA1 Signature, key ID 00f97f56: NOKEY
error: Failed dependencies:
        epel-release >= 6 is needed by remi-release-6.6-2.el6.remi.noarch

Other than the fact that I have to find and install a GPG key for Remi, why is version 6 failing a dependency which says GE 6?

Best Answer

It is likely that you have installed the EPEL repositories by simply hand-editing an appropriate file in /etc/yum.repos.d. That is perfectly OK in terms of getting the EPEL packages onto your system, but for more sophisticated usage it falls down a bit.

The REMI software knows that it needs EPEL packages, so the installation is made dependent on those being configured in. The recommended way to enable the EPEL packages on your system is to install the epel-release RPM. This contains the relevant GPG key, the yum repo file, and not much else - but its presence is a quick way for packages to know that EPEL packages will be available if needed.

If you do install the epel-release RPM, then not only will your system be able to access EPEL packages, as it already can, but other software packages will know that they can rely on EPEL's availability, which they currently cannot.