Articles in this section

Warnings during system updates on a Plesk server with Ubuntu 22.04: Key is stored in legacy trusted.gpg keyring

kb: bug

Symptoms

During apt update on Ubuntu 22.04, the deprecation warnings are displayed:

CONFIG_TEXT: W: http://autoinstall.plesk.com/PMM_0.1.11/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.

W: http://autoinstall.plesk.com/pool/PSA_18.0.45_9186/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.

W: http://autoinstall.plesk.com/PHP74_17/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.

W: http://autoinstall.plesk.com/PHP80_17/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.

Cause

Plesk bug PPPM-13644

Resolution

Until the issue is fixed, It is possible to manually re-install the key by running the following command:

# curl -s https://autoinstall.plesk.com/plesk.gpg | gpg --no-default-keyring --keyring gnupg-ring:/etc/apt/trusted.gpg.d/plesk.gpg --import && chown _apt /etc/apt/trusted.gpg.d/plesk.gpg

As for errors related to non plesk keys it can be solved by:

# cd /etc/apt
# sudo cp trusted.gpg trusted.gpg.d

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.