ci: resolute rust-based gpg-sq rejects short GPG keyids#6710
Merged
blackboxsw merged 4 commits intocanonical:mainfrom Feb 26, 2026
Merged
ci: resolute rust-based gpg-sq rejects short GPG keyids#6710blackboxsw merged 4 commits intocanonical:mainfrom
blackboxsw merged 4 commits intocanonical:mainfrom
Conversation
holmanb
approved these changes
Feb 2, 2026
Member
holmanb
left a comment
holmanb
left a comment
There was a problem hiding this comment.
Please include example error message for future reference. Otherwise, this looks good to me.
I'm guessing we need to update some documentation since this is a UI change, right?
blackboxsw
force-pushed
the
ci-resolute-sequoia-gpg-no-short-keys
branch
from
caab93b to
326c416
Compare
2 tasks
Member
|
Dismissing review due to failing tests. |
github-actions
bot
added
the
documentation
holmanb
requested changes
Feb 3, 2026
doc/examples/cloud-config-apt.txt
Outdated
| # Additionally, if the repository requires a custom signing key, it can be | ||
| # specified via the same fields as for custom sources: | ||
| # 'keyid': providing a key to import via shortid or fingerprint | ||
| # 'keyid': providing a key to import via longid or fingerprint |
Collaborator
Author
There was a problem hiding this comment.
changed to 16-bit ID. The 'long' version from the gpg --list-keys --keyid-format section of the gpg man-page
Select how to display key IDs. "short" is the traditional 8-character key ID.
"long" is the more accurate (but less convenient) 16-character key ID.
Add an "0x" to either to include an "0x" at the beginning of the key ID, as in 0x99242560.
Member
There was a problem hiding this comment.
One character contains more than one bit, so the new wording is confusing. Also, it isn't clear that the "16-bit" in "16-bit ID or fingerprint" applies only to the ID and not to fingerprint.
Use long-keyid for testing to avoid non-zero exit codes warning of insecure short IDs in gpg (GnuPG-compatible Sequoia Chameleon) 2.2.40.
blackboxsw
force-pushed
the
ci-resolute-sequoia-gpg-no-short-keys
branch
from
326c416 to
b4ae6f9
Compare
blackboxsw
force-pushed
the
ci-resolute-sequoia-gpg-no-short-keys
branch
from
e07fcd9 to
56f74ac
Compare
holmanb
approved these changes
Feb 26, 2026
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
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.
Proposed Commit Message
Additional Context
Success run on questing:
https://github.com/blackboxsw/cloud-init/actions/runs/21609823450/job/62275681732
Success run on resolute:
https://github.com/blackboxsw/cloud-init/actions/runs/21610228334/job/62277053444
Test Steps
Merge type