sean finney on 4 Nov 2005 17:17:54 -0000 |
hi mike, On Fri, Nov 04, 2005 at 11:58:26AM -0500, Mike Leone wrote: > I'm getting this warning, when running apt-get update: > > W: GPG error: http://secure-testing.debian.net etch/security-updates > Release: The following signatures couldn't be verified because the public > key is not available: NO_PUBKEY 946AA6E18722E71E > W: You may want to run apt-get update to correct these problems the latest version of apt in unstable now has built-in support for gpg verification of packages, which is really a Good Thing, as i'm sure you know. basically, apt is notices that it knows nothing about the pubkey in question, so it's whining a bit. my guess is that this is because the Release.gpg on secure-testing.d.o uses a different key than the main archives. apt-key(8) is what you'll want to use to import this key into apt's trusted keyring. sean Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|