Packagers: PGP signing key changes for Breathe >= v4.23.0

[vermeeren]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

The PGP key that was used for Breathe < v4.23.0 is:
pub   rsa4096/9EF1DC92B5F301BD 2015-08-09 Melvin Vermeeren <mail@mel.vin>
 Primary key fingerprint: 79DC 0FAF 18C3 1807 E82E  1A6B 9EF1 DC92 B5F3 01BD

The PGP key that will be used for Breathe >= v4.23.0 is:
pub   rsa4096/A72F627716EA9D96 2019-09-26 Melvin Vermeeren (vermware) <vermeeren@vermwa.re>
 Primary key fingerprint: 8AED 5802 1FEA CDD5 F27B  A0E6 A72F 6277 16EA 9D96

Public key itself can be found on the usual keyservers.
I submit them manually to https://keys.openpgp.org/ and the SKS pool.

Maintainership will continue without any changes.
This message is signed by the old key.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETnzUjuV5O+rCrz6nRiwQnTrHuFkFAl+PAfIACgkQRiwQnTrH
uFnQWhAAo/1yw9QYbrCZLfVLZAadgUsslRsA0RDK8Gcv52wz0Ix4zNTF7jwc4Ewr
gQI0u0Hn4Gezdphtxji/EhJT5b6UipTyvyPNh3LRpa3BI6md4z9yKg/9OB23EH8r
xTTUA5424bi2rIpcD/NMbDJHWaCTKuXa3Dt1r3k+bP/7+rORyu2DqiSxvE3j4YwV
O9HkvQwvuY7pjbRyh7zDmv1rT12AuHzUcnkNBvezFex7a60Z3Yc1QdeZI21+lus9
ph7w9AeKhk2She2auWdAK9OiopLjdCEACBV1WqHlh/bITi02lddO5Av/W6dbrjnV
6vsFe5rE3G6axN6om9rfzDf5ycjtNVm6JcCtgwfgwCMSfhna042m6sO5unePp3kp
IjLlCyv0/9GQETscRjoJI1PYeksTIkVZq0Zzry9Kfsr13d7YQn71C8q+X7l+wFd/
9qn0iEfoFlmoUk7zMDMIhp1Unahe5Y9WjKIqCoLQC2TB8BPFsmn0EQB0/Hp6N8HU
fD3LTBBmSG1xrwiWMj8hRhhQxoBwf83ZU0B/z/zQlMil4jrGfYbgenm5ZavkVQyp
mQAsrIKDbbWPsNI+/5tWIPByPB00JifwEIuAoNnFOEYo9sQEYAvZZiqcHVP6bbfN
H2uTDpzScyalzo9+qQuzYZczMQlkeHdd/qtZe+mePqH+tnIMNzg=
=2iZy
-----END PGP SIGNATURE-----

[michaeljones]

@vermeeren - to check, the deploy key email I've just had is from you?

[vermeeren]

@michaeljones Yeah. To check more, the SHA512 of the deploy key itself, including ssh-rsa and comment at the end is, is 91b23af945b12f1cde4b89fc6bdfbe62232681e4a835a0382ad1373b52bfb5bb434220a165b12f5a033d564f4e0efb9e1d98d095ae34c65358d4b041ce7ccd40.

[michaeljones]

Thanks for the extra validation. All makes me a little nervous though :)

I'm afraid it errors saying "Key is already in use." Perhaps you've already got it for another project? Only a guess though. I don't know what the actual restrictions are.

[vermeeren]

@michaeljones Added the key to my personal GitHub account earlier to make sure things are set up properly. Indeed that would cause conflict, I just removed it. Can you try again?

[michaeljones]

Done!

[vermeeren]

@michaeljones Confirmed it works nicely over here, thanks again!

[vermeeren]

Commit 8004da9 removes the notice from the README as it's been up for approx half a year, so I also consider it time to unpin this issue and close it.