CentOS 7 update appears: Solution to Multilib version problems problem

  • 2020-06-19 12:33:31
  • OfStack

preface

Don't say a lot about CentOS origins, all function and performance of a RHEL even more friendly, free, is the most important 1 point was deeply loved by everyone, no popularity CentOS Ubuntu, before installing the CentOS7, about the installation of the tutorial, friends in need can refer to this article: https: / / www ofstack. com article / 95263. htm, few words said, below 1 look at the detailed introduction.

Found the problem

During the update of CentOS7 system in recent two days, the error of Multilib version problems appeared. The command was executed:


# yum update

Error message that appears:


....
---> Package libcap-ng.i686 0:0.7.5-4.el7 will be installed
---> Package libstdc++.i686 0:4.8.5-16.el7 will be installed
--> 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 glibc which is missing some
  dependency that another package requires. Yum is trying to
  solve this by installing an older version of glibc 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 glibc.otherarch ... this should give you an error
  message showing the root cause of the problem.

  2. You have multiple architectures of glibc 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 glibc 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: glibc-2.17-196.el7.i686 != glibc-2.17-157.el7_3.1.x86_64
Error: Protected multilib versions: pcre-8.32-17.el7.i686 != pcre-8.32-15.el7_2.1.x86_64
Error: Protected multilib versions: elfutils-libs-0.168-8.el7.i686 != elfutils-libs-0.166-2.el7.x86_64
......

The solution process is as follows:


// Query for duplicate packages 
# rpm -q systemd-libs
systemd-libs-219-30.el7.x86_64
systemd-libs-219-42.el7_4.1.x86_64

// Delete the old version 
# rpm -e systemd-libs-219-30.el7.x86_64
error: Failed dependencies:
 systemd-libs = 219-30.el7 is needed by (installed) libgudev1-219-30.el7.x86_64

// The dependency problem still exists, continue the query libgudev1 Version information of 
# rpm -q libgudev1
libgudev1-219-30.el7.x86_64

// Found only 1 Multiple versions, upgrade try 1 Under the 
# yum update libgudev1
......
Updated:
 libgudev1.x86_64 0:219-42.el7_4.1                              

Complete!
# rpm -q libgudev1
libgudev1-219-42.el7_4.1.x86_64

// When the upgrade is complete, delete the old version systemd-libs
# rpm -e systemd-libs-219-30.el7.x86_64
# rpm -q systemd-libs
systemd-libs-219-42.el7_4.1.x86_64

The final query found that only the latest version of systemd-ES32en, other duplicate version of the package, the same process.

The core commands are:


rpm -q package-names
rpm -e package-full-version

conclusion


Related articles: