Bug 24963 – autoconf PGP signed; up2date doesn't like

Bug 24963 - autoconf PGP signed; up2date doesn't like

Summary:	autoconf PGP signed; up2date doesn't like

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Adrian Likins
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-01-25 16:10 EST by Alan Shutko
Modified:	2007-04-18 12:30 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-06-20 15:32:42 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Alan Shutko 2001-01-25 16:10:21 EST

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 18:39:39 EST

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-08 22:42:05 EST

*** 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.