2 Replies Latest reply on May 20, 2020 11:03 AM by Sven Jansen

    Oracle Linux 7.8 UEK 6 Multilib Problem with libcom_err

    Sven Jansen



      today i updated some test machines from UEK 5 to UEK 6 and one of my machines have libcom_err in 32bit and 64bit installed and fails to update because of a multilib conflict.


      UEK 6 repo provides "libcom_err-1.45.4-2.el7.x86_64.rpm" only in 64bit.

      Latest base repo provides "libcom_err-1.42.9-17.el7.i686.rpm" and "libcom_err-1.42.9-17.el7.x86_64.rpm"


      Updateing fails because UEK 6 user space tools need the new libcom_err 1.45 but does not provide a 32bit version.



      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 libcom_err which is missing some

                   dependency that another package requires. Yum is trying to

                   solve this by installing an older version of libcom_err 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 libcom_err.otherarch ... this should give you an error

                   message showing the root cause of the problem.


                2. You have multiple architectures of libcom_err 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 libcom_err 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-Version: libcom_err-1.45.4-2.el7.x86_64 != libcom_err-1.42.9-17.el7.i686