Conflito da versão do CentOS Multilib

Question

Estou tentando instalar o HHVM no meu CentOS 6.6, mas esse problema de multilib não está me deixando.

Ao executar yum upgrade , obtenho esse resultado.

root@invictus [~]# yum upgrade
Loaded plugins: fastestmirror
Setting up Upgrade Process
Loading mirror speeds from cached hostfile
 * aso: repo-uscentral.asonoc.com
 * base: centos.mirror.lstn.net
 * epel: fedora-epel.mirror.lstn.net
 * extras: repos.dfw.quadranet.com
 * rpmforge: mirror.nexcess.net
 * updates: repos.dfw.quadranet.com
Resolving Dependencies
--> Running transaction check
---> Package cpp.x86_64 0:4.4.7-11.el6 will be updated
---> Package cpp.x86_64 0:4.8.2-8.el6 will be an update
--> Processing Dependency: libmpc.so.2()(64bit) for package: cpp-4.8.2-8.el6.x86_64
---> Package curl.x86_64 0:7.19.7-40.el6_6.3 will be updated
---> Package curl.x86_64 0:7.29.0-4.el6 will be an update
---> Package gcc.x86_64 0:4.4.7-11.el6 will be updated
---> Package gcc.x86_64 0:4.8.2-8.el6 will be an update
---> Package gcc-c++.x86_64 0:4.4.7-11.el6 will be updated
---> Package gcc-c++.x86_64 0:4.8.2-8.el6 will be an update
---> Package gmp.x86_64 0:4.3.1-7.el6_2.2 will be updated
---> Package gmp.x86_64 1:4.3.2-4.el6 will be an update
---> Package libcurl.x86_64 0:7.19.7-40.el6_6.3 will be updated
---> Package libcurl.x86_64 0:7.29.0-4.el6 will be an update
---> Package libevent.x86_64 0:1.4.13-4.el6 will be updated
---> Package libevent.x86_64 0:1.4.14b-2.hphp.el6 will be an update
---> Package libgcc.x86_64 0:4.4.7-11.el6 will be updated
---> Package libgcc.x86_64 0:4.8.2-8.el6 will be an update
---> Package libgomp.x86_64 0:4.4.7-11.el6 will be updated
---> Package libgomp.x86_64 0:4.8.2-8.el6 will be an update
---> Package libstdc++.x86_64 0:4.4.7-11.el6 will be updated
---> Package libstdc++.x86_64 0:4.8.2-8.el6 will be an update
---> Package libstdc++-devel.x86_64 0:4.4.7-11.el6 will be updated
---> Package libstdc++-devel.x86_64 0:4.8.2-8.el6 will be an update
---> Package libtool.x86_64 0:2.2.6-15.5.el6 will be updated
---> Package libtool.x86_64 0:2.4.2-21.el6 will be an update
---> Package libtool-ltdl.x86_64 0:2.2.6-15.5.el6 will be updated
---> Package libtool-ltdl.x86_64 0:2.4.2-21.el6 will be an update
---> Package libtool-ltdl-devel.x86_64 0:2.2.6-15.5.el6 will be updated
---> Package libtool-ltdl-devel.x86_64 0:2.4.2-21.el6 will be an update
---> Package mpfr.x86_64 0:2.4.1-6.el6 will be updated
---> Package mpfr.x86_64 0:2.4.2-1.el6 will be an update
--> Running transaction check
---> Package libmpc.x86_64 0:0.8.3-0.3.svn855.el6 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 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 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 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).

       Protected multilib versions: libgcc-4.8.2-8.el6.x86_64 != libgcc-4.4.7-11.el6.i686
root@invictus [~]# 

Ao executar yum check

root@invictus [~]# yum check
Loaded plugins: fastestmirror
python-libs-2.6.6-52.el6.x86_64 has missing requires of libffi.so.5()(64bit)
Error: check all
root@invictus [~]# 

    

Answer 1

O problema é que é nenhum pacote libgcc.x86_64 0:4.8.2-8.el6 no RHEL6 / CentOS6. A versão atual do EL6 é a 4.4.7-11, que é a versão que você instalou atualmente.

A tarefa à sua frente é descobrir por que o yum encontrou tal pacote em primeiro lugar.

Primeiro, limpe seu cache do yum completamente. É possível que alguém tenha criado um pacote desse tipo por acidente e tenha sido puxado mais tarde, mas seu sistema ainda tem metadados referentes a ele.

yum clean all

Em segundo lugar, descubra onde o yum pensa que esse pacote está vindo. Executar:

yum list all libgcc

Em um sistema limpo do CentOS 6.6 você deve obter a seguinte saída:

Installed Packages
libgcc.x86_64                         4.4.7-11.el6                         @base
Available Packages
libgcc.i686                           4.4.7-11.el6                         base 

Se você obtiver alguma outra coisa, o repositório será identificado e você poderá desativar esse repositório, contatar seu mantenedor, suspeitar de atividade maliciosa, etc.

Se você obtiver uma saída idêntica, poderá continuar com a atualização do sistema.

    

Answer 2

Eu tenho problema semelhante. Quando eu tento atualizar centos7 eu recebo resultado:

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 device-mapper-libs which is missing some
     dependency that another package requires. Yum is trying to
     solve this by installing an older version of device-mapper-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 device-mapper-libs.otherarch ... this should give you an error
     message showing the root cause of the problem.

  2. You have multiple architectures of device-mapper-libs 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 device-mapper-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).

Chronione wersje multilib: 7:device-mapper-libs-1.02.135-1.el7_3.2.x86_64 != 7:device-mapper-libs-1.02.135-1.el7_3.1.i686

No meu caso, tenho problema com device-mapper-libs . Na primeira etapa, verifique os pacotes duplicados:

yum list --showduplicates device-mapper-libs-1.02.135-1.el7_3.1

Wczytane wtyczki: fastestmirror, langpacks Loading mirror speeds from
cached hostfile  * base: centos1.hti.pl  * epel: ftp.icm.edu.pl  *
extras: centos1.hti.pl  * nux-dextop: li.nux.ro  * updates:
ftp.icm.edu.pl  * webtatic: uk.repo.webtatic.com Zainstalowane pakiety
device-mapper-libs.i686                                               
7:1.02.135-1.el7_3.1                                                  
@updates device-mapper-libs.x86_64                                    
7:1.02.135-1.el7_3.1                                                  
@updates Dostępne pakiety device-mapper-libs.i686                     
7:1.02.135-1.el7_3.1                                                  
updates  device-mapper-libs.x86_64

Em seguida, remova o pacote inválido:

yum erase device-mapper-libs.i686

E agora execute atualização / atualização. Funcionou.

    

Answer 3

Eu tenho um problema parecido quando estava atualizando meu sistema do CentOS 7. O principal problema é que o processo de atualização está puxando algumas dependências que estão em conflito com a versão que está instalada na máquina local. Para poder atualizar uma máquina, é necessário remover a versão mais antiga dos pacotes que estão em conflito, ou seja,

rpm -e --justdb --nodeps libgcc-4.4.7-11.el6.i686

Em algum momento, pode ser também um problema com pacotes 32 vs 64, que podem ser resolvidos como aqui