[
https://issues.apache.org/jira/browse/CASSANDRA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515694#comment-15515694
]
Sylvain Lebresne commented on CASSANDRA-12239:
----------------------------------------------
bq. Updated wiki page https://wiki.apache.org/cassandra/DebianPackaging
Thanks, but we should probably consider explicitly marking that page obsolete
and redirecting to the
http://cassandra.apache.org/doc/latest/getting_started/installing.html#installation-from-debian-packages
page. No point in having to update 2 places every time we have a change to
make.
bq. I'll have to go dig around the docs source to find where to update
You'll have to discover the joys of the svn. But basically, you need to
checkout https://svn.apache.org/repos/asf/cassandra/site/, and read the
{{README}} file in the {{src}} directory.
> Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
> -------------------------------------------------
>
> Key: CASSANDRA-12239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
> Reporter: Michael Shuler
> Assignee: Michael Shuler
> Priority: Blocker
> Fix For: 3.8
>
> Attachments: KEYS+mshuler.diff.txt
>
>
> I've started working on packaging with the 3.8 release and signed the staging
> artifacts with FE4B2BDA. This key will need to be added for the debian
> repository signature to function correctly, if it's released as-is, or
> perhaps [~tjake] will need to re-sign the release. Users will need to also
> fetch this new key and add to {{apt-key}}.
> {{KEYS}} patch attached.
> Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn
> somewhere or a direct upload? :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
