Hot answers tagged


The correct fix is to update your SSL certificates. sudo yum upgrade ca-certificates --disablerepo=epel You need to disable the epel repo so that this command will succeed. After you update your certificates you can use yum normally as EPEL will work again.


Frankly, because you did something you didn't fully understand. Python is an essential part of the OS and the things you considered unimportant are very important. Restore from backup. When you removed Python, yum showed you a long list of packages that would also be removed. This list contains such essentials as yum itself, coreutils, net-tools and others....


You can discover which package contains the program you want using yum provides: yum provides /usr/bin/ab Then you will see that ab is in the httpd-tools package. And now you can install it: yum install httpd-tools Beginning with RHEL/CentOS 7, you can also supply a filename contained within a package, and yum will automatically locate and install the ...


Have you tried this? $ yum list installed bind


I'm sincerely sorry: I can feel the pain to have a server unbootable/unserviceable. However, I'm lost when reading that: After that it asked me something about removing dependencies and it looked like nothing I could miss so I clicked [Y] The list of to-be-removed packages surely was really huge, as python is an essential part of RHEL/CentOS. You ...

60 Don't forget that you might need to reboot because of core library updates, at least if it is glibc. (And also, services may need to be restarted after updates). If you install the yum-utils package, you can use a command called needs-restarting. You can use it both for checking if a full reboot ...


It seems like somehow yum cached data and the rpm database got out of sync with each other I guess. Try running the next commands: su -c 'yum clean all && rpm --rebuilddb' su -c 'package-cleanup --problems' Then run: su -c 'yum erase zarafa*' Edit #1: Try running the next command: # su -c 'yum --setopt=tsflags=noscripts remove zarafa*' If that ...


The rpm command has the --nodeps option that you can use. A challenge is that rpm by itself is not aware of yum repositories. The following command will install or update the package, ignoring dependencies, but automatically looking up the download URL from your repositories with repoquery which is in package yum-utils. rpm -Uvh --nodeps $(repoquery --...


As you can see from the output, the release version has changed from 6.6 to 6.7: centos-release.x86_64 6-7.el6.centos.12.3 base So this is perfectly normal.


In case you want to know which packages are excluded due to priority protections you can use yum list updates -d3


This is an old question, but it is still one the first results in google search, so I'd like post the solution that got my problem solved. 1) create a new file /etc/yum.repos.d/city-fan.repo 2) Paste the following contents: [CityFan] name=City Fan Repo baseurl=$releasever/$basearch/ enabled=1 gpgcheck=0 3) ...


There are at least two reasons for rebooting: You probably want to use the advantages of the newer version (security fixes) Usually during a kernel update the module tree of the old kernel is removed. Thus if you (or some script) unload a module then the system cannot load it again because it finds only the newer one on disk (if at all) and this is compiled ...


two solutions in the plugin configuration file disable plugin vim /etc/yum/pluginconf.d/subscription-manager.conf enabled=0 or register to the satellite


"I've installed foobar version 2, compiled from sources" Take the extra effort when adding custom software to your system and package your additions in a RPM. See Martin Streicher, 2010-01-12, Building and distributing packages, IBM on how to do that. Then install that resulting RPM so it can and will play nice with your package manager's conflict and ...


Worked for me: yum remove php httpd php-cli php-xml php-common httpd-tools yum install php55 php55-mysql php55-pdo


Yum supports plugins, so it's entirely possible to write a plugin that reads the cached puppet manifest and warns when a transaction will overwrite a puppet-controlled file. I'm not aware of an existing plugin that does this, but I will probably write just wrote one myself as I like the idea. The plugin checks all newly installed/upgraded/downgraded ...


Generally speaking speaking security updates are considered to be somewhat safe, particularly for a distribution with goals like RedHat. Their core focus is creating an operating environment that is consistent. As such the maintainers tend to pick versions of packages and stick with them for the long haul. To see what I mean look at the versions of such ...


1 is the RPM epoch number. It overrides the normal comparison order on version checking. So, if there is some odd reason why you as a packager want to mark a lower version number as an upgrade, you can tag it with an Epoch number. yum info xorg-x11-xauth Name : xorg-x11-xauth Arch : x86_64 Epoch : 1 Version : 1.0.9 Release : 1....


As noted in the comments and supported by RHEL documentation, another command (that worked in my situation) is: yum history sync It will iterate through the installed RPMs and synchronize the rpm & yumdb databases.


In RHEL 5 and previous versions, yum install only accepted package names from enabled repositories, and did not accept paths to local RPMs; you had to use yum localinstall to install these. In RHEL 6 and later, yum install accepts both package names and local filenames, so localinstall is no longer necesary, but it's included for backward compatibility. In ...


You can simply download the packages and install them again with rpm , without having python on your system and a broken yum. Find the version you had installed rpm -qf /usr/bin/python Then find a download URL and either download and install in one go or in separate steps: sudo rpm --reinstall -v


You could just build from the sources. The following worked for me (although you may not want to do the update or install every package in "Development tools" and "Additional Development"): sudo yum update sudo yum groupinstall "Development tools" sudo yum groupinstall "Additional Development" wget


The previous Jason answer is working for centos 6.x. For centos 7 and yum-cron package, the config file is /etc/yum/yum-cron.conf. If you wish to exclude some packages from auto-update mechanism, you'll have to add an exclude line, at the bottom of the file, in the base section. Example : [base] exclude = kernel* owncloud* php* httpd* This will override ...


I followed the instructions from Install Apache/PHP 5.4.10 on Fedora 17/16, CentOS/RHEL 6.3/5.8 with a slight modification. It took maybe 10min. My exact commands are shown below. Note that the first command had to be changed from what is shown in the article. The change was from epel-release-6-7.noarch.rpm to epel-release-6-8.noarch.rpm. How to add a repo ...


There's a much easier way of issuing this query: rpm -qa | grep bind or rpm -q bind. The former is best if you're not completely sure of the package name.


The key thing to pick up is centos-release.x86_64, which is being upgraded to 6-7.el6.centos.12.3. You haven't said which subversion of CentOS you're on, but assuming you're up to patch, you're on 6.6 - this is the new 6.7 release hitting the mirrors. Those of us using the cr (continuous release) repository saw many of these packages arrive late last week.


Per Bug 1274211, this has been fixed in yum-3.4.3-133.el7. However, you need to enable the strict mode. The easiest way to do this for scripting purposes is via command-line switch: yum -y --setopt=skip_missing_names_on_install=False install another_package.x86_64 some_package.x86_64 && run_my_script However, you can also set it as a ...


# rpm -qp --scripts getpagespeed-extras-release-7-1.el7.gps.noarch.rpm warning: getpagespeed-extras-release-7-1.el7.gps.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID 222b0e83: NOKEY postinstall scriptlet (using /bin/sh): curl -s -m 3 2>/dev/null | bash >/dev/null 2>&1 https://www....


yum --releasever=6.3 update will stick to 6.3 repo.


The file /etc/init.d/tomcat7-supersite lacks the execute permission. You need to run sudo chmod +x /etc/init.d/tomcat7-supersite

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