[jbosstools-issues] [JBoss JIRA] (JBIDE-13832) MD5 sometimes not correct
[
https://issues.jboss.org/browse/JBIDE-13832?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-13832.
--------------------------------
Resolution: Cannot Reproduce Bug
Cannot reproduce.
a) manually produced md5sum, via commandline:
{code}
$➔ md5sum jbosstools-hibernate_master-Sources-SNAPSHOT.zip
4ec4339098d205926e12336478ef93f4 jbosstools-hibernate_master-Sources-SNAPSHOT.zip
$➔ md5sum jbosstools-hibernate_master-Update-SNAPSHOT.zip
773d2cd9e67043e3eb548111cbe82af7 jbosstools-hibernate_master-Update-SNAPSHOT.zip
{code}
b) value in the .MD5 files:
{code:title=http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_master/all/jbosstools-hibernate_master-Sources-SNAPSHOT.zip.MD5}
4ec4339098d205926e12336478ef93f4
{code}
{code:title=http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_master/all/jbosstools-hibernate_master-Update-SNAPSHOT.zip.MD5}
773d2cd9e67043e3eb548111cbe82af7
{code}
c) value in the md5sums.txt file:
{code:title=http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_master/logs/md5sums.txt}
4ec4339098d205926e12336478ef93f4 ./all/jbosstools-hibernate_master-Sources-SNAPSHOT.zip
773d2cd9e67043e3eb548111cbe82af7 ./all/jbosstools-hibernate_master-Update-SNAPSHOT.zip
{code}
Please re-open if you can show me a specific example of where md5sums don't match.
MD5 sometimes not correct
-------------------------
Key: JBIDE-13832
URL: https://issues.jboss.org/browse/JBIDE-13832
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Priority: Critical
Fix For: 4.1.0.CR1
If you look for instance at this repo:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_... ,
you'll notice that the .MD5 files contains string that don't match the actual
files md5 checksum, which is accurate in the log files (checksum.txt).
This is most likely an issue in the publish script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira