On Thu, May 28, 2026 at 11:10:31AM +0800, Otto Kekäläinen wrote: > > 1) B-D: > > > - Dual compatibility: If the package actively supports both engines and > > > you wish > > > to keep an alternative runtime path open for users drawing from > > > third-party > > > repositories, you can declare an OR dependency. For example > > > 'Depends: mariadb-client | mysql-client'. > > > > Whats the correct Build-Depends equivalent? src:pdns uses a > > (comparatively small) libmysqlclient API surface. > > I haven't tested, but I'd guess the pdns should have `Build-Depends: > libmariadb-dev` or `Build-Depends: libmariadb-dev-compat`. Based on > https://github.com/PowerDNS/pdns/blob/36f6762677539abd610f33fc48310bcf39defe05/docs/upgrading.rst#430-to-431 > seems PowerDNS has been updated to use `mariadb` directly and no > longer needs the compat shim that provides `mariadb` using the library > name `mysql`.
JFTR, this doesn't work. The autoconf-based build needs a working libmysqlclient. I assume upstream also used the compat-libs on RHEL. Lets see if the meson builds will fare better, once meson lands. For now src:pdns Build-Depends: libmariadb-dev-compat | libmysqlclient-dev . I imagine that means the Ubuntu builds will also switch to libmariadb, probably not what Ubuntu wanted. But who knows! Chris
