Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apt-get claims missing PUBLIC KEY for "configng stable InRelease" #267

Closed
1 task done
sauerbi opened this issue Nov 22, 2024 · 6 comments
Closed
1 task done

apt-get claims missing PUBLIC KEY for "configng stable InRelease" #267

sauerbi opened this issue Nov 22, 2024 · 6 comments
Labels
Bug Something isn't working as it should Duplicate Issue is already present Good first issue Feel free to contribute :)

Comments

@sauerbi
Copy link

sauerbi commented Nov 22, 2024

What happened?

When calling "apt-get update" the following message comes up:

Err:5 https://github.armbian.com/configng stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5

How to reproduce?

after running apt-get upgrade to install latest version of armbian-config (ng) the NEXT call to apt-get update will produce the above error.

I am running 'debian bullseye' on a rock-3a system.
uname -a gives
Linux nginx 6.1.11-rk35xx #23.02.2 SMP PREEMPT Sat Feb 18 00:05:58 UTC 2023 aarch64 GNU/Linux

On which host OS are you running the build script and observing this problem?

Other

Code of Conduct

  • I agree to follow this project's Code of Conduct
@sauerbi sauerbi added the Bug Something isn't working as it should label Nov 22, 2024
Copy link

Hey @sauerbi !

Looks like it's your first time interacting with Armbian here on GitHub.

Welcome and thank you for taking the time to report an issue ❤️.

Don't forget to star ⭐ the repo.

@github-actions github-actions bot added the Good first issue Feel free to contribute :) label Nov 22, 2024
@igorpecovnik igorpecovnik added the Duplicate Issue is already present label Nov 23, 2024
@igorpecovnik
Copy link
Member

igorpecovnik commented Nov 23, 2024

Bullseye is unsupported as costs of maintaining it went out of our range. If someone comes out with a fix that doesn't require complete rework of packaging, which is one of the possible solutions, we will implement it, PR will be accepted. Same goes for workaround, which was proposed in other ticket related to the same problem: #265

Recommendation is to upgrade OS to bookworm. Not just for this reason.

@igorpecovnik
Copy link
Member

Found a fix. Now it should work:
armbian/scripts@9fe944b

@dimitry-ishenko
Copy link
Collaborator

If I may suggest, the keyring should be packaged in a Debian package. Both Debian and Ubuntu have theirs in debian-archive-keyring and ubuntu-keyring packages respectively. This has at least 2 advantages:

  1. You can install the keyring like a normal package. Eg, sudo apt install armbian-keyring.
  2. In the future, if you need to add and/or revoke a key, you can release updated package and will be propagated to the users next time they update their system.

Just my 2 cents.

@igorpecovnik
Copy link
Member

@sauerbi

Adding key old way should work. Implementing it to the build framework.
armbian/build#7524

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working as it should Duplicate Issue is already present Good first issue Feel free to contribute :)
Projects
None yet
Development

No branches or pull requests

4 participants