Jump to content

http://apt.armbian.com/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.


Myron
 Share

Go to solution Solved by Igor,

Recommended Posts

Recently, successfully, upgraded from Ubuntu Focal to Ubuntu Jammy.  Does anyone know the correct procedure to sort out the apt-key deprecation issue? 

I've read apt-key(8), but I don't fully understand what I need to do. I think a Linux guru is needed here.  🙂

 

~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
myron@loki:~$ s apt-get update
Hit:1 http://ports.ubuntu.com jammy InRelease
Hit:2 http://ports.ubuntu.com jammy-security InRelease
Hit:3 http://ports.ubuntu.com jammy-updates InRelease
Hit:4 http://ports.ubuntu.com jammy-backports InRelease
Hit:5 http://packages.azlux.fr/debian bullseye InRelease
Hit:7 https://armbian.github.io/configurator stable InRelease
Hit:6 http://armbian.hosthatch.com/apt jammy InRelease
Reading package lists... Done
W: http://apt.armbian.com/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

 

Link to comment
Share on other sites

Armbian Linux community supported weekly builds download

@Igor, seems to be a bit of a problem. Server returning error 500.

 

myron@loki:~/Install Armbian repo key$ sudo wget https://apt.armbian.com/armbian.key -O key
--2022-08-16 18:04:47--  https://apt.armbian.com/armbian.key
Resolving apt.armbian.com (apt.armbian.com)... 107.175.134.226
Connecting to apt.armbian.com (apt.armbian.com)|107.175.134.226|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2022-08-16 18:04:47 ERROR 500: Internal Server Error.

 

Link to comment
Share on other sites

38 minutes ago, Myron said:

seems to be a bit of a problem. Server returning error 500.


Working here ... re-director is currently under some re-work. Could be related. Its should be a temporal problem.

Link to comment
Share on other sites

i am new to armbian not use to deb way.

that i use to rpm way from fedora. (it did work on pine64)

The problem is i need klipper to work for 3d printer, but did not work on fedora and i discovery most come from deb so i start doing on armbain because of pine64 arm. 

 

i had problem apt update (first time tonight before no problem) give error and i had dig info but at end i wipe gpg off and apt key del all. and i found your link and rebutli. it seem work but gpg still do same error.

i would like clean gpg off and rebutli refresh and lastest gpg so i can get apt update to work.   i did not know why it come out error like that tonight first time. it was work well than broken.

 

i copy and paste show you.

 

klipper@192.168.0.23's password:
 ____  _             __   _  _
|  _ \(_)_ __   ___ / /_ | || |
| |_) | | '_ \ / _ \ '_ \| || |_
|  __/| | | | |  __/ (_) |__   _|
|_|   |_|_| |_|\___|\___/   |_|

Welcome to Armbian 22.05.3 Jammy with Linux 5.15.48-sunxi64

System load:   77%              Up time:       26 min
Memory usage:  11% of 1.94G     IP:            192.168.0.23
CPU temp:      41°C             Usage of /:    19% of 29G

[ General system configuration (beta): armbian-config ]

Last login: Wed Aug 17 23:18:18 2022 from 192.168.0.1
klipper@pine64:~$ sudo apt update
[sudo] password for klipper:
Hit:3 http://deb.volian.org/volian scar InRelease
Hit:1 https://ryanfortner.github.io/box64-debs/debian ./ InRelease
Hit:5 http://ports.ubuntu.com jammy InRelease
Hit:2 https://cli.github.com/packages stable InRelease
Hit:4 http://au-mirror.bret.dk/armbian/apt jammy InRelease
Hit:6 http://ports.ubuntu.com jammy-security InRelease
Hit:7 http://ports.ubuntu.com jammy-updates InRelease
Hit:8 http://ports.ubuntu.com jammy-backports InRelease
Err:5 http://ports.ubuntu.com jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:6 http://ports.ubuntu.com jammy-security InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:7 http://ports.ubuntu.com jammy-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:8 http://ports.ubuntu.com jammy-backports InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ports.ubuntu.com jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: Failed to fetch http://ports.ubuntu.com/dists/jammy/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: Failed to fetch http://ports.ubuntu.com/dists/jammy-security/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: Failed to fetch http://ports.ubuntu.com/dists/jammy-updates/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: Failed to fetch http://ports.ubuntu.com/dists/jammy-backports/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
W: Some index files failed to download. They have been ignored, or old ones used instead.
klipper@pine64:~$
 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...