Hot answers tagged

4

RPM packages can declare Provides: which mean that they provide some named capability. These are treated as equivalent to package names when yum decides what packages to install. A recent version of the mariadb package does indeed declare several provides: $ rpm -q --provides mariadb config(mariadb) = 3:10.4.13-2.fc32 mariadb = 3:10.4.13-2.fc32 mariadb(x86-...


3

It looks like the repomd.xml file hosted by the various mirrors has a newer timestamp than expected, given by the metalink URL: For example, https://mirror.vcu.edu/pub/gnu_linux/epel/7/x86_64/repodata/repomd.xml returns: <repomd> <revision>1591901338</revision> <!-- ... --> </repomd> While the metalink server tells Yum to ...


3

CentOS 6 went completely end of life on November 30. Therefore, you won't be able to patch, or install any new software. The only exception to this would be if you were to convert your system to RHEL 6, and purchase Red Hat Extended Life Cycle Support. I wouldn't even recommend that, however. You should upgrade to CentOS 7, or even CentOS 8 instead.


3

While CentOS 6 is truly dead, and the ultimate fix is upgrading, you can still install packages by using the Vault repositories as detailed here. To quickly fix up your CentOS 6 so you can yum install things, run: curl https://www.getpagespeed.com/files/centos6-eol.repo --output /etc/yum.repos.d/CentOS-Base.repo


3

Officially there is nothing you can do with CentOS 6 - it's dead and buried - there will be no more updates from the CentOS project. From the CentOS-devel mailing list on 9th Nov 2020 All, This is a friendly reminder. CentOS 6.10 will EOL at the end of November 2020. During the first week in December 2020, the 6.10 directory will move to vault.centos.org ...


3

I am doing Enterprise Linux based on RHEL CentOS for almost 20 years. What you need is a (snapshot) clone of a repository. Then you can ensure all servers (qa, prod) have exactly the same versions Problem is that the reposities are changing (with updates) and you want to avoid that, right? In enterprise environments, redhat network or satellite is used to ...


2

With RPM Package Manager you can simply provide foo 4 bar. This is a stupid dummy spec example, purists will remove the rpmlint ;-) warnings: $ cat ~/rpmbuild/SPECS/provides-httpd.spec Summary: Dummy package to provide with httpd for httpd24 Name: provides-httpd Version: 0.1 Release: 1%{?dist} License: GPLv2 Requires: httpd24-httpd Provides: ...


2

Always use yum. yum provides vim 2:vim-enhanced-7.4.629-6.el7.x86_64 : A version of the VIM editor which includes recent enhancements Repo : base Matched from: Provides : vim = 7.4.629-6.el7 Explicit provides like this are rare in packaging. yum can also search name, file names, or automatically generated library provides from the linker.


2

You cannot put new versions of a package into a repository, unless it is managed by you (which is not the case, especially for the standard repos). Often the official repositories only include newer versions of a package very late, if ever. (For example for stability reasons) But you can add other repositories to your system, so that yum can get the newer ...


2

Case sensitivity should not matter so much here, because both packages virtually provide mariadb-server capability (same case). The major reason why DNF wants to install MariaDB from AppStream is that it has a preference for modular packages. Which means, that if specific packages (names) or virtual provides are part of a module, and there are packages with ...


2

yum makecache fast Will refresh your mirrors so that you get valid install sources.


2

You can interpret the errors as follows from this example: Error: Package: php72w-pecl-imagick-3.4.3-1.2.w7.x86_64 (@webtatic) Requires: libMagickCore.so.5()(64bit) Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@base) libMagickCore.so.5()(64bit) Updated By: ImageMagick-6.9.10.68-3.el7.x86_64 (base) ...


2

yum clean medatada Taken from "man yum" ?clean CLEAN OPTIONS yum clean expire-cache Eliminate the local data saying when the metadata and mirrorlists were downloaded for each repo. This means yum will revalidate the cache for each repo. next time it is used. However if the cache is still valid, nothing significant was deleted. yum ...


2

You need to be connected to the Internet in order to download packages. Check that you have an IP address (with ip a), that you have a default route (with ip r), and that you have nameservers defined so you can resolve names (with cat /etc/resolv.conf).


2

I think the problem is that your repo file is not correctly formatted and contains whitespace where there should not be any. You should re-create the file according to the instructions: cat <<EOF > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/ enabled=1 ...


