These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Problematic updates on the new forum.
Hi all just wandering if anyone else has seen this and how I should best go about fixing it?
Now updating libstdc++ ..
Installing package(s) with command yum -y install libstdc++ ..
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.hmc.edu
* epel: mirror.hmc.edu
* extras: centos-distro.cavecreek.net
* updates: centos-mirror.jchost.net
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package libstdc++.x86_64 0:4.4.6-4.el6 will be updated
---> Package libstdc++.x86_64 0:4.4.7-3.el6 will be an update
--> 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 libstdc++ which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libstdc++ 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 libstdc++.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libstdc++ 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 libstdc++ 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: libstdc++-4.4.7-3.el6.x86_64 != libstdc++-4.4.6-4.el6.i686
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
.. install failed!
Now updating libxml2 ..
Installing package(s) with command yum -y install libxml2 ..
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.hmc.edu
* epel: mirror.hmc.edu
* extras: centos-distro.cavecreek.net
* updates: centos-mirror.jchost.net
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package libxml2.x86_64 0:2.7.6-8.el6_3.4 will be updated
---> Package libxml2.x86_64 0:2.7.6-12.el6_4.1 will be an update
--> 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 libxml2 which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libxml2 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 libxml2.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libxml2 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 libxml2 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: libxml2-2.7.6-12.el6_4.1.x86_64 != libxml2-2.7.6-8.el6_3.4.i686
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
.. install failed!
Howdy,
Hmm, that's an odd one!
You appear to have a third party repo, the EPEL repo enabled.
That one usually doesn't cause problems, but it wouldn't hurt to rule that out... is there any chance you could disable that, and then try the update again?
-Eric
Where do I go about disabling the repo?
Still needing help with this guys, how can i go about disabling that repo to test?
Look for the epel repo config file in /etc/yum.repos.d/, and in there, set "enabled=0" in that file.
-Eric