I can confirm this bug still exists in mysql-server-5.1 (5.1.30-2ubuntu3), from an upgrade of Intrepid to Jaunty, then installing 5.1. This breaks the upgrade, however, commenting out skip-bdb fix works and apt continues the upgrade
I can confirm this bug still exists in mysql-server-5.1 (5.1.30-2ubuntu3), from an upgrade of Intrepid to Jaunty, then installing 5.1.
This breaks the upgrade, however, commenting out skip-bdb fix works and apt continues the upgrade