DescriptionIf an Operating System update is interrupted (due to loss of communication, etc) a second update attempt may fail due to duplicate versions of libgcc attempting to be installed.
If restarting the update via CLI (yum -y update), the following is displayed:
--> 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 libgcc which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libgcc 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 libgcc.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libgcc 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 libgcc 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).
Solution1. List duplicate versions of libgcc. Type
package-cleanup --dupes
2. If duplicates are reported, run the following command to remove them. Type
package-cleanup --cleandupes
3. Restart Operating System update
yum -y update
See also
https://wpguru.co.uk/2017/01/how-to-fix-duplicate-packages-in-yum/
