Item14413: Incorrect checksum from downloads on website for 2.1.4

# cat Foswiki-upgrade-2.1.4.md5
d25c04f32b9d444078d058938341bd9a  Foswiki-2.1.4.tgz
4f9eaae1d42dc825387ac1892b96e821  Foswiki-2.1.4.zip
4bb06e31f728d5d09391eea9f6e1238c  Foswiki-upgrade-2.1.4.tgz
2ae082eae4ef4f78b50d471ebbbdbd5f  Foswiki-upgrade-2.1.4.zip
# cat Foswiki-2.1.4-vmware.md5
ef69ce45aa082bfbb2c1fb3831b604e5  Foswiki-2.1.4-vmware.7z

# md5 Foswiki-upgrade-2.1.4.tgz
MD5 (Foswiki-upgrade-2.1.4.tgz) = 008c1efa74af9a57adf3502e3a8a4fb6
# md5 Foswiki-upgrade-2.1.4.zip
MD5 (Foswiki-upgrade-2.1.4.zip) = 0e5fa9c6b51e95624810835756035c07
# md5 Foswiki-2.1.4.zip
MD5 (Foswiki-2.1.4.zip) = 5732cb5ac799e71809652c54724e1a8e
# md5 Foswiki-2.1.4.tgz
MD5 (Foswiki-2.1.4.tgz) = 9150a1e4891961c9ac4f8df06bc5db51
# md5 Foswiki-2.1.4-vmware.7z
MD5 (Foswiki-2.1.4-vmware.7z) = ef69ce45aa082bfbb2c1fb3831b604e5

Tested with Tenet and Pilot Sourceforge mirrors.

Foswiki-2.1.4-vmware.7z is the only file with a matching checksum

-- ManasB - 03 Jun 2017

I had a very minor build error when I first built 2.1.4 - The VERSION string was 2.1.3_0004 instead of 2.1.4 - the rollover from an "alpha" numbering to the release didn't happen. We rebuilt all of the files and vmware image using the updated version. There were no other changes other than some random number generated anchor tags in the root HTML files.

It appears that while the whole release was uploaded, that one file didn't make it to Sourceforge. The file on https://github.com/foswiki/distro/releases/tag/FoswikiRelease02x01x04 is correct. The correct checksums are:

cat Foswiki-2.1.4.md5
9150a1e4891961c9ac4f8df06bc5db51  Foswiki-2.1.4.tgz
5732cb5ac799e71809652c54724e1a8e  Foswiki-2.1.4.zip
008c1efa74af9a57adf3502e3a8a4fb6  Foswiki-upgrade-2.1.4.tgz
0e5fa9c6b51e95624810835756035c07  Foswiki-upgrade-2.1.4.zip

The files Foswiki-upgrade-2.1.4.sha1 and Foswiki-upgrade-2.1.4.md5 are out of date. But the files Foswiki-2.1.4.md5 and Foswiki-2.1.4.sha1 have the correct contents. I've rerun the upload, but it will take a while for the updates to propagate in the sourceforge network. Thanks for pointing out the issue.

Closing this as resolved. If you still see an issue or if you have any troubles using the non-upgrade version of the md5/sha1 files, please reopen the task.

-- Main.GeorgeClark - 03 Jun 2017 - 06:28