Will try this on Linux, on Mac there's curl instead of wget.

At one point the artifact upload timed out, we have a few large ones, so I had 
to restart release:perform. That may be an explanation.

Hadrian




On Feb 9, 2010, at 4:30 AM, Gert Vanthienen wrote:

> L.S.,
> 
> For Felix and ServiceMix, we have a script to validate the
> signatures/hashes in a staged release.  I have created a similar
> script for Camel in
> http://svn.apache.org/viewvc/camel/scripts/check_camel_release.sh.
> 
> It does report problems with the SHA/MD5 hashes in the uploaded
> release candidate (tried running it as check_camel_release 007).  I've
> also tried validating the files manually, but that still gives me
> different hash values, but I'm not an expert on these things so
> perhaps I'm missing something or doing things wrong.
> 
> g...@pantoef:/tmp/camel-staging/007/org/apache/camel/camel-core/2.2.0$
> for f in *.jar; do echo "`cat $f.md5` <-> `md5sum $f`"; done;
> 4222e0cf273b1f0c5d0c0e726b3a0f4d <-> 45c4c6d2469832e648b6e1fafe3a3330
> camel-core-2.2.0.jar
> 0367eb9ba508638e0cea22fac160283c <-> 4634a859faf50d6d1284b02206fc7bd8
> camel-core-2.2.0-javadoc.jar
> afbdb070cc55bfa0373843630dcedd5d <-> 88fb8f7c49260435e29cba525a164762
> camel-core-2.2.0-sources.jar
> b5856cf16623249153c3372b45fa61d8 <-> 4e2be691ff30ffd66c8ee9179f842b72
> camel-core-2.2.0-tests.jar
> 
> Is anyone else seeing these problems?
> 
> Regards,
> 
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
> 
> 
> 
> On 9 February 2010 07:36, Claus Ibsen <claus.ib...@gmail.com> wrote:
>> Hi
>> 
>> camel-gae was missing LICENSE.txt in the -source .jar (eg not in
>> src/main/resources/META-INF)
>> I have committed the needed files to trunk.
>> 
>> 
>> 
>> On Sun, Feb 7, 2010 at 7:49 AM, Hadrian Zbarcea <hzbar...@gmail.com> wrote:
>>> Hi,
>>> 
>>> The Apache Camel 2.2.0 Release Candidate is built and available at [1]. The 
>>> only issue I noticed is the missing pdf manual due to a http 502 during the 
>>> release:perform phase after building fine in previous builds. I don't think 
>>> this is a blocker, I will upload it manually, but I need to find a more 
>>> reliable way of generating/deploying it.
>>> 
>>> I will start a vote tomorrow, after a more thorough test of this release 
>>> candidate.  Many thanks to all the contributors!
>>> Hadrian
>>> 
>>> [1] https://repository.apache.org/content/repositories/orgapachecamel-007/
>> 
>> 
>> 
>> --
>> Claus Ibsen
>> Apache Camel Committer
>> 
>> Author of Camel in Action: http://www.manning.com/ibsen/
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>> 

Reply via email to