-
Notifications
You must be signed in to change notification settings - Fork 140
Bintray consistently providing distribution with incorrect checksum #132
Comments
As a note, the most concerning thing about this is that the distribution from the giant Download button goes exclusively to bintray. |
Wow, I hadn't spotted that before. Normally, the zips and checksums should be identical regardless of whether you download them from Apache or Bintray, e.g. do your experiment with 2.4.14 and you will see they are the same. For 2.4.15 I had a disk crash midway through the release and for e.g. 2.6.0-alpha-3, Daniel was the release manager but had troubles with one step, so I did one step from my machine. In both cases, we slipped up - a zip with identical contents but different timestamps was loaded in each case. Short-term please check Apache zips against the Apache checksum and Bintray zips against the Bintray checksum (just append ".sha256" to the bintray zips url). I'll see if we can't get things rectified in the meantime. |
Note that Apache Groovy is doing two things wrong here apart from the mismatched zips.
|
Hi Gav, not sure what akamai.bintray.com is, we have a special groovy account for bintray. Is there some doco on how to access the apache one somewhere? |
I'll close this since we identified and fixed what was causing the checksum errors. |
As noted in the title, I've downloaded multiple distributions from bintray and all did not match the checksum...
The text was updated successfully, but these errors were encountered: