Bug 113460 - up2date gives GPG signature error for corrupt downloads
Summary: up2date gives GPG signature error for corrupt downloads
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: php
Version: 1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Joe Orton
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-14 04:55 UTC by Bob Cochran
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-01-15 08:17:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bob Cochran 2004-01-14 04:55:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
Gecko/20031007 Firebird/0.7

Description of problem:
Running 'up2date -u' to install this version yeilds the following
up2date error message:

"The package php-4.3.4-1.1 is not signed with a GPG signature.
Aborting...".

Version-Release number of selected component (if applicable):
4.3.4-1.1

How reproducible:
Always

Steps to Reproduce:
1. run up2date -u
2. 
3.
    

Actual Results:  php-4.3.4-1.1 and related packages refuse to install
due to the missing gpg signature.

Expected Results:  php packages, along with httpd and mod_ssl updates
should install normally. 

Additional info:

Comment 1 Joe Orton 2004-01-14 07:03:25 UTC
You can get GPG errors from a corrupt download, have you tried
deleting the RPMs out of /var/spool/up2date and downloading them again?

Comment 2 Bob Cochran 2004-01-15 05:59:14 UTC
I just did this and that fixed the problem. I apologize for not 
trying this before filing the bug, it did not occur to me. 

I think the error message in up2date should be changed to reflect 
your advice or better yet, up2date should delete and attempt to re-
download packages getting the 'gpg signature' error before reporting 
it as such to the user. Perhaps with some approach that makes sense. 

Comment 3 Joe Orton 2004-01-15 08:17:18 UTC
No problem. It looks like there are a few bugs filed against up2date
for that issue already, e.g. bug 111601.


Note You need to log in before you can comment on or make changes to this bug.