On Thu, 26 Aug 2004, Villalovos, John L wrote: > Not sure if this is a known issue or not. > > I did the following: > > # Show my currently installed keys > [root@linuxjohn rpm-gpg-key]# rpm -qa gpg-pubkey* > gpg-pubkey-db42a60e-37ea5438 > gpg-pubkey-1a25d86c-3868173c > gpg-pubkey-897da07a-3c979a7f > > # Import in the new key > [root@linuxjohn rpm-gpg-key]# rpm --import key.gpg > > # Use GPG to see the key ID which is: 0x9C800ACA > [root@linuxjohn rpm-gpg-key]# gpg < key.gpg > pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@xxxxxxx> > sub 2048g/8495160C 2000-10-19 [expires: 2008-06-21] > > # See this list of keys > [root@linuxjohn rpm-gpg-key]# rpm -qa gpg-pubkey* > gpg-pubkey-db42a60e-37ea5438 > gpg-pubkey-1a25d86c-3868173c > gpg-pubkey-897da07a-3c979a7f > gpg-pubkey-218d18d7-3e8eace2 <<<---- New key > > The new keys ID is NOT the same as what GPG reports. Why is that? All > of my other keys ID matches the version field in the RPM database. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90952 - it's not exactly a new bug. - Panu - _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
