Red Hat Bugzilla – Bug 86457
no valid GPG signature on glibc-debug-static-2.3.2-4.80.i386.rpm
Last modified: 2007-04-18 12:52:17 EDT
Description of problem: Update package glibc-debug-static-2.3.2-4.80.i386.rpm is lacking a valid GPG signature. (Sorry if this should have been reported via a different product or component.) Up2date has downloaded several other packages without issue, but this one came up with an alert. Version-Release number of selected component (if applicable): glibc-debug-static-2.3.2-4.80.i386.rpm How reproducible: 100% of the one time I tried. Steps to Reproduce: 1. Start with a system updated on ~3/15. 2. Run up2date; select all packages. 3. Download the packages. Actual results: A "Question" box comes up: The package glibc-debug-static-2.3.2-4.80 does not have a valid GPG signature. It has been tampered with or corrupted. Continue? Expected results: The package should have a valid signature, like the other packages in the same group. Additional info:
Oops! I should have looked at the error message sent to stdout/stderr. There had been a transient SSL error. Perhaps this should be shifted to up2date so that if there is an error in downloading it says so (or retries) rather than reporting a GPG signature problem.