[
https://issues.apache.org/jira/browse/HADOOP-16494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927260#comment-16927260
]
Christopher Tubbs commented on HADOOP-16494:
--------------------------------------------
[~rohithsharma] While that isn't a new thing, it is probably still going to be
a source of frustration, since it is very unlikely that whoever is verifying
the file is going to be doing so in a path that beings with
{{/build/source/target}}, and therefore, it might be a good idea to address
this in a new issue. Do you think?
> Add SHA-256 or SHA-512 checksum to release artifacts to comply with the
> release distribution policy
> ---------------------------------------------------------------------------------------------------
>
> Key: HADOOP-16494
> URL: https://issues.apache.org/jira/browse/HADOOP-16494
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Akira Ajisaka
> Assignee: Akira Ajisaka
> Priority: Blocker
> Fix For: 2.10.0, 3.3.0, 2.8.6, 3.2.1, 2.9.3, 3.1.3
>
>
> Originally reported by [~ctubbsii]:
> https://lists.apache.org/thread.html/db2f5d5d8600c405293ebfb3bfc415e200e59f72605c5a920a461c09@%3Cgeneral.hadoop.apache.org%3E
> bq. None of the artifacts seem to have valid detached checksum files that are
> in compliance with https://www.apache.org/dev/release-distribution There
> should be some ".shaXXX" files in there, and not just the (optional) ".mds"
> files.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
