Automated Release v0.1.4

[github-actions]

Auto-generated pull request creating version 0.1.4.

Changelog:

• Update the docker image to Ubuntu 24. (632) [Fabian Ruffy]

[github-actions]

Maintainers: Mark this PR as ready to trigger CI.

Please use Squash and merge to include the changelog in the release message.

[chreekat]

Interesting, this failed for some reason I can't immediately interpret.

[jafingerhut]

Interesting, this failed for some reason I can't immediately interpret.

I suspect it is because the container being used has Python packages installed system-wide, and the failing script is trying to add more packages using pip install ..., but as a non-root user.

I think one option for handling this is to always install Python packages during builds into an explicitly chosen Python virtual environment, which is selected by doing source $MYVENV_DIR/bin/activate (which in turn assigns a value to the environment variable VIRTUAL_ENV). That would seem to require adding such commands to all p4lang repositories that use these containers, and the necessary commands to create such a virtual environment in any docker scripts that create a docker image that isn't based on a different p4lang docker image.

[jafingerhut]

Interesting, this failed for some reason I can't immediately interpret.

I suspect it is because the container being used has Python packages installed system-wide, and the failing script is trying to add more packages using pip install ..., but as a non-root user.

I think one option for handling this is to always install Python packages during builds into an explicitly chosen Python virtual environment, which is selected by doing source $MYVENV_DIR/bin/activate (which in turn assigns a value to the environment variable VIRTUAL_ENV). That would seem to require adding such commands to all p4lang repositories that use these containers, and the necessary commands to create such a virtual environment in any docker scripts that create a docker image that isn't based on a different p4lang docker image.

A small correction to the above message. The error occurs when running a pip install command, and the destination where the package should be installed is a system-wide directory, e.g. /usr/lib/python<x>.<y>/, or /usr/local/lib/python<x>.<y>/, and then with recent versions of pip as installed by default on Ubuntu 24.04 and later versions of Ubuntu, it will give the error message that this CI check is failing with, because there is a new check that prevents one from using pip to install in system-wide directories.

Many p4lang projects CI scripts attempt to install Python packages in system-wide directories, because it always worked before. I think we should move away from doing so, because of the newer behavior of pip (which has been since some version around 2023, I think, so not exactly new behavior).

[jafingerhut]

The changes in PR #669 (or something similarly effective) should enable the PI build & test to work again, with the new Ubuntu 24.04-based docker images.

[chreekat]

Let's close this one and let the next one pick up the fixes.

[jafingerhut]

Let's close this one and let the next one pick up the fixes.

Sounds reasonable. PR #670 was merged on this repo, that should hopefully enable the next automated release CI tests to pass.