On 11/22/20 7:17 PM, Otto Kekäläinen wrote:
> Package: puppet-module-puppetlabs-mysql
>
> Hello!
>
> I noticed the source package has references to libmariadbclient-dev:
> https://salsa.debian.org/search?search=libmariadbclient-dev&project_id=6453&group_id=2572
>
> This is a deprecated package and you should instead use
> libmariadb-dev[1] or libmariadb-dev-compat if you need to build
> something old that does not find the correct soname otherwise.
>
> I am not sure if the params.pp is relevant in Debian, but filing this
> just in case.
>
> Thanks!
>
> 1: https://packages.debian.org/search?keywords=libmariadb-dev
Hi Otto,
Thanks a lot for this helpful bug report.
It is relevant to Debian. If you read it, you can see:
case $::osfamily {
[...]
'Debian': {
if $provider == 'mariadb' {
$client_dev_package_name = 'libmariadbclient-dev'
$daemon_dev_package_name = 'libmariadbd-dev'
As I would prefer this puppet module to work with both Buster and
Bullseye, I have to ask: is 'libmariadb-dev' replacing
'libmariadbclient-dev' in both Buster and Bullseye, or only in Bullseye?
Will Bullseye continue to have 'libmariadbclient-dev' as a transition
package for Bullseye (in which case, we may fix the package only after
Bullseye is released)?
Cheers,
Thomas Goirand (zigo)
