New git signing key for Eric Bavier?

New git signing key for Eric Bavier?

[Mark H Weaver]

Hi Eric,

bavier@member.fsf.org (Eric Bavier) writes:
> bavier pushed a commit to branch master
> in repository guix.
>
> commit d56c55fffbe962cf7c44030ae4eac53ffa1e1f85
> Author: Eric Bavier <bavier@member.fsf.org>
> Date:   Thu Jun 15 00:37:17 2017 -0500
>
>     gnu: tomb: Upgrade to 2.4.

This commit, and another recent commit (e0c9530) of yours, were signed
using a key that's different from the one you've previously used to sign
commits, and different from the key you have registered on Savannah.

Can you please confirm that A0C5E3522EF8EF5C64CDB7F0FD73CAC719D32566 is
your new key, sign it with your old key if possible, and upload this new
key to Savannah?

      Mark

Re: New git signing key for Eric Bavier?

[Eric Bavier]

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

On Sun, 18 Jun 2017 01:30:07 -0400
Mark H Weaver <mhw@netris.org> wrote:

> Hi Eric,
> 
> bavier@member.fsf.org (Eric Bavier) writes:
> > bavier pushed a commit to branch master
> > in repository guix.
> >
> > commit d56c55fffbe962cf7c44030ae4eac53ffa1e1f85
> > Author: Eric Bavier <bavier@member.fsf.org>
> > Date:   Thu Jun 15 00:37:17 2017 -0500
> >
> >     gnu: tomb: Upgrade to 2.4.  
> 
> This commit, and another recent commit (e0c9530) of yours, were signed
> using a key that's different from the one you've previously used to sign
> commits, and different from the key you have registered on Savannah.
> 
> Can you please confirm that A0C5E3522EF8EF5C64CDB7F0FD73CAC719D32566 is
> your new key,

That is indeed my new key.

> sign it with your old key if possible, and upload this new
> key to Savannah?

I've just put the new key on Savannah.  It should be signed with my old
key.

Thanks for saying something.  I'm still learning things about gpg.

`~Eric

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]