MySQL Bugs: #80626: Cannot install from repositories to Ubuntu 14.04.04 i386

Bug #80626	Cannot install from repositories to Ubuntu 14.04.04 i386 - many packages missing
Submitted:	6 Mar 2016 13:21	Modified:	23 Aug 2017 10:21
Reporter:	Stephen Parry	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S1 (Critical)
Version:	5.6 community	OS:	Ubuntu (14.04.04 i386)
Assigned to:	Lars Tangvald	CPU Architecture:	Any

Description:
Had serious problems with regular upgrades of MySQL from apt repositories - unmet dependencies. Tried uninstalling client and reinstalling to see if this fixed the problem this is the output:

parrysg@mainscreen:~$ sudo apt-get install mysql-community-client
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 mysql-community-client : Depends: mysql-common (= 5.6.29-1ubuntu14.04)
E: Unable to correct problems, you have held broken packages.

Looking at the actual contents of the repository, many of the 14.04 i386 packages are missing. The 14.04 x64 versions seem to be OK; some other versions look as if they may also be missing.

How to repeat:
Install Ubuntu 14.04.04 i386
Install apt-config
Download mysql-apt-config_0.6.0-1_all.deb
<code>
sudo dpkg -i ~/mysql-apt-config_0.6.0-1_all.deb
</code>
choose MySQL Server 5.6 and apply
<code>
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install mysql-community-client
</code>

Suggested fix:
Review and rebuild 5.6 repo packages

Sorry for the trouble.

Verified that i386 packages for 5.6.29 are missing on repo.mysql.com, with the exception of Ubuntu 15.10

Hi,

This problem should be resolved now. Can you verify that it works?

Have to be a visual inspection - The bug had been there for quite a while without answer (I posted a community query a while back before posting the bug report. That post never got approved). Hence I felt I had to take the opportunity and upgraded to 5.7. So can't check for real anymore.

We'll handle verifying that it's fixed, then. 
Thanks for bringing it to our attention!