[rhn-users] unknown GPG signature for bonobo-activation

[Bret McMillan]

On Fri, Jan 14, 2005 at 07:36:16PM +0200, Alex Lyashkov wrote:
> I have same error. i try to update few minutes ago.
> 
> > 1)  what's the md5sum on the package post download?
> 50ae7765ba89de98ebebb52b6d77806b  bonobo-activation-2.2.2-1.1E.i386.rpm
> > 2)  what OS are you running?
> # cat /etc/issue
> Red Hat Enterprise Linux AS release 3 (Taroon Update 4)
> 
> > 3)  what versions of up2date + rpm are you running?
> # rpm -qa | grep up2date
> up2date-4.2.57-2
> up2date-gnome-4.2.57-2
> # rpm -qa | grep rpm
> rpm-4.2.3-13
> redhat-java-rpm-scripts-1.0.2-2
> rpm-libs-4.2.3-13
> rpm-python-4.2.3-13
> redhat-rpm-config-8.0.28-2
> rpm-devel-4.2.3-13
> rpmdb-redhat-3-0.20041216
> rpm-build-4.2.3-13
> 
> > 5)  what key does the package appear to be signed with?
> >     (rpm --checksig -v <filename>.rpm)
> >  LANG=en; rpm --checksig -v bonobo-activation-2.2.2-1.1E.i386.rpm
> bonobo-activation-2.2.2-1.1E.i386.rpm:
>     Header V3 DSA signature: NOKEY, key ID 897da07a
>     Header SHA1 digest: OK (20b36106fc52f5cba4494797f5621fdfa26454f1)
>     MD5 digest: OK (06c3585ac7f88782f99893d9f24c0832)
>     V3 DSA signature: NOKEY, key ID 897da07a

Please check to see whether your systems are subscribed to the beta
channels (https://rhn.redhat.com/).

If they are, and you wish to receive the beta packages on your system,
you'll need to add the beta key to the appropriate up2date keyring.

For RHEL3+, it's just:

rpm --import <filename>.gpg

For more information on the beta package signing process:

https://www.redhat.com/security/team/key/#beta

--Bret