mysql_install_db is installed by mariadb-server-core and requires my_print_defaults that is provided by package mariadb-server.
Step to reproduce (on 10.1 and 10.3):
{code:bash}
$ sudo apt install mariadb-server-core-10.1
$ /usr/bin/mysql_install_db
FATAL ERROR: Could not find /usr/bin/my_print_defaults
If you compiled from source, you need to either run 'make install' to
copy the software into the correct location ready for operation.
If you don't want to do a full install, you can use the --srcdir
option to only install the mysql database and privilege tables
If you compiled from source, you need to either run 'make install' to
copy the software into the correct location ready for operation.
If you don't want to do a full install, you can use the --srcdir
option to only install the mysql database and privilege tables
If you are using a binary release, you must either be at the top
level of the extracted archive, or pass the --basedir option
pointing to that location.
mysql_install_db is installed by mariadb-server-core and requires my_print_defaults that is provided by package mariadb-server.
Step to reproduce (on 10.1 and 10.3):
{code:bash}
$ sudo apt install mariadb-server-core-10.1
$ /usr/bin/mysql_install_db
FATAL ERROR: Could not find /usr/bin/my_print_defaults
If you compiled from source, you need to either run 'make install' to
copy the software into the correct location ready for operation.
If you don't want to do a full install, you can use the --srcdir
option to only install the mysql database and privilege tables
If you compiled from source, you need to either run 'make install' to
copy the software into the correct location ready for operation.
If you don't want to do a full install, you can use the --srcdir
option to only install the mysql database and privilege tables
If you are using a binary release, you must either be at the top
level of the extracted archive, or pass the --basedir option
pointing to that location.
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...
Faustin Lammler
added a comment - 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.
Elena Stepanova
added a comment - 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.
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).
Faustin Lammler
added a comment - - edited 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).
Faustin Lammler
added a comment - 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.
Elena Stepanova
added a comment - - edited 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.
Sergei Golubchik
added a comment - 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.
It should be updated on upstream too and this is maybe already in otto's wip list?
Faustin Lammler
added a comment - 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?
Bug
Major
MDEV-6284 Merge downstream Debian/Ubuntu packaging into upstream MariaDB
Does it create any practical problem? mysql_install_db won't work anyway if the server is not installed.