yum Install oracle-validated fails dependency on glibc
I am trying to install the oracle-validated rpm on a new Oracle Enterprise Linux 5.5 install. I have configured the public-yum.oracle.com repository. Durng dependency checks i get the follwoing output.
I try to manually install the dependency on glibc and end up stuck at this message....
Please help I am stuck. I have tried updating kernel headers and clearing the yum cache but no success.
Aaran
--> Finished Dependency Resolution
glibc-headers-2.5-49.x86_64 from el5_u5_base has depsolving problems
--> Missing Dependency: glibc = 2.5-49 is needed by package glibc-headers-2.5-49.x86_64 (el5_u5_base)
glibc-devel-2.5-49.x86_64 from el5_u5_base has depsolving problems
--> Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.x86_64 (el5_u5_base)
glibc-devel-2.5-49.i386 from el5_u5_base has depsolving problems
--> Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.i386 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-headers-2.5-49.x86_64 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.i386 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.x86_64 (el5_u5_base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
I try to manually install the dependency on glibc and end up stuck at this message....
[root@dac-pasdb01 Server]# yum install glibc
Loaded plugins: security
Setting up Install Process
Package matching glibc-2.5-49.x86_64 already installed. Checking for update.
Package matching glibc-2.5-49.i686 already installed. Checking for update.
Nothing to do
[root@dac-pasdb01 Server]#
Please help I am stuck. I have tried updating kernel headers and clearing the yum cache but no success.
Aaran
Have you tried removing the RHEL glibc then trying your install again, thus using the Oracle build instead?
could you run rpm -qa | grep glibc?
What is the output?
try yum install glibc-headers-2.5-49 glibc-devel-2.5-49
What is the output?
try yum install glibc-headers-2.5-49 glibc-devel-2.5-49
Here is architecture conflict. You do have both versions of 32-bit and 64-bit libraries installed.
I guess that your machine is x86_64, but oracle RPM is for i386 and there is a compatibility problem.
You should try to install 64bit Oracle rpm.
Regards,
Arty
I guess that your machine is x86_64, but oracle RPM is for i386 and there is a compatibility problem.
You should try to install 64bit Oracle rpm.
Regards,
Arty
I tried arnold suggestion....
yum install glibc-headers-2.5-49 glibc-devel-2.5-49
and get the output i(n snippet 708628)
I am on a 64 bit architecture on VMware vSphere 4
the grep -qa | grep glibc didnt give me much detail i(n snippet 708628)
I tried a similar command in yum i(n snippet 708628)
If i try and uninstall the i686 version yum and rpm both compain that it is being used by 154 other packages. Can I just tell it to ignor this and not break the box?
Thanks for your help everyone.
yum install glibc-headers-2.5-49 glibc-devel-2.5-49
and get the output i(n snippet 708628)
I am on a 64 bit architecture on VMware vSphere 4
the grep -qa | grep glibc didnt give me much detail i(n snippet 708628)
I tried a similar command in yum i(n snippet 708628)
If i try and uninstall the i686 version yum and rpm both compain that it is being used by 154 other packages. Can I just tell it to ignor this and not break the box?
Thanks for your help everyone.
[root@dac-pasdb01 ~]# yum install glibc-headers-2.5-49 glibc-devel-2.5-49
Loaded plugins: security
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package glibc-devel.i386 0:2.5-49 set to be updated
--> Processing Dependency: glibc = 2.5-49 for package: glibc-devel
---> Package glibc-devel.x86_64 0:2.5-49 set to be updated
--> Processing Dependency: glibc = 2.5-49 for package: glibc-devel
---> Package glibc-headers.x86_64 0:2.5-49 set to be updated
--> Processing Dependency: glibc = 2.5-49 for package: glibc-headers
--> Finished Dependency Resolution
glibc-devel-2.5-49.i386 from el5_u5_base has depsolving problems
--> Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.i386 (el5_u5_base)
glibc-headers-2.5-49.x86_64 from el5_u5_base has depsolving problems
--> Missing Dependency: glibc = 2.5-49 is needed by package glibc-headers-2.5-49.x86_64 (el5_u5_base)
glibc-devel-2.5-49.x86_64 from el5_u5_base has depsolving problems
--> Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.x86_64 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-headers-2.5-49.x86_64 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.i386 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.x86_64 (el5_u5_base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
[root@dac-pasdb01 ~]# rpm -qa | grep glibc
glibc-common-2.5-49.el5_5.2
glibc-2.5-49.el5_5.2
glibc-2.5-49.el5_5.2
[root@dac-pasdb01 ~]# yum list | grep glibc
glibc.i686 2.5-49.el5_5.2 installed
glibc.x86_64 2.5-49.el5_5.2 installed
glibc-common.x86_64 2.5-49.el5_5.2 installed
compat-glibc.i386 1:2.3.4-2.26 el5_ga_base
compat-glibc.x86_64 1:2.3.4-2.26 el5_ga_base
compat-glibc-headers.x86_64 1:2.3.4-2.26 el5_ga_base
glibc-devel.i386 2.5-49 el5_u5_base
glibc-devel.x86_64 2.5-49 el5_u5_base
glibc-headers.x86_64 2.5-49 el5_u5_base
glibc-utils.x86_64 2.5-49 el5_u5_base
[root@dac-pasdb01 ~]#
remove all 32bit devel packages
grep rpm -qa for i386 and devel
after that your build will not break anymore
PS oracle does proper build environment diagnostics. In current state you can only create broken build i.e oracle compalining about missing linktime dependencies.
grep rpm -qa for i386 and devel
after that your build will not break anymore
PS oracle does proper build environment diagnostics. In current state you can only create broken build i.e oracle compalining about missing linktime dependencies.
i only had one devel package installed which I have now removed...
this has had no effect on the problem. Can I remove the i686 glibc without removing all the other packages it thinks are using it?
this has had no effect on the problem. Can I remove the i686 glibc without removing all the other packages it thinks are using it?
[root@dac-pasdb01 ~]# yum remove selinux-policy-devel-2.4.6-279.el5
Loaded plugins: security
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package selinux-policy-devel.noarch 0:2.4.6-279.el5 set to be erased
--> Processing Dependency: selinux-policy-devel for package: policycoreutils-gui
--> Running transaction check
---> Package policycoreutils-gui.x86_64 0:1.33.12-14.8.el5 set to be erased
--> Finished Dependency Resolution
Dependencies Resolved
=================================================================================================
Package Arch Version Repository Size
=================================================================================================
Removing:
selinux-policy-devel noarch 2.4.6-279.el5 installed 4.1 M
Removing for dependencies:
policycoreutils-gui x86_64 1.33.12-14.8.el5 installed 496 k
Transaction Summary
=================================================================================================
Remove 2 Package(s)
Reinstall 0 Package(s)
Downgrade 0 Package(s)
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : policycoreutils-gui 1/2
Erasing : selinux-policy-devel 2/2
Removed:
selinux-policy-devel.noarch 0:2.4.6-279.el5
Dependency Removed:
policycoreutils-gui.x86_64 0:1.33.12-14.8.el5
Complete!
No, you should not remove any x86_64 packages as that will break your box.
The error gives you options to try to correct this issue i.e.using the --skip-broken
or running
"You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
"
The install log file if any will likely reveal what it was checking.
The error gives you options to try to correct this issue i.e.using the --skip-broken
or running
"You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
"
The install log file if any will likely reveal what it was checking.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial