-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Comments
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. |
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. |
Found a fix. Now it should work: |
If I may suggest, the keyring should be packaged in a Debian package. Both Debian and Ubuntu have theirs in
Just my 2 cents. |
Adding key old way should work. Implementing it to the build framework. |
What happened?
When calling "
apt-get update
" the following message comes up:How to reproduce?
after running
apt-get upgrade
to install latest version of armbian-config (ng) the NEXT call toapt-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
The text was updated successfully, but these errors were encountered: