Comment 22 for bug 1366174

2.4.10-8ubuntu1 is now in vivid-proposed and should fix this bug for Vivid and for future releases, but it won't land in Vivid itself until bug 1393832 is fixed. I'd like to focus on this SRU before working on that bug.

Alex, could you please verify that the bug is fixed in vivid-proposed for you? Plain Vivid won't work. I suggest that you update to latest vivid, enable vivid-proposed and upgrade apache2's binary packages only to test, to avoid pulling various unrelated things in.

So next, the SRU for this. This is a pretty extensive thing to SRU, but given the severity of the bug I think we should do it. I've spoken to Chris Arges (SRU team) and we considered options, and settled on using your backport provided that I give it a careful review, so I need to do this next. Chris will still have the final call though after I've uploaded.

I'm not sure I'll manage to get it done today though (still at a sprint) and I'm on vacation next week. If I don't report back today, if another Ubuntu dev with upload rights wants to take on the review next week, please go ahead without any need to coordinate with me.

Alex, thanks for your patience on this. I appreciate the work you've already put into this. One of the things we discussed at this sprint was on onboarding more developers to be able to take this sort of work on, so I hope that it won't take so long to process next time.