Skip to content

feat: build trixie or bookworm, trixie by default - #30

Merged
dedene merged 1 commit into
mainfrom
feat/debian-suite-input
Oct 23, 2026
Merged

dedene merged 1 commit into
mainfrom
feat/debian-suite-input

Conversation

@dedene

@dedene dedene commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

Nimbu is moving its app image from bookworm to trixie (zenjoy/nimbu#2177), so the break-glass build has to produce trixie images too.

  • The "Build Ruby image" workflow gets a debian_suite input (trixie or bookworm, default trixie). Tags become X.Y.Z-<suite> and X.Y-<suite>, same as before for bookworm.
  • The Dockerfile defaults to DEBIAN_SUITE=trixie. Upstream's trixie and bookworm templates differ in one line: trixie cleans up with apt-get dist-clean, which bookworm's apt doesn't have. That's now a case on the suite.
  • PR smoke builds use trixie.

Tested locally: built 4.0.9 on trixie (arm64). It reports ruby 4.0.9 and OpenSSL 3.5.7 and keeps -z relro -z now in RbConfig.

After merge, run the workflow with 4.0.9 / trixie so Nimbu can pin zenjoy/ruby:4.0.9-trixie until the official image is published.

The workflow takes a debian_suite input and tags the image X.Y.Z-<suite>.
Mirrors upstream's trixie template, which cleans up with apt-get dist-clean.
@dedene
dedene merged commit 0cb8010 into main Oct 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant