Bug 24963 - autoconf PGP signed; up2date doesn't like
Summary: autoconf PGP signed; up2date doesn't like
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 6.2
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-25 21:10 UTC by Alan Shutko
Modified: 2007-04-18 16:30 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-06-20 19:32:42 UTC
Embargoed:

Attachments (Terms of Use)

Description Alan Shutko 2001-01-25 21:10:21 UTC 
up2date -a libtool reported

autoconf-2.13-5.noarch.rpm...
The package autoconf-2.13-5 is not signed with a GPG signature.  Aborting...

RPM says

[15:17:29] hubert:/hubert/home/ats $ rpm --checksig autoconf-2.13-5.noarch.rpm
exec failed!
Could not run pgp.  Use --nopgp to skip PGP checks.

Looks like it has a pgp but not a gpg signature, and up2date will complain
without a GPG sig.
Comment 1 Jakub Jelinek 2001-01-27 23:39:39 UTC 
autoconf simply has not changed between 6.0 and 6.2 nor any updates
for it have been issued, and 6.0 had pgp signed packages, so this
really is not an autoconf bug.
Perhaps up2date should not complain about this in the 6.2 version
(in 7.0 and above all packages should have gpg signatures so only
the 6.2 version could be changed).
Reassigning to up2date.
Comment 2 Preston Brown 2001-02-09 03:42:05 UTC 
*** Bug 25185 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.