Thanks, Henry!

On Fri, Jul 1, 2016 at 10:19 PM, Henry Saputra <[email protected]>
wrote:

> As I remember the LDAP sync will automatically update the key group file.
>
> - Henry
>
> On Thu, Jun 30, 2016 at 10:15 PM, Michael Wu <[email protected]> wrote:
>
> > Hi Henry,
> >
> > My gpg fingerprint has been updated on id.apache.org, how can I add my
> key
> > to keys/groups/eagle.asc, is there any place that automatically sync the
> > keys to groups, please? Thanks!
> >
> > Michael
> >
> > On Thu, Jun 30, 2016 at 3:56 PM, Henry Saputra <[email protected]>
> > wrote:
> >
> > > Putting the KEYS in dis folder is used to verify the signature of the
> > > release artifacts.
> > >
> > > I think it is more used for convenience since Eagle already have group
> > sig
> > > file at https://people.apache.org/keys/group/eagle.asc
> > >
> > > - Henry
> > >
> > > On Thu, Jun 30, 2016 at 1:55 PM, Michael Wu <[email protected]>
> wrote:
> > >
> > > > Hi Hemanth,
> > > >
> > > > Reading your WIKI of release process, I've merged my gpg-pub-key into
> > > KEYS
> > > > file, and have committed it to svn, which is visible at
> > > > http://www.apache.org/dist/incubator/eagle/.
> > > >
> > > > However, I got confused on step-14 at below fragment, see:
> > > > *********************
> > > > ......
> > > > Once this file has been updated, you need to publish it in the
> > > appropriate
> > > > dist directory for the project on http://www.apache.org/dist. To do
> > > this,
> > > > you must copy the file as follows:
> > > >       $ scp KEYS people.apache.org:/www/
> > > > www.apache.org/dist/incubator/eagle/KEYS
> > > >       <http://org/www/www.apache.org/dist/incubator/sentry/KEYS>
> > > > ......
> > > > *********************
> > > >
> > > > My question is, now that the KEYS has been committed to svn, what's
> the
> > > use
> > > > this fragment? Will it block releasing if I ignore it? Also, what
> does
> > it
> > > > mean in the angle bracket pair "<>", do you mean we have to scp the
> > KEYS
> > > to
> > > > the 2 urls, both?
> > > >
> > > > Thanks.
> > > > Michael
> > > >
> > >
> >
>

Reply via email to