[debian-mysql] Bug#917075: mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev

[Luca Boccassi]

On Tue, 25 Dec 2018 09:16:57 +0100 Sebastiaan Couwenberg <sebastic at xs4a
ll.nl> wrote:
> On 12/25/18 8:57 AM, Otto Kekäläinen wrote:
> > Can you please provide an actual pbuilder command or something I
can
> > copy-paste to reproduce the actual problem (and not just the
aptitude
> > symptom)?
> 
> Sure:
> 
>  sudo cowbuilder --create \
>                  --distribution=sid \
>                  --basepath=/var/cache/pbuilder/base-sid.cow
>  dget -u \
>   http://deb.debian.org/debian/pool/main/g/gdal/gdal_2.3.3+dfsg-1.dsc
>  cd gdal-2.3.3/
>  dch -nm "Test rebuild"
>  pdebuild --pbuilder cowbuilder -- \
>           --basepath /var/cache/pbuilder/base-sid.cow/
> 
> pbuilder will be unstable to install the build dependencies, causing
the
> configure target to disable MySQL support despite using the --with-
mysql
> option:
> 
>    MySQL support:             no
> 
> 
> Please also answer my questions:
> 
> > Isn't the appropriate fix to build libmariadbclient-dev-compat from
> > the mariadb-10.3 instead of 10.1? Aren't you now transitioning from
> > 10.1 to 10.3? And shouldn't mysql-defaults be updated for that too?
> 
> default-libmysqlclient-dev depends on libmariadbclient-dev-compat
which
> is built from the mariadb-10.1 source package.
> 
> libmariadbclient-dev-compat depends on libmariadbclient-dev (also
built
> from the mariadb-10.1 source package), which in turn depends on
> libmariadbclient18 (= 1:10.1.37-3).
> 
> As long as the 10.3 packages Conflict or Break 10.1 packages, the
> default-* packages cannot be installed along with the 10.3 packages,
as
> the default packages are depending on the 10.1 packages.
> 
> Kind Regards,
> 
> Bas

Hi,

I just encountered a similar issue, causes a build regression in
collectd [1].

The issue is that build-depending on default-libmysqlclient-dev causes
libmariadbclient-dev-compat from 10.1 to be installed instead of
libmariadb-dev-compat from 10.3, which means the mysql_config binary is
missing and the configure step of collectd thus fails.
Manually installing libmariadb-dev-compat, which causes
libmariadbclient-dev-compat to be removed, fixes the issue.

-- 
Kind regards,
Luca Boccassi

[1] https://buildd.debian.org/status/fetch.php?pkg=collectd&arch=amd64&ver=5.8.1-1.1&stamp=1545690583&raw=0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20181225/d37fe59a/attachment.sig>