CentOS'ta güncelleme yapmak istediğinizde "Multilib version problems with" hatası alabilirsiniz. Benim örneğimde bu hataya 
Hatanın nedeni mimari farklılık. 64 Bit bir sistemde 32 Bit sürümler varsa çakışma olabiliyor. Yapmanız gereken çakışma yapan RPM'i silmek.
	
	
	
	
	
		
Öncelikle kaç tane glib yüklü olduğuna bakıyoruz:
	
	
	
	
	
		
Sonuç:
	
	
	
	
	
		
Şimdi hataya sebep olan
	
	
	
	
	
		
Artık özgürce güncelleme yapabiliriz:
	
	
	
	
	
		
	
		
			
		
		
	
				
			glibc sebep oluyordu.Hatanın nedeni mimari farklılık. 64 Bit bir sistemde 32 Bit sürümler varsa çakışma olabiliyor. Yapmanız gereken çakışma yapan RPM'i silmek.
		Kod:
	
	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-307.el7.1.i686 != glibc-2.17-292.el7.x86_64
Error: Protected multilib versions: libselinux-2.5-15.el7.i686 != libselinux-2.5-14.1.el7.x86_64
Error: Protected multilib versions: elfutils-libelf-0.176-4.el7.i686 != elfutils-libelf-0.176-2.el7.x86_64
Error: Protected multilib versions: libcap-2.22-11.el7.i686 != libcap-2.22-10.el7.x86_64
Error: Protected multilib versions: pam-1.1.8-23.el7.i686 != pam-1.1.8-22.el7.x86_64
	Öncelikle kaç tane glib yüklü olduğuna bakıyoruz:
		Kod:
	
	rpm -qa | grep glibc
	Sonuç:
		Kod:
	
	glibc-common-2.17-292.el7.x86_64
glibc-common-2.17-307.el7.1.x86_64
glibc-2.17-307.el7.1.x86_64
glibc-2.17-292.el7.x86_64
glibc-devel-2.17-292.el7.x86_64
glibc-headers-2.17-292.el7.x86_64
glibc-2.17-292.el7.i686
glibc-static-2.17-292.el7.x86_64
	Şimdi hataya sebep olan
glibc-2.17-292.el7.i686 sürümünü uçuralım:
		Kod:
	
	yum remove glibc-2.17-292.el7.i686
	Artık özgürce güncelleme yapabiliriz:
		Kod:
	
	yum --enablerepo=cr update