Re: Re: Trouble importing gpg keys in stretch

[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

[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

[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

[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 5553
uid   [ unknown] Debian Archive Automatic Signing Key
(7.0/wheezy) 

/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
--
pub   rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
  126C 0D24 BD8A 2942 CC7D  F8AC 7638 D044 2B90 D010
uid   [ unknown] Debian Archive Automatic Signing Key
(8/jessie) 

Are these in the right places? What is the first half of the full key?

Thanks, Pete

Re: Re: Trouble importing gpg keys in stretch

[Peter Miller]

Frank,

It was already installed, and showing version 2014.3

Thanks, Pete

Re: Re: Trouble importing gpg keys in stretch

[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_PUBKEY
7638D0442B90D010The repository
'http://debian.mirror.digitalpacific.com.au/debian stretch InRelease'
is not signed.Updating from such a repository can't be done securely,
and is therefore disabled by default.See apt-secure(8) manpage for
repository creation and user configuration details.GPG error:
http://debian.mirror.digitalpacific.com.au/debian stretch-updates
InRelease: The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
7638D0442B90D010The repository
'http://debian.mirror.digitalpacific.com.au/debian stretch-updates
InRelease' is not signed.Updating from such a repository can't be done
securely, and is therefore disabled by default.See apt-secure(8)
manpage for repository creation and user configuration details.An
error occurred during the signature verification. The repository is
not updated and the previous index files will be used. GPG error:
http://security.debian.org stretch/updates InRelease: The following
signatures couldn't be verified because the public key is not
available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553

Thanks, Pete

Fwd: Trouble importing gpg keys in stretch

[Peter Miller]

Hi,

I am using the http://debian.mirror.digitalpacific.com.au/debian/ mirror
for stretch. The url http://debian.mirror.digitalpa
cific.com.au/debian/dists/stretch/ contains the Release.gpg

file. When I download and try to import it I receive an error:

The selected file may not be a GPG key file or it might be corrupt.

The file looks valid in gedit. I also tried the file from the "testing"
directory on the mirror.

I can't find the key file for these keys anywhere else, and trying to use
anything like (with or without the "0x"):

apt-key adv --keyserver keyring.debian.org --recv-keys 0x8B48AD6246925553

doesn't work (gpg: no valid OpenPGP data found.).

Is there something I am doing wrong or is this a bug?

Thanks,
Pete Miller

Fwd: Gnome/X/Display device issues since before Testing freeze

[Peter Miller]

I've had the "Oh no! Something went wrong" screen for a couple of
weeks now, since just before Testing went into freeze.

I've looked everywhere I can and tried all sorts of things, but
nothing solves the problem. I recently upgraded to sid to see if that
helped, but still no luck.

In the included journal file below, it seems the problem lies in the
"cannot determine display-device" entry, but I can't tell what is
causing that.

I have a lot more diagnostic output, but I can't have attachments, apparently.

I would file a bug report, but I am not sure which package to report under.

One thing I have not been able to work out if is whether the memory
conflict message is an issue, and, if it is, how to solve it...

Thanks for any assistance...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/capmdcemcnrgwafcexolfvbggo5qsab3h5vgjwih6uzpgueo...@mail.gmail.com