Re: Signature verification for 4.1.3-RC1

We should ensure that AOO people join the keysignings @ ApacheCon > On Oct 8, 2016, at 9:08 AM, Andrea Pescetti wrote: > > This is not a blocker for the release (and moreover signature files are > explicitly allowed to be updated during the release vote if needed), but I >

Re: Signature verification for 4.1.3-RC1

Patricia Shanahan wrote: Please test again. I have tried to fix both MIT and the KEYS file. Thanks, it works now after importing the new KEYS file: $ gpg --verify apache-openoffice-4.1.3-r1761381-src.tar.gz.asc apache-openoffice-4.1.3-r1761381-src.tar.gz gpg: Signature made Sat Oct 1

Re: Signature verification for 4.1.3-RC1

Patricia Shanahan wrote: I had to make a change in the key preferences to meet the release signing requirements. I uploaded to a couple of servers, including MIT, and waited a few days. I can find mine here (note: you have to add "0x" for the search to succeed):

Re: Signature verification for 4.1.3-RC1

I had to make a change in the key preferences to meet the release signing requirements. I uploaded to a couple of servers, including MIT, and waited a few days. I didn't think we were supposed to update KEYS directly? On 10/8/2016 6:08 AM, Andrea Pescetti wrote: This is not a blocker for the

Signature verification for 4.1.3-RC1

This is not a blocker for the release (and moreover signature files are explicitly allowed to be updated during the release vote if needed), but I couldn't verify signatures in a straightforward way for source packages. One of the signatures is mine; no problem with that, and that itself is