On Thu, Jan 22, 2009 at 02:22:02AM -0000, Tom Worley wrote:
> 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
Could you check if mysql-common has been upgraded? If so have you been
prompted for a configuration change? If so did you accept it?
mysql-common is part of mysql-dfsg-5.0 and not mysql-dsfg-5.1. The fix
for this bug is in mysql-dfsg-5.0 - mysql-dfsg-5.1 hasn't been changed.
On Thu, Jan 22, 2009 at 02:22:02AM -0000, Tom Worley wrote:
> 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
Could you check if mysql-common has been upgraded? If so have you been
prompted for a configuration change? If so did you accept it?
mysql-common is part of mysql-dfsg-5.0 and not mysql-dsfg-5.1. The fix
for this bug is in mysql-dfsg-5.0 - mysql-dfsg-5.1 hasn't been changed.
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://