大网数据广告活动
服务器运维问答

I think I've resolved dependency, rpm doesn't

· 52CE 我爱测

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 bas…

问题原文

原帖链接 · Richard Grevers · CC BY-SA 3.0

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?

已采纳解答

原帖链接 · MadHatter · CC BY-SA 3.0

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.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-03-28)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。