[From nobody Sun Sep 6 07:51:06 2026 Received: (at submit) by bugs.debian.org; 3 Sep 2026 13:41:32 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-16.9 required=4.0 tests=BAYES_00, BODY_INCLUDES_PACKAGE,FOURLA,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM, HAS_PACKAGE,SPF_HELO_PASS,SPF_SOFTFAIL,SPOOFED_FREEMAIL, XMAILER_REPORTBUG autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 41; hammy, 150; neutral, 199; spammy, 0. spammytokens: hammytokens:0.000-+--H*Ad:N*Bug, 0.000-+--HTo:N*Debian, 0.000-+--forky, 0.000-+--HTo:N*System, 0.000-+--HTo:N*Bug Return-path: <manul91@abv.bg> Received: from mail.gurulink.ca ([206.223.179.205]:3468) by buxtehude.debian.org with esmtp (Exim 4.96) (envelope-from <manul91@abv.bg>) id 1x27h4-002eEI-2b for submit@bugs.debian.org; Thu, 03 Sep 2026 13:41:32 +0000 Received: from siduxbox.localdomain by mail.gurulink.ca (MDaemon PRO v10.0.0) with ESMTP id md50009498169.msg for <submit@bugs.debian.org>; Thu, 03 Sep 2026 09:33:37 -0400 X-Authenticated-Sender: system@gurulink.ca X-MDRemoteIP: 206.248.171.64 X-Return-Path: manul91@abv.bg X-Envelope-From: manul91@abv.bg X-MDaemon-Deliver-To: submit@bugs.debian.org Received: from manul by siduxbox.localdomain with local (Exim 4.100) (envelope-from <manul91@abv.bg>) id 1x27ZJ-000000004WH-0esM; Thu, 03 Sep 2026 09:33:29 -0400 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: manul <manul91@abv.bg> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: libmariadb-dev: mariadb_config shim dropped --cc_version, breaking Connector/Python builds Message-ID: <178844240915.17275.14664176880493592197.reportbug@siduxbox.localdomain> X-Mailer: reportbug 13.2.0+nmu1 Date: Thu, 03 Sep 2026 09:33:29 -0400 X-Greylist: delayed 467 seconds by postgrey-1.37 at buxtehude; Thu, 03 Sep 2026 13:41:31 UTC Delivered-To: submit@bugs.debian.org Package: libmariadb-dev Version: 1:11.8.9+ds-1 Severity: important Tags: patch Dear Maintainer, Since 1:11.8.9+ds-1, /usr/bin/mariadb_config no longer implements the --cc_version option: $ mariadb_config --cc_version /usr/bin/mariadb_config: unrecognized option '--cc_version' The predecessor, 1:11.8.8-1, shipped upstream MariaDB Connector/C's compiled mariadb_config, which does implement it (extracted from the cached .deb): $ ./usr/bin/mariadb_config --help Copyright 2011-2020 MariaDB Corporation AB Get compiler flags for using the MariaDB Connector/C. [...] --version [11.8.8] --cc_version [3.4.9] In 1:11.8.9+ds-1 that binary was replaced by an architecture-independent shell script, as part of making libmariadb-dev Multi-Arch: same co-installable (#1140296). The replacement implements ten of upstream's options but not --cc_version, which looks like an oversight rather than an intended removal. /usr/bin/mariadb-config is a symlink to the same script, so there is no unaffected alternative on the system. Impact: MariaDB Connector/Python (the "mariadb" distribution on PyPI, MariaDB's officially supported Python driver, not packaged in Debian) calls exactly this option during its build to verify Connector/C >= 3.3.1. It now dies on the empty answer: File ".../mariadb_posix.py", line 63, in get_config if version.Version(cc_version[0]) < version.Version(required_version): IndexError: list index out of range So `pip install mariadb` fails on a sid system with libmariadb-dev installed, where it succeeded under 1:11.8.8-1. Any other consumer that asks for the Connector/C version through this documented interface is affected the same way. Nothing is actually missing from the package. The value the option should report is already in the shipped headers, and it is the very macro upstream's binary compiles its own answer from: $ grep MARIADB_PACKAGE_VERSION /usr/include/mariadb/mariadb_version.h #define MARIADB_PACKAGE_VERSION "3.4.10" #define MARIADB_PACKAGE_VERSION_ID 30410 The script already reads that same header for --version, so restoring the option is a two-line change: --- a/usr/bin/mariadb_config +++ b/usr/bin/mariadb_config @@ version=$(sed -n 's/.*MARIADB_CLIENT_VERSION_STR[^"]*"\([^"]*\)".*/\1/p' "$vhdr" 2>/dev/null) [ -n "$version" ] || version=unknown +cc_version=$(sed -n 's/.*MARIADB_PACKAGE_VERSION[^"]*"\([^"]*\)".*/\1/p' "$vhdr" 2>/dev/null) +[ -n "$cc_version" ] || cc_version=unknown @@ usage() - --version --variable=VAR (pkglibdir|plugindir) + --version --cc_version --variable=VAR (pkglibdir|plugindir) @@ case "$arg" in --version) printf '%s\n' "$version" ;; + --cc_version) printf '%s\n' "$cc_version" ;; I verified locally that supplying --cc_version from that macro, and delegating every other option to /usr/bin/mariadb_config unchanged, lets mariadb 1.1.14 build and import against the installed Connector/C 3.4.10. Thanks for maintaining this package. manul -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.18.15+deb14-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmariadb-dev depends on: ii libmariadb3 1:11.8.9+ds-1 ii libssl-dev 3.6.4-1 ii zlib1g-dev 1:1.3.dfsg+really1.3.2-3 libmariadb-dev recommends no packages. libmariadb-dev suggests no packages. -- no debconf information ]