topic title: apt-get: "W: There is no public key available"
Posts: 71
jtwdyp
Joined: 08 Apr 2012
#1
I've been busy with other aspects of my so called life. And wasn't paying any
attention to how long it's been since I updated my Linux distributions. Suddenly I
realized it's been too long...

I did an apt-get update on my jessie/sid rolling antiX and got an error and a couple
of warnings, which I initially thought were related...

But the error:

Code: Select all

Err http://www.deb-multimedia.org testing InRelease
Was easily resolved by following the nice pasteable instructions for downloading and
installing the deb-multimedia-keyring at

Code: Select all

 http://www.deb-multimedia.org
Yet the warnings still remain:

Code: Select all

Fetched 186 kB in 4s (39.0 kB/s)
Reading package lists... Done
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
Anybody know what's causing this? Or even which repository belongs to these two
key IDs??

TIA
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#2
I bet those are expired keys for the debian repos.
Posts: 88
kmathern
Joined: 25 Aug 2012
#3
They don't look like they're expired to me.

Code: Select all

$ apt-key list | grep -e 2B90D010 -e C857C906 -B3 -A2

/ etc/apt/trusted.gpg.d//debian-archive-jessie-automatic.gpg
-----------------------------------------------------------
pub   4096R/2B90D010 2014-11-21 [expires: 2022-11-19]
uid                  Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>

/ etc/apt/trusted.gpg.d//debian-archive-jessie-security-automatic.gpg
--------------------------------------------------------------------
pub   4096R/C857C906 2014-11-21 [expires: 2022-11-19]
uid                  Debian Security Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>
Maybe try reinstalling the keyring package

Code: Select all

sudo apt-get --reinstall install debian-archive-keyring
Posts: 71
jtwdyp
Joined: 08 Apr 2012
#4
Thanks for responding so quickly...

And trying to reinstall the keyring package sounds like a good idea.

But there's a new wrinkle that I hope doesn't matter.
Since there is a difference between an apt-get error, and a warning about a public
key, I went ahead with the apt-get upgrade... Which completed without errors.
but suggested apt-get autoremove, and left 452 packages"not upgraded".

(I did say it had been too long since I updated my Linux distros...)

I had to meet someone for a lunch date. So I shut down.
When I got back, I ran apt-get upgrade again, just to get the"not upgraded" list.
So I could decide if I wanted to bother with apt-get dist-upgrade or not.
(if your curious look at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://pastebin.com/AGmbMBTV"
linktext was:"http://pastebin.com/AGmbMBTV"
====================================
)

Then I ran the apt-get autoremove which complained about a few things that"failed"
Would you mind looking at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://pastebin.com/5CsTxGJE"
linktext was:"http://pastebin.com/5CsTxGJE"
====================================
. Just to confirm
that these"fail"ures aren't likely to interfere with apt-get when I try to reinstall
the keyring, and/or run the dist-upgrade?