Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 445309

Summary:	All eclipse-jee-luna-SR1-win32-x86_64.zip hashes are wrong on the Download site
Product:	Community	Reporter:	David Tesler <protobufel>
Component:	Cross-Project	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	P3	CC:	david_williams, denis.roy, shankhba
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows All
Whiteboard:

Description David Tesler

2014-09-29 03:58:26 EDT

All published hashes at least for eclipse-jee-luna-SR1-win32-x86_64.zip are wrong:

The published on the Download site sha512:
49fb3aba8531dd936894b247af57f2937dfe7db3756a58d8e029952a85d31e46fdc7abc088f4742c134fef8b1ae113c544df9274920382ae43031c2547d532a5

Real/calculated by me sha512:  
569170CB8DEA09CA94C5C8195A05A5A8174ED9B0746CF550DAC1E3C8FA227BC1057535217457AC4DF2234167F8346DE0660291D97FA22D0988CA633A294DEBDB

All others are different also; I've downloaded from 3 mirrors and from the Main Site!

I hope it is only wrong hashes!

Please fix ASAP!

Thanks in advance,
David

Comment 1 shankha banerjee

2014-09-29 04:01:28 EDT

Assigning it to Platform releng.

Comment 2 David Williams

2014-09-29 07:24:26 EDT

Moving to "infrastructure". 

I've confirmed, for win32-x86_64.zip

Website reports: 
49fb3aba8531dd936894b247af57f2937dfe7db3756a58d8e029952a85d31e46fdc7abc088f4742c134fef8b1ae113c544df9274920382ae43031c2547d532a5  eclipse-jee-luna-SR1-win32-x86_64.zip

As calculated after download: 

569170cb8dea09ca94c5c8195a05a5a8174ed9b0746cf550dac1e3c8fa227bc1057535217457ac4df2234167f8346de0660291d97fa22d0988ca633a294debdb  eclipse-jee-luna-SR1-win32-x86_64.zip

= = = = = = 

To "make things worse", I tried for linux x86_64: 

https://www.eclipse.org/downloads/sums.php?file=/technology/epp/downloads/release/luna/SR1/eclipse-jee-luna-SR1-linux-gtk-x86_64.tar.gz&type=sha512

Web site reports: 
nofile  eclipse-jee-luna-SR1-linux-gtk-x86_64.tar.gz

Comment 3 David Williams

2014-09-29 07:27:21 EDT

I've moved to "cross-project" for wide-spread visibility, 
but, I think the webmasters simply need to "flush the cache" of computed checksums. 

I'm pretty sure this happened simply because we had one set "ready to go" then decide at last minute to "respin" ... and for "final packages", the names are the same.

Comment 4 Denis Roy

2014-09-29 08:33:47 EDT

(In reply to David Williams from comment #3)
> I've moved to "cross-project" for wide-spread visibility, 
> but, I think the webmasters simply need to "flush the cache" of computed
> checksums. 
> 
> I'm pretty sure this happened simply because we had one set "ready to go"
> then decide at last minute to "respin" ... and for "final packages", the
> names are the same.

Indeed, this is a correct use case .. the files on disk were changed after the checksums were computed initially.

Since we have a perfectly valid explanation, I've reset them.