Yum doesn't recognize installed dependency versionyum error when installing memcachedDependency Hell trying to install GCC on CentOS4How can I install VLC on RHEL 6.3?Fedora19: YUM glibc is a duplicate of glibcCentOS 5.5 php-posix with dependency error php53-commonYUM Update ErrorCentOS - yum install - Fails: Protected Multilib versions: problems found libselinuxyum dependency resolution not workingyumdownloader doesn't resolve dependency?php error installing imagick

Why are C64 games inconsistent with which joystick port they use?

Full backup on database creation

What is the most important source of natural gas? coal, oil or other?

Is there a down side to setting the sampling time of a SAR ADC as long as possible?

LASSO Regression - p-values and coefficients

How were these pictures of spacecraft wind tunnel testing taken?

Why doesn't the Earth's acceleration towards the Moon accumulate to push the Earth off its orbit?

Is CD audio quality good enough for the final delivery of music?

How can I get exact maximal value of this expression?

Infinite Sequence based on Simple Rule

Identifying an object pointer by generating and using a unique ID

What is the object moving across the ceiling in this stock footage?

How can I find where certain bash function is defined?

Is this resistor leaking? If so, is it a concern?

Where did Wilson state that the US would have to force access to markets with violence?

reinterpret_cast from rvalue to rvalue reference

I think I may have violated academic integrity last year - what should I do?

Can a Beholder use rays in melee range?

How strong are Wi-Fi signals?

What is the difference between nullifying your vote and not going to vote at all?

Looking for a soft substance that doesn't dissolve underwater

Tic-tac-toe for the terminal, written in C

General purpose replacement for enum with FlagsAttribute

Would jet fuel for an F-16 or F-35 be producible during WW2?



Yum doesn't recognize installed dependency version


yum error when installing memcachedDependency Hell trying to install GCC on CentOS4How can I install VLC on RHEL 6.3?Fedora19: YUM glibc is a duplicate of glibcCentOS 5.5 php-posix with dependency error php53-commonYUM Update ErrorCentOS - yum install - Fails: Protected Multilib versions: problems found libselinuxyum dependency resolution not workingyumdownloader doesn't resolve dependency?php error installing imagick






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I'm trying to install gcc-c++ on CentOS 7.6.1810. This is the error output:



Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
(cut)
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7


It seems that yum doesn't recognize glibc-common-2.17-260.el7_6.3.x86_64 as the same as (or equivalent of) glibc-common-2.17-260.el7_6.3.x86_64. What can I do to tell it to honor this installed version, or how can I reinstall it from centos_7_x64_32 (obviously I can't remove glibc-common first).



FULL OUTPUT



Resolving Dependencies
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: gcc = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libstdc++-devel = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpc.so.3()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpfr.so.4()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Running transaction check
---> Package gcc.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: cpp = 4.8.5-36.el7 for package: gcc-4.8.5-36.el7.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-36.el7.x86_64
---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed
---> Package libstdc++-devel.x86_64 0:4.8.5-36.el7 will be installed
---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed
--> Running transaction check
---> Package cpp.x86_64 0:4.8.5-36.el7 will be installed
---> Package glibc-devel.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-headers = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-260.el7.i686
---> Package glibc-headers.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.17-260.el7.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
---> Package kernel-headers.x86_64 0:3.10.0-957.1.3.el7 will be installed
---> Package nss-softokn-freebl.i686 0:3.36.0-5.el7_5 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
Available: glibc-common-2.17-78.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-78.el7
Available: glibc-common-2.17-105.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-105.el7
Available: glibc-common-2.17-106.el7_2.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.1
Available: glibc-common-2.17-106.el7_2.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.4
Available: glibc-common-2.17-106.el7_2.6.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.6
Available: glibc-common-2.17-106.el7_2.8.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.8
Available: glibc-common-2.17-157.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7
Available: glibc-common-2.17-157.el7_3.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.1
Available: glibc-common-2.17-157.el7_3.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.2
Available: glibc-common-2.17-157.el7_3.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.4
Available: glibc-common-2.17-157.el7_3.5.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.5
Available: glibc-common-2.17-196.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7
Available: glibc-common-2.17-196.el7_4.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7_4.2
Available: glibc-common-2.17-222.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-222.el7
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest









