[debian-mysql] MySQL in Jessie

[Norvald Ryeng]

----- clint at fewbar.com wrote:

> Excerpts from Norvald Ryeng's message of 2014-10-01 11:37:58 -0700:
> > ----- james.page at ubuntu.com wrote:
> > 
> > > On 01/10/14 16:01, Emilio Pozuelo Monfort wrote:
> > > >>> If the release team is OK with this, we'll go ahead and upload
> 
> > > >>> mysql-5.6 to unstable and raise bugs for the three impacted
> > > >>> packages. Please can you confirm.
> > > > I think it's rather late for such an upload, especially when it
> > > > involves an ABI break. I asked other RT members and the answer
> I
> > > > got also was that it was too late for this.
> > > > 
> > > > So I'd say we stay at 5.5 for Jessie.
> > > 
> > > OK; upstream support lifetimes are OK for this so should be ok.
> > 
> > There's one more issue. MySQL 5.6 is already almost 2 years old. 5.7
> is probably released before jessie+1, but the recommended upgrade path
> is 5.5 -> 5.6 -> 5.7, so there should be one release with 5.6 first in
> order to provide an upgrade path.
> > 
> 
> Are you suggesting that mysql_upgrade in 5.7 cannot upgrade from 5.5
> directly?

It's not something we recommend. I know people successfully have skipped 5.5 when going from 5.1 to 5.6. I haven't tried going directly from 5.5 to 5.7 yet, but idea of making such leaps makes me a bit uneasy.

> That would be most unfortunate. I still don't think we can ship 5.6 in
> jessie if there are ABI issues.

There's an ABI issue, but it only affects installations that use a PAM plugin for authentication on the MySQL server. We've found only two packages that _may_ be broken by the upgrade. They match the search for the broken part of the ABI, so we suggest they rebuild just to make sure. No packages are confirmed broken (and again, they would only be broken in certain setups).

So, yes, an ABI breakage, but a minor one that I think is manageable.

Regards,

Norvald H. Ryeng