#1 2019-09-04 17:07:43

rbh

Member

From: Sweden/Vasterbotten/Rusfors

Registered: 2016-08-11

Posts: 661

GPG-error

Hi!

I have an virtual guest.I have not used for some time.
Started it and changed BunsenLabs repo to Lithium for updating.

Got error:

W: GPG Error: http://192.168.1.254/kelaino.bunsenlabs.org/~johnraff/debian lithium InRelease: The following signatures could not be verified because the open key is unavailable: NO_PUBKEY 8FFD2CE993071671
E: The repository 'http://192.168.1.254/kelaino.bunsenlabs.org/~johnraff/debian lithium InRelease' is not signed.
N: Updating from such a repository cannot be done securely, and is therefore disabled by default.
N: See apt-secure (8) manpage for repository creation and user configuration details

apt-key list

list the key. No differense if I import key again

No gpg error on the host.

I can not find anyone describing the same problem.

Anyone know howto fix it?

---

// Regards rbh

twoion

ほやほや

Registered: 2015-08-10

Posts: 2,934

Re: GPG-error

John's experimental Lithium repo is not signed using the BL main signing key. Post https://forums.bunsenlabs.org/viewtopic.php?id=5546 contains instructions how to get and set up his signing key.

---

Per aspera ad astra.

rbh

Member

From: Sweden/Vasterbotten/Rusfors

Registered: 2016-08-11

Posts: 661

Re: GPG-error

Post https://forums.bunsenlabs.org/viewtopic.php?id=5546 contains instructions

Yes, I have followed that, but sloppy!

I just copied the two rows in to an terminal:

wget https://kelaino.bunsenlabs.org/~johnraff/helium-dev.asc
sudo cp helium-dev.asc /etc/apt/trusted.gpg.d/

As i already was root, the copy failed.

When I listed the keys, I misread.

Now when I checked that the trusted key realy got copiedto the target, it works.

I se now that " # apt-key list" does not list the lithium-dev key...

Last edited by rbh (2019-09-04 17:48:16)

---

// Regards rbh