Bug#845205: [debian-mysql] Bug#845205: Incompatible with MariaDB 10.1

Rene Engelhard rene at debian.org
Mon Nov 21 13:02:12 UTC 2016

[ Not a exim maintainer ]


On Mon, Nov 21, 2016 at 11:48:56PM +1100, Matt Li wrote:
> Package: exim4
> Version: 4.88~RC4-2
> X-Debbugs-CC: pkg-mysql-maint at lists.alioth.debian.org
> It appears that exim4 from exim4-daemon-heavy is now linked to libmariadbclient.so.18 which does not exist in MariaDB 10.1 - only libmysqlclient.so.18 is provided.

And? MariaDB in Debian is 10.0 *and* it has a libmariadbclient18 package
which exim4-daemon-heavy depends on. So where's the bug? Did you hack the
depdencdies somehow?

MariaDB 10.1 isn't in Debian and if it was and it changed names one would
need a rebuild.

> /usr/sbin/exim4: error while loading shared libraries: libmariadbclient.so.18: cannot open shared object file: No such file or directory

As said, exim4-daemon-heavy depends on libmariadbclient18, so how did you
get into this?

> Manually symlinking to libmysqlclient.so.18 results in:
> /usr/sbin/exim4: /usr/lib/libmariadbclient.so.18: version `libmariadbclient_18' not found (required by /usr/sbin/exim4)

Of course, symlinking is always a a bad idea.

> This did not occur in the last testing build 4.87-3+b1.

Of course, because it was built against libmysqclient, not libmariadbclient:

exim4 (4.88~RC1-1) experimental; urgency=low
  * B-d on default-libmysqlclient-dev.

 -- Andreas Metzler <ametzler at debian.org>  Sun, 25 Sep 2016 15:44:00 +0200

Still not a bug. (default-libmysqlclient-dev) is libmariadbclient
(see https://packages.debian.org/stretch/default-libmysqlclient-dev)



More information about the Pkg-exim4-maintainers mailing list