-
Notifications
You must be signed in to change notification settings - Fork 249
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
Removed apt-key for deb-based install instructions #1653
Conversation
|
Hi @jgreenbow-userful. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test nice thank you |
(sorry about the CLA but we will need it to be signed to be able to merge this pr) |
@chmouel no worries, I was just contributing the fix I tracked down for |
If apt-key is used to import the gpg key for the tektoncd PPA, users receive a warning every time they issue an `apt update` due to apt-key deprecation. Instead, download the tektoncd key to /etc/apt/keyrings/ (as per sources.list(5)) and use the signed-by option in sources.list. This is the currently documented replacement for apt-key usage. Warning shown as: W: http://ppa.launchpad.net/tektoncd/cli/ubuntu/dists/eoan/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
2b439e1
to
0e1cd55
Compare
/retest |
1 similar comment
/retest |
Hey there, I am totally new to open source contribution. I sync'd this branch with tektoncd:main, but that has produced an (unecessary) merge commit. My guess is that I should rebase my tiny branch onto tektoncd:main and let it test through again. Is it kosher to issue rewrites to my fork during a PR review, or should I preserve the history of syncing up my branch and keep the merge commit in? |
I think you good, it doesn't conflict or CI will tell you it needs a merge/rebase. Thanks for your contribution /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chmouel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
Updated gpg key import for PPA
Users may receive a warning every apt-get update due to apt-key deprecation
W: http://ppa.launchpad.net/tektoncd/cli/ubuntu/dists/eoan/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Users on older versions of apt may require the bare binary key, instead of the keybox
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Includes tests (if functionality changed/added)Run the code checkers withmake check
Regenerate the manpages, docs and go formatting withmake generated
See the contribution guide
for more details.
Release Notes