A clarification on the root cause, found while building a working multi-arch
repackaging:
libmariadb-dev-compat both *provides* and *conflicts/breaks* the same virtual
packages:
Provides: libmariadb-client-lgpl-dev-compat, libmariadbclient-dev-compat
Conflicts: libmariadb-client-lgpl-dev-compat, libmariadbclient-dev-compat,
...
Breaks: libmariadb-client-lgpl-dev-compat, libmariadbclient-dev-compat,
...
So beyond the missing "Multi-Arch: same" field, two architecture instances
trip over each other's self-provided virtuals. In my repackaging I had to BOTH
stamp "Multi-Arch: same" AND strip these self-provided names from
Conflicts/Breaks before the two arches would co-install. Please verify that
marking the package Multi-Arch: same is sufficient on its own, or whether the
self-conflicting virtuals also need adjusting.
(verified in trixie 1:11.8.6-0+deb13u1 and unstable 1:11.8.8-1)
