The build container already ships the Python toolchain, so there is no
need to map the toolchain from the base container.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
image: ghcr.io/igaw/linux-nvme/debian:latest
steps:
- uses: actions/checkout@v4
- - uses: actions/setup-python@v4
- with:
- python-version: '3.x'
- name: build
run: |
scripts/build.sh -b ${{ matrix.buildtype }} -c ${{ matrix.compiler }}
image: ghcr.io/igaw/linux-nvme/debian:latest
steps:
- uses: actions/checkout@v4
- - uses: actions/setup-python@v4
- with:
- python-version: '3.x'
- name: build
run: |
scripts/build.sh -b release -c gcc libdbus
if: github.ref == 'refs/heads/master'
steps:
- uses: actions/checkout@v4
- - uses: actions/setup-python@v4
- with:
- python-version: '3.x'
- name: build
run: |
scripts/build.sh -b release -c gcc fallback