On Tue, May 30, 2006 at 08:32:14PM -0500, helices wrote: > * Alexander Samad <alex@samad.com.au> [2006:05:31:11:00:11+1000] scribed: > > On Wed, May 31, 2006 at 10:12:18AM +1000, Sam Varghese wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > On Tue, May 30, 2006 at 04:51:52PM -0500 helices said: > > > > * On 2006:05:30:08:45:45-0500 I, helices <helices@helices.org>, scribed: > > > > > > > > OK, I am making progress, in understanding and in practice, with 64-bit > > > > packages. > > > > > > > > However, I am still unclear: what is the proper way to get SECURITY > > > > updates in amd64? > > > > > > For stable: > > > > > > deb http://security.debian.org/ stable/updates main contrib non-free > > > > for etch > > > > deb http://secure-testing.debian.net/debian-secure-testing > > etch/security-updates main contrib non-free > > deb-src http://secure-testing.debian.net/debian-secure-testing > > etch/security-updates main contrib non-free > > Cool! But, what is this update error? > > 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 that means that the gpg key associated with that repository is not in the apt-key chain. do something like gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 946AA6E18722E71E gpg --armor --export 946AA6E18722E71E | apt-key add - > > > -- > Best Regards, > > helices > - > Dare to fix things before they break . . . > - > Our capacity for understanding is inversely proportional to how much > we think we know. The more I know, the more I know I don't know . . . > --
Attachment:
signature.asc
Description: Digital signature