Apologies for the typo. the gpg command to update my key is actually: gpg --recv-keys 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D
On 24 March 2018 at 13:42, Matt Sicker <[email protected]> wrote: > Hello all, it's been a while since the previous release of Logging Parent. > As this is a parent pom not directly used by users, this is a lazy vote and > requires only more +1s than -1s after 72 hours. Please leave your +1, +0, > -0, or -1, if you wish. > > Changes: > > * Java source and target version changed to 1.8 by default > * Jenkins pipeline added to parent pom > * Default dev mailing list fixed to use dev@ > * Upgrade to Apache parent pom version 19 > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachelogging-1033/ > > Git: > > https://git-wip-us.apache.org/repos/asf?p=logging-parent.git;a=commit;h= > 7a22bb7ef655721c7870625f3bbd1c2e2f8b37f9 > > Tag: logging-parent-2 > > Signed with my updated GPG key which uses the same ID as before ( > 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D, aka FA1C814D), though I > recently uploaded a modification to the key to expand the expiration date > by three years (otherwise, my previous key expired yesterday). The updated > version of the key is available in the standard KEYS file: > > https://dist.apache.org/repos/dist/release/logging/KEYS > > If you already have my key, you can update it by running: > > gpg --recv-keys 748F15B2CF9BA8F024155E6ED7C92B70FA1C814Dc > > You can import the keys file directly by running: > > gpg --import <(curl https://dist.apache.org/repos/ > dist/release/logging/KEYS) > > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
