Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1270845 > unrolled thread

Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid aquilamacedo@riseup.net - 2025-11-19 20:20 +0100
    Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid Otto Kekäläinen <otto@debian.org> - 2025-11-19 20:30 +0100
      Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid aquilamacedo@riseup.net - 2025-11-19 21:10 +0100
        Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid Otto Kekäläinen <otto@debian.org> - 2025-11-27 06:10 +0100

#1270845 — Bug#1121027: mariadb: Salsa CI Python-MySQLdb job fails in sid

Source: mariadb
X-Debbugs-Cc: aquilamacedo@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.

[toc] | [next] | [standalone]

#1270848

Thanks for looking into this!

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

Makes sense. Asking the package to revert potential dependency changes
is an alternative, but would require a lot more work. Feel free to
open a MR to add `build-essential` in the CI job, as that will make it
pass again and make it able to detect true regressions on the code
compatibility level.

[toc] | [prev] | [next] | [standalone]

#1270854

On 2025-11-19 16:24, Otto Kekäläinen wrote:
> Thanks for looking into this!
> 
>> Suggested fix:
>>
>> Explicitly install a compiler (for instance, build-essential) in the job
>> before calling pip.
> 
> Makes sense. Asking the package to revert potential dependency changes
> is an alternative, but would require a lot more work. Feel free to
> open a MR to add `build-essential` in the CI job, as that will make it
> pass again and make it able to detect true regressions on the code
> compatibility level.

I had a look at the current control file for python-pip and I don't see
any recent regression in the package itself. python3-pip still only
Recommends build-essential (and python3-dev), and the recent change was
in Build-Depends (switch to flit), not in the runtime Depends/Recommends
of python3-pip.

The failure comes from our CI setup, we were implicitly relying on that
Recommends to pull in a toolchain in the debian:${RELEASE} container. In
the current environment that no longer happens, so the job started
failing.

I just opened the MR to fix this in our side.

[toc] | [prev] | [next] | [standalone]

#1271773

This was fixed via
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/34b945a557256e02115dfd155cf73cb63aa22359
and merged.

We have webhooks configured at
https://salsa.debian.org/mariadb-team/mariadb-server/-/hooks as
documented at https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages
but for
some reason it didn't update this Debian bug automatically..

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web