Back port fix for Mysql defect #34236?

Asked by Mark Goris

We are currently running Lucid, with Mysql 5.1.41-3ubuntu12.9. We are seeing mysqld segfaults due to defect http://bugs.mysql.com/bug.php?id=34236, which was fixed in Mysql 5.1.49. I was hoping that you would consider back porting that fix to 5.1.41, because we would rather stay on the LTS release rather than have to move to Maverick in order to address this issue.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu mysql-dfsg-5.1 Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Eliah Kagan (degeneracypressure) said :
#1

To get the Ubuntu developers to listen to your request that this fix be backported, you should report it as a bug in the mysql-dfsg-5.1 package in Ubuntu. (Before filing your bug, you should first search through existing bug reports to see if this has already been reported.)

To report this as a bug, first read https://help.ubuntu.com/community/ReportingBugs carefully. After you have filed your bug, you can link it and this question to each other by using the "Link existing bug" link at the top of this question. It is a good idea to do that, but your bug should nonetheless be self contained--the Ubuntu developers should not need to refer to this question in order to understand and appreciate your bug report. (Make sure your bug report contains at least all the information you have provided here thus far.)

Revision history for this message
mycae (mycae) said :
#2

You can request a backport here:
https://launchpad.net/lucid-backports/+filebug

A backport could take a while to be completed, and to propagate. If you need a faster solution, you can just apply the patch to generate your own package, and install that instead.

patch:
http://lists.mysql.com/commits/110270

using this procedure:
http://www.moosechips.com/2008/09/ubuntu-rebuild-a-source-package/

You would need to put the patch into the debain/patches/ folder, then add a line to debian/patches/list with the name of the patch. The number at the beginning of the patch specifies the order in which it is applied.

You would have to pin your patched mysql version of the package, or disable auto-updates.
https://help.ubuntu.com/community/PinningHowto

Can you help with this problem?

Provide an answer of your own, or ask Mark Goris for more information if necessary.

To post a message you must log in.