Looking for Feedback: Update mysql from 5.1 to 5.5

[Clint Byrum]

On Wed, 2011-02-09 at 07:23 -0600, Jamie Strandboge wrote:
> Mysql is very difficult to maintain in stable releases and we have tried
> very hard in the past to have only one version of mysql supported per
> release (eg, 5.0 dropped to universe when 5.1 entered into karmic).
> Having both 5.1 and 5.5 in main is a major red flag for the security
> team, and the MIR for 5.5 will need to demonstrate why the benefits of
> this outweigh the support costs.
> 
> Based on the above, I recommend getting 5.5 into universe so people can
> play with it (being very careful about the client libraries!), then
> working with Debian and upstream to see what it will take to get 5.5
> into acceptable shape for the upcoming LTS (and ideally for natty+1).
> 

I have to agree. After further investigation it just seems that the've
gotten this wrong and need to fix it before we can start compiling
things against the new client libraries.

So, I think we'll drop the client libraries completely out of the
control file(including the -dev packages) so nobody build-deps on them
before they've figured out how to version the libs properly.

I opened this bug this morning, which should hopefully clearly spell out
the issues for them:

http://bugs.mysql.com/60061

I don't think we should ship a 5.5.x based libmysqlclient* until that
bug is fixed upstream, which means it stays in universe. Just having the
server side available will be highly useful to a number of users.