Use explicit key for Debian / Ubuntu repo #2080
Merged
Conversation
This file contains hidden or 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
Contributor
|
Thanks |
hustcer
added a commit
to nushell/integrations
that referenced
this pull request
Nov 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Debian in recent years prefers explicit key for 3rd-party repo. So this PR moves the key to /etc/apt/keyrings/, and add
signed-byoption to the .list file.Note, in the latest versions, Debian recommends to use deb282 format. But we don't have an one-line command to quickly add file of this format yet, so we continue to use "list" format.
This PR also changes from
curltowgetfor downloading key, becausewgetis pre-installed on Debian / Ubuntu, whereascurlneeds to be installed by users.