- Posted in: Admin-tips
Few days ago I’ve started migration of some of my non-critical servers to Debian Etch (from Sarge). Just after first apt-get update && apt-get dist-upgrade, when apt has been upgraded, I noticed really strange (as for me) error: when I’ve tried to do “apt-get update” it worked fine, but there was annoying message like following:
1 2 3 4 5 6 7 8 | # apt-get update ...... Fetched 5562B in 13s (421B/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 # |
UPDATE: Thanks to Kurt Fitzner we know, that:
There is already a mechanism to do this automatically:
This will obtain the necesary keys and import them. No need to go through gpg directly.
After not so long research I figured out, that this problem was caused by change of gpg key used by ftpmaster on Debian official repository servers. Google gave me some information and I found some fix which works fine for me:
1 2 3 4 5 6 | # gpg --keyserver wwwkeys.eu.pgp.net --recv-keys XXXXXXXXXXXXXXXX ... # apt-key add /root/.gnupg/pubring.gpg ... # apt-get update ... |
Where XXXXXXXXXXXXXXXX is your missing key (e.g A70DAF536070D3A1).
That’s it! Happy using Debian GNU/Linux!