Red Hat Bugzilla – Bug 160988
yum default config on FC4 fails because packages signed with RH key
Last modified: 2014-01-21 17:52:04 EST
I did a small basic FC4 install using anaconda, then started adding the stuff I
needed using yum. In a few cases, the installs would fail because of errors like:
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID db42a60e
public key not available for sgml-common-0.6.3-17.noarch.rpm
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
The GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora (0x4F2A6FD2)
is already installed but is not the correct key for this package.
Check that this is the correct key for the "Fedora Core 4 - i386 - Base" repository.
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY
fixes the problem for the couple of packages I saw this on
The issue is that packages in Fedora Core are signed with (at least) two
different keys. Most are signed with /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora but
some are instead signed with /etc/pki/rpm-gpg/RPM-GPG-KEY
should be added to either /etc/yum.conf or /etc/yum.repos.d/fedora.repo to go
along with the
that's already there
Refiling under general distro b/c the distro shouldn't be signed with two keys.
Closing as NEXTRELEASE; we'll take better care of this with FC5, but there's not
much that can be done for FC4 at this point.
*** Bug 169407 has been marked as a duplicate of this bug. ***
In response to comment #2: a lot can be done for FC4 at this point. All that's
needed is an updated fedora-release RPM with a fedora.repo containing the extra
gpgkey= file. This will save a lot of people the hassle of finding out the 'rpm
--import /etc/pki/rpm-gpg/RPM-GPG-KEY' workaround by them selves. And a lot of
duplicate bugreports as well....
*** Bug 174750 has been marked as a duplicate of this bug. ***
*** Bug 174752 has been marked as a duplicate of this bug. ***
*** Bug 174757 has been marked as a duplicate of this bug. ***
*** Bug 174751 has been marked as a duplicate of this bug. ***
*** Bug 174754 has been marked as a duplicate of this bug. ***
*** Bug 174755 has been marked as a duplicate of this bug. ***