Re: Re: Trouble importing gpg keys in stretch

2017-05-20 Thread Peter Miller
Frank, The answers are: 7 7 0 So, it doesn't look like the issue. Thanks for your help anyway. Except, now I am left with a system I can't update properly. Cheers, PEte

Re: Re: Trouble importing gpg keys in stretch

2017-05-18 Thread Peter Miller
Frank, So sorry, I was premature - now the messages appear at the end instead of the middle. Still a legend, but problem not actually solved. Cheers, Pete

Re: Re: Trouble importing gpg keys in stretch

2017-05-18 Thread Peter Miller
Frank, Yes, same behaviour from the command line. apt and gnupg were the same versions. Clearing the cache *worked* You are a legend! Thanks so much. Cheers, Pete

Re: Re: Trouble importing gpg keys in stretch

2017-05-16 Thread Peter Miller
Frank, Yes, they do, but associated with Wheezy and Jessie, by the looks? /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg -- pub rsa4096 2012-04-27 [SC] [expires: 2020-04-25] A1BD 8E9D 78F7 FE5C 3E65 D8AF 8B48 AD62 4692 5

Re: Re: Trouble importing gpg keys in stretch

2017-05-15 Thread Peter Miller
Frank, It was already installed, and showing version 2014.3 Thanks, Pete

Re: Re: Trouble importing gpg keys in stretch

2017-05-15 Thread Peter Miller
Thanks Frank, Sorry, I should have started with the why: when I do an reload in synaptic I get: GPG error: http://debian.mirror.digitalpacific.com.au/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBK