[From nobody Mon Aug 31 21:39:06 2026
Received: (at submit) by bugs.debian.org; 16 Jun 2026 14:43:11 +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=-15.1 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
 DKIM_VALID_EF,FOURLA,HAS_PACKAGE,SPF_HELO_NONE,SPF_PASS autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 13; hammy, 150; neutral, 139; spammy,
 0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--H*Ad:N*Bug,
 0.000-+--H*Ad:N*Tracking, 0.000-+--HTo:N*Debian, 0.000-+--forky
Return-path: <dick@softplc.com>
Received: from email.softplc.com ([158.101.43.211]:46150)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <dick@softplc.com>) id 1wZV0R-00FVMc-07
 for submit@bugs.debian.org; Tue, 16 Jun 2026 14:43:11 +0000
Received: from [192.100.100.6] (unknown [143.244.184.175])
 by email.softplc.com (Postfix) with ESMTPSA id 289B17EDC1;
 Tue, 16 Jun 2026 14:43:10 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softplc.com; s=2023;
 t=1781620990;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:mime-version:mime-version:content-type:content-type:
 content-transfer-encoding:content-transfer-encoding;
 bh=xMRFcpHId9rzd3hi7lqpM3N8PMe3MiTb8EAoQi5sOj4=;
 b=ObP2ZZiJQNJPjGZ8pFNJPuKCS9UQIZysD/ErquamjiGAhIySjeGiLkflHDenZlmiIZX6Ho
 4eoIGVCSZB819smwSfilUikETd+/eIbhfj3Dcb6bw/XaMiDM0dpe3D2+6kcD+9Dvc87hyO
 wl8nej7NO04FrPCo0f2SSTvCUOFhmc5onxUFlsdXTiqvTSOg179d6OA74FgySBIOnPFYGX
 HRyNiqReyaYf64yA3s2cSjjUyhYvlgtZHFPR0MdcJxwll1qlgMpMr0EjeEkyTYYKNk3K26
 rnMub0oRDdPm1vRdnK1xWtW5hJ9W0yclssn9qzChJhlEk+HgJo8lIbi7g9dC0A==
Message-ID: <77be87ce-511d-4af2-abb9-75c6983f29ff@softplc.com>
Date: Tue, 16 Jun 2026 09:43:08 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libmariadb-dev-compat: not Multi-Arch co-installable (blocks
 cross-arch -dev installs)
Content-Language: en-US
From: Dick Hollenbeck <dick@softplc.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org

Package: libmariadb-dev-compat
Version: 1:11.8.6-0+deb13u1
Severity: normal

Dear Maintainer,

libmariadb-dev-compat (and the libmariadb-dev it depends on) cannot be
installed for two architectures at once, because the package is not marked
"Multi-Arch: same". dpkg therefore generates an implicit cross-architecture
conflict:

# docker run --rm debian:sid bash
dpkg --add-architecture arm64
apt-get update
apt-get install -s libmariadb-dev-compat:amd64 libmariadb-dev-compat:arm64
...
libmariadb-dev-compat:amd64 Conflicts libmariadb-dev-compat:arm64
libmariadb-dev-compat:arm64 : Depends: libmariadb-dev:arm64 (= ...)
but it is not installable

The package's explicit Conflicts: field only lists the old
libmysqlclient-dev / lgpl compat names; the cross-arch conflict above is the
*implicit* one dpkg adds to any package that is not Multi-Arch: same.

This blocks cross-architecture C/C++ development against the MySQL/MariaDB
client. In particular it blocks libpoco-dev from being co-installable across
architectures even after libpoco-dev itself is fixed: libpoco-dev depends on
default-libmysqlclient-dev, which resolves to libmariadb-dev-compat, so the
two libpoco-dev arches cannot coexist solely because of this package. (See my
related report against libpoco-dev.)

This is the same underlying issue as #1006388.

Status across releases (verified):
- trixie: 1:11.8.6-0+deb13u1 - not Multi-Arch: same, not co-installable
- unstable: 1:11.8.8-1 - still not Multi-Arch: same, still not
co-installable (so not fixed for forky
either)

Request: please make the MariaDB client -dev packages (libmariadb-dev and
libmariadb-dev-compat) Multi-Arch: same / co-installable, moving any
architecture-dependent files into the triplet directories as needed. I'm
happy to help test candidates across amd64/arm64.

Steps to reproduce: as above.

Thanks,
Dick Hollenbeck



-- System Information:
Debian Release: 13.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.74+deb13+1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmariadb-dev-compat depends on:
ii libmariadb-dev 1:11.8.6-0+deb13u1

libmariadb-dev-compat recommends no packages.

libmariadb-dev-compat suggests no packages.

-- no debconf information
]