RPi Fresh install - the public key is not available: NO_PUBKEY

petrus · Aug 12th 2024

Hey !

I did a fresh install with current Raspbian
2024-07-04-raspios-bookworm-armhf-lite.img
This image has a little bug, solved by hand with this thread : https://github.com/raspberrypi/bookworm-feedback/issues/109

Then, time for OMV !

But after the last reboot, when I try a apt update, I got this error (same in the web GUI) :

Code

# apt update
Get:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
Get:2 file:/var/cache/openmediavault/archives  Release
Ign:2 file:/var/cache/openmediavault/archives  Release
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Hit:5 http://packages.openmediavault.org/public sandworm InRelease
Get:6 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:7 http://httpredir.debian.org/debian bookworm-backports InRelease [56.6 kB]
Hit:8 http://raspbian.raspberrypi.com/raspbian bookworm InRelease
Hit:9 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:10 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease
Hit:11 https://openmediavault.github.io/packages sandworm InRelease
Err:6 http://security.debian.org/debian-security bookworm-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8
Err:7 http://httpredir.debian.org/debian bookworm-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
Reading package lists... Done
W: GPG error: http://security.debian.org/debian-security bookworm-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8
E: The repository 'http://security.debian.org/debian-security bookworm-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://httpredir.debian.org/debian bookworm-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
E: The repository 'http://httpredir.debian.org/debian bookworm-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Display More

How to fix this bug ?

Thx for your help !

Soma · Aug 12th 2024

Quote from petrus

How to fix this bug ?

Do not use the armhf (32bit) version.

Use the arm64 (64bit) one.

petrus · Aug 12th 2024

Quote from Soma

Do not use the armhf (32bit) version.

Use the arm64 (64bit) one.

Thx for your answer.

Humm, I'm not sure 64bit version is ok on a Raspberry Pi 2B ?

On the download page, the 64bits version looks like starting with the RPi 3

https://www.raspberrypi.com/software/operating-systems/

Soma · Aug 12th 2024

Quote from petrus

I'm not sure 64bit version is ok on a Raspberry Pi 2B ?

You never mentioned what Pi you had.

A Pi2 will be very limited on what you can do.

petrus · Aug 12th 2024

Quote from Soma

You never mentioned what Pi you had.

You never asked on which Pi it's running

Quote from Soma

A Pi2 will be very limited on what you can do.

Enough powered for my purpose

petrus · Aug 12th 2024

So, can we think about an OMV bug, as the RPi 2B is the lower RPi supported ? https://wiki.omv-extras.org/do…install#supported_devices

Humm, I'm not sure how to report this to devs

ryecoaaron · Aug 12th 2024

Quote from petrus

You never asked on which Pi it's running

I wish everyone would put their hardware in their signature so we don't have to guess or ask.

Quote from petrus

Enough powered for my purpose

But it also has to be enough for OMV. That is where most rpi2 are painfully slow - applying config changes in OMV.

Quote from petrus

can we think about an OMV bug, as the RPi 2B is the lower RPi supported ?

It technically isn't wrong. OMV does work on the RPi2 with 32 bit os. And some later RPi2 actually have the same cpu as the RPi3 and can run 64 bit. I will change it since I don't think people should use an RPi2 and the number of RPi2 with RPi3 cpus is low enough to not worry about it.

Quote from petrus

I'm not sure how to report this to dev

You just did.

petrus · Aug 13th 2024

Quote from ryecoaaron

I wish everyone would put their hardware in their signature so we don't have to guess or ask.

+1.
I was just replying to Soma on the same tone

Quote from ryecoaaron

But it also has to be enough for OMV. That is where most rpi2 are painfully slow - applying config changes in OMV.

And thx to you devs, this one is running OMV since many years ! Yep, it can be slow to save config changes, but I usually do it only some times a year... I hope this support will stay in future As the hardware is ok and not so "obsolete" for home users and their purposes, like my case.

Quote from ryecoaaron

And some later RPi2 actually have the same cpu as the RPi3 and can run 64 bit.

Ok, never seen this information before. Hummm so I'm not sure about my RPi 2B, if it's 64 bits capable... I'll try to find some informations about it.

Quote from ryecoaaron

You just did.

RPi Fresh install - the public key is not available: NO_PUBKEY

Participate now!

Tags