Description of problem:
Public key for elfutils-libelf-0.129-1.fc7.i386.rpm is not installed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
no idea why this went to me, I don't own elfutils...
though honestly doubt if it's even an elfutils (packaging) bug. Over to you
anyway, Roland :)
This lacks all necessary details about the problem. But whatever it is, it
cannot be a problem inside the rpm itself. Signatures are part of the
I have the same problem on 20+ F7 machines. The output of yum is:
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 30c9ecf8
Error: Public key for elfutils-libelf-0.129-1.fc7.i386.rpm is not installed
which of course stops the update.
The problem occurs on both i386 and x86_64.
It seems that this eltutils is signed with testing key.
This bug is a duplicate of bug #262821.
*** Bug 262821 has been marked as a duplicate of this bug. ***
I'm getting same error.
*** Bug 263781 has been marked as a duplicate of this bug. ***
Perhaps someone else has already suggested it, but it seems that the
signing process really ought to include a quick "sanity-check" or
"repo lint" sort of script/tool that catches errors like this before
they get mirrored and hit by so many users.
Is there a planned feature or could we please open an RFE for some sort
of "repo lint" tool?
[And yes, a number of my machines also ran into this problem.]
*** Bug 264201 has been marked as a duplicate of this bug. ***
The just finished update push should solve this issue.
As to a repo lint, the repo production tool is supposed to only allow packages
signed with the given signature into the repo. There may have been a
configuration foul up that I'm investigating. Ongoing work into repo sanity is
being discussed and tracked in bodhi's Trac instance,
Please confirm that with an updated mirror or the Fedora master mirror that the
correctly signed packages are in place.
The updates installed successfully when I ran: yum clean all && yum -y update
*** Bug 265741 has been marked as a duplicate of this bug. ***
*** Bug 265981 has been marked as a duplicate of this bug. ***
*** Bug 266161 has been marked as a duplicate of this bug. ***
*** Bug 264361 has been marked as a duplicate of this bug. ***