Hello,

The warning basically says that Rui hasn't signed Haisheng's key so I guess
it is normal.

Best,
Stamatis

On Wed, May 13, 2020 at 12:48 AM Haisheng Yuan <[email protected]> wrote:

> Hi Rui,
>
> Thanks for verifying. apache.org will sync hyuan.asc once a day. So that
> should be available in a few hours.
> Regarding the warning, need to investigate what went wrong.
>
> Thanks,
> Haisheng
>
> On 2020/05/12 22:05:47, Rui Wang <[email protected]> wrote:
> > Found something that is worth mentioning in this candidate:
> >
> > 1. hyuan.asc [1] is not found on the server. Maybe the step that login
> > Apache account [2] and filled out the public key fingerprint didn't
> finish?
> > 2. Verify the artifact by "gpg --verify
> > apache-calcite-1.23.0-src.tar.gz.asc apache-calcite-1.23.0-src.tar.gz"
> but
> > got the following warning:
> >
> > gpg: Signature made Mon May 11 21:20:56 2020 PDT
> >
> > gpg:                using RSA key
> ECA9CF33AF2CEC28F3B66A5C3CD22ABAC50DDCEF
> >
> > gpg: Good signature from "Haisheng Yuan <[email protected]>" [unknown]
> >
> > gpg: WARNING: This key is not certified with a trusted signature!
> >
> > gpg:          There is no indication that the signature belongs to the
> > owner.
> >
> > Primary key fingerprint: ECA9 CF33 AF2C EC28 F3B6  6A5C 3CD2 2ABA C50D
> DCEF
> >
> >
> > [1]: https://people.apache.org/keys/committer/hyuan.asc
> > [2]: https://id.apache.org
> >
> > -Rui
> >
> >
> > On Tue, May 12, 2020 at 10:53 AM Julian Hyde <[email protected]> wrote:
> >
> > > Even though the vote is canceled, everyone please continue to test on
> RC0
> > > (until an RC1 is available). The earlier you find and report issues,
> the
> > > sooner we get to a good release.
> > >
> > >
> > > > On May 12, 2020, at 6:11 AM, Haisheng Yuan <[email protected]> wrote:
> > > >
> > > > The vote for Apache Calcite 1.23.0 release candidate 0 has beed
> > > cancelled due to regression.
> > > >
> > > > We will fix this and make rc1 available for voting.
> > > >
> > > > Best,
> > > > Haisheng Yuan
> > >
> > >
> >
>

Reply via email to