There is 1 open security issue in forky.
commit f6953b6aafa734dc261db7cff508d929e714c5a3
Author: Otto Kekäläinen <otto@debian.org>
Date: Mon Aug 12 12:08:57 2024 -0700
Make all MariaDB client plugins available in server plugin path
The MariaDB server has only one plugin directory (--plugin-dir). If the
server is running as a replica, it will act as a client when connecting
to the primary database instance. In those cases it may need to use the
client plugins, but it is unable to load the client plugins in the same
way as other client library using code would, and instead expects to find
the plugins in the server plugin directory. Add the client plugins as
symlinks there to prevent the server from failing to connect as client
when using plugin dependant client features.
This was copied by upstream in 57629c2 as part of MDEV-34744.
commit 87e8d8a86099d3d7aee68a14a1de2a70a9db35cc
Author: Aquila Macedo <aquilamacedo@riseup.net>
Date: Mon Nov 24 11:13:43 2025 -0300
Relax perl client dependencies in mariadb-client (Closes: #1115678)
Drop libconfig-inifiles-perl from mariadb-client Depends, none of the
current Perl client tools use Config::IniFiles, and ${perl:Depends} no
longer pulls it in.
Demote libdbi-perl, libdbd-mariadb-perl | libdbd-mysql-perl, and
libterm-readkey-perl from Recommends to Suggests so the Perl DBI stack
is optional and not strongly dragged in by a plain mariadb-client
install.
Document the optional Perl modules in debian/mariadb-client.README.Debian
so users seeing "Can't locate DBI.pm" (for mytop, innotop,
mariadb-report, etc) know which packages to install.
Among the 11 debian patches available in version 1:11.8.5-1 of the package, we noticed the following issues:
There is 1 open security issue in trixie.
You can find information about how to handle this issue in the security team's documentation.
There is 1 open security issue in bookworm.
You can find information about how to handle this issue in the security team's documentation.