[debian-mysql] On IRC?

[Otto Kekäläinen]

Now when the new config proposal is complete and we have running code I
would like to review and test it before we start to deploy it, ok?

I think I can do it over the weekend while listening to talks in FOSDEM
 30.1.2015 12.55 kirjoitti "Robie Basak" <robie.basak at canonical.com>:

> On Fri, Jan 30, 2015 at 01:42:58PM +0200, Otto Kekäläinen wrote:
> > I am at Fosdem. My irssi is idling, I'll see your message when I at back
> at
> > the hotel. Email though will get read faster though as I have it on my
> phone
> > 30.1.2015 12.26 kirjoitti "Robie Basak" <robie.basak at canonical.com>:
>
> Ah of course. Sorry! I'll copy in the list on this now I think, to
> be more inclusive.
>
> 11:03 <rbasak> otto: I only realised yesterday that mariadb 10.0 is
> FTBSing on Vivid amd64 right now, including from experimental. So I'm
> thinking of leaving it behind for now.
>
> 11:04 <rbasak> otto: I can upload a new mysql-common that breaks
> mariadb-<something>-10.0 << 10.0.16-1, but that means that if you upload
> a 10.0.16-1 without using the new my.cnf mechanism then things will
> break.
>
> The issue is that if I upload my new changes, then mariadb will assume
> that it's getting a my.cnf that works (because that was previously
> shipped by mysql-common), but mysql-common will now only ship the client
> sections by default, and the server variant packages need to supply the
> configurations they need.
>
> So, it'll break.
>
> But I'd really like to Vivid today, to unblock Percona. So is it OK if I
> break older mariadb in the new mysql-common, and then when you're back
> we can work on and upload the new mariadb that works?
>
> As a reminder, here's a summary of what the new mariadb packaging will
> have to do:
>
> 1) Ship /etc/mysql/mariadb.cnf, which includes /etc/mysql/mariadb.cnf.d/
> and
> /etc/mysql/conf.d/
>
> 2) Ship whatever you wish in /etc/mysql/mariadb.cnf.d/ - probably the same
> as what you were previously getting from mysql-common's default my.cnf?
>
> 3) Depend on mysql-common (>= 5.6.19-1~) to get the new functionality.
>
> 4) Call in your postinst for configure:
>
>     /usr/share/mysql-common/configure-symlinks install mysql
> "/etc/mysql/mariadb.cnf"
>
>    and in your postrm for remove or disappear:
>
>     /usr/share/mysql-common/configure-symlinks remove mysql
> "/etc/mysql/mariadb.cnf"
>
> You can see an example of this in action
> https://github.com/basak/debian-percona-server-5.6
>
> It's also fully operational in ppa:mysql-ubuntu/collab
>
> So is it OK to push to Debian master and to upload to Vivid a new
> src:mysql-5.6 which includes a new mysql-common with this functionality?
> I could even hold it in vivid-proposed for now if you wish. I just want
> to get to a position that I can upload the Percona stuff in a way that
> works with the new mechanism.
>
> Robie
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20150130/eacf6918/attachment.html>