Bug 122307 - up2date complains about gpg signature after grabbing any package
Summary: up2date complains about gpg signature after grabbing any package
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: up2date
Version: rawhide
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-02 23:58 UTC by Alex Markley
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-05-07 17:59:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alex Markley 2004-05-02 23:58:14 UTC
Description of problem: Up2date complains about not recognizing the
GPG signature of any updated fedora package it downloads.

Version-Release number of selected component (if applicable): Red Hat
Update Agent 4.3.17

How reproducible: Always

Steps to Reproduce:
1.Start up2date
2.Begin package update
3.Up2date complains about GPG signature.
  
Actual results: Updates can not be fully automated, since it is
nessicary to confirm each and every package.

Expected results: Updates should run smoothly out of the box.

Additional info: None

Comment 1 Bill Roman 2004-05-06 22:02:42 UTC
This appears to be a duplicate of bug 119957.

rpm --import /usr/share/doc/fedora-release*/RPM-GPG-KEY*


Comment 2 Adrian Likins 2004-05-07 17:59:25 UTC
The fedora key needs to be imported, fedora versions
should be doing this automatically in gui mode
(or warning in commandline mode). 

However, for versions that are in rawhide, they
import the rawhide key, not the fedora key by default.

Official fedora versions should import the proper
key by default, avoiding this problem.


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