share|improve this question
























  • Looks like the private mirror you are using is incomplete. Go have a chat with whoever maintains it.

    – Michael Hampton
    Feb 13 at 17:55











  • @MichaelHampton I had similar problem before with not so important package. The required dependency was installed from @updates with some "_x.y" version suffix and yum didn't like it. I had to uninstall it, and install the same version from centos_7_x64_32, but without the suffix. Then it worked ok. I can't do that with glibc-common.

    – Furgas
    Feb 13 at 18:00











  • Again, you aren't using an official CentOS repository to obtain base packages. You can either yell at whoever maintains your private copy of the repository, or switch back to the official repository (if your company even allows this).

    – Michael Hampton
    Feb 13 at 18:02


















1















I'm trying to install gcc-c++ on CentOS 7.6.1810. This is the error output:



Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
(cut)
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7


It seems that yum doesn't recognize glibc-common-2.17-260.el7_6.3.x86_64 as the same as (or equivalent of) glibc-common-2.17-260.el7_6.3.x86_64. What can I do to tell it to honor this installed version, or how can I reinstall it from centos_7_x64_32 (obviously I can't remove glibc-common first).



FULL OUTPUT



Resolving Dependencies
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: gcc = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libstdc++-devel = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpc.so.3()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpfr.so.4()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Running transaction check
---> Package gcc.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: cpp = 4.8.5-36.el7 for package: gcc-4.8.5-36.el7.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-36.el7.x86_64
---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed
---> Package libstdc++-devel.x86_64 0:4.8.5-36.el7 will be installed
---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed
--> Running transaction check
---> Package cpp.x86_64 0:4.8.5-36.el7 will be installed
---> Package glibc-devel.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-headers = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-260.el7.i686
---> Package glibc-headers.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.17-260.el7.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
---> Package kernel-headers.x86_64 0:3.10.0-957.1.3.el7 will be installed
---> Package nss-softokn-freebl.i686 0:3.36.0-5.el7_5 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
Available: glibc-common-2.17-78.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-78.el7
Available: glibc-common-2.17-105.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-105.el7
Available: glibc-common-2.17-106.el7_2.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.1
Available: glibc-common-2.17-106.el7_2.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.4
Available: glibc-common-2.17-106.el7_2.6.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.6
Available: glibc-common-2.17-106.el7_2.8.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.8
Available: glibc-common-2.17-157.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7
Available: glibc-common-2.17-157.el7_3.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.1
Available: glibc-common-2.17-157.el7_3.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.2
Available: glibc-common-2.17-157.el7_3.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.4
Available: glibc-common-2.17-157.el7_3.5.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.5
Available: glibc-common-2.17-196.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7
Available: glibc-common-2.17-196.el7_4.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7_4.2
Available: glibc-common-2.17-222.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-222.el7
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest









share|improve this question
























  • Looks like the private mirror you are using is incomplete. Go have a chat with whoever maintains it.

    – Michael Hampton
    Feb 13 at 17:55











  • @MichaelHampton I had similar problem before with not so important package. The required dependency was installed from @updates with some "_x.y" version suffix and yum didn't like it. I had to uninstall it, and install the same version from centos_7_x64_32, but without the suffix. Then it worked ok. I can't do that with glibc-common.

    – Furgas
    Feb 13 at 18:00











  • Again, you aren't using an official CentOS repository to obtain base packages. You can either yell at whoever maintains your private copy of the repository, or switch back to the official repository (if your company even allows this).

    – Michael Hampton
    Feb 13 at 18:02














1












1








1








I'm trying to install gcc-c++ on CentOS 7.6.1810. This is the error output:



Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
(cut)
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7


It seems that yum doesn't recognize glibc-common-2.17-260.el7_6.3.x86_64 as the same as (or equivalent of) glibc-common-2.17-260.el7_6.3.x86_64. What can I do to tell it to honor this installed version, or how can I reinstall it from centos_7_x64_32 (obviously I can't remove glibc-common first).



FULL OUTPUT



