Updated channel with clone-by-date, now glibc-common fails to install

Latest response

I recently updated our prerelease channel with spacewalk-clone-by-date. Now glibc-common is a requirement for itself? See below.

Error: Package: glibc-2.12-1.166.el6_7.1.x86_64 (jci-rhel-x86_64-server-6-prerelease)
Requires: glibc-common = 2.12-1.166.el6_7.1
Removing: glibc-common-2.12-1.132.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201311111358.x86_64/6.5)
glibc-common = 2.12-1.132.el6
Updated By: glibc-common-2.12-1.149.el6_6.9.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.149.el6_6.9
Available: glibc-common-2.12-1.7.el6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.7.el6
Available: glibc-common-2.12-1.7.el6_0.3.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.7.el6_0.3
Available: glibc-common-2.12-1.7.el6_0.4.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.7.el6_0.4
Available: glibc-common-2.12-1.7.el6_0.5.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.7.el6_0.5
Available: glibc-common-2.12-1.25.el6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.25.el6
Available: glibc-common-2.12-1.25.el6_1.3.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.25.el6_1.3
Available: glibc-common-2.12-1.47.el6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.47.el6
Available: glibc-common-2.12-1.47.el6_2.5.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.47.el6_2.5
Available: glibc-common-2.12-1.47.el6_2.9.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.47.el6_2.9
Available: glibc-common-2.12-1.47.el6_2.12.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.47.el6_2.12
Available: glibc-common-2.12-1.80.el6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.80.el6
Available: glibc-common-2.12-1.80.el6_3.3.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.80.el6_3.3
Available: glibc-common-2.12-1.80.el6_3.4.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.80.el6_3.4
Available: glibc-common-2.12-1.80.el6_3.5.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.80.el6_3.5
Available: glibc-common-2.12-1.80.el6_3.6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.80.el6_3.6
Available: glibc-common-2.12-1.80.el6_3.7.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.80.el6_3.7
Available: glibc-common-2.12-1.107.el6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.107.el6
Available: glibc-common-2.12-1.107.el6_4.2.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.107.el6_4.2
Available: glibc-common-2.12-1.107.el6_4.4.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.107.el6_4.4
Available: glibc-common-2.12-1.107.el6_4.5.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.107.el6_4.5
Available: glibc-common-2.12-1.132.el6_5.1.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.132.el6_5.1
Available: glibc-common-2.12-1.132.el6_5.2.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.132.el6_5.2
Available: glibc-common-2.12-1.132.el6_5.3.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.132.el6_5.3
Available: glibc-common-2.12-1.132.el6_5.4.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.132.el6_5.4
Available: glibc-common-2.12-1.149.el6.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.149.el6
Available: glibc-common-2.12-1.149.el6_6.4.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.149.el6_6.4
Available: glibc-common-2.12-1.149.el6_6.5.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.149.el6_6.5
Available: glibc-common-2.12-1.149.el6_6.7.x86_64 (jci-rhel-x86_64-server-6-prerelease)
glibc-common = 2.12-1.149.el6_6.7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Responses

Not really, According to the output, yum sees a newer version of glibc (2.12-1.166.el6_7.1) but not the same version of glibc-common. And, you can only update glibc if you update glibc-common at the same time.

That's normally not an issue because glibc and glibc-common are supposed to be in the same repo, so when an update is released, you should be able to update both packages. Perhaps the jci-rhel-x86_64-server-6-prerelease repo isn't fully synced.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.