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

[Christian Hammers]

Am Mon, 29 Jun 2009 13:34:28 -0400
schrieb Mathias Gug <mz at mathiaz.net>:

> Hi Christian,
> 
> On Mon, Jun 29, 2009 at 9:40 AM, Christian Hammers<ch at debian.org>
> wrote:
> > I've just read that MySQL has released 5.4 so it should be time to
> > get 5.1 into unstable, right? Are there any major blockers?
> 
> While merging 5.1 from experimental into karmic (the Ubuntu
> development version), I looked into replacing 5.0 by 5.1 in main. I've
> identified two blockers so far:
> 
> 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?

> 2. The 5.1 test suite fails during the build process while it's
> successful in 5.0.

Argh... I found the answer for 2:
The mysql test tries to connect to the database test although it was
only granted USAGE and not e.g. READ. With USAGE alone it
cannot change to a database except the bootstrap permission happens
to grant access to the test database to everyone from the beginning.
And we eliminated these grants in our patch: 
33_scripts__mysql_create_system_tables__no_test.dpatch 

I'll try to fix the tests.

bye,

-christian-