MySQL Bugs: #85133: mysql-apt-config Cannot Use Alternate Port

Bug #85133	mysql-apt-config Cannot Use Alternate Port
Submitted:	22 Feb 2017 18:04	Modified:	5 Apr 2017 6:50
Reporter:	Jake S	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Package Repos	Severity:	S1 (Critical)
Version:	mysql-apt-config_0.8.2-1_all.deb	OS:	Debian (Typical LAMP Stack)
Assigned to:	Lars Tangvald	CPU Architecture:	Any
Tags:	installation, upgrade

Description:
The debian apt repository private key for the mysql repo expired Fab 16, 2017. When running apt-get upgrade after the key expired it is impossible to get the new key over any port except 11371. This leaves the installation in a broken state.

I was able to manually get and install the new key with this command:

sudo apt-key adv --keyserver hkp://pgp.mit.edu:80 --recv-keys 5072E1F5

However, even after manually upgrading it, mysql-apt-config tries to get the key again but can only use port 11371.

This leaves me in a loop where I cannot finish installing the latest upgrade.

How to repeat:
Block port 11371 and try to upgrade to latest version of mysql-server.

Suggested fix:
If the default port is blocked, try accessing the new keyfile over port 80.

Updating Category.

"--keyserver hkp://pgp.mit.edu:80" would replace "pgp.mit.edu" in the executed command during upgrade process. Sepcifying :80 without the protocol does not seem to work.

Hi,

At the very least we should make the config package have a fallback if it can't download the key, rather than abort with an error.

As a temporary workaround you can make a copy of /etc/apt/sources.list.d/mysql.list, remove mysql-apt-config, then copy the file back and run apt-get update.

Posted by developer:
 
Hi,

The new 0.8.3 release no longer downloads the key, but goes back to including it. Can you verify this fixes the problem for you?

Fixed by refactoring done in 0.8.3.