Bug 86457

Summary: no valid GPG signature on glibc-debug-static-2.3.2-4.80.i386.rpm
Product: [Retired] Red Hat Linux Reporter: Robert M. Riches Jr. <rm.riches>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED NOTABUG QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-20 20:22:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Robert M. Riches Jr. 2003-03-22 19:49:47 UTC
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):

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:

Comment 1 Robert M. Riches Jr. 2003-03-22 20:13:48 UTC
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.