Re: Re: Trouble importing gpg keys in stretch

2017-05-21 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: Trouble importing gpg keys in stretch

2017-05-18 Thread Frank
Pete, Maybe one more thing to check. I found a reference to an old bug which seems to suggest the number of keyrings gnupg can handle is limited. How many items does apt-key list show? How many files does /etc/apt/trusted.gpg.d contain? If a file /etc/apt/trusted.gpg exists, how big is it?

Re: Trouble importing gpg keys in stretch

2017-05-18 Thread Frank
Op 18-05-17 om 10:44 schreef Peter Miller: So sorry, I was premature - now the messages appear at the end instead of the middle. Sorry to hear that. This is really weird. Your system does have the keys it needs to verify the signatures. These errors make no sense. To make sure the InRelease

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: Trouble importing gpg keys in stretch

2017-05-16 Thread Frank
Op 16-05-17 om 11:53 schreef 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]

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

Re: Trouble importing gpg keys in stretch

2017-05-15 Thread Frank
Op 16-05-17 om 01:25 schreef Peter Miller: Frank, It was already installed, and showing version 2014.3 Odd. Do the keys mentioned show up if you enter apt-key list in a terminal? Regards, Frank

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: Trouble importing gpg keys in stretch

2017-05-15 Thread Frank
Op 15-05-17 om 10:25 schreef Peter Miller: Sorry, I should have started with the why: when I do an reload in synaptic I get: [snip GPG-errors] Well, the keys mentioned are signing keys from 2012 and 2014, so I would expect them to be present in the current debian-archive-keyring package

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

Re: Trouble importing gpg keys in stretch

2017-05-11 Thread Frank
Op 09-05-17 om 05:09 schreef Peter Miller: I am using the http://debian.mirror.digitalpacific.com.au/debian/ mirror for stretch. The url http://debian.mirror.digitalpacific.com.au/debian/dists/stretch/ contains the Release.gpg file. When I download and try to import it I receive an error: