The RC0 BOM specifies Livy 0.9.0
<https://github.com/apache/bigtop/blob/release-3.6.0-RC0/bigtop.bom#L326-L333>,
but every x86_64 repository contains Livy 0.8.0, while the corresponding
ARM64 repository contains 0.9.0.

Nice catch.
I guess I forgot to re-run the (relevant part of) packaging CI job after 
merging BIGTOP-4530.
I rebuilt the Livy packages and replaced the uploaded ones.

* 
https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/DISTRO=rockylinux-9,PLATFORM=amd64-slave,PRODUCT=livy/
* 
https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/DISTRO=fedora-40,PLATFORM=amd64-slave,PRODUCT=livy/
* 
https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/DISTRO=openeuler-22.03,PLATFORM=amd64-slave,PRODUCT=livy/
* 
https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/DISTRO=debian-12,PLATFORM=amd64-slave,PRODUCT=livy/
* 
https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/DISTRO=ubuntu-24.04,PLATFORM=amd64-slave,PRODUCT=livy/

The smoke-tests is running based on the updated Livy packages.
The tests of Spark and Livy are a bit flaky on CI machines
due to limited resources.

* https://ci.bigtop.apache.org/job/Bigtop-3.6.0-smoke-tests/

The tests passed on my local machines.
I verified that the Livy 0.9.0 was downloaded and installed as expected.

Since pre-built binaries provided for users' convenience do not affect
signed release artifacts, I think we do not need to sink the RC0.

Thanks,
Masatake Iwasaki

On 8/6/2026 8:50 AM, Evans Ye wrote:
Hi all,

I think there's a mismatch between the RC0 source and the published package
repositories.

The RC0 BOM specifies Livy 0.9.0
<https://github.com/apache/bigtop/blob/release-3.6.0-RC0/bigtop.bom#L326-L333>,
but every x86_64 repository contains Livy 0.8.0, while the corresponding
ARM64 repository contains 0.9.0.

Reproduce steps:

docker run --rm --platform linux/amd64 debian:12-slim sh -c '
apt-get update >/dev/null &&
apt-get install -y curl gnupg >/dev/null &&
curl -fsSL \

https://dist.apache.org/repos/dist/dev/bigtop/bigtop-3.6.0-RC0/repos/GPG-KEY-bigtop
|
   gpg --dearmor -o /usr/share/keyrings/bigtop.gpg &&
echo "deb [signed-by=/usr/share/keyrings/bigtop.gpg]
http://repos.bigtop.apache.org/releases/3.6.0/debian/12/amd64 bigtop
contrib" \
   > /etc/apt/sources.list.d/bigtop.list &&
apt-get update >/dev/null &&
apt-cache policy livy
'

...

livy:
   Installed: (none)
   Candidate: 0.8.0-1
   Version table:
      0.8.0-1 500
         500 http://repos.bigtop.apache.org/releases/3.6.0/debian/12/amd64
bigtop/contrib amd64 Packages

The cause is visible in Jenkins. The x86_64 Livy build
<https://ci.bigtop.apache.org/job/Bigtop-3.6.0-x86_64/DISTRO=ubuntu-24.04,PLATFORM=amd64-slave,PRODUCT=livy/4/consoleText>
  checked out commit 7477ca4 and downloaded Livy 0.8.0. The upgrade to 0.9.0
<https://github.com/apache/bigtop/commit/f81ee3aa45cabea815416e8dbc716e87957a568e>
  was committed about eight minutes after that build started.


The rest looks good to me! Shall we align the version?

- Evans

Masatake Iwasaki <[email protected]> 於 2026年8月3日週一 上午3:55寫道:

Hi Bigtop PMC members,

I'm still waiting for the vote.
I will appreciate your help for the release process.
We need 2 more +1 in addition to mine.

Regards,
Masatake Iwasaki

On Fri, Jul 10, 2026 at 6:04 PM Masatake Iwasaki <[email protected]>
wrote:

This is the vote for release 3.6.0 of Apache Bigtop. (RC0)

It fixes the following issues:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12356069&styleName=Text&projectId=12311420

The vote will be going for at least 72 hours.
Please download, test and vote with

[ ] +1, accept RC0 as the official 3.6.0 release of Apache Bigtop
[ ] +0, I don't care either way,
[ ] -1, do not accept RC0 as the official 3.6.0 release of Apache
Bigtop, because...

Source and binary files:
     https://dist.apache.org/repos/dist/dev/bigtop/bigtop-3.6.0-RC0/

Maven staging repo:

https://repository.apache.org/content/repositories/orgapachebigtop-1056

The git tag to be voted upon is release-3.6.0-RC0:
     https://github.com/apache/bigtop/tree/release-3.6.0-RC0

Bigtop's KEYS file containing PGP keys we use to sign the release:
     https://dist.apache.org/repos/dist/release/bigtop/KEYS

The results of packaging, deployment and smoke tests on the CI
environment are as follows:

https://cwiki.apache.org/confluence/display/BIGTOP/Overview+of+Bigtop+3.6.0+Support+Matrix

Regards,
Masatake Iwasaki



Reply via email to