5.6 installing my.cnf to /usr

Bug #1225189 reported by Ignacio Nin on 2013-09-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server
Status tracked in 5.6
5.1
Undecided
Unassigned
5.5
Undecided
Unassigned
5.6
Medium
Ignacio Nin

Bug Description

As of 5.6.13-60.5 in debian versions, Percona Server 5.6 installs a file /usr/my.cnf, probably packaged by mistake. This needs to be removed from the packaging.

Related branches

lp:~ignacio-nin/percona-server/5.6-bug1225189
Merged into lp:percona-server at revision 471
Laurynas Biveinis: Approve on 2013-10-10

Why do we think this is a bug? Looks like /usr/my.cnf is a new and documented "feature" of upstream MySQL 5.6. Check:

http://dev.mysql.com/doc/refman/5.6/en/mysql-install-db.html:

"As of MySQL 5.6.8, on Unix platforms, mysql_install_db creates a default option file named my.cnf in the base installation directory. This file is created from a template included in the distribution package named my-default.cnf. You can find the template in or under the base installation directory."

http://bugs.mysql.com/bug.php?id=68318
http://bugs.mysql.com/bug.php?id=68416
...

So, if basedir is /usr and mysql_install_db is called in the process, this looks like an expected and documented (even if new and unexpected) upstream MySQL 5.6 behavior.

Alexey Kopytov (akopytov) wrote :

Yes, I have verified that /usr/my.cnf is not really packaged, but is created by mysql_install_db. So it is a duplicate of upstream http://bugs.mysql.com/bug.php?id=68416.

tags: added: upstream
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.