Oh here's some more output...
yum update glibc* && yum update Loading "fastestmirror" plugin Loading "priorities" plugin Loading mirror speeds from cached hostfile * kde-all: apt.uk.kde-redhat.org * kde-testing-all: apt.uk.kde-redhat.org * kde: apt.uk.kde-redhat.org * kde-testing: apt.uk.kde-redhat.org * extras: ftp.funet.fi * base: ftp.funet.fi * updates: ftp.klid.dk * addons: ftp.funet.fi * adobe-linux-i386: linuxdownload.adobe.com Excluding Packages from CentOS-5 - Base Finished Excluding Packages from CentOS-5 - Updates Finished 0 packages excluded due to repository priority protections Setting up Update Process Could not find update match for glibc* No Packages marked for Update Loading "fastestmirror" plugin Loading "priorities" plugin Loading mirror speeds from cached hostfile
Jarmo
On Sun, 2009-04-05 at 13:04 +0200, jarmo wrote:
Oh here's some more output...
yum update glibc* && yum update
When I did my update I just did
yum update glibc # No *
and all worked well. An rpm -q --last shows
glibc-common-2.5-34 Wed 01 Apr 2009 04:16:25 PM EDT
along with a bunch of other stuff.
If you do
yum list available glibc* yum list glibc*
does it show available and/or installed? I ask because the common was apparently available on the mirror my system used and installed with no problems. So I wonder if the mirror your system selects has a problem or something on your system is causing the problem.
<snip>
Jarmo
<snip sig stuff>
HTH
On Sun, Apr 5, 2009 at 6:04 AM, jarmo oh1mrr@nic.fi wrote:
Oh here's some more output... yum update glibc* && yum update Loading "fastestmirror" plugin Loading "priorities" plugin Loading mirror speeds from cached hostfile * kde-all: apt.uk.kde-redhat.org * kde-testing-all: apt.uk.kde-redhat.org * kde: apt.uk.kde-redhat.org * kde-testing: apt.uk.kde-redhat.org * extras: ftp.funet.fi * base: ftp.funet.fi * updates: ftp.klid.dk * addons: ftp.funet.fi * adobe-linux-i386: linuxdownload.adobe.com Excluding Packages from CentOS-5 - Base Finished Excluding Packages from CentOS-5 - Updates Finished 0 packages excluded due to repository priority protections
Jarmo: I don't think you have priorities configured properly. Looks like it is not working. The number of protected packages should be more than "0". Be sure priorities is working properly, so the box doesn't get screwed up. Lanny
-
jarmo -
Lanny Marcus -
William L. Maltby