| Summary: | The MD5 given for this download does not match | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Larry Matthias <lmatthias> |
| Component: | jee-package | Assignee: | Project Inbox <epp.packager-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | david_williams, mknauer, pwebster, remy.suen |
| Version: | 1.3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Larry Matthias
I would have thought it _should_ be computed on the gz file ... that is, computed on exactly what is downloaded. Is that not the case? Yes, the full contents of MD5 "file" mentions the gz file ... 0e6b7dc34a0891fe6d7d4356799d8100 eclipse-jee-helios-macosx-cocoa-x86_64.tar.gz ... so this is working as designed. Let us know if I've misunderstood, or if other sites use other conventions which we should consider. Yes, that works as designed - it is a checksum that is provided for the *file* which happens to be a tar.gz file. You can always check if it is valid with a simple mknauer@build:~/downloads/technology/epp/downloads/release/helios/R> md5sum -c eclipse-jee-helios-macosx-cocoa-x86_64.tar.gz.md5 eclipse-jee-helios-macosx-cocoa-x86_64.tar.gz: OK (given that you have both, the *.tar.gz file and the *.tar.gz.md5 file in the same directory) |