You can manually delete all the contents of the cache folder, or use the yum command itself to clean it: yum clean all Sometimes, the cache can become corrupt and cause the command to fail completely. The package manager can be configured to keep package data on disk after an installation, in order to speed up future tasks.īy default, the location where the data is stored is the /var/cache/yum folder. In some cases, the only option is to configure an additional repository where the correct dependency can be found. Version conflicts can be fixed by uninstalling the package found on the system.
#GPG SUITE UPGRADE INSTALL#
Sometimes you can simply install the missing dependencies manually, and then execute the initial command again. This issue can be quite complex and there is no general fix available for it. There are cases however when a package can’t be installed because a dependency is not found or is the wrong version.
#GPG SUITE UPGRADE UPDATE#
Yum will normally install and update any dependencies automatically, without additional user input. Unlike other yum issues, this one tends to be easy to diagnose because the program will display an error that indicates the failed repository.Įdit its file in /etc/ and either correct the mistake or disable the broken repository completely, in order to allow the rest of the update to finish. This can happen for several reasons, such as a typo in the configuration files, or repositories that are no longer available or have changed their URLs. Broken repositoriesĪnother very common problem is the presence of broken repositories, which can make the entire yum update process fail. These are configured in the /etc/yum.conf file, look for a line that starts with exclude. Individual packages can also be excluded from updates.
#GPG SUITE UPGRADE SOFTWARE#
The easy fix is to change the value on the enabled line to 1, then run yum update to refresh the package list and install the software you need. Gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 Name=Extra Packages for Enterprise Linux 7 - $basearch Here is an example of a disabled repository in the file /etc//epel.repo: Disabled repositoriesĪnother possible issue is when a repository is configured but disabled, which is hard to troubleshoot because no error message is displayed.įor example, if the epel repository is disabled, trying to install a package such as htop will fail because yum is unable to find it. A Google search will help you find the right repository information for your version of CentOS 7. If they are missing, you will have to create and populate the files yourself. You can quickly check if this is the case by navigating to the /etc/ folder to see if any files are present, or by executing the following command: yum repolist all Some CentOS 7 installations don’t configure any yum repositories by default, so yum will be unable to install or update any package.
The goal of this post is to discuss the most common examples of yum command failure, explaining both the root cause and how it can be fixed. In this article, we will assume there are no general issues such as a broken Internet connection or serious system-wide problems. While software can still be installed from RPMs or compiled from source, yum has many advantages such as the automatic installation of dependencies and easy system updates. If the command fails to work, due to various reasons, the update, installation and removal of packages becomes a very difficult task. Package manager yum is one of the most important tools available to a CentOS 7 system administrator.
0 kommentar(er)
