Bug 143468 - rpm --import fails
rpm --import fails
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-12-21 04:53 EST by Nigel Horne
Modified: 2014-01-21 17:50 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-19 02:19:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nigel Horne 2004-12-21 04:53:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Firefox/0.10.1

Description of problem:
Running yum update tells you to run rpm --import, but that command
doesn't work so yum fails.

Version-Release number of selected component (if applicable):
yum-2.1.11-3

How reproducible:
Always

Steps to Reproduce:
1. Start kde
2. Start terminal
3. Run yum update
Run advised rpm --import
    

Actual Results:  error: public.gpg.key: import read failed.

Expected Results:  Yum should download patches

Additional info:

[root@njh RPMS]# yum update

You have enabled checking of packages via GPG keys. This is a good thing.
However, you do not have any GPG public keys installed. You need to
download
the keys for packages you wish to install and install them.
You can do that by running the command:
    rpm --import public.gpg.key
For more information contact your distribution or package provider.
[root@njh RPMS]# rpm --import public.gpg.key
error: public.gpg.key: import read failed.
[root@njh RPMS]#
Comment 1 Nigel Horne 2004-12-21 04:59:50 EST
Further investigation shows that the error message should have said:

rpm --import http://www.fedora.us/FEDORA-GPG-KEY

NOT

rpm --import public.gpg.key
Comment 2 Seth Vidal 2005-01-19 02:19:00 EST
Closing this as steps taken in the yum code now provide a better solution than this.

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