Red Hat Bugzilla – Bug 120788
up2date fails due to bad GConf2 GPG sig
Last modified: 2007-11-30 17:07:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2)
Description of problem:
Up2date for RHEL3 WS Beta 2 and Extras Beta 2 fails because
the GConf2-2.2.1-4 package is signed with an unknown GPG key.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install a RHEL3 WS 3 update 1 system with GConf2
2.add RHEL3 WS Beta 2 and Extras Beta 2 channels
3.up2date --nox -d -u
Actual Results: The package GConf2-2.2.1-4 is signed, but with an
uknown GPG key. Aborting...
Package GConf2-2.2.1-4 has a unknown GPG signature.
Expected Results: New Beta 2 RPMs would be downloaded.
BTW: Note the typo in the error message:
"... but with an uknown GPG key"
What does 'rpm -vK Gconf-2.2.1-4*.rpm' say?
rpm -vK Gconf-2.2.1-4*.rpm says nothing without a sound driver :-)
rpm -vK GConf2-2.2.1-4.i386.rpm says:
Header V3 DSA signature: NOKEY, key ID 897da07a
Header SHA1 digest: OK
MD5 digest: OK (f7615823d6fbcb1fb6cebf835e6cb225)
V3 DSA signature: NOKEY, key ID 897da07a
You need to import the beta key. To do so, run this command on the machine you wish to
update prior to running up2date:
rpm --import /usr/share/doc/rpm-4.2.2/BETA-GPG-KEY