What happens?
CI is failing during sqlite3 installation because the build Linux (linux_amd64, ubuntu-24.04, x64-linux-release, x64-linux-release) runs in a manylinux container that uses yum for package installation: https://github.com/duckdb/duckdb-sqlite/actions/runs/16147955464/job/45571776013
The build uses extension-ci-tools/docker/linux_amd64/Dockerfile which is based on quay.io/pypa/manylinux_2_28_x86_64 (Red Hat-based).
Fix: Add yum to Makefile:13
- command -v sqlite3 || (command -v brew && brew install sqlite) || (command -v choco && choco install sqlite -y) || (command -v apt-get &&
apt-get install -y sqlite3) || (command -v apk && apk add sqlite) || echo "no sqlite3"
+ command -v sqlite3 || (command -v brew && brew install sqlite) || (command -v choco && choco install sqlite -y) || (command -v apt-get &&
apt-get install -y sqlite3) || (command -v yum && yum install -y sqlite) || (command -v apk && apk add sqlite) || echo "no sqlite3"
To Reproduce
https://github.com/duckdb/duckdb-sqlite/actions/runs/16147955464/job/45571776013
OS:
n/a
SQLite Version:
n/a
DuckDB Version:
n/a
DuckDB Client:
n/a
Full Name:
Adam Kirby
Affiliation:
Kanerai
Have you tried this on the latest main branch?
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
What happens?
CI is failing during sqlite3 installation because the build Linux (linux_amd64, ubuntu-24.04, x64-linux-release, x64-linux-release) runs in a manylinux container that uses yum for package installation: https://github.com/duckdb/duckdb-sqlite/actions/runs/16147955464/job/45571776013
The build uses
extension-ci-tools/docker/linux_amd64/Dockerfilewhich is based onquay.io/pypa/manylinux_2_28_x86_64(Red Hat-based).Fix: Add yum to Makefile:13
To Reproduce
https://github.com/duckdb/duckdb-sqlite/actions/runs/16147955464/job/45571776013
OS:
n/a
SQLite Version:
n/a
DuckDB Version:
n/a
DuckDB Client:
n/a
Full Name:
Adam Kirby
Affiliation:
Kanerai
Have you tried this on the latest
mainbranch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?