Vivid is end of life, marking as won't fix. There is one "lost" update - which was [1]. But that was lost in a follow on security update - see c#26 + c#27 for details.
That makes mysql-5.6 in Trusty "triaged" instead of "Fix Committed" It does not seem a later stable release has intregated that particular fix you had - maybe an alternative. @Dannf - any plan to reroll these - or will this go to Won't Fix? After all that time I'll mark won't fix now, please update if this is still work in progress (or a zombie that should be WIP). [1]: https://launchpad.net/ubuntu/+source/mysql-5.6/5.6.19-0ubuntu0.14.04.2 ** Changed in: mysql-5.6 (Ubuntu Vivid) Status: Fix Committed => Won't Fix ** Changed in: mysql-5.6 (Ubuntu Trusty) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to MySQL. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1427406 Title: data corruption on arm64 and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : [email protected] Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
