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

[Christian Hammers]

Hi

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.
> 2. The 5.1 test suite fails during the build process while it's
> successful in 5.0.
> 

I filed a MySQL bug for the fail of main.concurrent_innodb_unsafelog:
	http://bugs.mysql.com/bug.php?id=45888

But after running "make test-force" I now see that 10+ tests failed.
Wonderful quality assurance... let's see if we can get a statement of
a MySQL guy. 

When creating the packages for Ubuntu, did you do any other changes
to the Debian .diff from experimental? The README.Maintainer lists
some points which might be fixed until the great masses installs it:

* debian-sys-maint is not created properly in postinst
* Asking for root passwort has not yet been backported^H^H^H^Htested.
* Debconf template translations need testing
* Incompatible change: The table_cache system variable has been renamed
  to table_open_cache. -> sed over /etc/mysql/*
* Append --syslog to /etc/mysql/*
* call the REPAIR TABLE statement for each table that contains any
  FULLTEXT  indexes.
* put this trigger-recreation thing into the init scripts

bye,

-christian-