I've had Auto Update enabled for some time, but noticed the other day that last update was April 20th.
Running "yum update" in a shell, I received a dependency error for glibc :
Question is if it's safe to run this with "--skip-broken" or if there's something else I need to check. I really like to resolve this correctly...
Thanks in advance!
/Andreas
Running "yum update" in a shell, I received a dependency error for glibc :
--> Finished Dependency Resolution
Error: Package: glibc-2.17-105.el7.i686 (clearos-centos)
Requires: glibc-common = 2.17-105.el7
Removing: glibc-common-2.17-78.el7.x86_64 (@anaconda/7.1.0)
glibc-common = 2.17-78.el7
Updated By: glibc-common-2.17-106.el7_2.4.x86_64 (clearos)
glibc-common = 2.17-106.el7_2.4
Available: glibc-common-2.17-105.el7.x86_64 (clearos-centos)
glibc-common = 2.17-105.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Question is if it's safe to run this with "--skip-broken" or if there's something else I need to check. I really like to resolve this correctly...
Thanks in advance!
/Andreas
In Support
Share this post:
Responses (9)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
clearos-centos-updates is already enabled.
Why are you trying to install 32-bit packages (i686)? ClearOS is 64-bit (x86_64).
couse its in his dependencies: Link -
Accepted Answer
-
Accepted Answer
hi dears,
please advise(my connection was cut in the middle of installation and there were 37 dependencies, i've removed manually(rpm -e) all old packages, however cannot delete/updare glibc) what to do:
yum upgrade
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.prometeus.net
* epel: ftp.fau.de
* extras: mirrors.prometeus.net
* updates: mirrors.prometeus.net
Resolving Dependencies
--> Running transaction check
---> Package device-mapper-persistent-data.x86_64 0:0.5.5-1.el7 will be updated
---> Package device-mapper-persistent-data.x86_64 0:0.6.2-1.el7_2 will be an update
---> Package epel-release.noarch 0:7-7 will be updated
---> Package epel-release.noarch 0:7-8 will be an update
---> Package glibc.i686 0:2.17-106.el7_2.6 will be updated
--> Processing Dependency: glibc = 2.17-106.el7_2.6 for package: glibc-common-2.17-106.el7_2.6.x86_64
---> Package glibc.i686 0:2.17-106.el7_2.8 will be an update
---> Package kernel.x86_64 0:3.10.0-327.36.3.el7 will be installed
---> Package kpartx.x86_64 0:0.4.9-85.el7_2.5 will be updated
---> Package kpartx.x86_64 0:0.4.9-85.el7_2.6 will be an update
---> Package libarchive.x86_64 0:3.1.2-7.el7 will be updated
---> Package libarchive.x86_64 0:3.1.2-10.el7_2 will be an update
---> Package libtiff.x86_64 0:4.0.3-14.el7 will be updated
---> Package libtiff.x86_64 0:4.0.3-25.el7_2 will be an update
---> Package microcode_ctl.x86_64 2:2.1-12.el7 will be updated
---> Package microcode_ctl.x86_64 2:2.1-12.el7_2.1 will be an update
---> Package open-vm-tools.x86_64 0:9.10.2-4.el7 will be updated
---> Package open-vm-tools.x86_64 0:9.10.2-5.el7_2 will be an update
---> Package php-imap.x86_64 0:5.4.16-4.el7 will be updated
---> Package php-imap.x86_64 0:5.4.16-5.el7 will be an update
---> Package tuned.noarch 0:2.5.1-4.el7_2.3 will be updated
---> Package tuned.noarch 0:2.5.1-4.el7_2.6 will be an update
--> Finished Dependency Resolution
Error: Package: glibc-common-2.17-106.el7_2.6.x86_64 (@updates)
Requires: glibc = 2.17-106.el7_2.6
Removing: glibc-2.17-106.el7_2.6.i686 (@updates)
glibc = 2.17-106.el7_2.6
Updated By: glibc-2.17-106.el7_2.8.i686 (updates)
glibc = 2.17-106.el7_2.8
Available: glibc-2.17-105.el7.i686 (base)
glibc = 2.17-105.el7
Available: glibc-2.17-106.el7_2.1.i686 (updates)
glibc = 2.17-106.el7_2.1
Available: glibc-2.17-106.el7_2.4.i686 (updates)
glibc = 2.17-106.el7_2.4
You could try using --skip-broken to work around the problem
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
glibc-2.17-106.el7_2.8.x86_64 is a duplicate with glibc-2.17-106.el7_2.6.i686
glibc-common-2.17-106.el7_2.8.x86_64 is a duplicate with glibc-common-2.17-106.el7_2.6.x86_64
rpm -qa | grep glibc
glibc-common-2.17-106.el7_2.6.x86_64
glibc-2.17-106.el7_2.6.i686
glibc-2.17-106.el7_2.8.x86_64
glibc-common-2.17-106.el7_2.8.x86_64 -
Accepted Answer
Nick Howitt wrote:
If you have clearos-centos enabled you also need clearos-centos-updates enabled. Please do a:
Then re-run the update. I can't promise this will fix it but it needs to be done anyway.yum-config-manager --enable clearos-centos-updates
I added the updates repo, but it didn't solve the problem. Then I decided to update alphabetically (update a*, update b*, etc) and I just skipped the updates for letter that caused
the dependency error. After I got to Z, I tried to run a normal "yum update" and... lo and behold, now it worked. Strange...
Thanks for the assistance! -
Accepted Answer
If you have clearos-centos enabled you also need clearos-centos-updates enabled. Please do a:
Then re-run the update. I can't promise this will fix it but it needs to be done anyway.yum-config-manager --enable clearos-centos-updates
-
Accepted Answer
Thanks for the quick response....
Here's the output from "yum repolist":
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: ftp.nluug.nl
* clearos-centos: mirror.nsc.liu.se
* clearos-contribs: ftp.nluug.nl
* clearos-epel: mirror.nsc.liu.se
* clearos-fast-updates: download2.clearsdn.com
* clearos-infra: ftp.nluug.nl
* clearos-updates: ftp.nluug.nl
* private-clearcenter-dyndns: download4.clearsdn.com:80
repo id repo name status
clearos/7 ClearOS 7 - x86_64 - OS 718
clearos-centos/7/x86_64 CentOS-7 - Base 8,931+76
clearos-contribs/7 ClearOS 7 - x86_64 - Contribs 72
clearos-epel/7/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 10,073+31
clearos-fast-updates/7/x86_64 ClearOS 7 - x86_64 - Fast Updates 43
clearos-infra/7 ClearOS 7 - x86_64 - Infrastructure 17
clearos-updates/7 ClearOS 7 - x86_64 - Updates 388
private-clearcenter-dyndns ClearCenter Dynamic DNS 2
repolist: 20,244
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »