[debian-mysql] Bug#812812: MySQL client library should ship a symbols file, or at least not have a Lintian override to hide the problem

Otto Kekäläinen otto at seravo.fi
Tue Jan 26 20:03:37 UTC 2016


Package: mysql-5.6
Version: 5.6.28-1
Severity: serious

The mysql-5.5 source package produces the libmysqlclient18 shared
library, main file being libmysqlclient.so.18. So does the mysql-5.6
package too (even using the same "18" version string oddly, are there
no changes in the ABI?).

It seems the mysql-5.5 never shipped a symbols file. In mysql-5.6
there is a specific Lintian override about not shipping the symbols
file:
http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.6.git/tree/debian/libmysqlclient18.lintian-overrides

The Debian policy states "shared libraries must provide either a
symbols file or a shlibs file" at
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html

For implementation tips see also: https://wiki.debian.org/UsingSymbolsFiles

For examples you can also check libmariadb2 symbol file:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-client-lgpl.git/tree/debian/libmariadb2.symbols
The mariadb-5.5 package used to have a symbols file some years ago in
Debian until it was denied from shipping a libmariadbclient package,
but it can never the less be used as an example too:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/tree/debian/libmariadbclient18.symbols


Please do the following things:

1) Drop the Lintian override immediately. This problem should not be
hidden on purpose.

2) Add the symbols file and start tracking symbols.

3) If there are problems with the symbols changing from release to
release, please address it in appropriate ways, e.g. dump the soname
from .18 to .18.1 or .19 or what is most fit.


Thanks!



More information about the pkg-mysql-maint mailing list