[debian-mysql] dbconfig autopkgtests fail: Plugin caching_sha2_password could not be loaded: /usr/lib/aarch64-linux-gnu/mariadb19/plugin/caching_sha2_password.so

[Paul Gevers]

Hi Robie, Otto,

Thanks for the investigation. I think the situation is "interesting".

On 26-08-2020 18:37, Robie Basak wrote:
> The test does fail only against MySQL at the server end. When MariaDB is
> at the server end, as you observed the dep8 test passes. But the failure
> is at the client end. The difference is that MySQL defaults to the
> caching_sha2_password authentication mechanism, which is part of the
> MySQL wire protocol. Looks to me that in this case libmariadb3 attempts
> to load its own plugin for the mechanism but it does not exist.
> 
> It's not clear to me if MariaDB's client library is supposed to still be
> able to connect to MySQL.

I think this is the real question at stake. If MariaDB (client) has the
intention to be able to connect to MySQL (server) than this seems to be
a bug in MariaDB. If this effort is a lost cause, than I guess we should
all move on (and I should remove the test from dbconfig-common).

> Whether it is or not, I think its inability to
> do so is what's failing here. dbconfig-common has no choice but to use
> MariaDB's client library because it uses libdbd-mysql-perl and
> libdbd-mysql-perl builds against default-libmysqlclient-dev which is
> provided by MariaDB packaging.
> 
> If MariaDB (as packaged in Debian) can no longer connect[1] to MySQL, or
> at least if libdbd-mysql-perl when built against MariaDB cannot, then I
> think we have a wider problem here. But before we go into that, please
> could you see if you can confirm my conclusion?

I leave this to the MariaDB maintainers.

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20200827/ce709399/attachment.sig>