I see. Looks like we are not the only one that's missing the tar ball
signatures. HBase release on mirrors also doesn't come with tar ball
signatures, see http://apache.claz.org/hbase/hbase-1.0.3/ (
https://www.apache.org/dist/hbase/hbase-1.0.3/ for compare.).
On Mon, Dec 12, 2016 at 2:47 PM, Flav
That's not what we have in dis.apache.org:
zookeeper-3.5.2-alpha fpj$ ls
zookeeper-3.5.2-alpha.tar.gzzookeeper-3.5.2-alpha.tar.gz.md5
zookeeper-3.5.2-alpha.tar.gz.asczookeeper-3.5.2-alpha.tar.gz.sha1
The ones in the tar ball are for the jar only.
-Flavio
> On 12 Dec 2016, at
Hi Flavio,
Do you have a link to a problematic RC build? I just checked the mirrors
and it looks like the signature files are included as part of release tar
ball. An example: http://apache.claz.org/zookeeper/zookeeper-3.5.2-alpha/
where the tar ball file
includes zookeeper-3.5.2-alpha.jar.asc, zo
I was checking the Apache mirrors and our releases do not seem to have the
typical MD5 and SHA1 digests that we check for the release candidates. What's
going on here, have we not been publishing those as part of releasing?
http://www.apache.org/dyn/closer.cgi/zookeeper/
-Flavio
