I've got an inherited server in my estate that runs git, I'm just trying to perform security updates on it using # yum update --security and am running into an issue I'm not sure about, below is the tail of the output:
--> Finished Dependency Resolution
Error: Package: subversion-perl-1.6.11-9.el6_4.x86_64 (#rhel-x86_64-server-optional-6)
Requires: subversion = 1.6.11-9.el6_4
Removing: subversion-1.6.11-9.el6_4.i686 (#rhel-x86_64-server-6)
subversion = 1.6.11-9.el6_4
Updated By: subversion-1.6.11-10.el6_5.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-10.el6_5
Available: subversion-1.6.11-2.el6.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6
Available: subversion-1.6.11-2.el6_0.2.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6_0.2
Available: subversion-1.6.11-2.el6_0.3.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6_0.3
Available: subversion-1.6.11-2.el6_1.4.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6_1.4
Available: subversion-1.6.11-7.el6.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-7.el6
Error: Package: subversion-ruby-1.6.11-9.el6_4.x86_64 (#rhel-x86_64-server-optional-6)
Requires: subversion = 1.6.11-9.el6_4
Removing: subversion-1.6.11-9.el6_4.i686 (#rhel-x86_64-server-6)
subversion = 1.6.11-9.el6_4
Updated By: subversion-1.6.11-10.el6_5.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-10.el6_5
Available: subversion-1.6.11-2.el6.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6
Available: subversion-1.6.11-2.el6_0.2.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6_0.2
Available: subversion-1.6.11-2.el6_0.3.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6_0.3
Available: subversion-1.6.11-2.el6_1.4.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-2.el6_1.4
Available: subversion-1.6.11-7.el6.i686 (rhel-x86_64-server-6)
subversion = 1.6.11-7.el6
Error: Package: ruby-ri-1.8.7.352-12.el6_4.x86_64 (#rhel-x86_64-server-optional-6)
Requires: ruby-rdoc = 1.8.7.352-12.el6_4
Removing: ruby-rdoc-1.8.7.352-12.el6_4.x86_64 (#rhel-x86_64-server-6)
ruby-rdoc = 1.8.7.352-12.el6_4
Updated By: ruby-rdoc-1.8.7.352-13.el6.x86_64 (rhel-x86_64-server-6)
ruby-rdoc = 1.8.7.352-13.el6
Available: ruby-rdoc-1.8.7.352-7.el6_2.x86_64 (rhel-x86_64-server-6)
ruby-rdoc = 1.8.7.352-7.el6_2
Available: ruby-rdoc-1.8.7.352-10.el6_4.x86_64 (rhel-x86_64-server-6)
ruby-rdoc = 1.8.7.352-10.el6_4
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
The server is RHEL 6.4 and is dedicated to runnig Git (version 1.7.1).
Is this due to multiple copies of the same package but for different architectures? Is there any way around it?
Let me know if you need more info from me.
Cheers
I should add that if I run it with --skip-broken I get the following:
--> Finished Dependency Resolution
Packages skipped because of dependency problems:
ruby-irb-1.8.7.352-13.el6.x86_64 from rhel-x86_64-server-6
ruby-rdoc-1.8.7.352-13.el6.x86_64 from rhel-x86_64-server-6
subversion-1.6.11-10.el6_5.i686 from rhel-x86_64-server-6
subversion-1.6.11-10.el6_5.x86_64 from rhel-x86_64-server-6
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for ruby-libs which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of ruby-libs of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude ruby-libs.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of ruby-libs installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of ruby-libs installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: ruby-libs-1.8.7.352-12.el6_4.i686 != ruby-libs-1.8.7.352-13.el6.x86_64
You could try running: rpm -Va --nofiles --nodigest
It turns out it was a n00b issue, although I had the #rhel-x86_64-server-optional-6 channel, I hadn't cleared the yum cache!
# yum clean all
# yum repolist
Sorted it.
Related
I am running Centos 7 with additional repositories remi-safe and mariaDB-10.5.
Everything worked fine for several months, now I get a package conflict when running yum update:
Error: Package: libzip5-1.8.0-2.el7.remi.x86_64 (remi-safe)
Required: libzstd(x86-64) >= 1.3.6
Available: libzstd-1.3.4-1.el7.x86_64 (mariadb-main)
libzstd(x86-64) = 1.3.4-1.el7
Error: Package: libzip5-1.8.0-2.el7.remi.x86_64 (remi-safe)
Required: libzstd(x86-64) >= 1.3.6
Install: libzstd-1.3.4-1.el7.x86_64 (mariadb-main)
libzstd(x86-64) = 1.3.4-1.el7
I tried to solve this by setting priorities to the yum repos (I gave 1 to MariaDB, 2 to Remi, 3 to Centos Base packages and 4 to EPEL) but this did not solve the issue.
How could I get remi-safe and mariadb-10.5 to live on the system again without quarreling?
EPEL have zstd 1.5.0, so you must use this one
So should either disable priority plugin or configure it properly, with higher priority for base and EPEL repository, higher priority means lower value.
Notice that mariadb 10.5 is available in official CentOS SCLo repository, which is probably better integrated to system.
I am trying to get a server up and running to run python scripts (Django framework) and such by using the mod_wsgi apache module to handle the scripts, however, it's not playing ball and I don't know enough to figure out what's happening or what I'm doing wrong.
I have been unable to come right using the YUM installer. So far, this is the output:
# sudo yum install mod_wsgi
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 169.255.59.74
* cpanel-addons-production-feed: 169.255.59.74
* base: mirror.wiru.co.za
* epel: fedora.mirror.ac.za
* extras: mirror.wiru.co.za
* ius: mirrors.ircam.fr
* updates: mirror.wiru.co.za
* webtatic: uk.repo.webtatic.com
Resolving Dependencies
--> Running transaction check
---> Package mod_wsgi.x86_64 0:3.4-12.el7_0 will be installed
--> Processing Dependency: httpd-mmn = 20120211x8664 for package:
mod_wsgi-3.4-12.el7_0.x86_64
--> Finished Dependency Resolution
Error: Package: mod_wsgi-3.4-12.el7_0.x86_64 (base)
Requires: httpd-mmn = 20120211x8664
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
The first thing that jumped out is the dependency httpd which I tried (and failed) to install using yum. After this, I did some research and found out its an issue with cPanel and that apparently it prevents you from using Yum to install Apache modules and everywhere says I am supposed to use the interface but I have no idea how?
My goal is to figure out how I'm 'supposed' to be loading these modules to get around these obstacles and get my server going. Someone, please help!
I am running:
CentOs 7.5
Apache 2.4.34
EasyApache 4
cPanel 7.40
PHP 5.6.38
On a CentOS 7.5 machine, I updated httpd (Apache) using yum to 2.4.6-80.el7.centos.1. Not exactly sure what your situation is with your pre-installed httpd version 2.4.34. Like I said in my comment above, I only trust versions of software available though yum. Your version is above the standard version so you could experience unexpected results.
Updated:
httpd.i686 0:2.4.6-80.el7.centos.1
Dependency Updated:
httpd-devel.i686 0:2.4.6-80.el7.centos.1
httpd-manual.noarch 0:2.4.6-80.el7.centos.1
httpd-tools.i686 0:2.4.6-80.el7.centos.1
mod_ldap.i686 0:2.4.6-80.el7.centos.1
mod_ssl.i686 1:2.4.6-80.el7.centos.1
After upgrading httpd, I added mod_wsgi and it installed without any problems:
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
mod_wsgi i686 3.4-12.el7_0 base 75 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 75 k
Installed size: 187 k
Is this ok [y/d/N]: y
Downloading packages:
mod_wsgi-3.4-12.el7_0.i686.rpm | 75 kB 00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : mod_wsgi-3.4-12.el7_0.i686 1/1
Verifying : mod_wsgi-3.4-12.el7_0.i686 1/1
Installed:
mod_wsgi.i686 0:3.4-12.el7_0
Complete!
I guess the point I'm trying to make is that if you use version of software no available through yum you can experience unexpected results. I have been down this road before and I now use version of software only if they are available through yum.
The error you recieved: Requires: httpd-mmn = 20120211x8664 is for a package not yet available through yum. I performed a yum search on a CentOS 7.5 machine and it yields nothing available for httpd-mmn:
yum search httpd-mmn
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Warning: No matches found for: httpd-mmn
No matches found
So, you would have to compile it yourself possibly to get your setup to work.
I am trying to install g++ 4.1.2 (seems gcc 4.1.2 is already installed) in a Redhat Linux 6 machine. When I first tried running gcc-c++-4.1.2 rpm through yum, I get the following dependency issues,
[root#Cham1WS Desktop]# yum install gcc-c++-4.1.2-55.el5.x86_64.rpm
Setting up Install Process
Examining gcc-c++-4.1.2-55.el5.x86_64.rpm: gcc-c++-4.1.2-55.el5.x86_64
Marking gcc-c++-4.1.2-55.el5.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.1.2-55.el5 will be installed
--> Processing Dependency: libstdc++ = 4.1.2-55.el5 for package: gcc-c++- 4.1.2-55.el5.x86_64
--> Processing Dependency: libstdc++-devel = 4.1.2-55.el5 for package: gcc-c++-4.1.2-55.el5.x86_64
--> Finished Dependency Resolution
Error: Package: gcc-c++-4.1.2-55.el5.x86_64 (/gcc-c++-4.1.2-55.el5.x86_64)
Requires: libstdc++-devel = 4.1.2-55.el5
Error: Package: gcc-c++-4.1.2-55.el5.x86_64 (/gcc-c++-4.1.2-55.el5.x86_64)
Requires: libstdc++ = 4.1.2-55.el5
Installed: libstdc++-4.4.7-16.el6.x86_64 (#anaconda- RedHatEnterpriseLinux-201507020259.x86_64/6.7)
libstdc++ = 4.4.4-15.el6
libstdc++ = 4.4.7-16.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
So, it seems I need to install libstdc++-devel-4.1.2-55.el5.x86_64.rpm. So I tried installing it and I get the follwoing dependencies,
[root#Cham1WS Desktop]# yum install libstdc++-devel-4.1.2-55.el5.x86_64.rpm
Setting up Install Process
Examining libstdc++-devel-4.1.2-55.el5.x86_64.rpm: libstdc++-devel-4.1.2-55.el5.x86_64
Marking libstdc++-devel-4.1.2-55.el5.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package libstdc++-devel.x86_64 0:4.1.2-55.el5 will be installed
--> Processing Dependency: libstdc++ = 4.1.2-55.el5 for package: libstdc++-devel-4.1.2-55.el5.x86_64
--> Finished Dependency Resolution
Error: Package: libstdc++-devel-4.1.2-55.el5.x86_64 (/libstdc++-devel-4.1.2-55.el5.x86_64)
Requires: libstdc++ = 4.1.2-55.el5
Installed: libstdc++-4.4.7-16.el6.x86_64 (#anaconda-RedHatEnterpriseLinux-201507020259.x86_64/6.7)
libstdc++ = 4.4.4-15.el6
libstdc++ = 4.4.7-16.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
It seems an earlier version of libstdc++ is already installed. Anyways, I tried installing libstdc++-4.1.2-55.el5.x86_64.rpm (not the "devel"), and it says it's already installed.
[root#Cham1WS Desktop]# yum install libstdc++-4.1.2-55.el5.x86_64.rpm
Setting up Install Process
Examining libstdc++-4.1.2-55.el5.x86_64.rpm: libstdc++-4.1.2-55.el5.x86_64
libstdc++-4.1.2-55.el5.x86_64.rpm: does not update installed package.
Error: Nothing to do
But if I try to install the "libstdc++-devel-4.1.2-55.el5.x86_64.rpm" I get the ealier dependencies again. It seems the issue is that I have a newer version of libstdc++ is already installed
1) How do I fix this issue?
2) Do I need to uninstall the later version of libstdc++?
It seems like you are using yum the wrong way: You should let yum connect to some repositories, and let him figure out the dependencies.
By the way you are installing el5 packages, that means packages for centos5, not centos6. Try finding similar packages but for centos6, that would be better; try using the epel repository which might help you (take a look here on how to enable it: https://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/)
I have a problem when going to install the latest MariaDB on CentOS 7. I use yum repository from MariaDB, for only mariadb, another module like php use remirepo. I added a yum repo for MariaDB-10 but installed always mariadb-55.
--> Finished Dependency Resolution
Error: MariaDB-common conflicts with 1:mariadb-libs-5.5.52-1.el7.x86_64
Error: Package: 1:mariadb-5.5.52-1.el7.x86_64 (base)
Requires: mariadb-libs(x86-64) = 1:5.5.52-1.el7
Installed: MariaDB-shared-10.1.21-1.el7.centos.x86_64 (#mariadb)
mariadb-libs(x86-64) = 1:10.1.21-1.el7.centos
Error: Package: 1:mariadb-server-5.5.52-1.el7.x86_64 (base)
Requires: mariadb-libs(x86-64) = 1:5.5.52-1.el7
Installed: MariaDB-shared-10.1.21-1.el7.centos.x86_64 (#mariadb)
mariadb-libs(x86-64) = 1:10.1.21-1.el7.centos
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Also i have exclude option on remi.repo
/etc/yum.repos.d/remi.repo
## Exclude following Packages Updates ##
exclude=mariadb-server mariadb mariadb-libs MariaDB-common MariaDB-client
mariadb doesn't not come from "remi" repository, but from base/updates standard repositories.
On last Friday morning, I tried a "yum update" on my CentOS laptop, and it reported this:
Loaded plugins: fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
* base: repo1.dal.innoscale.net
* epel: fedora-epel.mirror.lstn.net
* extras: mirror.unl.edu
* nux-dextop: mirror.li.nux.ro
* rpmfusion-free-updates: mirror.us.leaseweb.net
* updates: mirror.spro.net
Resolving Dependencies
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.16.2.3-13.el7_1 will be updated
---> Package nss-softokn-freebl.i686 0:3.16.2.3-14.2.el7_2 will be an update
---> Package python-ecdsa.noarch 0:0.11-3.el7.centos will be obsoleted
---> Package python2-ecdsa.noarch 0:0.13-4.el7 will be obsoleting
---> Package tzdata.noarch 0:2016c-1.el7 will be updated
---> Package tzdata.noarch 0:2016d-1.el7 will be an update
---> Package tzdata-java.noarch 0:2016c-1.el7 will be updated
---> Package tzdata-java.noarch 0:2016d-1.el7 will be an update
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for nss-softokn-freebl which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of nss-softokn-freebl of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude nss-softokn-freebl.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of nss-softokn-freebl installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of nss-softokn-freebl installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: nss-softokn-freebl-3.16.2.3-14.2.el7_2.i686 != nss-softokn-freebl-3.16.2.3-13.el7_1.x86_64
I asked about this on #centos, and someone gave me some exploratory advice, but no real solution.
I experienced the very same issue on a Fedora 20 system (run in a docker container) when trying to install i686 development libraries. Reason were two not matching versions for x86_64 and i686, respectively.
Protected multilib versions: nss-softokn-freebl-3.19.1-1.0.fc20.i686 != nss-softokn-freebl-3.19.2-1.0.fc20.x86_64
For me it helped to call
yum distribution-synchronization
That automatically downgraded the x86_64 version. After that
I could install with
yum install nss-softokn-freebl.i686
and
yum list installed | grep nss-softokn-freebl
showed now:
nss-softokn-freebl.i686 3.19.1-1.0.fc20 #updates
nss-softokn-freebl.x86_64 3.19.1-1.0.fc20 #updates
Problem solved.