[SPARK-44168][FOLLOWUP] Change v3.4 GPG_KEY to full key fingerprint#50
Closed
Yikun wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-44168][FOLLOWUP] Change v3.4 GPG_KEY to full key fingerprint#50Yikun wants to merge 1 commit intoapache:masterfrom
Yikun wants to merge 1 commit intoapache:masterfrom
Conversation
9 tasks
Member
Author
Member
Author
|
It only effect on docker image build process (gpg verify process), consider CI already has passed, I will merge this soon to let DOI review. Please let me know if you have more concern. |
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
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.
What changes were proposed in this pull request?
Change GPG key from
34F0FC5CtoF28C9C925C188C35E345614DEDA00CE834F0FC5Cto avoid pontential collision.The full finger print can get from below cmd:
Why are the changes needed?
34F0FC5Cis from https://dist.apache.org/repos/dist/dev/spark/KEYSthis should be the full key fingerprint: F28C9C925C188C35E345614DEDA00CE834F0FC5C (generating a collision for such a short key ID is trivial.Does this PR introduce any user-facing change?
No
How was this patch tested?
CI passed