You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/01/02 18:21:33 UTC
[jira] Commented: (UIMA-677) improve MD5 and SHA1 checksum
generation
[ 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.
Re: [jira] Commented: (UIMA-677) improve MD5 and SHA1 checksum generation
Posted by Marshall Schor <ms...@schor.com>.
Marshall Schor wrote:
> Marshall Schor wrote:
>
>> Hi Thilo -
>>
>> I forgot about that email trail :-) The Eclipse update site is created
>> using an ant build script. Is there a way to make the poms work for these?
>> That would be nicer than more build scripts.
>>
>>
> Looking at the pom xml more carefully, I'm guessing it could be modified
> to create sha1 and md5 for the eclipse update site.
> I'll give it a try...
>
Adding these lines in the checksum task to Thilo's pom version for
uimaj-distr worked:
<fileset
dir="../uimaj-eclipse-update-site/target/features">
<include name="*.jar" />
</fileset>
<fileset
dir="../uimaj-eclipse-update-site/target/plugins">
<include name="*.jar" />
</fileset>
I'll check in these changes to the uimaj-distr pom. We still need to
add signing of eclipse update site jars. I'll take a look at that.
-Marshall
> -Marshall
>
>> -Marshall
>>
>> Thilo Goetz wrote:
>>
>>
>>> Marshall,
>>>
>>> how does this relate to this mail trail:
>>> http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg05057.html
>>>
>>> --Thilo
>>>
>>> Marshall Schor (JIRA) wrote:
>>>
>>>
>>>
>>>> [ 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.
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>
Re: [jira] Commented: (UIMA-677) improve MD5 and SHA1 checksum generation
Posted by Marshall Schor <ms...@schor.com>.
Marshall Schor wrote:
> Hi Thilo -
>
> I forgot about that email trail :-) The Eclipse update site is created
> using an ant build script. Is there a way to make the poms work for these?
> That would be nicer than more build scripts.
>
Looking at the pom xml more carefully, I'm guessing it could be modified
to create sha1 and md5 for the eclipse update site.
I'll give it a try...
-Marshall
> -Marshall
>
> Thilo Goetz wrote:
>
>> Marshall,
>>
>> how does this relate to this mail trail:
>> http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg05057.html
>>
>> --Thilo
>>
>> Marshall Schor (JIRA) wrote:
>>
>>
>>> [ 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.
>>>>
>>>>
>>
>>
>>
>
>
>
>
Re: [jira] Commented: (UIMA-677) improve MD5 and SHA1 checksum generation
Posted by Marshall Schor <ms...@schor.com>.
Hi Thilo -
I forgot about that email trail :-) The Eclipse update site is created
using an ant build script. Is there a way to make the poms work for these?
That would be nicer than more build scripts.
-Marshall
Thilo Goetz wrote:
> Marshall,
>
> how does this relate to this mail trail:
> http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg05057.html
>
> --Thilo
>
> Marshall Schor (JIRA) wrote:
>
>> [ 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.
>>>
>
>
>
>
Re: [jira] Commented: (UIMA-677) improve MD5 and SHA1 checksum generation
Posted by Thilo Goetz <tw...@gmx.de>.
Marshall,
how does this relate to this mail trail:
http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg05057.html
--Thilo
Marshall Schor (JIRA) wrote:
> [ 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.
>