Fix Chrome GPG key import for Bookworm#106
Merged
graygilmore merged 1 commit intomainfrom Apr 7, 2026
Merged
Conversation
The raw signing key needs to be dearmored into a binary GPG keyring for the signed-by directive to work. Without this, apt can't verify the Chrome repo signature. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
tgeselle
approved these changes
Apr 7, 2026
tgeselle
left a comment
tgeselle
left a comment
There was a problem hiding this comment.
My claude agent tells me it's ok to merge 🫡
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.
Summary
Fixes the
build-base-imageworkflow failure from #104.The raw Google signing key needs to be piped through
gpg --dearmorto produce a binary keyring file that thesigned-byAPT directive can use. Without dearmoring, apt can't verify the Chrome repo signature: