[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: again update problem



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Pobega wrote:
> On Wed, May 16, 2007 at 11:20:44AM +0200, Ivan Glushkov wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> trying to update, I get bad signature from debian repository:
>>
>> Fetched 79.8kB in 2s (31.1kB/s)
>> Reading package lists... Done
>> W: GPG error: http://ftp2.de.debian.org unstable Release: The following
>> signatures were invalid: BADSIG A70DAF536070D3A1 Debian Archive
>> Automatic Signing Key (4.0/etch) <ftpmaster@debian.org>
>> W: You may want to run apt-get update to correct these problems
>>
>>
>> I have debian-archive-keyring installed:
>>
>> # dpkg -l | grep  debian-archive-keyring
>> ii  debian-archive-keyring            2007.02.19
>>   GnuPG archive keys of the Debian archive
>>
>> Any idea how to solve this? I don't want to install unsigned packages..
>>
>> 	Cheers,
>> 	Ivan
>>
> 
> Try purging and reinstalling the keyring to see what happens.
> 

I tried, but when apt-get warn me about something very bad that will
happen if I continue, and ask me to type "Yes I say so" or something
similar, I got scared not to completely screw up my system.

Anyway, the problem mysteriously disappeared after installing the
"unsigned" packages. Don't ask me why and how, but the problem is
solved. This happens at least once in a month: suddenly I get a "BADSIG"
message from the official Debian repositories. Shouldn't the signature
acquired once and added to the keyring be valid at least for an year or so?

	Cheers,
	Ivan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGSuikoPV3uf0E1nsRAr3jAKCNaEqWAaYCGFPPBQM3AP7bDO6FawCcCas6
GqPKPT98P5YYhr/KmHCfgGU=
=LkGu
-----END PGP SIGNATURE-----



Reply to: