On 2021/12/14 03:25:45 linlin wrote:
> This is the first release candidate for Apache Pulsar, version 2.8.2.
>
> It fixes the following issues:
> https://github.com/apache/pulsar/issues?q=label%3Acherry-picked%2Fbranch-2.8+is%3Aclosed+label%3Arelease%2F2.8.2
>
> *** Please download, test and v
-1,
I verified the packages, but the signatures are invalid.
It looks like the
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.8.2-candidate-1/apache-pulsar-2.8.2-bin.tar.gz.asc
file is from December 1st.
I checked this in the SVN staging repository history (
https://dist.apache.org/repos
Lin Lin,
-1 (binding)
I have verified the packages, all good:
- unit tests are passing (many flaky tests)
- RAT passes
- build passes (JDK11 on Ubuntu)
- Pulsar standalone works (basic smoke tests)
But I am not able to verify the signatures.
Please check the commands you used to stage the releas
Thank you for the rc!
I also found the same problem mentioned by Nicolo, when running:
sha512sum -c apache-pulsar-2.8.2-bin.tar.gz
I get the error:
sha512sum: WARNING: 1 computed checksum did NOT match
Also, when verifying the GPG keys, as well, running:
gpg --verify apache-pulsar-2.8.2-bin.t
Thank you for driving the release!
I found out a problem with the checksum of apache-pulsar-2.8.2-bin.tar.gz
You wrote in the email the sha512 is f51e93d5[..]683 and actually it is
correct (shasum -a 512 apache-pulsar-2.8.2-bin.tar.gz
But this file (
https://dist.apache.org/repos/dist/dev/pulsar/
This is the first release candidate for Apache Pulsar, version 2.8.2.
It fixes the following issues:
https://github.com/apache/pulsar/issues?q=label%3Acherry-picked%2Fbranch-2.8+is%3Aclosed+label%3Arelease%2F2.8.2
*** Please download, test and vote on this release. This vote will stay open
for at
