Apt shows incorrect suggestion to fix unavailability of public key of a given repository

Bug #380912 reported by Aleksander Morgado
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apt (Debian)
Confirmed
Unknown
apt (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

Binary package hint: apt

When I add a new repo to sources.list, for example one from a Ubuntu PPA, then I run apt-get update and I get the following warnings:

W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY <keyhere>
W: You may want to run apt-get update to correct these problems

The last message shown says that apt-get update will correct these problems, but that's not true.

A better explanation of how to fix that would be:
W: You may want to run `sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys <keyhere>' to correct this problem.

Or something similar (with a more generic keyserver path maybe).

I always end up googling to find the command used to add a new public key in apt's keyring... and would find such a useful tip a great enhancement.

Revision history for this message
Joseph Reeves (iknowjoseph) wrote :

It'd be nice, perhaps, if it produced a message:

Do you want to download key <keyhere> [y/N]?

Would make a handy enhancement for people like me who want to use apt at the command line, don't want to use _too_ many commands ;)

Revision history for this message
Philip Muškovac (yofel) wrote :

Setting wishlist/triaged on roberts request.

Changed in apt (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Changed in apt (Debian):
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.