my-default.cnf missing

[Robie Basak]

According to the mysql_install_db manpage, the tool ships my-default.cnf to install as a new my.cnf in the base installation directory. So I presume that my-default.cnf is shipped in packaging.

However, on rebuild of ruby-mysql2, I got:

FATAL ERROR: Could not find my-default.cnf

This was from the call (detected by set -x):

mysql_install_db --no-defaults --datadir=/tmp/tmp.A0oCiqJYWc --force --skip-name-resolve --user=root

Affected: 5.6.23-0ubuntu2

This causes ruby-mysql2 to FTBFS on rebuild, and the rebuild is needed to fix adt-vivid-redmine.

[Norvald H. Ryeng (nryeng)]

The file is indeed missing. It should've been in the mysql-server-core-5.6 package, but it's not.

In ruby-mysql2: Add --keep-my-cnf to the mysql_install_db command line. Since the server is started with --no-defaults, it's not going to read the my.cnf file, and mysql_install_db doesn't need to create it.

In mysql-server-core-5.6: Add usr/share/mysql/my-default.cnf to the package. mysql_install_db expects to find it.

[Robie Basak (racb)]

Thanks Norvald! Fix for mysql-5.6 pushed to Debian VCS. I'll pick this in my next Ubuntu upload.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mysql-5.6 - 5.6.23-1~exp1~ubuntu3

---------------
mysql-5.6 (5.6.23-1~exp1~ubuntu3) vivid; urgency=medium

  * Call dh "--with systemd" to enable systemd unit.
 -- Martin Pitt <email address hidden> Mon, 09 Mar 2015 09:38:35 +0100