Curtis Rey wrote:
On Wed October 4 2006 06:34, Joachim Schrod wrote:
pm --import /usr/lib/rpm/gnupg/packman-bwalle.asc
Ok, so I did as you suggested and it seemed to help, at least a bit. However, now when I run an rpm query (or anything else) I get a new message after I ran a querry on "packman" and got his message:
error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd
Then your rpm database is probably damaged. Check that the backup in /var/adm/backup/rpmdb is as current as the last changed file and run rpm --rebuilddb.
So I ran this and got the following:
Crusher-1:/home/crrey # rpm -qa 'gpg-pubkey*' | grep cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee error: rpmdbNextIterator: skipping h# 2131 Header V3 DSA signature: BAD, key ID cd3140cd gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee gpg-pubkey-cd3140cd-3f2e76ee Crusher-1:/home/crrey # rpm -e gpg-pubkey-cd3140cd-3f2e76ee error: "gpg-pubkey-cd3140cd-3f2e76ee" specifies multiple packages
This seems to happen when a GPG key is imported multiple times. (That the keys are imported multiple times in the first place is probably an error -- as I wrote, I have problems with the rpmkeys-packman package myself.) This probably doesn't concern your situation (you should try the rebuilddb option first), but in case that happens again: To delete a GPG key that got imported multiple times, one needs to add the option --allmatches to rpm -e. Now, if anybody can tell me how the vendor and the release attribute of an imported key are computed (the two strings in the pseudo package name after "gpg-pubkey-"), I would be very grateful, as I haven't grokked that part of RPM yet. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany