[debian-mysql] MySQL 5.1 in unstable and 5.4 to experimental?

[Christian Hammers]

Am Fri, 3 Jul 2009 16:35:03 -0500
schrieb Mathias Gug <mathiaz at ubuntu.com>:

> On Fri, Jul 3, 2009 at 4:27 PM, Christian Hammers<ch at debian.org>
> wrote:
> >> 1. The cluster engine is disabled in 5.1 while enabled in 5.0.
> >
> > From the changelog:
> >
> >  mysql-dfsg-5.1 (5.1.30-2) experimental; urgency=low
> >  * Drop MySQL Cluster support, it's deprecated since 5.1.24-RC.
> >
> > And from the mentioned upstream changelog:
> >
> >  "Those using MySQL Cluster in MySQL 5.1.23 and earlier MySQL 5.1
> >  mainline releases should upgrade to MySQL Cluster NDB 6.2.15 or a
> > later MySQL Cluster NDB 6.2 or 6.3 release."
> >
> > I guess that's a point for the Debian NEWS file?
> >
> > Do you think that we should check if clustering is used in the
> > preinst script to prevent upgrading in this condition?
> 
> Seems like a good intermediate solution. IIRC norbert was working on
> getting MySQL Cluster packaged separately. In this use case does it
> mean that 5.0 would be kept in the debian archive until MySQL Cluster
> is available?

I'd say it called "unstable" for a reason :) If possible, we
prevent upgrades if we figure out that ndb is enabled. In those cases
the user has to stick with the unsupported 5.0 but as Norbert is not
planning to release another 5.0 anyway (according to a bug report
comment) it would be the same for the user.

bye,

-christian-