I agree that would be great.
Meanwhile, I am using this script/command to achieve the same result:
for a in 1 256 512; do
for f in `find . -type f -name "*.sha${a}"`; do
claim=`cat $f |cut -d' ' -f1`;
actual=`shasum ${f%.sha*} -a ${a} |cut -d' ' -f1`;
if [[ "$claim" == "$actual" ]];
That would be great.
Gary
On Wed, Dec 29, 2021, 12:54 Matt Sicker wrote:
> The SHA files are generated via a Maven plugin that only outputs the hash,
> not the filename. Looks like we need to figure out how to configure that.
> --
> Matt Sicker
>
> > On Dec 29, 2021, at 02:53, Volkan Yazıcı wr
The SHA files are generated via a Maven plugin that only outputs the hash, not
the filename. Looks like we need to figure out how to configure that.
--
Matt Sicker
> On Dec 29, 2021, at 02:53, Volkan Yazıcı wrote:
>
> Certain hash files are not properly formatted (see below), can we (I?) fix
>
Certain hash files are not properly formatted (see below), can we (I?) fix
this?
wget \
--quiet \
--execute robots=off \
--timestamping \
--cut-dirs=7 \
--no-host-directories \
--recursive \
--page-requisites \
--no-parent \
--no-check-certificate \
https://dist.apache.org/repo
