[
https://issues.apache.org/jira/browse/HADOOP-16494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927236#comment-16927236
]
Rohith Sharma K S commented on HADOOP-16494:
--------------------------------------------
[~aajisaka] I created release artifacts for 3.2.1 and trying to verify sha512.
I see below error
{noformat}
rohithsharmaks@ip-172-31-38-26:~/branch-3.2.1/target/artifacts$ sha512sum -c
CHANGELOG.md.sha512
sha512sum: /build/source/target/artifacts/CHANGELOG.md: No such file or
directory
/build/source/target/artifacts/CHANGELOG.md: FAILED open or read
sha512sum: WARNING: 1 listed file could not be read
{noformat}
When sha512 is created, it is taking entire folder path into account because
*"${i}"* is entire folder patch.
{noformat}
for i in ${ARTIFACTS_DIR}/*; do
${GPG} --use-agent --armor --output "${i}.asc" --detach-sig "${i}"
sha512sum --tag "${i}" > "${i}.sha512"
done
{noformat}
Is this expected? or need fix to consider only file name. How was earlier md5
was running?
> 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: [email protected]
For additional commands, e-mail: [email protected]
