Debian

Does it create any practical problem? mysql_install_db won't work anyway if the server is not installed.

No, no other problem that script not found.
Is it possible to use mysql_install_db on a remote DB, this is the only reason where this could be considered as an issue for me...

mysql_install_db starts the server process in order to bootstrap the database, so it has to be local.
And even if it were possible, my_print_defaults still would need to be on the machine where the server runs (and not the client), since it reads server configuration files.

Thank you elenst for this quick answer!

So this is clearly not an issue. But I do not know if this is an acceptable situation regarding the Debian packaging guidelines.
I have to check this point (anybody aware on that please let me know).

cvicentiu, maybe you can help with that (or know who can)?

elenst what do you think about Olaf comment?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898367#15

I have just asked Viventiu on zulip also.

I don't have any strong preferences regarding Debian packaging, to a big extent it seems arbitrary to me. Maybe serg has an opinion. In any case, I hope cvicentiu will be able to coordinate it to everyone's satisfaction.

it's not about remote server or anything. It's the simple thing that if a package X uses something from the package Y, it needs to depend on the package Y, and this is not the case here.

That seems clear an logic to me.
Let's wait for cvicentiu decision.

Hi,
commit on debian repo from otto resolves this issue:
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/3689350ad30916aa68fe2c1b35c290fb5095bc9b

It should be updated on upstream too and this is maybe already in otto's wip list?

PR filed at https://github.com/MariaDB/server/pull/1451

PR https://github.com/MariaDB/server/pull/1451 was merged, thus this issue is closed for 10.5.