[WBEL-users] x64 yum update failing
Eric B.
ebenze at hotmail.com
Tue Mar 21 22:13:50 CST 2006
Okay, I'm updating my own question.
I finally figured out that adding rpm -qi --queryformat %{ARCH} will give
the architecture for the particular package.
Indeed, rpm -qi --queryformat %{ARCH} tells me that one pkg is i686 and the
other pkg is x86_64, as suspected.
So now the question becomes how can I safely remove the i686 pkg without
touching the x86_64 pkg?
Thanks,
Eric
"news.gmane.org" <ebenze at hotmail.com> wrote in message
news:dvqgjv$o80$1 at sea.gmane.org...
> Hi,
>
> I've got an WBEL4 x64 system that I installed a while back but sat
> awaiting deployment. I finally decided to start using it today, so first
> thing I did was a yum update. Unfortunately, yum is crashing on a
> dependency failure.
>
> [root at phoenix /]# yum update glibc
> Setting up Update Process
> Setting up Repos
> Extras 100% |=========================| 951 B 00:00
> updates-released 100% |=========================| 951 B 00:00
> base 100% |=========================| 1.1 kB 00:00
> Reading repository metadata in from local files
> updates-re: ################################################## 1293/1293
> base : ################################################## 2387/2387
> Excluding Packages in global exclude list
> Finished
> Resolving Dependencies
> --> Populating transaction set with selected packages. Please wait.
> ---> Package glibc.x86_64 0:2.3.4-2.13 set to be updated
> --> Running transaction check
> --> Processing Dependency: glibc-common = 2.3.4-2.13 for package: glibc
> --> Restarting Dependency Resolution with new changes.
> --> Populating transaction set with selected packages. Please wait.
> ---> Package glibc-common.x86_64 0:2.3.4-2.13 set to be updated
> --> Running transaction check
> --> Processing Dependency: glibc-common = 2.3.4-2 for package: glibc
> Traceback (most recent call last):
> File "/usr/bin/yum", line 7, in ?
> yummain.main(sys.argv[1:])
> File "/usr/share/yum-cli/yummain.py", line 109, in main
> (result, resultmsgs) = base.buildTransaction()
> File "__init__.py", line 224, in buildTransaction
> File "depsolve.py", line 211, in resolveDeps
> File "depsolve.py", line 338, in _processReq
> File "depsolve.py", line 412, in _requiringFromInstalled
> File "packageSack.py", line 257, in returnNewestByNameArch
> repomd.mdErrors.PackageSackError: No Package Matching glibc.i686
>
>
>
> There is obviously a copy of glibc on the machine - glibc-2.3.4-2 to be
> exact. What I believe is happening is that there might be 2 copies of
> it - one being the i386 copy and on is the x64 copy. Although when I
> check using rpm -qi glibc, it doesn't specify which is i386 and which is
> _x64. I am more than happy to remove the i386 copy, as I believe it is it
> that is causing me these headaches, but not sure how.
>
> Any ideas?
>
> Thanks,
>
> Eric
More information about the Whitebox-users
mailing list