actions / runner-images

GitHub Actions runner images

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

System `python` linked into `/usr/local/bin` interferes with Homebrew package installations

douglascamata opened this issue · comments

Description

The system Python is being linked into /usr/local/bin and this is interfering with the installation of Python through Homebrew.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Runner Image:
Image: macos-13
Version: 20240219.1
Runner version: 2.314.1

Build link: https://github.com/pgxman/pgxman/actions/runs/8226570015/job/22524288851#step:3:269

Is it regression?

Yes. It works on Runner Version 2.313.0 (see https://github.com/pgxman/pgxman/actions/runs/8145029332/job/22260431482) but fails on 2.314.1 (see https://github.com/pgxman/pgxman/actions/runs/8226570015/job/22524288851#step:3:269).

Expected behavior

Can link the Python installed by Homebrew into /usr/local/bin

Actual behavior

Can't link it because there's a system Python already linked there.

Repro steps

Install Python directly with brew install python@3.12 or through a package that depends on it with brew install qemu.

Duplicate of #9471, this is default brew behaviour, it links python whenever it installs it from scratch or python is being updated in runtime.

@mikhailkoliada why are all issues reporting this issue being auto closed? Everyone's still having to deal with this problem, very unsuccessfully. It's very annoying for all the projects relying on Github Actions that we can't install our dependencies with Homebrew because there's already some other dependency that we don't use installing something.

We should be able to request a "clean slate" macOS VM image to install only what we need and avoid these conflicts. Situations like this makes me want to stop using Github Actions. Never had this kind of problem in other platforms.

Plus the sad state that is interaction with user reported issues in this repository also makes me want to stop using GHA.