Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #189790
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Missing key |
| Date | 2017-12-11 14:50 +0100 |
| Message-ID | <uVwCZ-5S7-1@gated-at.bofh.it> (permalink) |
| References | <uVuKS-4FD-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
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
csiph-web