my-default.cnf missing
Bug #1422391 reported by
Robie Basak
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.6 (Ubuntu) |
Fix Released
|
High
|
Robie Basak |
Bug Description
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=
Affected: 5.6.23-0ubuntu2
This causes ruby-mysql2 to FTBFS on rebuild, and the rebuild is needed to fix adt-vivid-redmine.
Related branches
Changed in mysql-5.6 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Robie Basak (racb) |
tags: | added: mysql-5.6-transition |
To post a comment you must log in.
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.