You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/05/27 18:36:21 UTC
[jira] Reopened: (MEV-536) Broken checksums and signature for
maven-2.0.7.pom
[ http://jira.codehaus.org/browse/MEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey reopened MEV-536:
----------------------------
Assignee: Jason van Zyl (was: John Casey)
do we need to correct the gpg signatures for these archives? If not, is this going to be an issue with your gpg information going forward?
> Broken checksums and signature for maven-2.0.7.pom
> --------------------------------------------------
>
> Key: MEV-536
> URL: http://jira.codehaus.org/browse/MEV-536
> Project: Maven Evangelism
> Issue Type: Bug
> Reporter: Max Bowsher
> Assignee: Jason van Zyl
>
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.7/maven-2.0.7.pom
> .md5 and .sha1 are broken due to being in incorrect format (generated by BSD checksum tools?)
> .asc is bad signature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira