[
https://issues.apache.org/jira/browse/CASSANDRA-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064909#comment-16064909
]
Michael Shuler commented on CASSANDRA-13440:
--------------------------------------------
Basically, yes, it's the same method. It differs in that I'm using a Debian
machine and rpmsign is ignorant of how to deal with multiple gpg keys for the
same named ID (KeyID works), but essentially, yes, it is the same steps so
adding those to the readme is fine and can be adapted. Docker has barfed on me
in a few interesting ways, so I have not pushed the changes I made locally to
{{prepare_release.sh}}, since I'm completely clearing all docker instances to
start fresh and I hardcoded some paths. I don't want someone to rm all their
stuff, and I would also like to add some conditionals to fail early or not sign
and attempted to upload things, if there is no proper gpg key defined. I'll
keep cleaning those changes up and get them pushed, once I have some free time.
> Sign RPM artifacts
> ------------------
>
> Key: CASSANDRA-13440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13440
> Project: Cassandra
> Issue Type: Sub-task
> Components: Packaging
> Reporter: Stefan Podkowinski
> Assignee: Michael Shuler
> Fix For: 2.1.18, 2.2.10, 3.0.14, 3.11.0
>
>
> RPMs should be gpg signed just as the deb packages. Also add documentation
> how to verify to download page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