Resolving Dependencies
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: gcc = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libstdc++-devel = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpc.so.3()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpfr.so.4()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Running transaction check
---> Package gcc.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: cpp = 4.8.5-36.el7 for package: gcc-4.8.5-36.el7.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-36.el7.x86_64
---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed
---> Package libstdc++-devel.x86_64 0:4.8.5-36.el7 will be installed
---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed
--> Running transaction check
---> Package cpp.x86_64 0:4.8.5-36.el7 will be installed
---> Package glibc-devel.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-headers = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-260.el7.i686
---> Package glibc-headers.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.17-260.el7.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
---> Package kernel-headers.x86_64 0:3.10.0-957.1.3.el7 will be installed
---> Package nss-softokn-freebl.i686 0:3.36.0-5.el7_5 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
Available: glibc-common-2.17-78.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-78.el7
Available: glibc-common-2.17-105.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-105.el7
Available: glibc-common-2.17-106.el7_2.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.1
Available: glibc-common-2.17-106.el7_2.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.4
Available: glibc-common-2.17-106.el7_2.6.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.6
Available: glibc-common-2.17-106.el7_2.8.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.8
Available: glibc-common-2.17-157.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7
Available: glibc-common-2.17-157.el7_3.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.1
Available: glibc-common-2.17-157.el7_3.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.2
Available: glibc-common-2.17-157.el7_3.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.4
Available: glibc-common-2.17-157.el7_3.5.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.5
Available: glibc-common-2.17-196.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7
Available: glibc-common-2.17-196.el7_4.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7_4.2
Available: glibc-common-2.17-222.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-222.el7
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest









share|improve this question
















I'm trying to install gcc-c++ on CentOS 7.6.1810. This is the error output:



Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
(cut)
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7


It seems that yum doesn't recognize glibc-common-2.17-260.el7_6.3.x86_64 as the same as (or equivalent of) glibc-common-2.17-260.el7_6.3.x86_64. What can I do to tell it to honor this installed version, or how can I reinstall it from centos_7_x64_32 (obviously I can't remove glibc-common first).



FULL OUTPUT



Resolving Dependencies
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: gcc = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libstdc++-devel = 4.8.5-36.el7 for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpc.so.3()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Processing Dependency: libmpfr.so.4()(64bit) for package: gcc-c++-4.8.5-36.el7.x86_64
--> Running transaction check
---> Package gcc.x86_64 0:4.8.5-36.el7 will be installed
--> Processing Dependency: cpp = 4.8.5-36.el7 for package: gcc-4.8.5-36.el7.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-36.el7.x86_64
---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed
---> Package libstdc++-devel.x86_64 0:4.8.5-36.el7 will be installed
---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed
--> Running transaction check
---> Package cpp.x86_64 0:4.8.5-36.el7 will be installed
---> Package glibc-devel.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-headers = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc = 2.17-260.el7 for package: glibc-devel-2.17-260.el7.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-260.el7.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-260.el7.i686
---> Package glibc-headers.x86_64 0:2.17-260.el7 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.17-260.el7.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.17-260.el7.x86_64
--> Running transaction check
---> Package glibc.i686 0:2.17-260.el7 will be installed
--> Processing Dependency: glibc-common = 2.17-260.el7 for package: glibc-2.17-260.el7.i686
---> Package kernel-headers.x86_64 0:3.10.0-957.1.3.el7 will be installed
---> Package nss-softokn-freebl.i686 0:3.36.0-5.el7_5 will be installed
--> Finished Dependency Resolution
Error: Package: glibc-2.17-260.el7.i686 (centos_7_x64_32)
Requires: glibc-common = 2.17-260.el7
Installed: glibc-common-2.17-260.el7_6.3.x86_64 (@updates)
glibc-common = 2.17-260.el7_6.3
Available: glibc-common-2.17-78.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-78.el7
Available: glibc-common-2.17-105.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-105.el7
Available: glibc-common-2.17-106.el7_2.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.1
Available: glibc-common-2.17-106.el7_2.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.4
Available: glibc-common-2.17-106.el7_2.6.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.6
Available: glibc-common-2.17-106.el7_2.8.x86_64 (centos_7_x64_32)
glibc-common = 2.17-106.el7_2.8
Available: glibc-common-2.17-157.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7
Available: glibc-common-2.17-157.el7_3.1.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.1
Available: glibc-common-2.17-157.el7_3.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.2
Available: glibc-common-2.17-157.el7_3.4.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.4
Available: glibc-common-2.17-157.el7_3.5.x86_64 (centos_7_x64_32)
glibc-common = 2.17-157.el7_3.5
Available: glibc-common-2.17-196.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7
Available: glibc-common-2.17-196.el7_4.2.x86_64 (centos_7_x64_32)
glibc-common = 2.17-196.el7_4.2
Available: glibc-common-2.17-222.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-222.el7
Available: glibc-common-2.17-260.el7.x86_64 (centos_7_x64_32)
glibc-common = 2.17-260.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest






