-----Original Message-----
*From:* fedora-list-admin@xxxxxxxxxx [mailto:fedora-list-admin@xxxxxxxxxx]*On Behalf Of *Digant Kasundra
*Sent:* Tuesday, January 13, 2004 10:45 AM
*To:* fedora-list@xxxxxxxxxx
*Subject:* GPG verification errors?
I've been failing to upgrade packages recently due to failed GPG verification. Here is a sample:
"The package glibc-2.3.2-101.4 failed its gpg signature verification. This means the package is corrupt."
Anyone else have this problem using up2date?
Don wrote:
Yes, I get that all the time when the up2date servers are busy.... I press "up-arrow"/enter and try again... eventually it all works...
Hi Digant,
I think the solution mentioned many times on this list is to simply change up2date to retrieve from a different source as the default source location gets over loaded.
Personally I've setup a nightly rsync and then all the FC1 boxes here do their up2date from that. It then seems to be virtualy free of these errors.
As an aside, I would rather that up2date either just waited untill all the data is correctly received or timed out and failed if it can't retrieve the data correctly. This business of retrieving bad data and giving you the option of installing from it (the bad data) makes me uneasy. However I guess there must be good reason for this but it is one of many things I don't (yet) understand.
Kind regards,
Mike
