[debian-mysql] conf files decoupling (Re: On IRC?)

[Robie Basak]

Hi Otto,

On Sun, Feb 08, 2015 at 11:29:59AM +0200, Otto Kekäläinen wrote:
> 2015-02-05 13:19 GMT+02:00 Robie Basak <robie.basak at canonical.com>:
> > OK. We're running out of time now though - we have only two weeks to
> > feature freeze in Ubuntu now. I understand that you're busy, but I think
> > I have to start uploading things to Ubuntu now in order to make Vivid.
> > This might involve me having to diverge mariadb-10.0 in Ubuntu. I'll try
> > to minimize impact which a view to syncing back in the future as much as
> > I can.
> 
> OK

I've just uploaded mariadb-10.0 10.0.16-1ubuntu1 to Ubuntu.

Since Ubuntu was in sync with Debian before, it was auto-syncing from
unstable, and therefore your jessie branch.

Now that I want the my.cnf symlink change in Ubuntu (that is presumably
unsuitable for jessie), I needed Ubuntu to start following the master
branch.

This leads to a little potential confusion with version strings.
10.0.16-1 was published in Ubuntu and from the jessie branch, and my
10.0.16-1ubuntu1 switches to the master branch, and thus doesn't have
10.0.16-1 in its history.

I've also included your update that I found in
ppa:mysql-ubuntu/mariadb10.0 to include conf.d/*, but I didn't see it in
a VCS anywhere. I presume you just hadn't pushed it yet, but we should
sync up on it without any further as soon as you do.

Finally, the two addiitional changes I made in Ubuntu are to disable
TokuDB (since it fails tests, and so we weren't getting any amd64
binaries in Ubuntu otherwise), and for mariadb-common to depend on
mysql-common (>= 5.6.22-1~) in order to ensure that the symlink handling
is always available when the mariadb-common postinst runs to set it up.

I believe that users who receive these changes should still end up in a
state that we can sync back to Debian in future without issue.

Next I'll upload a new mysql-5.6 that includes the symlink changes.
Until this is built, I believe my mariadb-10.0 upload will be held in
vivid-proposed because mariadb-common will be uninstallable in the
meantime, which is what I want.

Robie