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

Re: [ot] lacking public keys on debian servers
Tomek, I am not sure it is related, but I recently tried to reinstall with a dated (January vintage) d-i image. A lot failed, and subsequent apt-get often failed to find previously available packages. It turned out that the previous year's public key had expired, and using a fresh d-i image fixed it. 

Don

On Thu, 15 Mar 2007, =?ISO-8859-2?Q?Tomasz Ka=BCmierczak ?= wrote:


Date: Thu, 15 Mar 2007 09:10:57 +0100
From: =?ISO-8859-2?Q?Tomasz Ka=BCmierczak ?= <tomek.fizyk@op.pl>
To: debian-amd64@lists.debian.org
Subject: [ot] lacking public keys on debian servers
Resent-Date: Thu, 15 Mar 2007 03:11:21 -0500 (CDT)
Resent-From: debian-amd64@lists.debian.org

Sorry for the off topic, but I've noticed something weird.

I wanted to install a new kernel on one of my debian systems. After
apt-get update
I got an error telling me that there are no public keys for security.debian.org and
for my local Debian repository (ftp.pl.debian.org). I've ignored it and installed
the new kernel but after reboot the system didn't boot up. I've tried the new and
the old kernel and the result was the same.
Now I know what was the problem - the automatically generated grub menu.lst
was incorrect, but before noticing that I've tried to update from several other
servers (not only Polish) and there always was the same error - no public key.

Is there something wrong with the repos?

Tomek





--
Reply to: