Red Hat Bugzilla – Bug 903731
yum upgrade protected multilib packages
Last modified: 2014-01-21 01:25:38 EST
+++ This bug was initially created as a clone of Bug #840543 +++
Description of problem:
When multilib packages are upgraded and only one arch is available yum suppose to fail and keep the old packages.
This is the behavior on RHEL-6 but on RHEL-7 it proceed with upgrade.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1/ Create test packages or find some similar in repos:
2/ Install the version 1:
# yum install pkg-1.i686.rpm pkg-1.x86_64.rpm
3/ Update only one architecture:
# yum localupdate pkg-2.x86_64.rpm
yum proceed with update and uninstall the version 1 packages and install the
available verion 2:
# rpm -qa pkg
yum report error like in RHEL-6:
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
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 pkg which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of pkg 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 pkg.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of pkg 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
3. You have duplicate versions of pkg 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: pkg-2.x86_64 != pkg-1.i686
# rpm -q pkg
> Actual results:
> yum proceed with update and uninstall the version 1 packages and install the available verion 2:
> # rpm -qa pkg
This is kind of different, in that when using "localupgrade" yum only sees the .x86_64 package, so it's assuming an arch. merge has happened and removes the .i686 package. This wouldn't be the case if both the .i686 and .x86_64 packages were in a repo.
Given that there is no old pkg-1.i686 left after the transaction, there is nothing for multilib_protection to complain about.