Package: libmariadb-dev-compat Version: 2.3.2-2 Severity: important Dear Maintainer,
I have been unable to install a static version of the MySQL client library at the same time as a static version of the mysql++ library. * What led up to the situation? I am trying to compile an app as a static binary, so it can run in an environment without known library versions. * What exactly did you do (or not do) that was effective (or ineffective)? Tried to find a package that contains libmysqlclient.a, found libmariadb-dev-compat and installed that. * What was the outcome of this action? The static MySQL client library was provided, but libmysql++-dev got removed in the process, so my code wouldn't compile. Trying to install mysql++ again said it would remove libmariadb-dev-compat. * What outcome did you expect instead? I was hoping for libmysqlclient.a installed along with a static version of libmysql++-dev. -- System Information: Docker image: debian:latest Debian Release: 8.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.3-1-ARCH (SMP w/16 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages libmariadb-dev-compat depends on: ii libmariadb-dev 2.3.2-2 libmariadb-dev-compat recommends no packages. libmariadb-dev-compat suggests no packages. -- debconf information excluded
