I think people can create tasks here: http://jira.codehaus.org/browse/MAVENUPLOAD
or at Sonatype: https://issues.sonatype.org/browse/OSSRH On Thu, Apr 29, 2010 at 4:12 PM, sebb <seb...@gmail.com> wrote: > OK thanks very much. > > If this problem recurs with other projects, is there a formal means of > reporting it? > e.g. via an issue tracker? > > On 29/04/2010, Juven Xu <ju...@sonatype.com> wrote: > > checksums on pgp signautes are deleted. > > > > > > On Wed, Apr 28, 2010 at 11:34 PM, sebb <seb...@gmail.com> wrote: > > > > > On 28/04/2010, Juven Xu <ju...@sonatype.com> wrote: > > > > On Wed, Apr 28, 2010 at 11:05 PM, sebb <seb...@gmail.com> wrote: > > > > > > > > > On 28/04/2010, Juven Xu <ju...@sonatype.com> wrote: > > > > > > you can use these shell scripts: > > > > > > > > > > > > find . -type f | xargs -i sh -c 'sha1sum {} | cut -d " " -f1 > > > > {}.sha1' > > > > > > find . -type f | xargs -i sh -c 'md5sum {} | cut -d " " -f1 > > > > {}.md5' > > > > > > > > > > Thanks, I have already created the fixed hashes. > > > > > > > > > > [BTW, the find command above needs to be changed, otherwise it > will > > > > > create md5 hashes for the sha1 hashes it has just created. Also, > not > > > > > all versions of xargs support the -i flag. Nor are sha1sum and > md5sum > > > > > universally available.] > > > > > > > > > > > > > > > > > yes, assume xargs -i , sha1sum, md5sum is supported: > > > > > > > > find . -type f | grep -e 'md5$' -e 'sha1$' -v | xargs -i sh -c > 'sha1sum > > > {} | > > > > cut -d " " -f1 > {}.sha1' > > > > > > > > > > Which will still create hashes for .asc files... > > > > > > > > > > > > > > > > > > release artifacts and their hashes in central will never be > updated > > > > > unless > > > > > > manual fix is needed. > > > > > > > > > > So how does the Nexus solution work if manual intervention is > > > required? > > > > > > > > > > > > > > > > > It's central, has nothing to do with Nexus, currently I will fix any > > > central > > > > artifacts problem > > > > > > > > > > > > > > > > > > > > > > > if your artifacts' hashes in central are incorrect, tell me > what > > > are > > > > > them so > > > > > > I can fix. > > > > > > > > > > The problem is with commons-compress-1.0: > > > > > > > > > > > > > > http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/ > > > > > > > > > > e.g. > > > > > > > > > > commons-compress-1.0-bin.tar.gz.md5: > > > > > commons-compress-1.0-bin.tar.gz: F8 F0 2E 1E AC 08 37 7D 75 14 > CB 94 > > > 87 AF > > > > > E2 > > > > > C9 > > > > > > > > > > All the other hashes have the wrong syntax too. > > > > > > > > > > > > > > > > > fixed > > > > > > > > > > Thanks, but you have also created unnecessary hashes for the .asc > files. > > > Please can those be deleted? > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Apr 28, 2010 at 10:12 PM, sebb <seb...@gmail.com> > wrote: > > > > > > > > > > > > > On 26/04/2010, sebb <seb...@gmail.com> wrote: > > > > > > > > What is the recommended procedure for fixing hash files in > a > > > Maven > > > > > > > > repo that have the wrong syntax? > > > > > > > > > > > > > > I have seen the reply about using Nexus, but if the project > does > > > not > > > > > > > use Nexus, what is the procedure? > > > > > > > > > > > > > > If I update the hashes in the release repo will these be > > > propagated to > > > > > > > the central repo? > > > > > > > And is that procedure permitted by the central repo rules? > > > > > > > > > > > > > > > For example: > > > > > > > > > > > > > > > > file.tar.gz.sha1: > > > > > > > > file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB > 52F3 > > > > > > > > 3B4C > > > > > > > > > > > > > > > > The hash is correct, but not all tools can process the > hash > > > when it > > > > > is > > > > > > > > split over two lines and has spaces in the hex string. > > > > > > > > > > > > > > > > > > > > > > > > Any advice on how best to fix this? > > > > > > > > Can I just replace the hash files in the Apache release > > > repository > > > > > > > > with the fixed versions? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > - juven > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > > > > > > > > > -- > > > > - juven > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > -- > > - juven > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - juven
