Bug #70067 mysql_install_db strictly relies on my-default.cnf
Submitted: 17 Aug 2013 8:18 Modified: 18 Aug 2013 10:42
Reporter: Bjoern Boschman (OCA) Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: Packaging Severity:S2 (Serious)
Version:5.6.13 OS:Any
Assigned to: CPU Architecture:Any
Tags: mysql install

[17 Aug 2013 8:18] Bjoern Boschman
mysql_install_db strictly relies on creating my.cnf by the my-default.cfn template
also when --defaults-file is provided.

as a package maintainer this is really blocking

How to repeat:
mysql_install_db --defaults-file=/etc/mysql/my.cnf --rpm

error occurs:

FATAL ERROR: Could not find my-default.cnf

If you compiled from source, you need to run 'make install' to
copy the software into the correct location ready for operation.

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.

Suggested fix:
enable mysql_install_db that it provides a mechanism without using my-default.cnf

I'll attach a simple patch
[17 Aug 2013 8:18] Bjoern Boschman
only create my.cnf from template when there is no --defaults-file option

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: mysql_install_db.diff (application/octet-stream, text), 2.12 KiB.

[18 Aug 2013 8:21] Valeriy Kravchuk
Looks like a duplicate of/closely related to Bug #68416
[18 Aug 2013 10:42] Bjoern Boschman
I thought that I already opened a bug against it, but haven't found it via search oO

-> duplicate
[2 Apr 2014 11:50] Ståle Deraas
Hi Bjoern, we are currently doing a rehaul of this code, and will probably not need your contribution. Thanks again for contributing to MySQL.