Skip to content

Migrate to Ubuntu 24.04#21761

Draft
cho-m wants to merge 1 commit intomainfrom
move-to-ubuntu24.04
Draft

Migrate to Ubuntu 24.04#21761
cho-m wants to merge 1 commit intomainfrom
move-to-ubuntu24.04

Conversation

@cho-m
Copy link
Member

@cho-m cho-m commented Mar 18, 2026

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same change?
  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your changes? Here's an example.
  • Have you successfully run brew lgtm (style, typechecking and tests) with your changes locally?

  • AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

Draft until we get closer to brew 5.2.0 release date.

Related work:

Homebrew/core PRs blocked by Ubuntu 22.04:

Formulae with LLVM Clang workarounds to revert after migrations:

  • apache-arrow
  • gnome-builder
  • mdk
  • mysql
  • opentelemetry-cpp
  • protobuf
  • qxmpp

Formulae with GCC dependency to rebuild after migration:

  • btop (?)
  • ladybug
  • libunicode
  • vroom

@cho-m cho-m added in progress Maintainers are working on this release blocker A new release should not be done until this is fixed. linux labels Mar 18, 2026
@cho-m
Copy link
Member Author

cho-m commented Mar 18, 2026

Failures:

  • formula audit runs on "ghcr.io/homebrew/brew:main" which is still Ubuntu 22.04 until PR is merged. Could either switch to "ghcr.io/homebrew/ubuntu24.04:main" or split docker images to separate PR.
  • Bookworm (old stable) is on GCC 12. Not sure yet if there is a Linux distro running glibc < 2.39 and has libstdc++ for gcc >= 14. May need to find a way to ignore that audit failure.
  • Docker image for 22.04 may need to be dropped if brew doctor cannot be ignored. Can add 26.04 pre-release image instead https://hub.docker.com/_/ubuntu#supported-tags-and-respective-dockerfile-links

@MikeMcQuaid
Copy link
Member

  • formula audit runs on "ghcr.io/homebrew/brew:main" which is still Ubuntu 22.04 until PR is merged. Could either switch to "ghcr.io/homebrew/ubuntu24.04:main"

@cho-m this makes sense to me 👍🏻.

  • Bookworm (old stable) is on GCC 12. Not sure yet if there is a Linux distro running glibc < 2.39 and has libstdc++ for gcc >= 14. May need to find a way to ignore that audit failure.

Which audit failure specifically? All we're trying to do in this case is ensure that the glibc formula is installed if needed. I do think we should aim to find another distro for this.

It looks from 👇🏻 that Ubuntu 22.04 may be enough for that?

Yes, we should drop it and bump to versions that don't need to install glibc such as yeh the 26.04 image.


At least some of this we can do before 5.2.0.

@cho-m
Copy link
Member Author

cho-m commented Mar 19, 2026

Which audit failure specifically? All we're trying to do in this case is ensure that the glibc formula is installed if needed. I do think we should aim to find another distro for this.

The CI / test-bot run failed due to https://github.com/Homebrew/brew/actions/runs/23263094267/job/67636951864?pr=21761#step:9:73

  libfaketime
    * Formulae in homebrew/core should not have a Linux-only dependency on GCC.

Maybe that audit itself shouldn't fail for :implicit dependency? Will experiment with this locally.

EDIT: If needed, RHEL 9-based distros (e.g. Rocky 9) use glibc 2.34 + GCC 14 and will be supported for a long time.

@MikeMcQuaid
Copy link
Member

EDIT: If needed, RHEL 9-based distros (e.g. Rocky 9) use glibc 2.34 + GCC 14 and will be supported for a long time.

Don't really care about support. If we can use e.g. Ubuntu that we've already used for this test: all the better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in progress Maintainers are working on this linux release blocker A new release should not be done until this is fixed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants