Bug 462979 - Need more informative error message for --import failures
Summary: Need more informative error message for --import failures
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 10
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 461154 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-19 22:55 UTC by Horst H. von Brand
Modified: 2009-12-18 06:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 06:24:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Horst H. von Brand 2008-09-19 22:55:27 UTC
Description of problem:
After the last intrusion mess, I tried to import the new keys, and that failed.

Version-Release number of selected component (if applicable):
rpm-4.5.90-0.git8461.7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora*
2. rpm -qa "
3.
  
Actual results:
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import failed.
(lots of lines, one for each key file)

"rpm -qa rpm-gpg-pubkey*" returns nothing

Expected results:
Import keys, list existing keys.

Additional info:

Comment 1 Panu Matilainen 2008-09-20 08:48:34 UTC
"rpm -qa rpm-gpg-pubkey*" is not going to return anything for sure, try "rpm -q gpg-pubkey" instead.

Most of the files in /etc/pki/rpm-gpg/ are just symlinks to the same main key, and rpm these days refuses to import duplicate keys, that's where all the errors come from. The only bug here is that the error message fails to give any clue *why* the import failed (in this case, "key already imported" basically).

Leaving this open as a reminder to fix the error message, but lowering priority as the keys get imported just fine.

Comment 2 Bug Zapper 2008-11-26 03:09:03 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Panu Matilainen 2009-02-05 12:20:18 UTC
*** Bug 461154 has been marked as a duplicate of this bug. ***

Comment 4 Bug Zapper 2009-11-18 12:38:44 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-12-18 06:24:45 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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