Hi everyone, I too would like to know why this is happening. I've worked around it by using the --no-verify flag on my local builds - it just skips the server package validation steps, so that I can build without keys, but it's not very safe. I asked this question on this forum earlier this month and got no response - does this mean no one knows the answer and no one is responsible for fixing the problem? Boyd Lynn Gerber wrote:

Hello,

I am trying to build some of the projects in my home:gerberb

Verifying integrity of cached packages

The following package could not be verified: /var/tmp/osbuild-packagecache/home:gerberb/openSUSE_10.3/i586/python-pydns-2.3.0-8.1.i586.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#d986a842)

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

Then, just start the build again.

This is what I get...

gpg --keyserver pgp.mit.edu --recv-keys d986a842 gpg: requesting key D986A842 from hkp server pgp.mit.edu gpgkeys: key D986A842 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0

What can be done?

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Wednesday 05 March 2008 11:17:21 wrote Dr. Peter Poeml:

Hi,

On Sat, Feb 23, 2008 at 03:25:52PM -0700, John Calcote wrote:

...

I too would like to know why this is happening. I've worked around it by using the --no-verify flag on my local builds - it just skips the server package validation steps, so that I can build without keys, but it's not very safe.

I asked this question on this forum earlier this month and got no response - does this mean no one knows the answer and no one is responsible for fixing the problem?

Indeed, it seems so :-)

The problem will be solved automatically when we build Factory within the OBS. We are working hard on this and this is scheduled until the end of the month. You can also manually go to the project and import the key, but be aware that the download redirector redirects you to the other Factory, which still comes from SUSE internal systems atm. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org