Fedora Core 1 / up2date glibc-common-2.3.2-101.1 problem

[Alan Wagstaff]

Hi,

We're just doing our first Fedora server here, and have encountered a
problem.  The install and such like went perfectly (except for CD3 being
corrupt, but a re-burn fixed that), but when running up2date, I started
running into problems.

The first, was that despite running "rpm --import
/usr/share/rhn/RPM-GPG-KEY", it kept coming up with a message telling me
to run it.  After a quick newsgroup search, I fixed it by running " rpm
--import /usr/share/rhn/RPM-GPG-KEY-fedora" instead.

Then, during the up2date process, it failed with the following error:

-----
glibc-2.3.2-101.1.i686.rpm: ########################## Done.
glibc-common-2.3.2-101.1.i3  The package glibc-common-2.3.2-101.1 does
not have a valid GPG signature. It has been tampered with or corrupted.
Aborting...

************ GPG VERIFICATION ERROR ****************
The package glibc-common-2.3.2-101.1 failed its gpg signature
verification. This means the package is corrupt.
****************************************************
-----

The error itself is fairly self explanatory, but I'm wondering if it is
genuinely a corrupt package on the Fedora/Redhat up2date servers, or
whether it's related to the rpm --import problem in some way, and if it
is, then how to fix the first problem?

Any ideas?

Many thanks,
Alan.

 --- 
Alan Wagstaff
Server Operations Manager
Dedipower Managed Hosting

Tel: 0870 922 4102
Fax: 0870 137 6116
http://www.dedipower.com

-- The UK's Leading Dedicated Server Provider --


The information in this email is confidential and may be legally privileged. It may not represent the views of Asuk Creative Limited. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (0870 922 4102 or alan.wagstaff at corp.asuk.com) immediately.