2

You couldn't install libcrypto.so.10 by mentioned command. First you should locate which package contains this library by executing yum provides libcrypto.so.10 and then install package. Or you could directly install required package.


2

Capability python(abi) = 3.6 and file /usr/bin/python3 are provided by python3 package in the base repository (reference). You should run yum install openscap-containers while the base repository is enabled. Since yum didn't pick it up as dependency, you have a problem that the base repository was disabled or its repo definition is missing. In the latter ...


2

You can just reinstall the package containing the missing file. yum reinstall /opt/rh/httpd24/root/etc/httpd/modules/librh-php72-php7.so


2

Well, I do have access to that subscriber-only article, and the solution it gives is pretty non-obvious. The problem described there is that at some point /etc/httpd was made a symbolic link to /opt/rh/httpd24/root/etc/httpd. This causes the old httpd package, which stores its configuration in /etc/httpd, to instead try to overwrite the files created by the ...


2

your issue is about yum cache . Yum download package into cache directory. Space is not enough in that directory to download header and metadata packages You must solve space issue ,clear cache and update package info again Also you can change cache directory to another ( you have free space) check cach directory in : cat /etc/yum.conf cachedir=/var/cache/...


2

First, caveat: Centos6 is end of life so you should be upgrading to at least Centos7. To install epel for a particular distro go to the epel website and that will tell you how to install epel for your particular distribution: https://fedoraproject.org/wiki/EPEL#Quickstart Do not try to mix different versions ie Centos7 / Centos8 as this will cause all sorts ...


2

Per the KB article you linked, kernel-3.10.0-1127.el7 is a RHEL 7.8 kernel. Upgrade to the latest RHEL 7, currently 7.9, rather than 7.6. Freezing this minor version is causing technical debt. Most obviously, a kernel version you want that is in a later release. Further, the support of older versions is limited. You would need to purchase extended update ...


2

All things considered about security and it being EOL, you can still make yum usable in CentOS 6: curl https://www.getpagespeed.com/files/centos6-eol.repo --output /etc/yum.repos.d/CentOS-Base.repo Or, update repo configuration manually.


2

Yes, it is that simple and that practical ! I have set it up my self on a bunch of one-app servers and it works like a charm (you need to restart the service of course). That being said, there could be some criticals machine that need to be handled with care before any update (make a vm snapshot, test the app after the update) with those i'd recommand a ...


1

You can't use the EPEL repository with Amazon Linux 2, because it is not compatible with this Linux distribution. Packages from EPEL are not intended for Amazon Linux 2, and even if you somehow managed to install one, it probably would not work. You will need to obtain certbot from another source, or use another Linux distribution.


1

VDO and in particular its kernel module are built specifically for the associated RHEL/CentOS kernels. Your server, however, has OpenVZ, which uses a custom kernel. At this time using VDO with a custom kernel is not supported. In order to install this, you would need to obtain the source RPM for kmod-kvdo and then rebuild the RPM against the particular ...


1

You cannot install packages until you have subscribed the system and obtained an entitlement. You can do this with the redhat_subscription module. After it is registered, you can use the rhsm_repository module to enable the repositories you want. Here is how I register my RHEL systems and enable my desired RHEL repositories: --- - hosts: all gather_facts: ...


1

Need 50 reputation... so instead of a comment, here's my "answer". Michael is right, but the answer could be a little confusing. This is just a clarification. The OLS install from OLS repositories guide is not for "Amazon Linux" or "Amazon Linux 2". Your OS version is the problem. You CAN run that install process on AWS/EC2......


1

You are trying to install packages for RHEL/CentOS on Amazon Linux 2. These packages are not compatible, as Amazon Linux 2 is not compatible with RHEL/CentOS and will not run software packaged for RHEL/CentOS except by sheer accident. To resolve the problem, use CentOS 8 or RHEL 8, the correct distributions for the package you are trying to install. Do not ...


1

This answer from the unix stack exchange is pretty much on point. It essentially says yum won't allow you to exclude a package as a dependency because then it would be doing a terrible job at being a package manager. There is a work around, in that you can use: rpm -i --nodeps [package].rpm to install the package without any dependencies, but then you'll ...


Only top voted, non community-wiki answers of a minimum length are eligible