[debian-mysql] mysql-defaults into unstable?

[Otto Kekäläinen]

Hello!

2016-07-21 21:44 GMT+03:00 Robie Basak <robie.basak at ubuntu.com>:
> On Thu, Jul 21, 2016 at 09:27:23PM +0300, Otto Kekäläinen wrote:
>> The new mysql-defaults has now been in experimental for 10+ days. We
>> haven't got any feedback from the package in general or to the message
>> posted to debian-devel at .
>>
>> Is it OK to everybody if I upload mysql-defaults to unstable in the
>> coming days to get broader exposure to it?
>
> Do we want to put mysql-5.7 in at the same time? Because otherwise
> src:mysql-5.6 still produces mysql-common, which is not ideal.

There is no strict dependency there. The only thing we need to be
careful about is not to upload any new versions of mysql-5.6 anymore
(or at least current git master that would provide mysql-common that
conflicts with the new mysql-common).

Let's just upload mysql-5.7 to unstable when it is ready, it does not
need to be in sync with mysql-defaults.

> I have one fix I found in mysql-5.7 I'd like to push before uploading to
> unstable, which is (IIRC) s/le-nl/le/ in the migration path code in
> mysql-server-5.7.postinst, but I'm out until Tuesday and won't have time
> to do it before then.

Ok. Take your time. By the way, I will be offline most of next week.

> What do you want to do in Ubuntu? Should we defer the move to
> mysql-defaults until Yakkety+1? If not, we need to decide what we're
> doing very soon, and if so, I'd like the opportunity to blacklist
> mysql-defaults and mariadb-10.0 so they don't auto-sync, so we can
> migrate in Ubuntu when we're ready.

We cannot really blacklist mysql-defaults, as any of the other
packages in the universe might declare it as a dependency. All you can
do is provide a customized version that behaves differently if you
need so. As Yakkety is not an LTS version I would maybe not hesitate
putting in the latest software versions there. The less there is
delta, the less we have to maintain, right?

> If we can resolve what we want to do about these three things, I have no
> other objection. The last obviously doesn't relate to Debian, but it
> would be helpful for me to know what we're doing on this too. Otherwise
> cleaning stuff up later just takes away from the time I could be
> spending sorting MySQL in Debian.

Summary:
- Uploading mysql-defaults will provide a new mysql-common but which
has exactly the same contents as it was already in mysql-5.6/5.7.
Regressions are unlikely. The other things mysql-defaults provides
will not have any effect until other packages start to use them. So
this should be safe to upload at any time. We are doing a slow
roll-out just in case.
- Uploading mariadb-10.0 will provide new libmariadbclient18 packages.
These again have no effect until other packages start to use them.
This should be safe to upload too.
- Uploading mysql-5.7 will provide new mysql-* packages. This will
cause new installs of mysql-server to behave differently. This has
however been tested in Ubuntu Xenial and Yakkety already, and Robie is
working on additional fixes. With those fixes it should be safe to
upload too.

My suggestion:
- upload mariadb-10.0 now
- upload mysql-5.7 next week
- upload mysql-defaults the week after that

This will allow a slow roll-out and give us time to catch potential
regressions. The ordering is not strict, but in the ideal situation
mysql-defaults is uploaded last, as it depends on stuff that
mariadb-10.0 and mysql-5.7 provide.

- Otto