Sorry Bowen for the delay.I'm looking into this , I never tried that.
Regards,Mohammad
On Monday, November 17, 2014 9:58 AM, bowen zhang
<[email protected]> wrote:
Hi Mohammad,I think the KEY issue is the reason Mona has problem signing the
page since I cannot commit my key to the repo. Can you resolve this
ASAP?Thanks,Bowen
From: Mona Chitnis <[email protected]>
To: "[email protected]" <[email protected]>; bowen zhang
<[email protected]>
Sent: Monday, November 17, 2014 9:15 AM
Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
Downloaded the tarball, built and installed Oozie (-DskipTests) and ran an
example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
Was unable to verify the md5 and gpg signatures. I dont find the key used for
signing the page in the list of public keys on the KEYS page. Please let me
know if I'm missing the right procedure.
Regards, Mona Chitnis
On Monday, November 17, 2014 8:08 AM, Shwetha GS <[email protected]>
wrote:
+1
On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
[email protected]> wrote:
> Hi,
>
> I have created a build for Oozie 4.1.0, candidate 1.
>
> Keys to verify the signature of the release artifact are available at
>
> http://www.apache.org/dist/oozie/KEYS
>
> Please download, test, and try it out:
>
> http://people.apache.org/~bzhang/oozie-4.1.0-rc1
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
> Vote closes on Monday EOD, the 17th.
>
> Bowen
>
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.
