You beet me to that. I verified myself as well and the digests are bad, both md5 and sha1. The asc looks good.
Here's what I used for builds: pebble:target hadrian$ mvn -version Apache Maven 2.2.0 (r788681; 2009-06-26 09:04:01-0400) Java version: 1.5.0_22 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x" version: "10.6.2" arch: "i386" Family: "unix" I intend to keep the tag and re-release off of the tag unless there is an objection. Hadrian On Feb 10, 2010, at 9:18 AM, Guillaume Nodet wrote: > -1 > The md5 are all wrongs, i haven't chedked the asc and sha1, but i > suppose they're bad too. > We need to re-upload a release. Hadrian, did you use maven 2.1 by any > chance ? That one is known to produce bad checksums ... > > On Mon, Feb 8, 2010 at 15:20, Hadrian Zbarcea <hzbar...@gmail.com> wrote: >> A new release apache-camel-2.2.0 is out with approximately 180 issues >> resolved: new features, improvements and bug fixes. >> >> Please find the staging repo here: >> https://repository.apache.org/content/repositories/orgapachecamel-007/ >> The tarballs are here >> https://repository.apache.org/content/repositories/orgapachecamel-007/org/apache/camel/apache-camel/2.2.0/ >> >> Please review and vote to approve this release binary >> >> [ ] +1 Release the binary as Apache Camel 2.2.0 >> [ ] -1 Veto the release (provide specific comments) >> Vote is open for 72 hours. >> >> Here's my +1 >> >> Hadrian > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com
