I've committed the updated .asc files in revision 24339. MD5 and SHA-512 hashes are still the same.
Do note that you can also verify the git tag using the same gpg key via this command: git tag --verify chainsaw-2.0.0-rc2 On 20 January 2018 at 16:47, Matt Sicker <boa...@gmail.com> wrote: > I didn't change my key (last 8 characters are the same as the short id). > Looks like I might have signed it wrong. > > On 20 January 2018 at 15:01, ralph.goers dslextreme.com < > ralph.go...@dslextreme.com> wrote: > >> Did you use a new signing key? When I try to verify I get >> >> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc >> apache-chainsaw-2.0.0-bin.tar.gz >> gpg: Signature made Fri Nov 10 11:41:12 2017 MST >> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708 >> 93B62BABE8 >> gpg: BAD signature from "Matthew Sicker (Signing Key) < >> mattsic...@apache.org>" [undefined] >> >> Ralph >> >> >> ----- Original Message ----- >> From: "Matt Sicker" <boa...@gmail.com> >> To: "Apache Logging Developers List" <dev@logging.apache.org> >> Sent: Saturday, January 20, 2018 10:42:21 AM >> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2 >> >> This is a vote to release Apache Chainsaw 2.0.0-rc2 >> >> Source and binary artifacts: >> >> https://dist.apache.org/repos/dist/dev/logging/chainsaw/ >> >> Committed under SVN revision 24337. >> >> Site: >> >> http://musigma.org/chainsaw-site/ >> https://github.com/jvz/chainsaw-site >> >> Git: >> >> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git >> tag: chainsaw-2.0.0-rc2 < >> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g >> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d >> > >> >> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D. >> >> This vote will be open for at least 72 hours and requires at least 3 +1 >> votes and no more -1 votes than +1 votes. >> >> -- >> Matt Sicker <boa...@gmail.com> >> >> > > > -- > Matt Sicker <boa...@gmail.com> > -- Matt Sicker <boa...@gmail.com>
