Bug #80903 Debian/Ubuntu packages fail to install because of empty config values
Submitted: 30 Mar 2016 7:53 Modified: 16 Jun 2016 17:13
Reporter: Lars Tangvald Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:5.7.11 OS:Linux
Assigned to: CPU Architecture:Any

[30 Mar 2016 7:53] Lars Tangvald
Description:
MySQL 5.7 will no longer accept empty values for non-string config options, and will throw an error and exit if it finds one.

There are packages (dbconfig-common) in Debian/Ubuntu that assume empty values for some options are ok (port, in this case), so the switch is a bit sudden.

How to repeat:
* Install MySQL 5.7
* Install some package that uses dbconfig, such as phpmyadmin, and pick mysql as the backend
* It fails with «[ERROR] mysql: Empty value for 'port' specified.»

Suggested fix:
A better solution might be to have a deprecation warning or something similar for 5.7 and change to a full error later.
[30 Mar 2016 11:05] MySQL Verification Team
Hello Lars,

Thank you for the report.
Observed this on Ubuntu 15.10 while configuring phpmyadmin using apt-get repository.

Thanks,
Umesh
[20 Apr 2016 14:35] Panayiotis Omirou
Hi, 

I confirm this on Debian 8 while trying to install phpmyadmin on mysql 5.7
[11 May 2016 9:25] Philippe Florent
will it be resolved ?
is there any workaround ?
since I need 5.7 for replications, I am so screwed...
[16 Jun 2016 11:41] Lars Tangvald
Posted by developer:
 
Docs team:
An empty value for the "port" configuration option will give a warning for 5.7 only. The treatment of other options is unchanged, and an empty "port" will no longer be accepted in MySQL 8
[16 Jun 2016 17:13] Paul DuBois
Posted by developer:
 
Noted in 5.7.14 changelog.

Specifying an empty value for the --port option (for example,
--port=, --port="") is now deprecated and results in a warning. An
empty value will be an error in MySQL 8.0.