On October 26, 2016 2:30:04 AM PDT, Nathan Anderson <nat...@nja.id.au> wrote: >In response to 'libmariadbclient18', here's a list of mariadb packages: > >dpkg -l | grep maria >ii libmariadbclient18 10.1.18+maria-1~sid amd64 > > MariaDB database client library >ii libmysqlclient18 10.1.18+maria-1~sid amd64 > > Virtual package to satisfy external depends >ii mariadb-client-10.1 10.1.18+maria-1~sid amd64 > > MariaDB database client binaries >ii mariadb-client-core-10.1 10.1.18+maria-1~sid amd64 > > MariaDB database core client binaries >ii mariadb-common 10.1.18+maria-1~sid all > > MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf) >ii mariadb-server 10.1.18+maria-1~sid all > > MariaDB database server (metapackage depending on the latest >version) >ii mariadb-server-10.1 10.1.18+maria-1~sid amd64 > > MariaDB database server binaries >ii mariadb-server-core-10.1 10.1.18+maria-1~sid amd64 > > MariaDB database core server files >ii mysql-common 10.1.18+maria-1~sid all > > MariaDB database common files (e.g. /etc/mysql/my.cnf) > >Postfix/postfix-mysql 3.1.0-5+b1 doesn't have this issue that's being >reported so are you sure it's just a bystander?
Prior to 3.1.3-1, postfix was compiled using the Debian MySQL packages. Based on the guidelines provided by the Debian team that is maintaining MySQL and it's variants, we changed to build against the default MySQL implementation, which is MariaDB. As far as I can tell, the error described in this bug report won't happen with the libmariadbclient18 packages in Debian. The problem is that the packages provided by MariaDB are done differently (files named like a MySQL package). The bottom line issue is the difference between the MariaDB packages in Debian and those provided by MariaDB. Scott K
