Thanks for the diff in comment #2, but that's not a valid approach for
updating the package in trusty.
Someone needs to actually update the package in trusty using the mysql
5.6.24 tarball from the vivid package.
** Changed in: mysql-5.6 (Ubuntu Trusty)
Status: Fix Committed = Confirmed
wily already has 5.6.24, closing the wily task.
** Also affects: mysql-5.6 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: mysql-5.6 (Ubuntu)
Status: Fix Committed = Fix Released
** Also affects: mysql-5.6 (Ubuntu Utopic)
Importance: Undecided
Status:
Here is a diff between source packages, one is Ubuntu Universe 5.6.19
source package and the other is mysql.com apt 5.6.24 ubuntu 14.04 source
package. How's that?
** Patch added: Diff between 5.6.19 (ubuntu) and 5.6.24 (mysql)
great :)
** Changed in: mysql-5.6 (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1445906
Title:
5.6.24 security update
To
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0498
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0499
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0500
** CVE added: http://www.cve.mitre.org/cgi-
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
