Re: debian problems with gpg-key?

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

sigi <dugongs@gmx.de> writes:

> Hi, 
>
>> > today I tried to update my debian-system, but there was a problem to 
>> > authenticate the gpg-keys:
>> >
>> >>---------------------------------------------------------------------<
>> > W: GPG error: ftp://ftp.nerim.net etch Release: 
>> > The following signatures couldn't be verified because the public key is 
>> > not available: NO_PUBKEY 07DC563D1F41B907
>> 
>> That isn't from the Debian-amd64 port. You have to ask the owner of
>> that for the right key.
>> 
>> > W: GPG error: ftp://ftp.de.debian.org stable Release: 
>> > The following signatures couldn't be verified because the public key is 
>> > not available: 
>> > NO_PUBKEY E415B2B4B5F5BBED
>> >
>> > W: GPG error: ftp://ftp.de.debian.org testing Release: 
>> > The following signatures couldn't be verified because the public 
>> > key is not available: NO_PUBKEY E415B2B4B5F5BBED
>> 
>> http://amd64.debian.net/archive.key
>> 
>> pub   1024D/B5F5BBED 2005-04-24
>>       Key fingerprint = C20C A1D9 499D ECBB D8BD  ACF9 E415 B2B4 B5F5 BBED
>> uid                  Debian AMD64 Archive Key <debian-amd64@lists.debian.org>
>> sub   2048g/34FC6FE5 2005-04-24
>> 
>> That is the normal Archive key ever since the archive moved to
>> amd64.debian.net.
>> 
>
> But why do I have these problems since yesterday? And why do I have the 
> wrong keys for _all_ my sources on my list since yesterday (not only 
> for the debian-servers)? 

Because yesterday you updated apt from sarge to etch/sid.

MfG
        Goswin