You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Brian Cho <ch...@gmail.com> on 2015/05/11 03:37:44 UTC
Adding public key to people.apache.org/keys/committer/
Hi,
As I'm next in line in the process (release manager for 0.12) I went ahead
and gave it a shot.
The end product was I got my key to appear on
http://people.apache.org/keys/committer/chobrian.asc . Here are the steps.
Please let me know if any of the steps can't be reproduced.
(I used Mac OS X)
1. Create a new key.
I followed exactly the steps at
http://www.apache.org/dev/openpgp.html#key-gen-generate-key
Fortunately, my default setup used sha512. You may want to double check
with the steps here http://www.apache.org/dev/openpgp.html#sha1
2. Export the key.
http://www.apache.org/dev/openpgp.html#export-key
3. scp the key to minotaur.apache.org:/home/chobrian/.pgpkey
Also, make sure read permissions are added to .pgpkey (`chmod +r .pgpkey`).
This part was in fact tricky because it wasn't clear where to ssh to, and
it turns out I didn't have my ssh public key setup yet.
I had to go to the LDAP page: https://id.apache.org
(a) The server to ssh to is under "SSH Access". For me it was
minotaur.apache.org
(b) Then I added an ssh public key to "SSH Key (authorized_keys line)" in
the format: ssh-rsa AAAA...8Yd4j bcho@Brians-MacBook-Pro.local (I've
redacted most of my public key here, but not on the form). Insert
"Password" again and press "Submit changes..."
After these two steps I could ssh/scp.
4. Add Fingerprint to LDAP
Add under "OpenPGP Public Key Primary Fingerprint" in the format: C666 0000
0000 0000 0000 0000 0000 0000 0000 0CF4 (I've redacted most of my
fingerprint here, but not on the form). Insert "Password" again and press
"Submit changes..."
5. Wait... :)
This is maybe the hardest part. It took about a couple hours before I saw
my key appear on http://people.apache.org/keys/committer/
Hope this helps!
-Brian
On Sun, May 10, 2015 at 5:45 PM, Byung-Gon Chun <bg...@gmail.com> wrote:
> I am still traveling. I just followed the guideline. Nothing else. Perhaps
> you need to contact the apache infrastructure team?
>
> - Gon
>
> 나의 iPhone에서 보냄
>
> 2015. 5. 10. 오전 7:13 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
>
> > Hi Gon,
> >
> > I did follow the steps and installed the key to the LDAP profile.
> However, I didn't see my key shown up at https://people.apache.org/keys.
> That was one of the questions I was asking.
> >
> > Would you mind we set up a few minutes to talk about how to do it if you
> are not traveling? That would save a lot of more time backing forth.
> >
> > Thanks,
> > Julia
> >
> > -----Original Message-----
> > From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> > Sent: Saturday, May 9, 2015 12:41 PM
> > To: dev@reef.incubator.apache.org
> > Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >
> > Juila,
> >
> > Did you do the following step in the How To OpenPGP page?
> >
> > PGPKEY
> >
> > The .pgpkey file in your home directory on people.apache.org should
> contain an ASCII armored <
> http://www.apache.org/dev/release-signing.html#ascii> public key <
> http://www.apache.org/dev/release-signing.html#public-private> export <
> http://www.apache.org/dev/release-signing.html#export> of all the keys
> which you use for signing Apache releases.
> >
> > To create an ASCII armored
> > <http://www.apache.org/dev/release-signing.html#ascii> export <
> http://www.apache.org/dev/release-signing.html#export> :
> >
> > -
> >
> > When using a transition
> > <http://www.apache.org/dev/release-signing.html#transition> , follow
> > these instructions
> > <http://www.apache.org/dev/key-transition.html#transition-export>.
> > -
> >
> > Otherwise gpg --output *KEYID*.asc --armor --export *KEYID* (where
> > *KEYID* is the key ID
> > <http://www.apache.org/dev/release-signing.html#key-id> of the key to
> be
> > exported). See this guide
> > <http://www.apache.org/dev/openpgp.html#export-key> for more details.
> >
> > The result should then be scp 'd into place in your home directory on
> people.apache.org and installed in your LDAP profile <
> https://id.apache.org/> (which will make it available on
> https://people.apache.org/keys/).
> > If you install your key in your LDAP profile, your key should be
> available under https://people.apache.org/keys/<yourid>.asc.
> >
> > -Gon
> >
> >
> >
> >
> >> On Sat, May 2, 2015 at 10:44 PM, Byung-Gon Chun <bg...@gmail.com>
> wrote:
> >>
> >> Hi Julia,
> >>
> >> A release candidate is typically put under
> .../dist/dev/incubator/reef...
> >>
> >> Last time I used my apache home directory.
> >>
> >> I think it is good to put only the final approved release under
> >> .../dist/release...
> >> It's likely that the folder is mirrored globally.
> >>
> >> I will check how I added my pub key when I have access to my laptop.
> >>
> >> Thanks.
> >> -Gon
> >>
> >> 나의 iPhone에서 보냄
> >>
> >> 2015. 5. 3. 오후 1:21 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
> >>
> >>> Hi Gon,
> >>>
> >>> Thanks for verifying it and catching some corner cases! I will
> >>> update
> >> the source in next round.
> >>>
> >>> Looks like our emails were delayed. I made rc3 on Friday, in which I
> >> used CygWin to regenerate the digests and uploaded. You can look at it
> >> to see if format is OK now.
> >>>
> >>> This is the command I used to generate .sha512 file:
> >>> sha512sum apache-reef-0.11.0-incubating-rc2.tar.gz >
> >> apache-reef-0.11.0-incubating-rc2.tar.gz.sha512
> >>>
> >>> One question: I tried to checkout
> >> https://people.apache.org/keys/committer. Got the following after
> >> typing the command line, but don't get anything really checked out.
> >>>
> >>>> svn co https://people.apache.org/keys/committer
> >>> Redirecting to URL 'https://people.apache.org/keys/committer':
> >>> Redirecting to URL 'https://people.apache.org/keys/committer':
> >>> svn: E195019: Redirect cycle detected for URL '
> >> https://people.apache.org/keys/committer'
> >>>
> >>> What is the right command to check it out so that I can add my key
> >>> file
> >> under committer?
> >>>
> >>> Thanks,
> >>> Julia
> >>>
> >>> -----Original Message-----
> >>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> >>> Sent: Friday, May 01, 2015 11:46 PM
> >>> To: dev@reef.incubator.apache.org
> >>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >>>
> >>> Thanks. I checked the tar ball.
> >>>
> >>> The copyright of the following files should be fixed.
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Client/run.cmd:@REM Copyright (C) 2013
> >> Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Client/run.cmd::: Copyright (C) 2013
> >>> Microsoft
> >> Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:@REM
> >>> Copyright
> >>> (C) 2013 Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:::
> >>> Copyright
> >> (C)
> >>> 2013 Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd:@REM Copyright (C) 2013
> >> Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd::: Copyright (C) 2013
> >>> Microsoft
> >> Corporation
> >>>
> >>>
> >>> find . -type f | xargs file
> >>>
> >>> shows that we have "ASCII English text", "ASCII English text, with
> >>> CRLF
> >> line terminators", "UTF-8 Unicode (with BOM) English text, with CRLF
> >> line terminators", etc. I'm wondering if we want to at least change
> >> ASCII English text, with CRLF line terminators to ASCII English text.
> >> Just a question.
> >>>
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest:
> >>> cannot
> >>> open
> >> `./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest' (No
> >> such file or directory)
> >>>
> >>> .cs:
> >>>
> >>> "IEvaluatorRequest .cs" There is a space between t and .cs. The file
> >> name should be fixed.
> >>>
> >>>
> >>> md5, sha1 match. The signature's verified.
> >>> How did you generate sha512? This's a binary file format. I didn't
> >>> check
> >> sha512.
> >>>
> >>>
> >>>
> >>> Tests pass on my local mac machine.
> >>> I didn't test with YARN and Mesos.
> >>>
> >>> On Sat, May 2, 2015 at 2:38 AM, Julia Wang (QIUHE) <
> >> Qiuhe.Wang@microsoft.com
> >>>> wrote:
> >>>
> >>>> I have update rc2 tar ball on
> >>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.0-in
> >>>> cub
> >>>> ating/
> >>>>
> >>>> " Could you put a new rc2 tar ball, for which we will vote, on the
> >>>> web?", Do you mean above web site?
> >>>
> >>> Yes. Thank you.
> >>>
> >>>
> >>>> " please update digests to check?". Could you please elaborate what
> >>>> is
> >> it?
> >>>>
> >>>> I meant md5, sha1, and sha512. Thanks!
> >>>
> >>>
> >>>> I don't see attached cleaned up key. Brain, could you please send
> again?
> >>>>
> >>>> I exported the key to a key file. And I tried to install the key to
> >>>> my LDAP profile, but it is not shown in
> https://people.apache.org/keys.
> >>>> Can someone share the detail steps for how to upload the juliaw.asc
> >>>> to Apache ( https://people.apache.org/keys/committer/juliaw.asc)?
> >>>>
> >>>> You can add your key under .../committer. Use svn.
> >>>
> >>> -Gon
> >>>
> >>>
> >>>
> >>>> Thanks,
> >>>> Julia
> >>>>
> >>>> -----Original Message-----
> >>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> >>>> Sent: Friday, May 1, 2015 12:49 AM
> >>>> To: dev@reef.incubator.apache.org
> >>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >>>>
> >>>> Also, please update digests to check. Thanks!
> >>>>
> >>>>> On Fri, May 1, 2015 at 3:51 PM, Byung-Gon Chun <bg...@gmail.com>
> >> wrote:
> >>>>>
> >>>>> Could you put a new rc2 tar ball, for which we will vote, on the web?
> >>>>> Thanks!
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Fri, May 1, 2015 at 3:13 PM, Julia Wang (QIUHE) <
> >>>>> Qiuhe.Wang@microsoft.com> wrote:
> >>>>>
> >>>>>> Yeah, I will remove those folders and files.
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Brian Cho [mailto:chobrian@gmail.com]
> >>>>>> Sent: Thursday, April 30, 2015 9:04 PM
> >>>>>> To: dev@reef.incubator.apache.org
> >>>>>> Cc: dev@reef.incubator.apache.org
> >>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >>>>>>
> >>>>>> In terms of the tarball:- I see many (all?) differences from the
> >> branch.
> >>>>>> It looks like the files have windows-style returns (\r\n)
> >>>>>>
> >>>>>> - We should remove .idea directory
> >>>>>>
> >>>>>> - We should remove reef-project.iml
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> -Brian
> >>>>>>
> >>>>>> On Fri, May 1, 2015 at 12:50 PM, Byung-Gon Chun
> >>>>>> <bg...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> Julia, could you address the problems Brian mentioned?
> >>>>>>> These points'll be raised again by the IPMC members.
> >>>>>>> On Fri, May 1, 2015 at 12:25 PM, Brian Cho <ch...@gmail.com>
> >>>> wrote:
> >>>>>>>> I also see a non-ascii character (a BOM perhaps?) on the md5,
> >>>>>>>> sha1,
> >>>>>>>> sha512 files, that prevent automatic checking of the hashes,
> >>>>>>>> e.g., using md5sum -c <file> on Linux.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> The checksums themselves match, it’s just the file format seems
> >>>>>>>> a little off because of the character at the beginning.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> -Brian
> >>>>>>>>
> >>>>>>>> On Fri, May 1, 2015 at 12:09 PM, Brian Cho <ch...@gmail.com>
> >>>> wrote:
> >>>>>>>>
> >>>>>>>>> I’ve attached a cleaned-up version of KEYS. There were some
> >>>>>>>>> carriage
> >>>>>>>> returns in the key, and also some missing newlines in the header.
> >>>>>>>>> This edited version worked for me.
> >>>>>>>>> -Brian
> >>>>>>>>> On Fri, May 1, 2015 at 12:03 PM, Brian Cho
> >>>>>>>>> <ch...@gmail.com>
> >>>>>> wrote:
> >>>>>>>>>> When I download the KEYS file and run `gpg —import KEYS`,
> >>>>>>>>>> Julia’s key
> >>>>>>>> is not imported. This leads to the verification `gpg —verify`
> >>>> failing.
> >>>>>>>>>> Only the following three keys are imported:
> >>>>>>>>>> ```
> >>>>>>>>>> gpg: key 7DF6AF74: public key "Byung-Gon Chun (CODE SIGNING
> >>>>>>>>>> KEY) <
> >>>>>>>> bgchun@apache.org>" imported
> >>>>>>>>>> gpg: key B876884A: public key "Chris Mattmann (CODE SIGNING
> >>>>>>>>>> KEY) <
> >>>>>>>> mattmann@apache.org>" imported
> >>>>>>>>>> gpg: key 3D0C92B9: public key "Owen O'Malley (Code signing) <
> >>>>>>>> omalley@apache.org>" imported
> >>>>>>>>>> gpg: Total number processed: 3
> >>>>>>>>>> gpg: imported: 3 (RSA: 2)
> >>>>>>>>>> ```
> >>>>>>>>>> It looks like Julia’s information is missing newlines, maybe
> >>>>>>>>>> confusing
> >>>>>>>> gpg. Is this a Unix / Windows newline thing?
> >>>>>>>>>> -Brian
> >>>>>>>>>> On Fri, May 1, 2015 at 11:27 AM, Julia Wang (QIUHE)
> >>>>>>>>>> <Qi...@microsoft.com> wrote:
> >>>>>>>>>>> This is to call for a new vote for the source release of
> >>>>>>>>>>> Apache REEF
> >>>>>>>> 0.11.0-incubating (rc2).
> >>>>>>>>>>> The source tar ball, including signatures, digests, etc can
> >>>>>>>>>>> be found
> >>>>>>>> at:
> >>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.
> >>>>>>>> 0
> >>>>>>>> -i
> >>>>>>>> ncu
> >>>>>>>> bating/
> >>>>>>>>>>> The Git tag is release-0.11.0-incubating-rc2 The Git commit
> >>>>>>>>>>> ID is
> >>>>>>>>>>> 57a3a3e1ac61d538e551c4804159ffe96ef686a6
> >>>>>>>>>>> Checksums of apache-reef-0.11.0-incubating-rc2.tar.gz:
> >>>>>>>>>>> MD5: 98f85baab21d1d12b3987fd92a0b7235
> >>>>>>>>>>> SHA1: e795962425f09ab78d47ae8f6181a36f36a2d2a0
> >>>>>>>>>>> SHA512:
> >>>>>>>> fee8800edc73bfa9c99b66522ca3dced3604d9d56b71b0e0f51a79e69dc9fb7
> >>>>>>>> 7
> >>>>>>>> b0
> >>>>>>>> e51 958593b43e28d321e863391f5740e43143ae0f065b193e90a9e5d00f58f
> >>>>>>>>>>> Release artifacts are signed with the key. The KEYS file is
> >>>>>>>>>>> available
> >>>>>>>> here:
> >>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/KE
> >>>>>>>>>>> YS
> >>>>>>>>>>> Issues Resolved:
> >>>>>>>>>>> 148 issues were closed/resolved for this release:
> >>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20REEF
> >>>>>>>> %
> >>>>>>>> 20
> >>>>>>>> AND
> >>>>>>>> %20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20in
> >>>>>>>> %
> >>>>>>>> 20
> >>>>>>>> (Fi
> >>>>>>>> xed%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex=1
> >>>>>>>> 5
> >>>>>>>> 0
> >>>>>>>>>>> The vote will be open for 72 hours. Please download the
> >>>>>>>>>>> release
> >>>>>>>> candidate, check the hashes/signature, build it and test it,
> >>>>>>>> and then please vote:
> >>>>>>>>>>> [ ] +1 Release this package as Apache REEF 0.11.0-incubating
> >>>>>>>>>>> [ ]
> >>>>>>>>>>> +0 no opinion [ ] -1 Do not release this package because ...
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> Julia
> >>>>>>> --
> >>>>>>> Byung-Gon Chun
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Byung-Gon Chun
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Byung-Gon Chun
> >>>
> >>>
> >>>
> >>> --
> >>> Byung-Gon Chun
> >
> >
> >
> > --
> > Byung-Gon Chun
>
Re: Adding public key to people.apache.org/keys/committer/
Posted by Brian Cho <ch...@gmail.com>.
Sure, I’ll add a child page to Release Manager Guide, that expands on Step 1.
-Brian
On May 11, 2015 at 11:39:15 AM, Byung-Gon Chun (bgchun@gmail.com) wrote:
Thanks for your help, Brian!
Could you write a short doc on the wiki?
나의 iPhone에서 보냄
2015. 5. 11. 오전 11:33 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
> Thanks Brian! That helps. I will check what I did differently and back to you.
>
> Thanks,
> Julia
>
> -----Original Message-----
> From: Brian Cho [mailto:chobrian@gmail.com]
> Sent: Sunday, May 10, 2015 6:38 PM
> To: dev@reef.incubator.apache.org
> Subject: Adding public key to people.apache.org/keys/committer/
>
> Hi,
>
> As I'm next in line in the process (release manager for 0.12) I went ahead and gave it a shot.
>
> The end product was I got my key to appear on http://people.apache.org/keys/committer/chobrian.asc . Here are the steps.
> Please let me know if any of the steps can't be reproduced.
>
> (I used Mac OS X)
>
> 1. Create a new key.
> I followed exactly the steps at
> http://www.apache.org/dev/openpgp.html#key-gen-generate-key
> Fortunately, my default setup used sha512. You may want to double check with the steps here http://www.apache.org/dev/openpgp.html#sha1
>
> 2. Export the key.
> http://www.apache.org/dev/openpgp.html#export-key
>
> 3. scp the key to minotaur.apache.org:/home/chobrian/.pgpkey
> Also, make sure read permissions are added to .pgpkey (`chmod +r .pgpkey`).
>
> This part was in fact tricky because it wasn't clear where to ssh to, and it turns out I didn't have my ssh public key setup yet.
> I had to go to the LDAP page: https://id.apache.org
> (a) The server to ssh to is under "SSH Access". For me it was minotaur.apache.org
> (b) Then I added an ssh public key to "SSH Key (authorized_keys line)" in the format: ssh-rsa AAAA...8Yd4j bcho@Brians-MacBook-Pro.local (I've redacted most of my public key here, but not on the form). Insert "Password" again and press "Submit changes..."
> After these two steps I could ssh/scp.
>
> 4. Add Fingerprint to LDAP
> Add under "OpenPGP Public Key Primary Fingerprint" in the format: C666 0000
> 0000 0000 0000 0000 0000 0000 0000 0CF4 (I've redacted most of my fingerprint here, but not on the form). Insert "Password" again and press "Submit changes..."
>
> 5. Wait... :)
> This is maybe the hardest part. It took about a couple hours before I saw my key appear on http://people.apache.org/keys/committer/
>
> Hope this helps!
> -Brian
>
>
>
>
>> On Sun, May 10, 2015 at 5:45 PM, Byung-Gon Chun <bg...@gmail.com> wrote:
>>
>> I am still traveling. I just followed the guideline. Nothing else.
>> Perhaps you need to contact the apache infrastructure team?
>>
>> - Gon
>>
>> 나의 iPhone에서 보냄
>>
>> 2015. 5. 10. 오전 7:13 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
>>
>>> Hi Gon,
>>>
>>> I did follow the steps and installed the key to the LDAP profile.
>> However, I didn't see my key shown up at https://people.apache.org/keys.
>> That was one of the questions I was asking.
>>>
>>> Would you mind we set up a few minutes to talk about how to do it if
>>> you
>> are not traveling? That would save a lot of more time backing forth.
>>>
>>> Thanks,
>>> Julia
>>>
>>> -----Original Message-----
>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>> Sent: Saturday, May 9, 2015 12:41 PM
>>> To: dev@reef.incubator.apache.org
>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>
>>> Juila,
>>>
>>> Did you do the following step in the How To OpenPGP page?
>>>
>>> PGPKEY
>>>
>>> The .pgpkey file in your home directory on people.apache.org should
>> contain an ASCII armored <
>> http://www.apache.org/dev/release-signing.html#ascii> public key <
>> http://www.apache.org/dev/release-signing.html#public-private> export
>> < http://www.apache.org/dev/release-signing.html#export> of all the
>> keys which you use for signing Apache releases.
>>>
>>> To create an ASCII armored
>>> <http://www.apache.org/dev/release-signing.html#ascii> export <
>> http://www.apache.org/dev/release-signing.html#export> :
>>>
>>> -
>>>
>>> When using a transition
>>> <http://www.apache.org/dev/release-signing.html#transition> , follow
>>> these instructions
>>> <http://www.apache.org/dev/key-transition.html#transition-export>.
>>> -
>>>
>>> Otherwise gpg --output *KEYID*.asc --armor --export *KEYID* (where
>>> *KEYID* is the key ID
>>> <http://www.apache.org/dev/release-signing.html#key-id> of the key
>>> to
>> be
>>> exported). See this guide
>>> <http://www.apache.org/dev/openpgp.html#export-key> for more details.
>>>
>>> The result should then be scp 'd into place in your home directory
>>> on
>> people.apache.org and installed in your LDAP profile <
>> https://id.apache.org/> (which will make it available on
>> https://people.apache.org/keys/).
>>> If you install your key in your LDAP profile, your key should be
>> available under https://people.apache.org/keys/<yourid>.asc.
>>>
>>> -Gon
>>>
>>>
>>>
>>>
>>>> On Sat, May 2, 2015 at 10:44 PM, Byung-Gon Chun <bg...@gmail.com>
>> wrote:
>>>>
>>>> Hi Julia,
>>>>
>>>> A release candidate is typically put under
>> .../dist/dev/incubator/reef...
>>>>
>>>> Last time I used my apache home directory.
>>>>
>>>> I think it is good to put only the final approved release under
>>>> .../dist/release...
>>>> It's likely that the folder is mirrored globally.
>>>>
>>>> I will check how I added my pub key when I have access to my laptop.
>>>>
>>>> Thanks.
>>>> -Gon
>>>>
>>>> 나의 iPhone에서 보냄
>>>>
>>>> 2015. 5. 3. 오후 1:21 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
>>>>
>>>>> Hi Gon,
>>>>>
>>>>> Thanks for verifying it and catching some corner cases! I will
>>>>> update
>>>> the source in next round.
>>>>>
>>>>> Looks like our emails were delayed. I made rc3 on Friday, in which
>>>>> I
>>>> used CygWin to regenerate the digests and uploaded. You can look at
>>>> it to see if format is OK now.
>>>>>
>>>>> This is the command I used to generate .sha512 file:
>>>>> sha512sum apache-reef-0.11.0-incubating-rc2.tar.gz >
>>>> apache-reef-0.11.0-incubating-rc2.tar.gz.sha512
>>>>>
>>>>> One question: I tried to checkout
>>>> https://people.apache.org/keys/committer. Got the following after
>>>> typing the command line, but don't get anything really checked out.
>>>>>
>>>>>> svn co https://people.apache.org/keys/committer
>>>>> Redirecting to URL 'https://people.apache.org/keys/committer':
>>>>> Redirecting to URL 'https://people.apache.org/keys/committer':
>>>>> svn: E195019: Redirect cycle detected for URL '
>>>> https://people.apache.org/keys/committer'
>>>>>
>>>>> What is the right command to check it out so that I can add my key
>>>>> file
>>>> under committer?
>>>>>
>>>>> Thanks,
>>>>> Julia
>>>>>
>>>>> -----Original Message-----
>>>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>>>> Sent: Friday, May 01, 2015 11:46 PM
>>>>> To: dev@reef.incubator.apache.org
>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>>>
>>>>> Thanks. I checked the tar ball.
>>>>>
>>>>> The copyright of the following files should be fixed.
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Client/run.cmd:@REM Copyright (C) 2013
>>>> Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Client/run.cmd::: Copyright (C) 2013
>>>>> Microsoft
>>>> Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:@REM
>>>>> Copyright
>>>>> (C) 2013 Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:::
>>>>> Copyright
>>>> (C)
>>>>> 2013 Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd:@REM Copyright (C) 2013
>>>> Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd::: Copyright (C) 2013
>>>>> Microsoft
>>>> Corporation
>>>>>
>>>>>
>>>>> find . -type f | xargs file
>>>>>
>>>>> shows that we have "ASCII English text", "ASCII English text, with
>>>>> CRLF
>>>> line terminators", "UTF-8 Unicode (with BOM) English text, with
>>>> CRLF line terminators", etc. I'm wondering if we want to at least
>>>> change ASCII English text, with CRLF line terminators to ASCII English text.
>>>> Just a question.
>>>>>
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest:
>>>>> cannot
>>>>> open
>>>> `./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest' (No
>>>> such file or directory)
>>>>>
>>>>> .cs:
>>>>>
>>>>> "IEvaluatorRequest .cs" There is a space between t and .cs. The
>>>>> file
>>>> name should be fixed.
>>>>>
>>>>>
>>>>> md5, sha1 match. The signature's verified.
>>>>> How did you generate sha512? This's a binary file format. I didn't
>>>>> check
>>>> sha512.
>>>>>
>>>>>
>>>>>
>>>>> Tests pass on my local mac machine.
>>>>> I didn't test with YARN and Mesos.
>>>>>
>>>>> On Sat, May 2, 2015 at 2:38 AM, Julia Wang (QIUHE) <
>>>> Qiuhe.Wang@microsoft.com
>>>>>> wrote:
>>>>>
>>>>>> I have update rc2 tar ball on
>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.0-
>>>>>> in
>>>>>> cub
>>>>>> ating/
>>>>>>
>>>>>> " Could you put a new rc2 tar ball, for which we will vote, on
>>>>>> the web?", Do you mean above web site?
>>>>>
>>>>> Yes. Thank you.
>>>>>
>>>>>
>>>>>> " please update digests to check?". Could you please elaborate
>>>>>> what is
>>>> it?
>>>>>>
>>>>>> I meant md5, sha1, and sha512. Thanks!
>>>>>
>>>>>
>>>>>> I don't see attached cleaned up key. Brain, could you please send
>> again?
>>>>>>
>>>>>> I exported the key to a key file. And I tried to install the key
>>>>>> to my LDAP profile, but it is not shown in
>> https://people.apache.org/keys.
>>>>>> Can someone share the detail steps for how to upload the
>>>>>> juliaw.asc to Apache ( https://people.apache.org/keys/committer/juliaw.asc)?
>>>>>>
>>>>>> You can add your key under .../committer. Use svn.
>>>>>
>>>>> -Gon
>>>>>
>>>>>
>>>>>
>>>>>> Thanks,
>>>>>> Julia
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>>>>> Sent: Friday, May 1, 2015 12:49 AM
>>>>>> To: dev@reef.incubator.apache.org
>>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>>>>
>>>>>> Also, please update digests to check. Thanks!
>>>>>>
>>>>>>> On Fri, May 1, 2015 at 3:51 PM, Byung-Gon Chun
>>>>>>> <bg...@gmail.com>
>>>> wrote:
>>>>>>>
>>>>>>> Could you put a new rc2 tar ball, for which we will vote, on the web?
>>>>>>> Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 1, 2015 at 3:13 PM, Julia Wang (QIUHE) <
>>>>>>> Qiuhe.Wang@microsoft.com> wrote:
>>>>>>>
>>>>>>>> Yeah, I will remove those folders and files.
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Brian Cho [mailto:chobrian@gmail.com]
>>>>>>>> Sent: Thursday, April 30, 2015 9:04 PM
>>>>>>>> To: dev@reef.incubator.apache.org
>>>>>>>> Cc: dev@reef.incubator.apache.org
>>>>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>>>>>>
>>>>>>>> In terms of the tarball:- I see many (all?) differences from
>>>>>>>> the
>>>> branch.
>>>>>>>> It looks like the files have windows-style returns (\r\n)
>>>>>>>>
>>>>>>>> - We should remove .idea directory
>>>>>>>>
>>>>>>>> - We should remove reef-project.iml
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -Brian
>>>>>>>>
>>>>>>>> On Fri, May 1, 2015 at 12:50 PM, Byung-Gon Chun
>>>>>>>> <bg...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Julia, could you address the problems Brian mentioned?
>>>>>>>>> These points'll be raised again by the IPMC members.
>>>>>>>>> On Fri, May 1, 2015 at 12:25 PM, Brian Cho
>>>>>>>>> <ch...@gmail.com>
>>>>>> wrote:
>>>>>>>>>> I also see a non-ascii character (a BOM perhaps?) on the md5,
>>>>>>>>>> sha1,
>>>>>>>>>> sha512 files, that prevent automatic checking of the hashes,
>>>>>>>>>> e.g., using md5sum -c <file> on Linux.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The checksums themselves match, it’s just the file format
>>>>>>>>>> seems a little off because of the character at the beginning.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Brian
>>>>>>>>>>
>>>>>>>>>> On Fri, May 1, 2015 at 12:09 PM, Brian Cho
>>>>>>>>>> <ch...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> I’ve attached a cleaned-up version of KEYS. There were some
>>>>>>>>>>> carriage
>>>>>>>>>> returns in the key, and also some missing newlines in the header.
>>>>>>>>>>> This edited version worked for me.
>>>>>>>>>>> -Brian
>>>>>>>>>>> On Fri, May 1, 2015 at 12:03 PM, Brian Cho
>>>>>>>>>>> <ch...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>> When I download the KEYS file and run `gpg —import KEYS`,
>>>>>>>>>>>> Julia’s key
>>>>>>>>>> is not imported. This leads to the verification `gpg —verify`
>>>>>> failing.
>>>>>>>>>>>> Only the following three keys are imported:
>>>>>>>>>>>> ```
>>>>>>>>>>>> gpg: key 7DF6AF74: public key "Byung-Gon Chun (CODE SIGNING
>>>>>>>>>>>> KEY) <
>>>>>>>>>> bgchun@apache.org>" imported
>>>>>>>>>>>> gpg: key B876884A: public key "Chris Mattmann (CODE SIGNING
>>>>>>>>>>>> KEY) <
>>>>>>>>>> mattmann@apache.org>" imported
>>>>>>>>>>>> gpg: key 3D0C92B9: public key "Owen O'Malley (Code signing)
>>>>>>>>>>>> <
>>>>>>>>>> omalley@apache.org>" imported
>>>>>>>>>>>> gpg: Total number processed: 3
>>>>>>>>>>>> gpg: imported: 3 (RSA: 2)
>>>>>>>>>>>> ```
>>>>>>>>>>>> It looks like Julia’s information is missing newlines,
>>>>>>>>>>>> maybe confusing
>>>>>>>>>> gpg. Is this a Unix / Windows newline thing?
>>>>>>>>>>>> -Brian
>>>>>>>>>>>> On Fri, May 1, 2015 at 11:27 AM, Julia Wang (QIUHE)
>>>>>>>>>>>> <Qi...@microsoft.com> wrote:
>>>>>>>>>>>>> This is to call for a new vote for the source release of
>>>>>>>>>>>>> Apache REEF
>>>>>>>>>> 0.11.0-incubating (rc2).
>>>>>>>>>>>>> The source tar ball, including signatures, digests, etc
>>>>>>>>>>>>> can be found
>>>>>>>>>> at:
>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.
>>>>>>>>>> 0
>>>>>>>>>> -i
>>>>>>>>>> ncu
>>>>>>>>>> bating/
>>>>>>>>>>>>> The Git tag is release-0.11.0-incubating-rc2 The Git
>>>>>>>>>>>>> commit ID is
>>>>>>>>>>>>> 57a3a3e1ac61d538e551c4804159ffe96ef686a6
>>>>>>>>>>>>> Checksums of apache-reef-0.11.0-incubating-rc2.tar.gz:
>>>>>>>>>>>>> MD5: 98f85baab21d1d12b3987fd92a0b7235
>>>>>>>>>>>>> SHA1: e795962425f09ab78d47ae8f6181a36f36a2d2a0
>>>>>>>>>>>>> SHA512:
>>>>>>>>>> fee8800edc73bfa9c99b66522ca3dced3604d9d56b71b0e0f51a79e69dc9f
>>>>>>>>>> b7
>>>>>>>>>> 7
>>>>>>>>>> b0
>>>>>>>>>> e51
>>>>>>>>>> 958593b43e28d321e863391f5740e43143ae0f065b193e90a9e5d00f58f
>>>>>>>>>>>>> Release artifacts are signed with the key. The KEYS file
>>>>>>>>>>>>> is available
>>>>>>>>>> here:
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/
>>>>>>>>>>>>> KE
>>>>>>>>>>>>> YS
>>>>>>>>>>>>> Issues Resolved:
>>>>>>>>>>>>> 148 issues were closed/resolved for this release:
>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20RE
>>>>>>>>>> EF
>>>>>>>>>> %
>>>>>>>>>> 20
>>>>>>>>>> AND
>>>>>>>>>> %20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20
>>>>>>>>>> in
>>>>>>>>>> %
>>>>>>>>>> 20
>>>>>>>>>> (Fi
>>>>>>>>>> xed%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex
>>>>>>>>>> =1
>>>>>>>>>> 5
>>>>>>>>>> 0
>>>>>>>>>>>>> The vote will be open for 72 hours. Please download the
>>>>>>>>>>>>> release
>>>>>>>>>> candidate, check the hashes/signature, build it and test it,
>>>>>>>>>> and then please vote:
>>>>>>>>>>>>> [ ] +1 Release this package as Apache REEF
>>>>>>>>>>>>> 0.11.0-incubating [ ]
>>>>>>>>>>>>> +0 no opinion [ ] -1 Do not release this package because ...
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Julia
>>>>>>>>> --
>>>>>>>>> Byung-Gon Chun
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Byung-Gon Chun
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Byung-Gon Chun
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Byung-Gon Chun
>>>
>>>
>>>
>>> --
>>> Byung-Gon Chun
>>
Re: Adding public key to people.apache.org/keys/committer/
Posted by Byung-Gon Chun <bg...@gmail.com>.
Thanks for your help, Brian!
Could you write a short doc on the wiki?
나의 iPhone에서 보냄
2015. 5. 11. 오전 11:33 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
> Thanks Brian! That helps. I will check what I did differently and back to you.
>
> Thanks,
> Julia
>
> -----Original Message-----
> From: Brian Cho [mailto:chobrian@gmail.com]
> Sent: Sunday, May 10, 2015 6:38 PM
> To: dev@reef.incubator.apache.org
> Subject: Adding public key to people.apache.org/keys/committer/
>
> Hi,
>
> As I'm next in line in the process (release manager for 0.12) I went ahead and gave it a shot.
>
> The end product was I got my key to appear on http://people.apache.org/keys/committer/chobrian.asc . Here are the steps.
> Please let me know if any of the steps can't be reproduced.
>
> (I used Mac OS X)
>
> 1. Create a new key.
> I followed exactly the steps at
> http://www.apache.org/dev/openpgp.html#key-gen-generate-key
> Fortunately, my default setup used sha512. You may want to double check with the steps here http://www.apache.org/dev/openpgp.html#sha1
>
> 2. Export the key.
> http://www.apache.org/dev/openpgp.html#export-key
>
> 3. scp the key to minotaur.apache.org:/home/chobrian/.pgpkey
> Also, make sure read permissions are added to .pgpkey (`chmod +r .pgpkey`).
>
> This part was in fact tricky because it wasn't clear where to ssh to, and it turns out I didn't have my ssh public key setup yet.
> I had to go to the LDAP page: https://id.apache.org
> (a) The server to ssh to is under "SSH Access". For me it was minotaur.apache.org
> (b) Then I added an ssh public key to "SSH Key (authorized_keys line)" in the format: ssh-rsa AAAA...8Yd4j bcho@Brians-MacBook-Pro.local (I've redacted most of my public key here, but not on the form). Insert "Password" again and press "Submit changes..."
> After these two steps I could ssh/scp.
>
> 4. Add Fingerprint to LDAP
> Add under "OpenPGP Public Key Primary Fingerprint" in the format: C666 0000
> 0000 0000 0000 0000 0000 0000 0000 0CF4 (I've redacted most of my fingerprint here, but not on the form). Insert "Password" again and press "Submit changes..."
>
> 5. Wait... :)
> This is maybe the hardest part. It took about a couple hours before I saw my key appear on http://people.apache.org/keys/committer/
>
> Hope this helps!
> -Brian
>
>
>
>
>> On Sun, May 10, 2015 at 5:45 PM, Byung-Gon Chun <bg...@gmail.com> wrote:
>>
>> I am still traveling. I just followed the guideline. Nothing else.
>> Perhaps you need to contact the apache infrastructure team?
>>
>> - Gon
>>
>> 나의 iPhone에서 보냄
>>
>> 2015. 5. 10. 오전 7:13 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
>>
>>> Hi Gon,
>>>
>>> I did follow the steps and installed the key to the LDAP profile.
>> However, I didn't see my key shown up at https://people.apache.org/keys.
>> That was one of the questions I was asking.
>>>
>>> Would you mind we set up a few minutes to talk about how to do it if
>>> you
>> are not traveling? That would save a lot of more time backing forth.
>>>
>>> Thanks,
>>> Julia
>>>
>>> -----Original Message-----
>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>> Sent: Saturday, May 9, 2015 12:41 PM
>>> To: dev@reef.incubator.apache.org
>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>
>>> Juila,
>>>
>>> Did you do the following step in the How To OpenPGP page?
>>>
>>> PGPKEY
>>>
>>> The .pgpkey file in your home directory on people.apache.org should
>> contain an ASCII armored <
>> http://www.apache.org/dev/release-signing.html#ascii> public key <
>> http://www.apache.org/dev/release-signing.html#public-private> export
>> < http://www.apache.org/dev/release-signing.html#export> of all the
>> keys which you use for signing Apache releases.
>>>
>>> To create an ASCII armored
>>> <http://www.apache.org/dev/release-signing.html#ascii> export <
>> http://www.apache.org/dev/release-signing.html#export> :
>>>
>>> -
>>>
>>> When using a transition
>>> <http://www.apache.org/dev/release-signing.html#transition> , follow
>>> these instructions
>>> <http://www.apache.org/dev/key-transition.html#transition-export>.
>>> -
>>>
>>> Otherwise gpg --output *KEYID*.asc --armor --export *KEYID* (where
>>> *KEYID* is the key ID
>>> <http://www.apache.org/dev/release-signing.html#key-id> of the key
>>> to
>> be
>>> exported). See this guide
>>> <http://www.apache.org/dev/openpgp.html#export-key> for more details.
>>>
>>> The result should then be scp 'd into place in your home directory
>>> on
>> people.apache.org and installed in your LDAP profile <
>> https://id.apache.org/> (which will make it available on
>> https://people.apache.org/keys/).
>>> If you install your key in your LDAP profile, your key should be
>> available under https://people.apache.org/keys/<yourid>.asc.
>>>
>>> -Gon
>>>
>>>
>>>
>>>
>>>> On Sat, May 2, 2015 at 10:44 PM, Byung-Gon Chun <bg...@gmail.com>
>> wrote:
>>>>
>>>> Hi Julia,
>>>>
>>>> A release candidate is typically put under
>> .../dist/dev/incubator/reef...
>>>>
>>>> Last time I used my apache home directory.
>>>>
>>>> I think it is good to put only the final approved release under
>>>> .../dist/release...
>>>> It's likely that the folder is mirrored globally.
>>>>
>>>> I will check how I added my pub key when I have access to my laptop.
>>>>
>>>> Thanks.
>>>> -Gon
>>>>
>>>> 나의 iPhone에서 보냄
>>>>
>>>> 2015. 5. 3. 오후 1:21 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
>>>>
>>>>> Hi Gon,
>>>>>
>>>>> Thanks for verifying it and catching some corner cases! I will
>>>>> update
>>>> the source in next round.
>>>>>
>>>>> Looks like our emails were delayed. I made rc3 on Friday, in which
>>>>> I
>>>> used CygWin to regenerate the digests and uploaded. You can look at
>>>> it to see if format is OK now.
>>>>>
>>>>> This is the command I used to generate .sha512 file:
>>>>> sha512sum apache-reef-0.11.0-incubating-rc2.tar.gz >
>>>> apache-reef-0.11.0-incubating-rc2.tar.gz.sha512
>>>>>
>>>>> One question: I tried to checkout
>>>> https://people.apache.org/keys/committer. Got the following after
>>>> typing the command line, but don't get anything really checked out.
>>>>>
>>>>>> svn co https://people.apache.org/keys/committer
>>>>> Redirecting to URL 'https://people.apache.org/keys/committer':
>>>>> Redirecting to URL 'https://people.apache.org/keys/committer':
>>>>> svn: E195019: Redirect cycle detected for URL '
>>>> https://people.apache.org/keys/committer'
>>>>>
>>>>> What is the right command to check it out so that I can add my key
>>>>> file
>>>> under committer?
>>>>>
>>>>> Thanks,
>>>>> Julia
>>>>>
>>>>> -----Original Message-----
>>>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>>>> Sent: Friday, May 01, 2015 11:46 PM
>>>>> To: dev@reef.incubator.apache.org
>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>>>
>>>>> Thanks. I checked the tar ball.
>>>>>
>>>>> The copyright of the following files should be fixed.
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Client/run.cmd:@REM Copyright (C) 2013
>>>> Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Client/run.cmd::: Copyright (C) 2013
>>>>> Microsoft
>>>> Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:@REM
>>>>> Copyright
>>>>> (C) 2013 Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:::
>>>>> Copyright
>>>> (C)
>>>>> 2013 Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd:@REM Copyright (C) 2013
>>>> Microsoft Corporation
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd::: Copyright (C) 2013
>>>>> Microsoft
>>>> Corporation
>>>>>
>>>>>
>>>>> find . -type f | xargs file
>>>>>
>>>>> shows that we have "ASCII English text", "ASCII English text, with
>>>>> CRLF
>>>> line terminators", "UTF-8 Unicode (with BOM) English text, with
>>>> CRLF line terminators", etc. I'm wondering if we want to at least
>>>> change ASCII English text, with CRLF line terminators to ASCII English text.
>>>> Just a question.
>>>>>
>>>>>
>>>>> ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest:
>>>>> cannot
>>>>> open
>>>> `./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest' (No
>>>> such file or directory)
>>>>>
>>>>> .cs:
>>>>>
>>>>> "IEvaluatorRequest .cs" There is a space between t and .cs. The
>>>>> file
>>>> name should be fixed.
>>>>>
>>>>>
>>>>> md5, sha1 match. The signature's verified.
>>>>> How did you generate sha512? This's a binary file format. I didn't
>>>>> check
>>>> sha512.
>>>>>
>>>>>
>>>>>
>>>>> Tests pass on my local mac machine.
>>>>> I didn't test with YARN and Mesos.
>>>>>
>>>>> On Sat, May 2, 2015 at 2:38 AM, Julia Wang (QIUHE) <
>>>> Qiuhe.Wang@microsoft.com
>>>>>> wrote:
>>>>>
>>>>>> I have update rc2 tar ball on
>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.0-
>>>>>> in
>>>>>> cub
>>>>>> ating/
>>>>>>
>>>>>> " Could you put a new rc2 tar ball, for which we will vote, on
>>>>>> the web?", Do you mean above web site?
>>>>>
>>>>> Yes. Thank you.
>>>>>
>>>>>
>>>>>> " please update digests to check?". Could you please elaborate
>>>>>> what is
>>>> it?
>>>>>>
>>>>>> I meant md5, sha1, and sha512. Thanks!
>>>>>
>>>>>
>>>>>> I don't see attached cleaned up key. Brain, could you please send
>> again?
>>>>>>
>>>>>> I exported the key to a key file. And I tried to install the key
>>>>>> to my LDAP profile, but it is not shown in
>> https://people.apache.org/keys.
>>>>>> Can someone share the detail steps for how to upload the
>>>>>> juliaw.asc to Apache ( https://people.apache.org/keys/committer/juliaw.asc)?
>>>>>>
>>>>>> You can add your key under .../committer. Use svn.
>>>>>
>>>>> -Gon
>>>>>
>>>>>
>>>>>
>>>>>> Thanks,
>>>>>> Julia
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>>>>> Sent: Friday, May 1, 2015 12:49 AM
>>>>>> To: dev@reef.incubator.apache.org
>>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>>>>
>>>>>> Also, please update digests to check. Thanks!
>>>>>>
>>>>>>> On Fri, May 1, 2015 at 3:51 PM, Byung-Gon Chun
>>>>>>> <bg...@gmail.com>
>>>> wrote:
>>>>>>>
>>>>>>> Could you put a new rc2 tar ball, for which we will vote, on the web?
>>>>>>> Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 1, 2015 at 3:13 PM, Julia Wang (QIUHE) <
>>>>>>> Qiuhe.Wang@microsoft.com> wrote:
>>>>>>>
>>>>>>>> Yeah, I will remove those folders and files.
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Brian Cho [mailto:chobrian@gmail.com]
>>>>>>>> Sent: Thursday, April 30, 2015 9:04 PM
>>>>>>>> To: dev@reef.incubator.apache.org
>>>>>>>> Cc: dev@reef.incubator.apache.org
>>>>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
>>>>>>>>
>>>>>>>> In terms of the tarball:- I see many (all?) differences from
>>>>>>>> the
>>>> branch.
>>>>>>>> It looks like the files have windows-style returns (\r\n)
>>>>>>>>
>>>>>>>> - We should remove .idea directory
>>>>>>>>
>>>>>>>> - We should remove reef-project.iml
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -Brian
>>>>>>>>
>>>>>>>> On Fri, May 1, 2015 at 12:50 PM, Byung-Gon Chun
>>>>>>>> <bg...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Julia, could you address the problems Brian mentioned?
>>>>>>>>> These points'll be raised again by the IPMC members.
>>>>>>>>> On Fri, May 1, 2015 at 12:25 PM, Brian Cho
>>>>>>>>> <ch...@gmail.com>
>>>>>> wrote:
>>>>>>>>>> I also see a non-ascii character (a BOM perhaps?) on the md5,
>>>>>>>>>> sha1,
>>>>>>>>>> sha512 files, that prevent automatic checking of the hashes,
>>>>>>>>>> e.g., using md5sum -c <file> on Linux.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The checksums themselves match, it’s just the file format
>>>>>>>>>> seems a little off because of the character at the beginning.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Brian
>>>>>>>>>>
>>>>>>>>>> On Fri, May 1, 2015 at 12:09 PM, Brian Cho
>>>>>>>>>> <ch...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> I’ve attached a cleaned-up version of KEYS. There were some
>>>>>>>>>>> carriage
>>>>>>>>>> returns in the key, and also some missing newlines in the header.
>>>>>>>>>>> This edited version worked for me.
>>>>>>>>>>> -Brian
>>>>>>>>>>> On Fri, May 1, 2015 at 12:03 PM, Brian Cho
>>>>>>>>>>> <ch...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>> When I download the KEYS file and run `gpg —import KEYS`,
>>>>>>>>>>>> Julia’s key
>>>>>>>>>> is not imported. This leads to the verification `gpg —verify`
>>>>>> failing.
>>>>>>>>>>>> Only the following three keys are imported:
>>>>>>>>>>>> ```
>>>>>>>>>>>> gpg: key 7DF6AF74: public key "Byung-Gon Chun (CODE SIGNING
>>>>>>>>>>>> KEY) <
>>>>>>>>>> bgchun@apache.org>" imported
>>>>>>>>>>>> gpg: key B876884A: public key "Chris Mattmann (CODE SIGNING
>>>>>>>>>>>> KEY) <
>>>>>>>>>> mattmann@apache.org>" imported
>>>>>>>>>>>> gpg: key 3D0C92B9: public key "Owen O'Malley (Code signing)
>>>>>>>>>>>> <
>>>>>>>>>> omalley@apache.org>" imported
>>>>>>>>>>>> gpg: Total number processed: 3
>>>>>>>>>>>> gpg: imported: 3 (RSA: 2)
>>>>>>>>>>>> ```
>>>>>>>>>>>> It looks like Julia’s information is missing newlines,
>>>>>>>>>>>> maybe confusing
>>>>>>>>>> gpg. Is this a Unix / Windows newline thing?
>>>>>>>>>>>> -Brian
>>>>>>>>>>>> On Fri, May 1, 2015 at 11:27 AM, Julia Wang (QIUHE)
>>>>>>>>>>>> <Qi...@microsoft.com> wrote:
>>>>>>>>>>>>> This is to call for a new vote for the source release of
>>>>>>>>>>>>> Apache REEF
>>>>>>>>>> 0.11.0-incubating (rc2).
>>>>>>>>>>>>> The source tar ball, including signatures, digests, etc
>>>>>>>>>>>>> can be found
>>>>>>>>>> at:
>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.
>>>>>>>>>> 0
>>>>>>>>>> -i
>>>>>>>>>> ncu
>>>>>>>>>> bating/
>>>>>>>>>>>>> The Git tag is release-0.11.0-incubating-rc2 The Git
>>>>>>>>>>>>> commit ID is
>>>>>>>>>>>>> 57a3a3e1ac61d538e551c4804159ffe96ef686a6
>>>>>>>>>>>>> Checksums of apache-reef-0.11.0-incubating-rc2.tar.gz:
>>>>>>>>>>>>> MD5: 98f85baab21d1d12b3987fd92a0b7235
>>>>>>>>>>>>> SHA1: e795962425f09ab78d47ae8f6181a36f36a2d2a0
>>>>>>>>>>>>> SHA512:
>>>>>>>>>> fee8800edc73bfa9c99b66522ca3dced3604d9d56b71b0e0f51a79e69dc9f
>>>>>>>>>> b7
>>>>>>>>>> 7
>>>>>>>>>> b0
>>>>>>>>>> e51
>>>>>>>>>> 958593b43e28d321e863391f5740e43143ae0f065b193e90a9e5d00f58f
>>>>>>>>>>>>> Release artifacts are signed with the key. The KEYS file
>>>>>>>>>>>>> is available
>>>>>>>>>> here:
>>>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/
>>>>>>>>>>>>> KE
>>>>>>>>>>>>> YS
>>>>>>>>>>>>> Issues Resolved:
>>>>>>>>>>>>> 148 issues were closed/resolved for this release:
>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20RE
>>>>>>>>>> EF
>>>>>>>>>> %
>>>>>>>>>> 20
>>>>>>>>>> AND
>>>>>>>>>> %20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20
>>>>>>>>>> in
>>>>>>>>>> %
>>>>>>>>>> 20
>>>>>>>>>> (Fi
>>>>>>>>>> xed%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex
>>>>>>>>>> =1
>>>>>>>>>> 5
>>>>>>>>>> 0
>>>>>>>>>>>>> The vote will be open for 72 hours. Please download the
>>>>>>>>>>>>> release
>>>>>>>>>> candidate, check the hashes/signature, build it and test it,
>>>>>>>>>> and then please vote:
>>>>>>>>>>>>> [ ] +1 Release this package as Apache REEF
>>>>>>>>>>>>> 0.11.0-incubating [ ]
>>>>>>>>>>>>> +0 no opinion [ ] -1 Do not release this package because ...
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Julia
>>>>>>>>> --
>>>>>>>>> Byung-Gon Chun
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Byung-Gon Chun
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Byung-Gon Chun
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Byung-Gon Chun
>>>
>>>
>>>
>>> --
>>> Byung-Gon Chun
>>
RE: Adding public key to people.apache.org/keys/committer/
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
Thanks Brian! That helps. I will check what I did differently and back to you.
Thanks,
Julia
-----Original Message-----
From: Brian Cho [mailto:chobrian@gmail.com]
Sent: Sunday, May 10, 2015 6:38 PM
To: dev@reef.incubator.apache.org
Subject: Adding public key to people.apache.org/keys/committer/
Hi,
As I'm next in line in the process (release manager for 0.12) I went ahead and gave it a shot.
The end product was I got my key to appear on http://people.apache.org/keys/committer/chobrian.asc . Here are the steps.
Please let me know if any of the steps can't be reproduced.
(I used Mac OS X)
1. Create a new key.
I followed exactly the steps at
http://www.apache.org/dev/openpgp.html#key-gen-generate-key
Fortunately, my default setup used sha512. You may want to double check with the steps here http://www.apache.org/dev/openpgp.html#sha1
2. Export the key.
http://www.apache.org/dev/openpgp.html#export-key
3. scp the key to minotaur.apache.org:/home/chobrian/.pgpkey
Also, make sure read permissions are added to .pgpkey (`chmod +r .pgpkey`).
This part was in fact tricky because it wasn't clear where to ssh to, and it turns out I didn't have my ssh public key setup yet.
I had to go to the LDAP page: https://id.apache.org
(a) The server to ssh to is under "SSH Access". For me it was minotaur.apache.org
(b) Then I added an ssh public key to "SSH Key (authorized_keys line)" in the format: ssh-rsa AAAA...8Yd4j bcho@Brians-MacBook-Pro.local (I've redacted most of my public key here, but not on the form). Insert "Password" again and press "Submit changes..."
After these two steps I could ssh/scp.
4. Add Fingerprint to LDAP
Add under "OpenPGP Public Key Primary Fingerprint" in the format: C666 0000
0000 0000 0000 0000 0000 0000 0000 0CF4 (I've redacted most of my fingerprint here, but not on the form). Insert "Password" again and press "Submit changes..."
5. Wait... :)
This is maybe the hardest part. It took about a couple hours before I saw my key appear on http://people.apache.org/keys/committer/
Hope this helps!
-Brian
On Sun, May 10, 2015 at 5:45 PM, Byung-Gon Chun <bg...@gmail.com> wrote:
> I am still traveling. I just followed the guideline. Nothing else.
> Perhaps you need to contact the apache infrastructure team?
>
> - Gon
>
> 나의 iPhone에서 보냄
>
> 2015. 5. 10. 오전 7:13 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
>
> > Hi Gon,
> >
> > I did follow the steps and installed the key to the LDAP profile.
> However, I didn't see my key shown up at https://people.apache.org/keys.
> That was one of the questions I was asking.
> >
> > Would you mind we set up a few minutes to talk about how to do it if
> > you
> are not traveling? That would save a lot of more time backing forth.
> >
> > Thanks,
> > Julia
> >
> > -----Original Message-----
> > From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> > Sent: Saturday, May 9, 2015 12:41 PM
> > To: dev@reef.incubator.apache.org
> > Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >
> > Juila,
> >
> > Did you do the following step in the How To OpenPGP page?
> >
> > PGPKEY
> >
> > The .pgpkey file in your home directory on people.apache.org should
> contain an ASCII armored <
> http://www.apache.org/dev/release-signing.html#ascii> public key <
> http://www.apache.org/dev/release-signing.html#public-private> export
> < http://www.apache.org/dev/release-signing.html#export> of all the
> keys which you use for signing Apache releases.
> >
> > To create an ASCII armored
> > <http://www.apache.org/dev/release-signing.html#ascii> export <
> http://www.apache.org/dev/release-signing.html#export> :
> >
> > -
> >
> > When using a transition
> > <http://www.apache.org/dev/release-signing.html#transition> , follow
> > these instructions
> > <http://www.apache.org/dev/key-transition.html#transition-export>.
> > -
> >
> > Otherwise gpg --output *KEYID*.asc --armor --export *KEYID* (where
> > *KEYID* is the key ID
> > <http://www.apache.org/dev/release-signing.html#key-id> of the key
> > to
> be
> > exported). See this guide
> > <http://www.apache.org/dev/openpgp.html#export-key> for more details.
> >
> > The result should then be scp 'd into place in your home directory
> > on
> people.apache.org and installed in your LDAP profile <
> https://id.apache.org/> (which will make it available on
> https://people.apache.org/keys/).
> > If you install your key in your LDAP profile, your key should be
> available under https://people.apache.org/keys/<yourid>.asc.
> >
> > -Gon
> >
> >
> >
> >
> >> On Sat, May 2, 2015 at 10:44 PM, Byung-Gon Chun <bg...@gmail.com>
> wrote:
> >>
> >> Hi Julia,
> >>
> >> A release candidate is typically put under
> .../dist/dev/incubator/reef...
> >>
> >> Last time I used my apache home directory.
> >>
> >> I think it is good to put only the final approved release under
> >> .../dist/release...
> >> It's likely that the folder is mirrored globally.
> >>
> >> I will check how I added my pub key when I have access to my laptop.
> >>
> >> Thanks.
> >> -Gon
> >>
> >> 나의 iPhone에서 보냄
> >>
> >> 2015. 5. 3. 오후 1:21 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
> >>
> >>> Hi Gon,
> >>>
> >>> Thanks for verifying it and catching some corner cases! I will
> >>> update
> >> the source in next round.
> >>>
> >>> Looks like our emails were delayed. I made rc3 on Friday, in which
> >>> I
> >> used CygWin to regenerate the digests and uploaded. You can look at
> >> it to see if format is OK now.
> >>>
> >>> This is the command I used to generate .sha512 file:
> >>> sha512sum apache-reef-0.11.0-incubating-rc2.tar.gz >
> >> apache-reef-0.11.0-incubating-rc2.tar.gz.sha512
> >>>
> >>> One question: I tried to checkout
> >> https://people.apache.org/keys/committer. Got the following after
> >> typing the command line, but don't get anything really checked out.
> >>>
> >>>> svn co https://people.apache.org/keys/committer
> >>> Redirecting to URL 'https://people.apache.org/keys/committer':
> >>> Redirecting to URL 'https://people.apache.org/keys/committer':
> >>> svn: E195019: Redirect cycle detected for URL '
> >> https://people.apache.org/keys/committer'
> >>>
> >>> What is the right command to check it out so that I can add my key
> >>> file
> >> under committer?
> >>>
> >>> Thanks,
> >>> Julia
> >>>
> >>> -----Original Message-----
> >>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> >>> Sent: Friday, May 01, 2015 11:46 PM
> >>> To: dev@reef.incubator.apache.org
> >>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >>>
> >>> Thanks. I checked the tar ball.
> >>>
> >>> The copyright of the following files should be fixed.
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Client/run.cmd:@REM Copyright (C) 2013
> >> Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Client/run.cmd::: Copyright (C) 2013
> >>> Microsoft
> >> Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:@REM
> >>> Copyright
> >>> (C) 2013 Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Network.Examples.Client/run.cmd:::
> >>> Copyright
> >> (C)
> >>> 2013 Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd:@REM Copyright (C) 2013
> >> Microsoft Corporation
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Tests/run.cmd::: Copyright (C) 2013
> >>> Microsoft
> >> Corporation
> >>>
> >>>
> >>> find . -type f | xargs file
> >>>
> >>> shows that we have "ASCII English text", "ASCII English text, with
> >>> CRLF
> >> line terminators", "UTF-8 Unicode (with BOM) English text, with
> >> CRLF line terminators", etc. I'm wondering if we want to at least
> >> change ASCII English text, with CRLF line terminators to ASCII English text.
> >> Just a question.
> >>>
> >>>
> >>> ./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest:
> >>> cannot
> >>> open
> >> `./lang/cs/Org.Apache.REEF.Driver/Evaluator/IEvaluatorRequest' (No
> >> such file or directory)
> >>>
> >>> .cs:
> >>>
> >>> "IEvaluatorRequest .cs" There is a space between t and .cs. The
> >>> file
> >> name should be fixed.
> >>>
> >>>
> >>> md5, sha1 match. The signature's verified.
> >>> How did you generate sha512? This's a binary file format. I didn't
> >>> check
> >> sha512.
> >>>
> >>>
> >>>
> >>> Tests pass on my local mac machine.
> >>> I didn't test with YARN and Mesos.
> >>>
> >>> On Sat, May 2, 2015 at 2:38 AM, Julia Wang (QIUHE) <
> >> Qiuhe.Wang@microsoft.com
> >>>> wrote:
> >>>
> >>>> I have update rc2 tar ball on
> >>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.0-
> >>>> in
> >>>> cub
> >>>> ating/
> >>>>
> >>>> " Could you put a new rc2 tar ball, for which we will vote, on
> >>>> the web?", Do you mean above web site?
> >>>
> >>> Yes. Thank you.
> >>>
> >>>
> >>>> " please update digests to check?". Could you please elaborate
> >>>> what is
> >> it?
> >>>>
> >>>> I meant md5, sha1, and sha512. Thanks!
> >>>
> >>>
> >>>> I don't see attached cleaned up key. Brain, could you please send
> again?
> >>>>
> >>>> I exported the key to a key file. And I tried to install the key
> >>>> to my LDAP profile, but it is not shown in
> https://people.apache.org/keys.
> >>>> Can someone share the detail steps for how to upload the
> >>>> juliaw.asc to Apache ( https://people.apache.org/keys/committer/juliaw.asc)?
> >>>>
> >>>> You can add your key under .../committer. Use svn.
> >>>
> >>> -Gon
> >>>
> >>>
> >>>
> >>>> Thanks,
> >>>> Julia
> >>>>
> >>>> -----Original Message-----
> >>>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> >>>> Sent: Friday, May 1, 2015 12:49 AM
> >>>> To: dev@reef.incubator.apache.org
> >>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >>>>
> >>>> Also, please update digests to check. Thanks!
> >>>>
> >>>>> On Fri, May 1, 2015 at 3:51 PM, Byung-Gon Chun
> >>>>> <bg...@gmail.com>
> >> wrote:
> >>>>>
> >>>>> Could you put a new rc2 tar ball, for which we will vote, on the web?
> >>>>> Thanks!
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Fri, May 1, 2015 at 3:13 PM, Julia Wang (QIUHE) <
> >>>>> Qiuhe.Wang@microsoft.com> wrote:
> >>>>>
> >>>>>> Yeah, I will remove those folders and files.
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Brian Cho [mailto:chobrian@gmail.com]
> >>>>>> Sent: Thursday, April 30, 2015 9:04 PM
> >>>>>> To: dev@reef.incubator.apache.org
> >>>>>> Cc: dev@reef.incubator.apache.org
> >>>>>> Subject: Re: [VOTE] Release Apache REEF 0.11.0-incubating (rc2)
> >>>>>>
> >>>>>> In terms of the tarball:- I see many (all?) differences from
> >>>>>> the
> >> branch.
> >>>>>> It looks like the files have windows-style returns (\r\n)
> >>>>>>
> >>>>>> - We should remove .idea directory
> >>>>>>
> >>>>>> - We should remove reef-project.iml
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> -Brian
> >>>>>>
> >>>>>> On Fri, May 1, 2015 at 12:50 PM, Byung-Gon Chun
> >>>>>> <bg...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> Julia, could you address the problems Brian mentioned?
> >>>>>>> These points'll be raised again by the IPMC members.
> >>>>>>> On Fri, May 1, 2015 at 12:25 PM, Brian Cho
> >>>>>>> <ch...@gmail.com>
> >>>> wrote:
> >>>>>>>> I also see a non-ascii character (a BOM perhaps?) on the md5,
> >>>>>>>> sha1,
> >>>>>>>> sha512 files, that prevent automatic checking of the hashes,
> >>>>>>>> e.g., using md5sum -c <file> on Linux.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> The checksums themselves match, it’s just the file format
> >>>>>>>> seems a little off because of the character at the beginning.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> -Brian
> >>>>>>>>
> >>>>>>>> On Fri, May 1, 2015 at 12:09 PM, Brian Cho
> >>>>>>>> <ch...@gmail.com>
> >>>> wrote:
> >>>>>>>>
> >>>>>>>>> I’ve attached a cleaned-up version of KEYS. There were some
> >>>>>>>>> carriage
> >>>>>>>> returns in the key, and also some missing newlines in the header.
> >>>>>>>>> This edited version worked for me.
> >>>>>>>>> -Brian
> >>>>>>>>> On Fri, May 1, 2015 at 12:03 PM, Brian Cho
> >>>>>>>>> <ch...@gmail.com>
> >>>>>> wrote:
> >>>>>>>>>> When I download the KEYS file and run `gpg —import KEYS`,
> >>>>>>>>>> Julia’s key
> >>>>>>>> is not imported. This leads to the verification `gpg —verify`
> >>>> failing.
> >>>>>>>>>> Only the following three keys are imported:
> >>>>>>>>>> ```
> >>>>>>>>>> gpg: key 7DF6AF74: public key "Byung-Gon Chun (CODE SIGNING
> >>>>>>>>>> KEY) <
> >>>>>>>> bgchun@apache.org>" imported
> >>>>>>>>>> gpg: key B876884A: public key "Chris Mattmann (CODE SIGNING
> >>>>>>>>>> KEY) <
> >>>>>>>> mattmann@apache.org>" imported
> >>>>>>>>>> gpg: key 3D0C92B9: public key "Owen O'Malley (Code signing)
> >>>>>>>>>> <
> >>>>>>>> omalley@apache.org>" imported
> >>>>>>>>>> gpg: Total number processed: 3
> >>>>>>>>>> gpg: imported: 3 (RSA: 2)
> >>>>>>>>>> ```
> >>>>>>>>>> It looks like Julia’s information is missing newlines,
> >>>>>>>>>> maybe confusing
> >>>>>>>> gpg. Is this a Unix / Windows newline thing?
> >>>>>>>>>> -Brian
> >>>>>>>>>> On Fri, May 1, 2015 at 11:27 AM, Julia Wang (QIUHE)
> >>>>>>>>>> <Qi...@microsoft.com> wrote:
> >>>>>>>>>>> This is to call for a new vote for the source release of
> >>>>>>>>>>> Apache REEF
> >>>>>>>> 0.11.0-incubating (rc2).
> >>>>>>>>>>> The source tar ball, including signatures, digests, etc
> >>>>>>>>>>> can be found
> >>>>>>>> at:
> >>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/0.11.
> >>>>>>>> 0
> >>>>>>>> -i
> >>>>>>>> ncu
> >>>>>>>> bating/
> >>>>>>>>>>> The Git tag is release-0.11.0-incubating-rc2 The Git
> >>>>>>>>>>> commit ID is
> >>>>>>>>>>> 57a3a3e1ac61d538e551c4804159ffe96ef686a6
> >>>>>>>>>>> Checksums of apache-reef-0.11.0-incubating-rc2.tar.gz:
> >>>>>>>>>>> MD5: 98f85baab21d1d12b3987fd92a0b7235
> >>>>>>>>>>> SHA1: e795962425f09ab78d47ae8f6181a36f36a2d2a0
> >>>>>>>>>>> SHA512:
> >>>>>>>> fee8800edc73bfa9c99b66522ca3dced3604d9d56b71b0e0f51a79e69dc9f
> >>>>>>>> b7
> >>>>>>>> 7
> >>>>>>>> b0
> >>>>>>>> e51
> >>>>>>>> 958593b43e28d321e863391f5740e43143ae0f065b193e90a9e5d00f58f
> >>>>>>>>>>> Release artifacts are signed with the key. The KEYS file
> >>>>>>>>>>> is available
> >>>>>>>> here:
> >>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/reef/
> >>>>>>>>>>> KE
> >>>>>>>>>>> YS
> >>>>>>>>>>> Issues Resolved:
> >>>>>>>>>>> 148 issues were closed/resolved for this release:
> >>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20RE
> >>>>>>>> EF
> >>>>>>>> %
> >>>>>>>> 20
> >>>>>>>> AND
> >>>>>>>> %20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20
> >>>>>>>> in
> >>>>>>>> %
> >>>>>>>> 20
> >>>>>>>> (Fi
> >>>>>>>> xed%2C%20Implemented)%20ORDER%20BY%20updated%20ASC&startIndex
> >>>>>>>> =1
> >>>>>>>> 5
> >>>>>>>> 0
> >>>>>>>>>>> The vote will be open for 72 hours. Please download the
> >>>>>>>>>>> release
> >>>>>>>> candidate, check the hashes/signature, build it and test it,
> >>>>>>>> and then please vote:
> >>>>>>>>>>> [ ] +1 Release this package as Apache REEF
> >>>>>>>>>>> 0.11.0-incubating [ ]
> >>>>>>>>>>> +0 no opinion [ ] -1 Do not release this package because ...
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> Julia
> >>>>>>> --
> >>>>>>> Byung-Gon Chun
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Byung-Gon Chun
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Byung-Gon Chun
> >>>
> >>>
> >>>
> >>> --
> >>> Byung-Gon Chun
> >
> >
> >
> > --
> > Byung-Gon Chun
>