[
https://issues.apache.org/jira/browse/UIMA-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555343#action_12555343
]
Marshall Schor commented on UIMA-677:
-------------------------------------
I found these utilities on Linux (Suse 10) and Windows (via Cygwin): sha1sum
and md5sum.
For signing the Eclipse update site (all "jars" need to be signed - since
they're archives) I wrote a small shell script. I also wrote one to
automatically check the signatures.
If you put gpg into the path, the scripts should work. I'll check them into
SVN. I would suggest they be combined with the other signing script, and the
other signing script altered to use the sha1sum/md5sum utilities.
> improve MD5 and SHA1 checksum generation
> ----------------------------------------
>
> Key: UIMA-677
> URL: https://issues.apache.org/jira/browse/UIMA-677
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Reporter: Michael Baessler
>
> Comes up on the incubator mailing list:
> There are some problems with the MD5 and SHA1 files.
> For example, uimaj-2.2.1-incubating-bin.tar.bz2.md5:
> ================
> uimaj-2.2.1-incubating-bin.tar.bz2: 53 20 6A FB 75 1F 07 9D BB 12 82 58 D0 7D
> CA 4B
> ================
> The hash is spread over two lines and into hex pairs. The normal
> format is either:
> 53206afb751f079dbb128258d07dca4b
> or
> 53206afb751f079dbb128258d07dca4b *uimaj-2.2.1-incubating-bin.tar.bz2
> The SHA1 checksums have the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
