+1

        * Signature: ok
        * Checksum : failed
        * Rat check (1.8.0_362): ok
         - mvn clean apache-rat:check
        * Built from source (1.8.0_362): ok
         - mvn clean install  -DskipTests
        * Unit tests pass (1.8.0_362): ok
         - mvn clean package -P runAllTests  -Dsurefire.rerunFailingTestsCount=3

I had a similar formatting problems in our automated checksum verification, but 
I manually confirmed that they match.

On 2025/01/18 13:17:11 "张铎(Duo Zhang)" wrote:
> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-4.1.10RC0
> 
> The VOTE will remain open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache hbase thirdparty 4.1.10
> [ ] -1 Do not release this package because ...
> 
> The tag to be voted on is 4.1.10RC0:
> 
>   https://github.com/apache/hbase-thirdparty/tree/4.1.10RC0
> 
> This tag currently points to git reference
> 
>   cddc2ce8a399f2e9c9f37cf0409496a1c2089fb2
> 
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
> 
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-4.1.10RC0/
> 
> Maven artifacts are available in a staging repository at:
> 
>   https://repository.apache.org/content/repositories/orgapachehbase-1562/
> 
> Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> 
>   https://downloads.apache.org/hbase/KEYS
> 
> To learn more about Apache hbase thirdparty, please see
> 
>   http://hbase.apache.org/
> 
> Thanks,
> Your HBase Release Manager
> 

Reply via email to