New git signing key for Jan Nieuwenhuizen?

New git signing key for Jan Nieuwenhuizen?

[Mark H Weaver]

Hi Jan,

> commit ebfb71d45615698040818a68b7dc34996ff4c046
> gpg: Signature made Fri 16 Jun 2017 07:22:49 AM EDT
> gpg:                using RSA key DB34CB51D25C9408156FCDD6A12F87978D701B99
> gpg: Can't check signature: No public key
> Author: Jan Nieuwenhuizen <janneke@gnu.org>
> Date:   Thu Jun 15 19:22:00 2017 +0200
> 
>     tests: Allow setting of qemu memory-size for system tests.
> 
>     * gnu/system/vm.scm (common-qemu-options): Remove hardcoded "-m 256".
>     (system-qemu-image/shared-store-script): New keyword argument: #:memory-size.

This commit was signed using a different key than the one you've been
using for your other commits, and different from the one you have
registered on Savannah.

Is DB34CB51D25C9408156FCDD6A12F87978D701B99 your key?

      Mark

Re: New git signing key for Jan Nieuwenhuizen?

[Jan Nieuwenhuizen]

Mark H Weaver writes:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

>> commit ebfb71d45615698040818a68b7dc34996ff4c046
>> gpg: Signature made Fri 16 Jun 2017 07:22:49 AM EDT
>> gpg:                using RSA key DB34CB51D25C9408156FCDD6A12F87978D701B99
>> gpg: Can't check signature: No public key
>> Author: Jan Nieuwenhuizen <janneke@gnu.org>
>> Date:   Thu Jun 15 19:22:00 2017 +0200
>> 
>>     tests: Allow setting of qemu memory-size for system tests.
>> 
>>     * gnu/system/vm.scm (common-qemu-options): Remove hardcoded "-m 256".
>>     (system-qemu-image/shared-store-script): New keyword argument: #:memory-size.
>
> This commit was signed using a different key than the one you've been
> using for your other commits, and different from the one you have
> registered on Savannah.
>
> Is DB34CB51D25C9408156FCDD6A12F87978D701B99 your key?

Yes, that's my new key.  Oops.  I have updated my key on savannah.
janneke
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE2zTLUdJclAgVb83WoS+Hl41wG5kFAllGFv4ACgkQoS+Hl41w
G5mcHg/+Pd3AvBLSmoPUrXrhFcFrhQyVdq/d6f2R0JiSkrPy402P003Bp6pzEdD8
OxQzT/ahk7XYRrD0KywCzn6Vd3b7xd+pnBzAJ3TV7lzyXKg97qm6CAAMEdaLNd/3
18dKOUmGI5oTRAvTc7Ubdwc4E1qmI4ckBT3QW2LBDOzPaMY6wiLgIA8vETN2bq+S
vIMN9XDQRbtdwwA+k2fXQUB8b5N+bWdc1/YH5DmuqhKUiaHVCHHBc2K5L8YEydPr
0o+MrbwpmlxXjmKQTYFX8L5Wc1DARWECbPIa70TB53uWIxSQdfQQha/Oqd1fMYU0
H9jPBF0PJHjJMyrTwmvMrZFC9Xi4u3UnKdCOPOCz2DXTttOGsGRsP16so34e9UzR
DyLD7kR9K/m5djxSYLcIr8mMAfPJ0g/mk1Jyj5Yv9MZVCmFggcfeamirgcvnClxe
Nhkfyf7SPeq/qpKIVpIOabthtuuoYiH2imnlLCL+TS6qGZYtBkhxlKUjRYMFWm+F
bTwo3c+FdwOeyWdKn4a6QwIzfaJ70o1EeIYS4MUCyB1TKzcsJWE/t5R0SOqz1SX5
ofLsn8amwE0dnoCKQhX92sse+sq4ITj3oD5YpehBl4pvzeIs+7LpLHJSVDSFRfwT
N1Xy/PscHohFgcbfD8dZn/xtxRTN8dz1ysrhwLRBl8zc/tRKYPA=
=xmQy
-----END PGP SIGNATURE-----

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Re: New git signing key for Jan Nieuwenhuizen?

[Christopher Allan Webber]

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

Jan Nieuwenhuizen writes:

> Mark H Weaver writes:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>>> commit ebfb71d45615698040818a68b7dc34996ff4c046
>>> gpg: Signature made Fri 16 Jun 2017 07:22:49 AM EDT
>>> gpg:                using RSA key DB34CB51D25C9408156FCDD6A12F87978D701B99
>>> gpg: Can't check signature: No public key
>>> Author: Jan Nieuwenhuizen <janneke@gnu.org>
>>> Date:   Thu Jun 15 19:22:00 2017 +0200
>>>
>>>     tests: Allow setting of qemu memory-size for system tests.
>>>
>>>     * gnu/system/vm.scm (common-qemu-options): Remove hardcoded "-m 256".
>>>     (system-qemu-image/shared-store-script): New keyword argument: #:memory-size.
>>
>> This commit was signed using a different key than the one you've been
>> using for your other commits, and different from the one you have
>> registered on Savannah.
>>
>> Is DB34CB51D25C9408156FCDD6A12F87978D701B99 your key?
>
> Yes, that's my new key.  Oops.  I have updated my key on savannah.
> janneke
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCAAdFiEE2zTLUdJclAgVb83WoS+Hl41wG5kFAllGFv4ACgkQoS+Hl41w
> G5mcHg/+Pd3AvBLSmoPUrXrhFcFrhQyVdq/d6f2R0JiSkrPy402P003Bp6pzEdD8
> OxQzT/ahk7XYRrD0KywCzn6Vd3b7xd+pnBzAJ3TV7lzyXKg97qm6CAAMEdaLNd/3
> 18dKOUmGI5oTRAvTc7Ubdwc4E1qmI4ckBT3QW2LBDOzPaMY6wiLgIA8vETN2bq+S
> vIMN9XDQRbtdwwA+k2fXQUB8b5N+bWdc1/YH5DmuqhKUiaHVCHHBc2K5L8YEydPr
> 0o+MrbwpmlxXjmKQTYFX8L5Wc1DARWECbPIa70TB53uWIxSQdfQQha/Oqd1fMYU0
> H9jPBF0PJHjJMyrTwmvMrZFC9Xi4u3UnKdCOPOCz2DXTttOGsGRsP16so34e9UzR
> DyLD7kR9K/m5djxSYLcIr8mMAfPJ0g/mk1Jyj5Yv9MZVCmFggcfeamirgcvnClxe
> Nhkfyf7SPeq/qpKIVpIOabthtuuoYiH2imnlLCL+TS6qGZYtBkhxlKUjRYMFWm+F
> bTwo3c+FdwOeyWdKn4a6QwIzfaJ70o1EeIYS4MUCyB1TKzcsJWE/t5R0SOqz1SX5
> ofLsn8amwE0dnoCKQhX92sse+sq4ITj3oD5YpehBl4pvzeIs+7LpLHJSVDSFRfwT
> N1Xy/PscHohFgcbfD8dZn/xtxRTN8dz1ysrhwLRBl8zc/tRKYPA=
> =xmQy
> -----END PGP SIGNATURE-----

Though I didn't confirm in-person, Janneke and I have had other
interactions using this key to make me reasonably confident it's their
key.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]