Re: Changing how we compute release hashes

2018-03-23 Thread Nicholas Chammas
.com> >>> wrote: >>> >>>> +1 there >>>> >>>> ------------------ >>>> *From:* Sean Owen <sro...@gmail.com> >>>> *Sent:* Friday, March 16, 2018 9:51:49 AM >>>> *To:* Felix Cheung >>>&

Re: Changing how we compute release hashes

2018-03-16 Thread Nicholas Chammas
elixcheun...@hotmail.com> >> wrote: >> >>> +1 there >>> >>> -- >>> *From:* Sean Owen <sro...@gmail.com> >>> *Sent:* Friday, March 16, 2018 9:51:49 AM >>> *To:* Felix Cheung >>> *Cc:* rb...

Re: Changing how we compute release hashes

2018-03-16 Thread Sean Owen
om> >> *Sent:* Friday, March 16, 2018 9:51:49 AM >> *To:* Felix Cheung >> *Cc:* rb...@netflix.com; Nicholas Chammas; Spark dev list >> >> *Subject:* Re: Changing how we compute release hashes >> I think the issue with that is that OS X doesn't have "

Re: Changing how we compute release hashes

2018-03-16 Thread Nicholas Chammas
> *To:* Felix Cheung > *Cc:* rb...@netflix.com; Nicholas Chammas; Spark dev list > > *Subject:* Re: Changing how we compute release hashes > I think the issue with that is that OS X doesn't have "sha512sum". Both it > and Linux have "shasum -a 512" thou

Re: Changing how we compute release hashes

2018-03-16 Thread Felix Cheung
+1 there From: Sean Owen <sro...@gmail.com> Sent: Friday, March 16, 2018 9:51:49 AM To: Felix Cheung Cc: rb...@netflix.com; Nicholas Chammas; Spark dev list Subject: Re: Changing how we compute release hashes I think the issue with that is that OS X doesn'

Re: Changing how we compute release hashes

2018-03-16 Thread Sean Owen
t change > to using sha512sum? That would output the right format that is in turns > verifiable. > > > -- > *From:* Ryan Blue <rb...@netflix.com.INVALID> > *Sent:* Friday, March 16, 2018 8:31:45 AM > *To:* Nicholas Chammas > *Cc:* Spark de

Re: Changing how we compute release hashes

2018-03-16 Thread Felix Cheung
hammas Cc: Spark dev list Subject: Re: Changing how we compute release hashes +1 It's possible to produce the same file with gpg, but the sha*sum utilities are a bit easier to remember the syntax for. On Thu, Mar 15, 2018 at 9:01 PM, Nicholas Chammas <nicholas.cham...@gmail.com<mailto:n

Re: Changing how we compute release hashes

2018-03-16 Thread Ryan Blue
+1 It's possible to produce the same file with gpg, but the sha*sum utilities are a bit easier to remember the syntax for. On Thu, Mar 15, 2018 at 9:01 PM, Nicholas Chammas < nicholas.cham...@gmail.com> wrote: > To verify that I’ve downloaded a Hadoop release correctly, I can just do > this: > >

Changing how we compute release hashes

2018-03-15 Thread Nicholas Chammas
To verify that I’ve downloaded a Hadoop release correctly, I can just do this: $ shasum --check hadoop-2.7.5.tar.gz.sha256 hadoop-2.7.5.tar.gz: OK However, since we generate Spark release hashes with GPG