Red Hat Bugzilla – Bug 112695
i get a nokey 4f2a6fd2 message when updating packages using rpm
Last modified: 2014-03-16 22:41:10 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; WMM; .NET CLR 1.1.4322) Description of problem: When i install a updated package i get the message: No Key 4f2a6fd2. I looked in the custumation guide (chapter 32.3) and tryed: rpm --import /usr/share/rhn/RPM-GPG-KEY this went okee. i did a rpm -qa gpg-pubkey* and i get a output like gpg-pubkey-db42a60e-37ea5438 I don't think this is correct. When i tryed a new installation of a package i did get again the message NoKEY ...... I think the key wasnot the correct key. Where can i find the correctkey and where have i to place it. Version-Release number of selected component (if applicable): version dillevered with fedora core 1 How reproducible: Always Steps to Reproduce: 1.rpm -Uvh *.rpm 2. 3. Actual Results: Nokey ..... Expected Results: No nokey message but just an installation. Additional info:
The key is probably (just a guess) one of the keys used by Fedora for signing. I don't know where or how Fedora is choosing to release their keys. Try http://fedora.redhat.com.
Correct, they're also in /usr/share/rhn/RPM-GPG-KEY-fedora*
Just a note, I just did a fresh install of FC3 and then tried to add some RPM's off the DVD later and ran into this NOKEY for 4f2a6fd2 -- on a fresh install! rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora fixed the problem, but users shouldn't have to do this on a fresh install. Why doesn't anacondea import the keys properly?