Bug #81045 Debian packages broken (mysql-common and libmysqlclient18) in mysql 5.6
Submitted: 12 Apr 2016 9:55 Modified: 12 Apr 2016 12:53
Reporter: Samer Afach Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.6 OS:Debian (Jessie)
Assigned to: Lars Tangvald CPU Architecture:Any

[12 Apr 2016 9:55] Samer Afach
Description:
The bug is explained here:

http://unix.stackexchange.com/questions/275818/upgrading-mysql-caused-broken-packages

How to repeat:
I'm not sure about repeating, but I have MySQL community server 5.6 for a long time, and yesterday this bug appeared. The apt entry seems to be wrong and must be fixed.

Suggested fix:
Fix the apt mysql entry.
[12 Apr 2016 12:08] Lars Tangvald
Hi,

Thanks for the report. This seems to be a bug in the new version of mysql-apt-config. 
In your /etc/apt/sources.list.d/mysql.list file, the line:
 «deb http://repo.mysql.com/apt//debian/ jessie mysql-5.6 mysql-5.7-dmr mysql-5.7 connector-python-2.0 connector-python-2.1 router-2.0 mysql-utilities-1.5 mysql-tools»
Should not contain the entries «mysql-5.6 mysql-5.7-dmr mysql-5.7»
As a workaround you can remove these entries from that line, until we can fix the bug.
[12 Apr 2016 12:51] Lars Tangvald
The issue here is with apt-config adding multiple server repositories to /etc/apt/sources.list.d/mysql.list rather than the packages themselves.
[12 Apr 2016 12:53] Samer Afach
Thank you. I fixed it on my server that's no biggie. I just wanted to make sure it's not a mistake from my end. Please fix it soon. Thank you.
[13 Apr 2016 11:04] Lars Tangvald
Hi,

A fixed version (0.7.2) has now been released, and should work as expected.
[13 Apr 2016 17:13] Nico Haase
The latest update killed my current MySQL server: even if I did not change in the dialog to change the version, it removed the server version 5.6 and installed 5.7. Afterwards, /etc/init.d/mysql did not run anymore, as it prints only dots. The method verify_server possibly needs a second argument?
[13 Apr 2016 17:23] Nico Haase
Okay - that it did not start anymore is caused by a wrong my.cnf. But I did not request an upgrade in the configuration dialog, so this is still an error to me
[13 Apr 2016 18:11] Lars Tangvald
Do you know which version of the config package you had installed that caused the problem?
Could you check the contents of your /etc/apt/sources.list.d/mysql.list file?
[13 Apr 2016 18:16] Nico Haase
/etc/apt/sources.list.d/mysql.list contains now:

### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out entries below, but any other modifications may be lost.
# Use command 'dpkg-reconfigure mysql-apt-config' as root for modifications.
deb http://repo.mysql.com/apt//debian/ jessie mysql-apt-config
deb http://repo.mysql.com/apt//debian/ jessie mysql-5.7
deb http://repo.mysql.com/apt//debian/ jessie connector-python-2.0 connector-python-2.1 router-2.0 mysql-utilities-1.5 mysql-tools

deb-src http://repo.mysql.com/apt//debian/ jessie mysql-5.7
[13 Apr 2016 18:17] Nico Haase
And the APT history tells me:

Start-Date: 2016-04-11  20:50:38
Upgrade: mysql-apt-config:i386 (0.5.3-1, 0.7.0-1), mysql-client:i386 (5.6.29-1debian8, 5.6.30-1debian8), mysql-community-client:i386 (5.6.29-1debian8, 5.6.30-1debian8), mysql-server:i386 (5.6.29-1debian8, 5.6.30-1debian8), mysql-common:i386 (5.6.29-1debian8, 5.6.30-1debian8), libmysqlclient18:i386 (5.6.29-1debian8, 5.6.30-1debian8), mysql-community-server:i386 (5.6.29-1debian8, 5.6.30-1debian8)
End-Date: 2016-04-11  21:50:32

Start-Date: 2016-04-13  18:48:06
Install: libmecab2:i386 (0.996-1.1, automatic)
Upgrade: mysql-apt-config:i386 (0.7.0-1, 0.7.2-1), mysql-client:i386 (5.6.30-1debian8, 5.7.12-1debian8), mysql-community-client:i386 (5.6.30-1debian8, 5.7.12-1debian8), mysql-server:i386 (5.6.30-1debian8, 5.7.12-1debian8), mysql-common:i386 (5.6.30-1debian8, 5.7.12-1debian8), libmysqlclient18:i386 (5.6.30-1debian8, 5.7.5-m15-2debian8), mysql-community-server:i386 (5.6.30-1debian8, 5.7.12-1debian8)
End-Date: 2016-04-13  18:51:57
[13 Apr 2016 18:25] Lars Tangvald
Seems that what happened is that you upgraded to apt-config 0.7.0 which had the bug described above. This added the mysql-5.7 repo to the source list, so when you upgraded to 0.7.2 5.7 was already made available, and apt upgraded your server.

I'm sorry for the trouble. Since we don't run mysql_upgrade during the install you might be able to simply downgrade by uninstalling the server, reconfiguring apt-config 0.7.2 and reinstalling (but take a backup of the data directory first).