[05:00] <GiGaHuRtZ> Anyone awake? I asked a kernel question in #ubuntu+1 cause sometimes people are knowledgeable there with this stuff
[05:01] <GiGaHuRtZ> Anyway, I like to test upcoming kernels.  And since the ppa mainline mirror, is no longer a ppa and doesnt work like a apt mirror. I wrote a simple script to use as a cron job
[05:01] <GiGaHuRtZ> And it grabs the 2 heads and the linux image of the daily build, and installs them via dpkg
[05:02] <GiGaHuRtZ> My question is, I know there is a 3.11rc3>rc4>rc5 (as of midnight EST) dir
[05:02] <GiGaHuRtZ> But I have been grabbing from the daily dir http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[05:03] <GiGaHuRtZ> And the dailies are like 3.11-99999999 or whatever, and I know 9999999 usually denotes daily
[05:03] <GiGaHuRtZ> My question is, inbetween rcX releases, those dailies include newer code not yet put into the rcX branch, right?
[05:04] <GiGaHuRtZ> So if I want newest, my current script grabbing from the daily dir, would be the best bet?
[05:04] <GiGaHuRtZ> razther than http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc5-saucy/ or whatever newest rc there is
=== smb` is now known as smb
[08:02] <tjaalton> what's holding back 3.11 from saucy?
[08:05] <smb> tjaalton, Appears to be something about "out of date" with the di modules... Wished I could understand Britney better...
[08:06] <tjaalton> oh, needs d-i rebuild?
[08:06] <tjaalton> makes sense
[08:06] <smb> Though I thought that now should happen automatic... So probably something holding that
[08:07] <tjaalton> ah, ok
[08:08] <smb> Guess we have to wait till infinity wakes up or rtg
[09:25] <mwhudson> is there someone i can bribe to have http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c5f927a6f62196226915f12194c9d0df4e2210d7 turn up in a kernel for raring?
[09:25] <mwhudson> (it's a fix for perf on arm32)
=== fmasi_afk is now known as fmasi
=== medberry is now known as med_
=== apachelogger is now known as yovel_
=== yovel_ is now known as apachelogger
=== fmasi is now known as fmasi_afk
[15:29] <rtg> jjohansen, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202161/comments/8
[15:29] <ubot2`> Launchpad bug 1202161 in linux (Ubuntu) "seccomp filter: execve(): Operation not permitted" [Medium,Incomplete]
[15:51] <jjohansen> rtg: yep thanks
[15:55] <rtg> let the carnage begin: [ubuntu/saucy] linux 3.11.0-1.4 (Accepted)
[17:36]  * rtg -> lunch
[19:48]  * rtg -> EOD
[20:07] <bjf> stgraber, can you verify bug 1204194 ?
[20:07] <ubot2`> Launchpad bug 1204194 in linux (Ubuntu Raring) "Please add iwldvm to nic-*-modules" [Medium,Fix committed] https://launchpad.net/bugs/1204194
[21:02] <nessita> jsalisbury, hey there! saw your comment in the bug 1201528. Question (perhaps silly): what's the point on testing a kernel from mainline released on 30-Jun-2013 when I already tested a kernel from mainline from 04-Aug-2013 (v3.10.5-saucy)?
[21:02] <ubot2`> Launchpad bug 1201528 in linux (Ubuntu Saucy) "[Realtek ALC889] - Audio Playback Unavailable" [Medium,Incomplete] https://launchpad.net/bugs/1201528
[21:03] <nessita> is worth noting that v3.10.5-saucy did not break audio
[21:27] <stgraber> bjf: I filed that bug by proxy for a machine we had around during a sprint in bluefin, but if you're happy with me grabbing the udev and confirming that iwldvm.ko is in there and marking it verification-done, sure I can do that ;)
[21:27] <bjf> stgraber, that works for me. we just like the bug 'owner' to be the one to verify (in general). 
[21:30] <stgraber> bjf: done
[21:30] <bjf> stgraber, thanks!