Jukka,
I get:
> md5 mahout-0.1-project.tar.gz
MD5 (mahout-0.1-project.tar.gz) = f7341a0eb773d9f96ea87914f3c845dc
>cat mahout-0.1-project.tar.gz.md5
f7341a0eb773d9f96ea87914f3c845dc
> cat mahout-0.1-project.tar.gz.sha1
5c84eb607c07119aceb1f3824e38205474dabc08
> openssl sha1 mahout-0.1-project.tar.gz
SHA1(mahout-0.1-project.tar.gz)=
5c84eb607c07119aceb1f3824e38205474dabc08
Am I doing something wrong? Seems like everything is right. This
stuff is all done automatically by Maven. I downloaded those files
today from http://people.apache.org/~gsingers/staging-repo/mahout/org/apache/mahout/mahout/0.1/
-Grant
On Mar 30, 2009, at 12:53 PM, Jukka Zitting wrote:
Hi,
On Sat, Mar 28, 2009 at 11:49 AM, Grant Ingersoll
<[email protected]> wrote:
Please review and vote for releasing Mahout 0.1.
-1 I'm getting conflicting checksums for the mahout-0.1-project.tar.gz
package that I'm using to review the sources. The checksums of my
download are:
MD5: f7341a0eb773d9f96ea87914f3c845dc
SHA1: 5c84eb607c07119aceb1f3824e38205474dabc08
But the .md5 and .sha1 files claim the following:
MD5: 46fd344aa6e88b7943e988dddaccd121
SHA1: 5b8bd6840718d2546b93656a3cc1528e7dfda75d
I'm still getting test errors on Windows, but now I also built the
release candidate on my Linux desktop where Mahout core passes all
tests. Note however the issues MAHOUT-112 and MAHOUT-113 which I
encountered in the taste-web and examples modules.
Other than those the release looks good. Thanks for resolving some of
the issues I raised earlier. I'd be willing to vote +1 even without a
new release candidate if the checksum issues can be tracked down and
fixed. The PGP signatures seem to be correct.
BR,
Jukka Zitting
