Error: Unable to locate executable file: lsb_release.

[ELY3M]

Description:
1s
Warning: Unexpected input(s) 'run', valid inputs are ['python-version', 'python-version-file', 'cache', 'architecture', 'check-latest', 'token', 'cache-dependency-path', 'update-environment', 'allow-prereleases', 'freethreaded']
Run actions/setup-python@v5
/usr/bin/docker exec 0785d8876fda0c349674625b08673844f3e96d5777d0cd28ca733e23db6bcde6 sh -c "cat /etc/*release | grep ^ID"
Installed versions

Error: Unable to locate executable file: lsb_release. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

Action version:
- uses: actions/setup-python@v5
with:
python-version: '3.10'
cache: 'pip' # caching pip dependencies
run: pip install lz4

Platform:
ubuntu-latest

Runner type:
github runner

Tools version:
trid 3.10 and 3.13.3

Repro steps:

  - uses: actions/setup-python@v5
    with:
      python-version: '3.10'
      cache: 'pip' # caching pip dependencies
      run: pip install lz4

A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

Expected behavior:
it should install lz4

Actual behavior:
it cant find lsb_release

https://github.com/ELY3M/Atmosphere/actions/runs/15181202968/job/42690791175

[ELY3M]

the action file is at https://github.com/ELY3M/Atmosphere/actions/runs/15181202968/workflow

[aparnajyothi-y]

Hello @ELY3M, Thank you for creating this issue and we will look into it :)

[mahabaleshwars]

Hi @ELY3M,

• actions/setup-python@v5 does not support a run input, so placing run: pip install lz4 inside the with: block is invalid.

• Correct usage is to install Python packages in a separate step after setting up Python. For example:

- name: Setup Python
  uses: actions/setup-python@v5
  with:
     python-version: '3.10'
     cache: 'pip'

- name: Install lz4
  run: pip install lz4

• If you're running into the lsb_release issue, try clearing the Python cache before setting up Python. You can add this step:

- name: Clear Python cache
  run: |
    sudo rm -rf /__t/Python

The container image currently in use (devkitpro/devkita64) is based on Debian, which may lead to the error: "version not found for Debian 11". This issue arises because the setup-python GitHub Action is designed to run on GitHub-hosted runners based on Ubuntu, macOS, and Windows environments, as specified in the official documentation.

To resolve this issue, consider switching to an Ubuntu-based container image.

[mahabaleshwars]

Hi @ELY3M,
Just giving you a gentle ping to see if the feedback provided is working out for you. Please feel free to let us know if you need any assistance or further clarification—we’re happy to help!