By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 37

Summary:	apt-get update can't verify GPG signature
Product:	TDE	Reporter:	Phillip Reed <preed>
Component:	tdebase	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, darrella, sam
Priority:	P5
Version:	3.5.10
Hardware:	i386
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Phillip Reed 2009-01-27 08:41:59 CST

I have the GPG listed on the main page in my trusted key list:
$ sudo apt-key list
/etc/apt/trusted.gpg
--------------------
[ ... ]
pub   1024D/E23CE692 2008-10-04
uid                  Timothy Pearson (Pearson Computing APT Repository) <kb9vqf@pearsoncomputing.net>
sub   4096g/8939724E 2008-10-04

But as of yesterday, when I run "apt-get update", it complains about not being able to verify the signature:

$ sudo apt-get update
[ ... ]
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CB2F6C86F77B1CA9
W: You may want to run apt-get update to correct these problems

This is the only repository at ppa.launchpad.net that I have in /etc/apt/sources.list, so I'm pretty sure it's the cause.

Comment 1 Timothy Pearson 2009-02-02 19:33:28 CST

*** Bug 39 has been marked as a duplicate of this bug. ***

Comment 2 Timothy Pearson 2009-02-02 19:34:26 CST

The PPAs have been altered by Canonical, and GPG signing should be available again soon.  Please be patient. ;-)

Comment 3 Timothy Pearson 2009-02-08 12:35:12 CST

I believe GPG signing has been repaired at this time.  The signing key has changed; you will need to go to the main page at http://apt.pearsoncomputing.net and follow the instructions under "Add the GPG signing key" again.  After you have done this, apt-get update should not throw any more signature warnings.