[
https://issues.apache.org/jira/browse/CASSANDRA-21346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078710#comment-18078710
]
Brandon Williams commented on CASSANDRA-21346:
----------------------------------------------
Well that is strange, I'm doing it the same way:
{noformat}
cassandra$ patch -p1 < KEYS.patch
patching file KEYS
Hunk #2 FAILED at 4395.
1 out of 2 hunks FAILED -- saving rejects to file KEYS.rej
{noformat}
KEYS.rej is the new addition, and if I try to use wiggle on that it leaves me
with a conflict, and that's the point where I gave up.
> Update aber's gpg key in project's KEYS file
> --------------------------------------------
>
> Key: CASSANDRA-21346
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21346
> Project: Apache Cassandra
> Issue Type: Task
> Components: Packaging
> Reporter: Abe Ratnofsky
> Assignee: Brandon Williams
> Priority: Normal
> Attachments: KEYS.patch
>
>
> I had some issues with my prior key (CASSANDRA-20981), so trying again. This
> removes my previous ed25519 key, matches rsa4096 keys from others doing
> releases.
> The patch adds my gpg public key to the project's KEYS file found at
> [https://dist.apache.org/repos/dist/release/cassandra/KEYS]
> My gpg public key here has the fingerprint
> F43BD1DCA7D5F5AFF5BBEC1EA4B9C195907CB45B
> References:
> - [https://www.apache.org/dev/release-signing#keys-policy]
> - [http://www.apache.org/legal/release-policy.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
