5.6 installing my.cnf to /usr
Bug #1225189 reported by
Ignacio Nin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Ignacio Nin | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
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
- Laurynas Biveinis (community): Approve
-
Diff: 54 lines (+7/-3)1 file modifiedPercona-Server/scripts/mysql_install_db.pl.in (+7/-3)
tags: | added: upstream |
To post a comment you must log in.
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 bugs.mysql. com/bug. php?id= 68416
http://
...
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.