[debian-mysql] mysql-5.6 -> unstable

Bjoern Boschman bjoern at boschman.de
Mon Jun 15 09:07:00 UTC 2015


Hi,

it builds, is installable and I am using it on my box?
Anyone who is willing to test it any further can fetch the build artifacts
here (in experimental)
http://www.boschman.de/debian/

Cheers
B
On Thu, Jun 11, 2015 at 4:22 PM Robie Basak <robie.basak at ubuntu.com> wrote:

> On Wed, Jun 10, 2015 at 02:18:58PM +0000, Bjoern Boschman wrote:
> > can anyone with upload rights pls upload mysql-5.6 to unstable?
> >
> >
> https://www.boschman.de/~jesusch/git/mysql/mysql-5.6_5.6.25-1_amd64.changes
> >
> > changes are commited and pushed to git.
>
> Please don't, it's broken. Have you actually build tested it?
>
> I have fixes/reversions in the pipeline. I should have them in git in
> the next few hours.
>
> However, based on experience from Ubuntu, I wonder if I should fix
> https://launchpad.net/bugs/1447944 before we upload, in order to break
> fewer users?
>
> In addition to that, any opinion on having a maintainer script disable
> the mysql service somehow if updating between releases and the
> maintainer script can detect that local configuration changes mean that
> mysqld cannot start, rather than failing the maintainer script and thus
> failing the upgrade? It seems to me that this would make for a better
> user experience. We can explain what happened in a critical debconf
> prompt, but at least this way it won't break the user's system (only
> the mysqld service).
>
> Something like creating /etc/mysql/my.cnf.migrated.disabled in this case
> (when my.cnf was previously modified and thus my.cnf.migrated is
> created) and if that file exists then the service can avoid starting
> mysqld.
>
> Robie
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20150615/0088dca5/attachment.html>


More information about the pkg-mysql-maint mailing list