On Wed, Nov 22, 2006 at 09:48:25 +0100, Florian Kulzer wrote:
> On Wed, Nov 22, 2006 at 13:58:52 +0800, Deephay wrote:
> > On 11/22/06, Kevin Mark wrote:
> > >On Wed, Nov 22, 2006 at 03:12:27PM +1100, M-L wrote:
> > >> On Wednesday 22 November 2006 15:08, Mark Grieveson wrote:
> > >> > Hello. After a recent upgrade of my Etch, I get the following warning:
> > >> >
> > >> > Fetched 30.2kB in 9s (3350B/s)
> > >> > Reading package lists... Done
> > >> > W: There are no public key available for the following key IDs:
> > >> > A70DAF536070D3A1
> > >> > W: You may want to run apt-get update to correct these problems
> > >> >
> > >> > What does this mean? Should I be concerned? Is anyone else receiving
> > >> > this warning?
[...]
> > Will this be fixed automatically later?
>
> It is not really broken at the moment because all the package lists are
> also still signed with the old automatic signing key (2D230C5F).
> Therefore you can just ignore the message; one verifiable signature is
> enough for apt.
[...]
> I guess that the post-install script of the updated keyring package
> could add the new key automatically to apt's keyring, but I do not know
> if this will indeed be the case.
I just saw that version 2006.11.22 of debian-archive-keyring has the new
key and adds it to the keyring of apt automatically.
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
