maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Max Bowsher (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MEV-536) Broken checksums and signature for maven-2.0.7.pom
Date Thu, 02 Aug 2007 13:22:13 GMT

    [ http://jira.codehaus.org/browse/MEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103861
] 

Max Bowsher commented on MEV-536:
---------------------------------

Is there any problem preventing this from being fixed?

AFAICS, it is just a simple job of regenerating the .md5 and .sha1 files correctly, and deleting
the .asc file.

Any investigation into why the checksums are broken should not require that the checksums
remain broken in the live repository, surely?

> 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

        

Mime
View raw message