On Thu, 22 Feb 2024 at 11:41, Daniel P. Berrangé <berra...@redhat.com> wrote: > > Python is transitioning to a world where you're not allowed to use 'pip > install' outside of a virutal env by default. The rationale is to stop > use of pip clashing with distro provided python packages, which creates > a major headache on distro upgrades. > > All our CI environments, however, are 100% disposable so the upgrade > headaches don't exist. Thus we can undo the python defaults to allow > pip to work. > > Signed-off-by: Daniel P. Berrangé <berra...@redhat.com> > --- > .gitlab-ci.d/cirrus/build.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > FYI lcitool recently added logic that purges the EXTERNALLY-MANAGED > marker in all the dockerfiles. QEMU will pick that up on the next > refresh, so Linux containers won't have trouble in future. > > The macos/FreeBSD build env isn't fully managed by lcitool though, > so we need this manual addition to purge the marker that prevents > use of 'pip'. > > This fixes the CI regression that just started hitting on Cirrus > CI macOS images, likely from homebrew python updates.
I've applied this directly to get the CI back to green; thanks. -- PMM