Forums

Resolved
0 votes
Hi,
I've noticed that my ClearOS haven't been updated for a while now, I have a lot of updates waiting in the list.
I have tried to manually update by clicking the "Update all" button without success.

You can see my enabled repositories in the attached picture.

I did a YUM update -v this evening and got this output:
---> Package hal.x86_64 0:0.5.14-11.el6 will be updated
Checking deps for hal.x86_64 0:0.5.14-11.el6 - ud
hal-storage-addon-0.5.14-11.el6.x86_64 requires: hal = 0.5.14-11.el6
--> Processing Dependency: hal = 0.5.14-11.el6 for package: hal-storage-addon-0.5.14-11.el6.x86_64
Potential Provider: hal.x86_64 0:0.5.14-11.el6
Mode is ud for provider of hal = 0.5.14-11.el6: hal.x86_64 0:0.5.14-11.el6
Mode for pkg providing hal = 0.5.14-11.el6: ud
Trying to update hal-storage-addon-0.5.14-11.el6.x86_64 to resolve dep
No update paths found for hal-storage-addon-0.5.14-11.el6.x86_64. Failure!
Searching pkgSack for dep: hal
---> Package libvirt-client.x86_64 0:0.10.2-46.el6_6.1 will be updated
Checking deps for libvirt-client.x86_64 0:0.10.2-46.el6_6.1 - ud
libvirt-0.10.2-46.el6_6.1.x86_64 requires: libvirt-client = 0.10.2-46.el6_6.1
--> Processing Dependency: libvirt-client = 0.10.2-46.el6_6.1 for package: libvirt-0.10.2-46.el6_6.1.x86_64
Potential Provider: libvirt-client.x86_64 0:0.10.2-46.el6_6.1
Mode is ud for provider of libvirt-client = 0.10.2-46.el6_6.1: libvirt-client.x86_64 0:0.10.2-46.el6_6.1
Mode for pkg providing libvirt-client = 0.10.2-46.el6_6.1: ud
Trying to update libvirt-0.10.2-46.el6_6.1.x86_64 to resolve dep
No update paths found for libvirt-0.10.2-46.el6_6.1.x86_64. Failure!
Searching pkgSack for dep: libvirt-client
--> Finished Dependency Resolution
Dependency Process ending
--> Running transaction check
---> Package hal.x86_64 0:0.5.14-11.el6 will be updated
Checking deps for hal.x86_64 0:0.5.14-11.el6 - ud
hal-storage-addon-0.5.14-11.el6.x86_64 requires: hal = 0.5.14-11.el6
--> Processing Dependency: hal = 0.5.14-11.el6 for package: hal-storage-addon-0.5.14-11.el6.x86_64
Potential Provider: hal.x86_64 0:0.5.14-11.el6
Mode is ud for provider of hal = 0.5.14-11.el6: hal.x86_64 0:0.5.14-11.el6
Mode for pkg providing hal = 0.5.14-11.el6: ud
Trying to update hal-storage-addon-0.5.14-11.el6.x86_64 to resolve dep
No update paths found for hal-storage-addon-0.5.14-11.el6.x86_64. Failure!
Searching pkgSack for dep: hal
---> Package kernel.x86_64 0:2.6.32-431.17.1.v6 will be erased
Checking deps for kernel.x86_64 0:2.6.32-431.17.1.v6 - e
---> Package libvirt-client.x86_64 0:0.10.2-46.el6_6.1 will be updated
Checking deps for libvirt-client.x86_64 0:0.10.2-46.el6_6.1 - ud
libvirt-0.10.2-46.el6_6.1.x86_64 requires: libvirt-client = 0.10.2-46.el6_6.1
--> Processing Dependency: libvirt-client = 0.10.2-46.el6_6.1 for package: libvirt-0.10.2-46.el6_6.1.x86_64
Potential Provider: libvirt-client.x86_64 0:0.10.2-46.el6_6.1
Mode is ud for provider of libvirt-client = 0.10.2-46.el6_6.1: libvirt-client.x86_64 0:0.10.2-46.el6_6.1
Mode for pkg providing libvirt-client = 0.10.2-46.el6_6.1: ud
Trying to update libvirt-0.10.2-46.el6_6.1.x86_64 to resolve dep
No update paths found for libvirt-0.10.2-46.el6_6.1.x86_64. Failure!
Searching pkgSack for dep: libvirt-client
--> Finished Dependency Resolution
Dependency Process ending
Depsolve time: 5.609
Error: Package: hal-storage-addon-0.5.14-11.el6.x86_64 (@clearos-core)
Requires: hal = 0.5.14-11.el6
Removing: hal-0.5.14-11.el6.x86_64 (@anaconda-ClearOSCommunity-201303291439.x86_64/6.4.0)
hal = 0.5.14-11.el6
Updated By: hal-0.5.14-14.el6.x86_64 (clearos)
hal = 0.5.14-14.el6
Error: Package: libvirt-0.10.2-46.el6_6.1.x86_64 (@contribs)
Requires: libvirt-client = 0.10.2-46.el6_6.1
Removing: libvirt-client-0.10.2-46.el6_6.1.x86_64 (@contribs)
libvirt-client = 0.10.2-46.el6_6.1
Updated By: libvirt-client-0.10.2-46.el6_6.3.x86_64 (clearos)
libvirt-client = 0.10.2-46.el6_6.3


What is wrong and how can I get my server updated again? http://www.clearfoundation.com/media/kunena/attachments/legacy/images/clearos_repos.png
Sunday, February 22 2015, 10:35 PM
Share this post:

Accepted Answer

Thursday, January 05 2017, 05:46 PM - #Permalink
Resolved
0 votes
Göran Amredahl wrote:

Please help me to fix this multilib issue.


These mulitlib errors can be a pain and are often caused by mixing 32-bit packages on a 64-bit system. First, try updating app-base:

yum upgrade app-base


Then run the normal upgrade:

yum upgrade


If that doesn't work and you have 32-bit packages installed, then you will need to add the CentOS repositories to the yum upgrade:

yum --enablerepo=centos-unverified,centos-updates-unverified upgrade
The reply is currently minimized Show
Responses (7)
Your Reply