On Fri, Apr 01, 2016 at 12:36:37PM -0000, Martin Pitt wrote:
> It looks like dbconfig-common needs to be adjusted for MySQL 5.7. It
> fails on "mysql: [ERROR] mysql: Empty value for 'port' specified."
Yeah. We're planning on patching MySQL to turn that into a warning
instead of an error. Upstream may be willing to do that for future 5.7
releases for us as well. Since the alternative is to adjust
dbconfig-common, and I'm told that is pretty invasive.
I'm not sure what this means in terms of blocking other things. I think
it'd be acceptable to allow other packages through proposed despite a
MySQL dep8 test failure. We'll hold MySQL until its own dep8 failures
are fixed.
On Fri, Apr 01, 2016 at 12:36:37PM -0000, Martin Pitt wrote:
> It looks like dbconfig-common needs to be adjusted for MySQL 5.7. It
> fails on "mysql: [ERROR] mysql: Empty value for 'port' specified."
Yeah. We're planning on patching MySQL to turn that into a warning
instead of an error. Upstream may be willing to do that for future 5.7
releases for us as well. Since the alternative is to adjust
dbconfig-common, and I'm told that is pretty invasive.
I'm not sure what this means in terms of blocking other things. I think
it'd be acceptable to allow other packages through proposed despite a
MySQL dep8 test failure. We'll hold MySQL until its own dep8 failures
are fixed.