Doc/readme debian trusted gpg #209
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aymanbagabas
added a commit
that referenced
this pull request
Oct 17, 2022
Use the recommended keyrings path /etc/apt/keyrings Per: https://manpages.debian.org/unstable/apt/apt-key.8.en.html#DEPRECATION Fixes: #208 Fixes: #209
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #208
Currently then using
apt-key add, a warning message is shown:Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8))and, then when executing
apt udpate:W: https://repo.charm.sh/apt/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.In this PR, I'm adding the updated instructions to avoid this warning message
Changes