[debian-mysql] Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid

[aquilamacedo at riseup.net]

Source: mariadb
X-Debbugs-Cc: aquilamacedo at riseup.net
Version: 1:11.8.3-2
Severity: normal

Hi,

The Salsa CI job "build mariadbclient consumer Python-MySQLdb" is
failing on sid:

https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/8590604

The job installs only:

  apt-get install -qq --yes pkg-config python3-pip
  pip3 install --break-system-packages mysqlclient

On a fresh debian:unstable container with APT::Install-Recommends=1,
installing python3-pip pulls in python3-dev, libpython3-dev,
libjs-sphinxdoc, etc., but no compiler. As a result, mysqlclient fails
to build:

[...]

building 'MySQLdb._mysql' extension
...
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2
-Wall -fPIC ...
error: command 'x86_64-linux-gnu-gcc' failed: No such file or directory
>From the CI log:
pip3 install --break-system-packages mysqlclient
error: command 'x86_64-linux-gnu-gcc' failed: No such file or directory
ERROR: Failed building wheel for mysqlclient
Failed to build mysqlclient
error: failed-wheel-build-for-install

[...]

This job worked around 2025-11-08
(https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/8565567),
likely because unstable previously installed a compiler indirectly via
Recommends. python3-pip still has:

  Recommends: build-essential, python3-dev, ${sphinxdoc:Depends}

but APT now installs only python3-dev and sphinxdoc here, not
build-essential.

Suggested fix:

Explicitly install a compiler (for instance, build-essential) in the job
before calling pip.