Comment 4 for bug 1651011

Ok the problem here is in 16.10.0 there was a patch added (patch A) that altered the artefact_file_mime_types table and set a new primary key on a new id column - by first dropping the existing primary key based on the key name.

Later there was another patch (patch B) that was added after patch A that dropped the table and set a new primary key based on two columns.

Patch B was backported to earlier branches, eg 16.04.5

This meant if one now upgrades from 16.04.5 to 16.10.0 things will fail as the code to drop the primary key is now wrong and so is ignored and then tries to add a new primary key to the table, which is not allowed.

To stop this happening for subsequent 16.10 branch releases we need to remove the upgrade part for (patch A) as it is not needed any more as the upgrade for Patch B supersedes it.