dbconfig-mysql sets blank port in config
Bug #1563274 reported by
Lars Tangvald
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbconfig-common (Debian) |
Fix Released
|
Unknown
|
|||
dbconfig-common (Ubuntu) |
Fix Released
|
Undecided
|
Norvald H. Ryeng | ||
mysql-5.7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
For non-remote setups, dbconfig will not set a port value, leaving it blank in generated option files.
MySQL 5.7 will no longer accept a blank port option in the config file (See https:/
If the port is not to be changed it should either be set to 3306 or the line omitted from the generated file.
The former is probably the better option, since other packages (e.g. redmine) use dbconfig variables for their own config generation.
tags: | added: mysql-5.7-transition |
Changed in dbconfig-common (Ubuntu): | |
milestone: | none → ubuntu-16.05 |
assignee: | nobody → Norvald H. Ryeng (nryeng) |
Changed in dbconfig-common (Debian): | |
status: | Unknown → Confirmed |
Changed in dbconfig-common (Debian): | |
status: | Confirmed → Fix Committed |
Changed in dbconfig-common (Debian): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As this isn't a simple fix, and is currently blocking MySQL 5.7 in Ubuntu 16, we will patch MySQL to allow the empty port option for now (it will print a warning instead of the error).
There's also a related upstream bug at http:// bugs.mysql. com/bug. php?id= 80903