Hi Kevin, On Tue, Feb 26, 2019 at 06:27:30AM +0000, Kevin Mao wrote: > Hi haproxy@, > > It seems like the sha256 checksum's are wrong for the latest 1.8 and 1.9 > HAProxy versions, Can you please confirm? > https://www.haproxy.org/download/1.9/src/, > $ shasum -a 256 -c haproxy-1.9.4.tar.gz.sha256haproxy-1.9.4.tar.gz: > FAILEDshasum: WARNING: 1 computed checksum did NOT match > $ shasum -a 256 -c haproxy-1.9.3.tar.gz.sha256haproxy-1.9.3.tar.gz: > FAILEDshasum: WARNING: 1 computed checksum did NOT match > $ shasum -a 256 -c haproxy-1.8.19.tar.gz.sha256haproxy-1.8.19.tar.gz: > FAILEDshasum: WARNING: 1 computed checksum did NOT match > $ shasum -a 256 -c haproxy-1.8.18.tar.gz.sha256haproxy-1.8.18.tar.gz: > FAILEDshasum: WARNING: 1 computed checksum did NOT match
It's not what I'm seeing here using the sha256sum utility : $ cat haproxy-1.9.4.tar.gz.sha256 8483fe12b30256f83d542b3f699e165d8f71bf2dfac8b16bb53716abce4ba74f haproxy-1.9.4.tar.gz $ sha256sum haproxy-1.9.4.tar.gz 8483fe12b30256f83d542b3f699e165d8f71bf2dfac8b16bb53716abce4ba74f haproxy-1.9.4.tar.gz $ sha256sum -c haproxy-1.9.4.tar.gz.sha256 haproxy-1.9.4.tar.gz: OK OpenSSL agrees with it : $ openssl sha256 haproxy-1.9.4.tar.gz SHA256(haproxy-1.9.4.tar.gz)= 8483fe12b30256f83d542b3f699e165d8f71bf2dfac8b16bb53716abce4ba74f So I suspect that you're facing a download issue or your shasum fails for whatever reason. The file above is 2357935 bytes long here. Please check that matches on your side. thanks, Willy
