[00:07] <jtaylor> hm is the bisect wiki still up to date?
[00:07] <jtaylor> I run into one dead end or wrong path after the next
[00:13] <jtaylor> or I'm just to dumb to read the prerequsite section  ...
[13:04] <tseliot> apw: the only dkms package (that I maintain) that needs an update for lts-trusty is bcmwl. rtg doesn't seem to be online but perhaps you can let him know
[13:05] <apw> tseliot, ack
[13:20] <apw> tseliot, and what about lts-utopic, as that will be in your balywick in the near term
[13:20] <tseliot> apw: sorry, I really meant to say lts-utopic, not lts-trusty
[13:21] <apw> tseliot, even better, thanks
[14:35] <jduck> sorry guys, haven't had time to report the kernel bug. i'm really surprised no one else is seeing it.
[18:00] <tzn> Hi guys
[18:01] <tzn> I’m looking for a way to get source for this kernel linux-image-3.11.0-18-generic_3.11.0-18.32~precise1_amd64.deb package
[18:01] <tzn> any hints?
[18:06] <tzn> Well, I;m particualry interested if this was fixed http://www.cvedetails.com/cve/CVE-2013-6382/
[18:15] <rww> tzn: I believe it is. If you look towards the end of that page, you'll see a bunch of USN links. Open them all, find the one that applies to your system, and check the version number it mentions as being fixed is lower than what you have
[18:16] <rww> if I'm reading right, http://www.ubuntu.com/usn/USN-2113-1/ , which says it was fixed in 3.11.0-17
[18:30] <tzn> Thanks, this is what I learned as well
[18:35] <jtaylor> hm what ubuntu kernel does mainline 3.13.8 correspond too? that may have introduced bug 1381815 from utopic into trusty
[19:50] <apw> jtaylor, 3.13.0-21.43 to 3.13.0-23.45 inclusive were based on 3.13.8