Skip to content

[CI] Fix Monolithic Linux Build in Ubuntu 24.04 #133628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

boomanaiden154
Copy link
Contributor

@boomanaiden154 boomanaiden154 commented Mar 30, 2025

This patch fixes the monolithic linux build in Ubuntu 24.04. Newer versions of debian/ubuntu pass a warning when installing packages at the system level using pip as it interferes with system package manager installed python packages. We do not use any system package manager installed python packages, so we just ignore the warning (that is an error without passing the flag) by passing the --break-system-packages flag.

This patch fixes the monolithic linux build in Ubuntu 24.04. Newer
versions of debian/ubuntu pass a warning when installing packages at the
system level using pip as it interferes with system package manager
installed python packages. We do not use any, so we just ignore the
warning (that is an error without passing the flag) by passing the
--break-system-packages flag.
Copy link
Contributor

@Endilll Endilll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@DavidSpickett DavidSpickett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose the "proper" way to do this is install virtualenv from apt and install into an isolated environment, which would help if we ever did decide to install anything from apt.

Then again, we prefer to have the package names in requirements.txt so they are easier to find, so it's unlikely we would use apt for something.

We do not use any,

I would say "any system package manager installed python packages" just to be extra clear, in case we have to refer back to this commit message later.

@boomanaiden154
Copy link
Contributor Author

I suppose the "proper" way to do this is install virtualenv from apt and install into an isolated environment, which would help if we ever did decide to install anything from apt.

Right. The intention behind this flag is to get people to do that. The recommendation doesn't make as much sense for containers that serve a single purpose though.

Then again, we prefer to have the package names in requirements.txt so they are easier to find, so it's unlikely we would use apt for something.

Yep.

I would say "any system package manager installed python packages" just to be extra clear, in case we have to refer back to this commit message later.

Updated.

@boomanaiden154 boomanaiden154 merged commit 23fb048 into llvm:main Apr 1, 2025
10 checks passed
@boomanaiden154 boomanaiden154 deleted the fix-pip-monolithic-linux-ubuntu-2404 branch April 1, 2025 19:55
boomanaiden154 added a commit that referenced this pull request Apr 1, 2025
This reverts commit 23fb048.

This broke the new premerge system as it appears the pip installations within
the CI image do not support this option. Buildkite was unaffected.
Ankur-0429 pushed a commit to Ankur-0429/llvm-project that referenced this pull request Apr 2, 2025
This patch fixes the monolithic linux build in Ubuntu 24.04. Newer
versions of debian/ubuntu pass a warning when installing packages at the
system level using pip as it interferes with system package manager
installed python packages. We do not use any system package manager
installed python packages, so we just ignore the warning (that is an
error without passing the flag) by passing the --break-system-packages
flag.
Ankur-0429 pushed a commit to Ankur-0429/llvm-project that referenced this pull request Apr 2, 2025
This reverts commit 23fb048.

This broke the new premerge system as it appears the pip installations within
the CI image do not support this option. Buildkite was unaffected.
boomanaiden154 added a commit that referenced this pull request Apr 5, 2025
This reverts commit d72be15.

Now that the container version got bumped, we need to reland this.
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.

3 participants