centos centos7 yum






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 13 at 18:10







Furgas

















asked Feb 13 at 12:46









FurgasFurgas

1063




1063












  • Looks like the private mirror you are using is incomplete. Go have a chat with whoever maintains it.

    – Michael Hampton
    Feb 13 at 17:55











  • @MichaelHampton I had similar problem before with not so important package. The required dependency was installed from @updates with some "_x.y" version suffix and yum didn't like it. I had to uninstall it, and install the same version from centos_7_x64_32, but without the suffix. Then it worked ok. I can't do that with glibc-common.

    – Furgas
    Feb 13 at 18:00











  • Again, you aren't using an official CentOS repository to obtain base packages. You can either yell at whoever maintains your private copy of the repository, or switch back to the official repository (if your company even allows this).

    – Michael Hampton
    Feb 13 at 18:02


















  • Looks like the private mirror you are using is incomplete. Go have a chat with whoever maintains it.

    – Michael Hampton
    Feb 13 at 17:55











  • @MichaelHampton I had similar problem before with not so important package. The required dependency was installed from @updates with some "_x.y" version suffix and yum didn't like it. I had to uninstall it, and install the same version from centos_7_x64_32, but without the suffix. Then it worked ok. I can't do that with glibc-common.

    – Furgas
    Feb 13 at 18:00











  • Again, you aren't using an official CentOS repository to obtain base packages. You can either yell at whoever maintains your private copy of the repository, or switch back to the official repository (if your company even allows this).

    – Michael Hampton
    Feb 13 at 18:02

















Looks like the private mirror you are using is incomplete. Go have a chat with whoever maintains it.

– Michael Hampton
Feb 13 at 17:55





Looks like the private mirror you are using is incomplete. Go have a chat with whoever maintains it.

– Michael Hampton
Feb 13 at 17:55













@MichaelHampton I had similar problem before with not so important package. The required dependency was installed from @updates with some "_x.y" version suffix and yum didn't like it. I had to uninstall it, and install the same version from centos_7_x64_32, but without the suffix. Then it worked ok. I can't do that with glibc-common.

– Furgas
Feb 13 at 18:00





@MichaelHampton I had similar problem before with not so important package. The required dependency was installed from @updates with some "_x.y" version suffix and yum didn't like it. I had to uninstall it, and install the same version from centos_7_x64_32, but without the suffix. Then it worked ok. I can't do that with glibc-common.

– Furgas
Feb 13 at 18:00













Again, you aren't using an official CentOS repository to obtain base packages. You can either yell at whoever maintains your private copy of the repository, or switch back to the official repository (if your company even allows this).

– Michael Hampton
Feb 13 at 18:02






Again, you aren't using an official CentOS repository to obtain base packages. You can either yell at whoever maintains your private copy of the repository, or switch back to the official repository (if your company even allows this).

– Michael Hampton
Feb 13 at 18:02











2 Answers
2






active

oldest

votes


















2















Error: Package: glibc-2.17-260.el7.i686
(My emphasis)




you are trying to install the i686 variant not the x86_64 variant. You need to meet the i686 requirements or install the x86_64 package.






share|improve this answer























  • yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

    – Furgas
    Feb 13 at 13:13






  • 1





    Because you installed it I guess.

    – Iain
    Feb 13 at 14:23











  • @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

    – Furgas
    Feb 13 at 18:01











  • Like you, I have no idea how your system got to be in such a state.

    – Iain
    Feb 13 at 22:05


















