[
https://issues.apache.org/jira/browse/LUCENE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138898#comment-16138898
]
Hoss Man commented on LUCENE-7935:
----------------------------------
i didn't test it, but skimming the patch the changes seem fine ... assuming
we're ok w/removing support for doing ref-guide releases on machines that don't
have {{shasum}} ... i assume that's fine? IIRC the problem we've had in the
past was the opposite: that some OSs/distros didn't provide {{sha1sum}}.
[~ctargett]: you tend to do most of the ref guide releases, do these commands
work for you (and produce the same output) on your dev machine...
{noformat}
$ echo "anything" | shasum -a 512
b64baad7af53a75d3cebec373cadc509b09be85199996844402f4f2d74355f9ef4488015d130f9d3874c09381daa9bca98452e6822a81b1a6cd4baeef356a781
-
$ echo "anything" | shasum
86b18486b5d0b47d7e6173dc2d90d6c9958518f3 -
{noformat}
If so then we're probably fine.
> Release .sha512 hash files with our artifacts
> ---------------------------------------------
>
> Key: LUCENE-7935
> URL: https://issues.apache.org/jira/browse/LUCENE-7935
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Jan Høydahl
> Attachments: LUCENE-7935.patch
>
>
> Currently we are only required to release {{.md5}} hashes with our artifacts,
> and we also include {{.sha1}} files. It is expected that {{.sha512}} will be
> required in the future (see
> https://www.apache.org/dev/release-signing.html#sha1), so why not start
> generating them right away?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
