Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #189782 > unrolled thread

Missing key

Started byTony van der Hoff <lists@vanderhoff.org>
First post2017-12-11 12:50 +0100
Last post2017-12-11 14:50 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.user


Contents

  Missing key Tony van der Hoff <lists@vanderhoff.org> - 2017-12-11 12:50 +0100
    Re: Missing key Michael Stone <mstone@debian.org> - 2017-12-11 14:50 +0100

#189782 — Missing key

FromTony van der Hoff <lists@vanderhoff.org>
Date2017-12-11 12:50 +0100
SubjectMissing key
Message-ID<uVuKS-4FD-3@gated-at.bofh.it>
Dragging up an old thread from the archive:

On Thu, 22 Jun 2017 12:25:07 -0300 Henrique Holschuh wrote:

> On Thu, 22 Jun 2017, Charles E. Blair wrote: > When I type "apt-get
> upgrade" I get > this message, and things stop: > > W: There is no
> public key available for the following key IDs: > EF0F382A1A7B6500 > >
> I hope there is a simple fix. You can ignore the warning _in this
> specific instance_: it is expected, and apt is using another key to
> verify the downloads. This warning will be fixed for the Debian 8.9
> oldstable point-release (due in about a month or so), which adds the
> missing key. 

I don't understand what oldstable has to do with it, but while upgrading to stretch, I am seeing the identical error message.

I'll ignore it, but shouldn't it have been fixed?
 

[toc] | [next] | [standalone]


#189790

FromMichael Stone <mstone@debian.org>
Date2017-12-11 14:50 +0100
Message-ID<uVwCZ-5S7-1@gated-at.bofh.it>
In reply to#189782
On Mon, Dec 11, 2017 at 11:43:16AM +0000, Tony van der Hoff wrote:
>Dragging up an old thread from the archive:
>
>On Thu, 22 Jun 2017 12:25:07 -0300 Henrique Holschuh wrote:
>
>> On Thu, 22 Jun 2017, Charles E. Blair wrote: > When I type "apt-get
>> upgrade" I get > this message, and things stop: > > W: There is no
>> public key available for the following key IDs: > EF0F382A1A7B6500 > >
>> I hope there is a simple fix. You can ignore the warning _in this
>> specific instance_: it is expected, and apt is using another key to
>> verify the downloads. This warning will be fixed for the Debian 8.9
>> oldstable point-release (due in about a month or so), which adds the
>> missing key.
>
>I don't understand what oldstable has to do with it, but while upgrading to stretch, I am seeing the identical error message.
>
>I'll ignore it, but shouldn't it have been fixed?

Did you upgrade the debian-archive-keyring package in jessie *before* 
changing the sources.list file to point to stretch?

Mike Stone

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web