-1














Somehow, you do not have the "updates" repo available. You either disabled it or you are using a private repo/mirror that does not has it.






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f953721%2fyum-doesnt-recognize-installed-dependency-version%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2















    Error: Package: glibc-2.17-260.el7.i686
    (My emphasis)




    you are trying to install the i686 variant not the x86_64 variant. You need to meet the i686 requirements or install the x86_64 package.






    share|improve this answer























    • yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

      – Furgas
      Feb 13 at 13:13






    • 1





      Because you installed it I guess.

      – Iain
      Feb 13 at 14:23











    • @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

      – Furgas
      Feb 13 at 18:01











    • Like you, I have no idea how your system got to be in such a state.

      – Iain
      Feb 13 at 22:05















    2















    Error: Package: glibc-2.17-260.el7.i686
    (My emphasis)




    you are trying to install the i686 variant not the x86_64 variant. You need to meet the i686 requirements or install the x86_64 package.






    share|improve this answer























    • yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

      – Furgas
      Feb 13 at 13:13






    • 1





      Because you installed it I guess.

      – Iain
      Feb 13 at 14:23











    • @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

      – Furgas
      Feb 13 at 18:01











    • Like you, I have no idea how your system got to be in such a state.

      – Iain
      Feb 13 at 22:05













    2












    2








    2








    Error: Package: glibc-2.17-260.el7.i686
    (My emphasis)




    you are trying to install the i686 variant not the x86_64 variant. You need to meet the i686 requirements or install the x86_64 package.






    share|improve this answer














    Error: Package: glibc-2.17-260.el7.i686
    (My emphasis)




    you are trying to install the i686 variant not the x86_64 variant. You need to meet the i686 requirements or install the x86_64 package.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 13 at 13:01









    IainIain

    106k14166259




    106k14166259












    • yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

      – Furgas
      Feb 13 at 13:13






    • 1





      Because you installed it I guess.

      – Iain
      Feb 13 at 14:23











    • @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

      – Furgas
      Feb 13 at 18:01











    • Like you, I have no idea how your system got to be in such a state.

      – Iain
      Feb 13 at 22:05

















    • yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

      – Furgas
      Feb 13 at 13:13






    • 1





      Because you installed it I guess.

      – Iain
      Feb 13 at 14:23











    • @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

      – Furgas
      Feb 13 at 18:01











    • Like you, I have no idea how your system got to be in such a state.

      – Iain
      Feb 13 at 22:05
















    yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

    – Furgas
    Feb 13 at 13:13





    yum install gcc-c++.x86_64 renders the same error and glibc-2.17-260.el7.x86_64 is already installed. Why does it want to install i686 variant?

    – Furgas
    Feb 13 at 13:13




    1




    1





    Because you installed it I guess.

    – Iain
    Feb 13 at 14:23





    Because you installed it I guess.

    – Iain
    Feb 13 at 14:23













    @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

    – Furgas
    Feb 13 at 18:01





    @lain I won't pretend that I understand you. What did I install? God, I hate CentOS;)

    – Furgas
    Feb 13 at 18:01













    Like you, I have no idea how your system got to be in such a state.

    – Iain
    Feb 13 at 22:05





    Like you, I have no idea how your system got to be in such a state.

    – Iain
    Feb 13 at 22:05













    -1














    Somehow, you do not have the "updates" repo available. You either disabled it or you are using a private repo/mirror that does not has it.






    share|improve this answer



























      -1














      Somehow, you do not have the "updates" repo available. You either disabled it or you are using a private repo/mirror that does not has it.






      share|improve this answer

























        -1












        -1








        -1







        Somehow, you do not have the "updates" repo available. You either disabled it or you are using a private repo/mirror that does not has it.






        share|improve this answer













        Somehow, you do not have the "updates" repo available. You either disabled it or you are using a private repo/mirror that does not has it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 14 at 15:14









        sigusrosigusro

        1




        1



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f953721%2fyum-doesnt-recognize-installed-dependency-version%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

            Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

            What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company