On 15.09.2015 12:44, Greg Stein wrote:
> On Tue, Sep 15, 2015 at 10:11:47AM +0000, Grierson, David wrote:
>>> From: wolfgang.ztoeg_at_web.de [mailto:wolfgang.ztoeg_at_web.de]
>>>
>>> http://subversion.apache.org/download.cgi#supported-releases:
>>> subversion-1.9.1.tar.bz2 2ba78f59b3669e461ef6f56326426918100e2073
>>>
>>> but sha1sum gives: 1244a741dbcf24f2b1d165225f0159a0c994e37a subversion-
>>> 1.9.1.tar.bz2
>>>
>>> all 1.9.1 files, different mirrors checked, yesterday and now.
>> Published:
>>
>> subversion-1.9.1.tar.bz2 2ba78f59b3669e461ef6f56326426918100e2073
>> subversion-1.9.1.tar.gz 59958ee5e112a242c37d829331dde38affe2337a
>> subversion-1.9.1.zip 5073ed3e5c449d4abb96dcb5eca9204611bf9e5b
>>
>> Actual (from mirror.catn.com):
>>
>> subversion-1.9.1.tar.bz2 1244a741dbcf24f2b1d165225f0159a0c994e37a
>> subversion-1.9.1.tar.gz db79ba6a563faf4092854f89618cfc52a2662a8f
>> subversion-1.9.1.zip 1427e52979097a316a392238f9806b14af1ec6b4
> These three (correct/actual) checksums were in the release
> announcement email. So it looks like some kind of breakdown between
> the announcement and the website update. We have scripts to perform
> these various steps. Maybe something broke down, or didn't get
> executed correctly. We'll review.
My mistake ... I forgot to update the hashes when I made the other site
updates after 1.9.1. Even worse, I actually noticed the problem but
forgot to follow up. :(
The actual .sha1 files should contain the correct hashes.
-- Brane
Received on 2015-09-15 13:11:27 CEST