You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/06/24 03:38:12 UTC
[jira] Closed: (MEV-663) Stale SHA1 hash causing problems for
commons-codec metadata
[ http://jira.codehaus.org/browse/MEV-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MEV-663.
----------------------------
Resolution: Fixed
Assignee: Brett Porter
I've fixed this at http://people.apache.org/repo/m2-ibiblio-rsync-repository/commons-codec/commons-codec/, as the .sha1 was not present there. It would have been synced if it had.
> Stale SHA1 hash causing problems for commons-codec metadata
> -----------------------------------------------------------
>
> Key: MEV-663
> URL: http://jira.codehaus.org/browse/MEV-663
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
> Reporter: SebbASF
> Assignee: Brett Porter
>
> The file:
> http://repo2.maven.org/maven2/commons-codec/commons-codec/maven-metadata.xml.sha1
> needs to be deleted, as it is out of date.
> It looks like this SHA hash was originally uploaded as .sha1, and is now .sha, so the old .sha1 hash was left behind instead of being overwritten.
> See listing:
> maven-metadata.xml 09-Aug-2009 22:30 396
> maven-metadata.xml.asc 09-Aug-2009 22:43 226
> maven-metadata.xml.md5 09-Aug-2009 22:42 34
> maven-metadata.xml.sha 09-Aug-2009 22:42 42
> maven-metadata.xml.sha1 09-Jul-2006 13:41 138
> Note the date of the .sha1 file.
--
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