Hi Otto, On Sun, 4 Mar 2018 00:06:53 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= <o...@debian.org> wrote: > It was not intended for the mariadb-10.x packages to ship the new LGPL > based client library. For that we have the separate > mariadb-connector-c package. > > The package mariadb-10.2 is to be removed from Debian unstable and the > next versions of mariadb-10.3 uploaded to Debian will not include this > libmariadb3 library.
That's fine. There's still the problem that testing / unstable / experimental users might have installed libmariadb3 when it was available to them, at version 10.2 or 10.3. Now if we go back to libmariadb3 3.0.3 from src:mariadb-connector-c, apt will refuse to upgrade the package for those users. That's why we need an epoch here, so that the new libmariadb3 from src:mariadb-connector-c has a higher version than any previous libmariadb3. That would also solve the problem with mariadb-connector-c failing to install into the archive, as you can see in [1] What I would suggest is that you upload mariadb-connector-c with an epoch (i.e. 1:3.0.3-2) and when it is built and installed, upload mariadb-10.3 without libmariadb3. Cheers, Emilio [1] https://buildd.debian.org/status/package.php?p=mariadb-connector-c&suite=unstable
