Mailinglist Archive: opensuse-buildservice (261 mails)

< Previous Next >
[opensuse-buildservice] Importing repo keys with OSC
  • From: Pavol Rusnak <prusnak@xxxxxxx>
  • Date: Mon, 30 Jun 2008 12:02:23 +0200
  • Message-id: <4868AF2F.1040901@xxxxxxx>
Hi all!

I was building one of my packages with OSC when it bailed out with error:

The following package could not be verified:
/var/tmp/osbuild-packagecache/games/openSUSE_11.0/x86_64/SDL-1.2.13-49.6.x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#53a2e3f5)


- If the key is missing, install it first.
For example, do the following:
gpg --keyserver pgp.mit.edu --recv-keys 53a2e3f5
gpg --armor --export 53a2e3f5 > /home/prusnak/keyfile-53a2e3f5
and, as root:
rpm --import /home/prusnak/keyfile-53a2e3f5

Obviously the key is missing, but the problem is that it is not available from public PGP/GPG servers (no one has uploaded there yet). While I agree that somebody (project maintainer and/or OBS folks) should take care of these keys, we shouldn't give instructions that do not work either. I usually solve this situation by adding repository through zypper and it asks whether to import the right key (thus it has to be present in the repo structure somewhere). Isn't it possible to import the key (interactively) from repodata instead of printing broken instructions?

--
Best Regards / S pozdravom,

Pavol RUSNAK SUSE LINUX, s.r.o
Package Maintainer Lihovarska 1060/12
PGP 0xA6917144 19000 Praha 9, CR
prusnak[at]suse.cz http://www.suse.cz
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups