[debian-mysql] mysql-defaults into unstable?

[Robie Basak]

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.

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.

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.

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.

Robie