[05:31] <infinity> BenC: D'oh.
[05:31] <BenC> infinity: ?
[05:31] <infinity> BenC: Your linux-ppc ended up being based on a kernel we're dumping from -proposed.
[05:31] <BenC> infinity: Errg…I took the latest Ubuntu tag
[05:31] <infinity> BenC: There are new ones in the PPA right now, but you may as well just wait a day and rebase tomorrow when we do another SRU round.
[05:31] <BenC> Ok
[05:32] <infinity> BenC: (Today's is an emergency security update, but that will be rolled into what you just rebased on tomorrow for the bigger SRU cycle)
[05:32] <BenC> infinity: So are the PPA kernels tagged in ubuntu-master git?
[05:32] <infinity> I'd assume so.
[05:32] <infinity> 21.32
[05:32] <BenC> Ok
[05:33] <infinity> Or, maybe 21.32 is a mess right now.
[05:33] <infinity> I'd just wait for 22.33 tomorrow, unless you're desperately keen on turning around this security fix tonight.
[05:35] <infinity> BenC: The upshot is that you'll get a tracking bug this time, unless bjf messed that up. ;)
[05:35] <infinity> Oh, which he did:
[05:36] <infinity> It was not possible to create or handle the tracking bugs for the following packages (their tracking bugs based on this update must be handled manually):
[05:36] <infinity> linux-ppc
[05:36] <infinity> bjf: ^--- shankbot fails at linux-ppc tracking bugs.
[05:36] <BenC> Bummer
[05:38] <infinity> BenC: I'll make sure that gets fixed. :P
[05:39] <infinity> BenC: Anyhow, you can either attempt to rebase on the 21.32 floating tag and get in on this emergency SRU bandwagon, or just wait a couple of days and get back into rhythm with 22.33.  Up to you.  The latter's probably less effort, if you're not desperately concerned.
[05:41] <BenC> infinity: Not desperately concerned...
[05:42] <infinity> BenC: Alright, I'll just poke you in a day or two when we get all our ducks in some sort of row, then.
[05:43] <BenC> infinity: Works for me, thanks
[07:46] <lag> apw: ogasawara: Damn lag!
[09:04] <cking> smb, perhaps c902ce1bfb40d8b049bd2319b388b4b68b04bc27 addresses that  bug
[09:06] <smb> cking, Hm, yeah. Sounds suspiciously familiar...
[09:06] <Laney> is bug #1157880 on somebody's radar?
[09:06] <ubot2> Launchpad bug 1157880 in bcmwl (Ubuntu) "bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build on kernel 3.9 [wl_cfg80211.c:2025:3: error: too few arguments to function ‘cfg80211_put_bss’]" [Undecided,Confirmed] https://launchpad.net/bugs/1157880
[09:08] <infinity> Laney: tseliot, perhaps?
[09:08] <infinity> HAH
[09:08] <infinity> TIMING
[09:08] <Laney> EXCELLENT
[09:08] <Laney> I did try to tab complete him at the time
[09:09]  * Laney gives a bug #1157880 shaped cookie to tseliot
[09:09] <ubot2> Launchpad bug 1157880 in bcmwl (Ubuntu) "bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build on kernel 3.9 [wl_cfg80211.c:2025:3: error: too few arguments to function ‘cfg80211_put_bss’]" [Undecided,Confirmed] https://launchpad.net/bugs/1157880
[09:09] <tseliot> :)
[09:10] <tseliot> Laney: right, it was on my todo list. I already have a patch for that
[09:10] <infinity> tseliot: Dude, you joined the channel literally two or three seconds after I invoked your name.  It was creepy.
[09:10] <tseliot> infinity: hehe :)
[09:10] <Laney> he said it five times while facing a mirror
[09:11] <tseliot> it usually works that way ;)
[09:17] <tseliot> apw: have you ever tried bcmwl 6.30.223.30?
[09:19] <apw> hmm probabally not, brcmsmac has been pretty good for me
[09:20] <apw> tseliot, tseliot oh it isn't in the archive, where is it
[09:21] <tseliot> apw: here (it works with kernels up to 3.8 for now) https://launchpad.net/~albertomilone/+archive/broadcom
[09:27] <tseliot> apw: or you can get one that should work with 3.9 here: https://launchpad.net/~eugenesan/+archive/ppa
[13:40] <rtg_> cking, can you create a bug for your raring nexus4 patch 'Enable lttng-modules-dkms to build' ?
[13:40] <cking> rtg_, yup, doh, I forgot to do that
[13:40] <rtg_> cking, it is for raring, right ?
[13:41] <rtg_> the repo organization is a little chaotic wrt nexus4/make and nexus7/grouper
[13:41] <rtg_> nexus4/mako*
[13:42] <cking> rtg_, urm, well it's for the nexus4 mako, currently raring, but won't we be moving to saucy with the same kernel?
[13:45] <rtg_> cking, we will, but I'm going to add lttng as part of the kernel under the ubuntu directory. see ubuntu-manta for example.
[13:46] <cking> rtg_, that's going to be fun - more bloat - and will lttng work OK if it's built-in? 
[13:47] <rtg_> cking, its modular, so the bloat issue is less of a problem. I'm assuming it'll work if the dkms package does.
[13:48] <rtg_> cking, Q/A would like to use lttng as a standard logging method. I've added it to the saucy distro kernel.
[13:49] <cking> rtg_, yup, I'm having issues with in on the nexus4 - the output seems to not work with babeltrace and I'm trying to profile it on these devices to see how expensive it is
[13:50] <rtg_> cking, is the dkms package from tip on the lttng repo ?
[13:50] <cking> rtg_, i've tried the default package + the tip of the lttng repo
[13:51] <cking> btw, bug is 1180394
[13:51] <rtg_> cking, see if you can see that same issues with the saucy distro kernel.
[13:51] <cking> rtg_, so, saucy + x86 it works fine
[13:51] <rtg_> cking, shit
[13:53] <cking> and 3.4 + x86 it works fine, but not  3.4 nexus4 
[13:53]  * cking tested x86 + saucy a couple of days ago, not sure about latest saucy kernels
[13:54] <rtg_> cking, no change wrt lttng
[13:54] <rtg_> only stable updates
[13:56] <cking> rtg_, ok, if you are going to integrate lttng into the n4 kernel I will give it is spin to see if that fixes the babeltrace issue
[13:57] <rtg_> cking, I think I'll leaving raring as is, but will build it in for saucy and newer. the touch dudes are going to stop raring development as soon as they flip the container model.
[13:57] <cking> rtg_, ok - any idea when that saucy kernel will be available?
[13:58] <rtg_> cking, I'm working on it today.
[13:58] <cking> ok, cool, let me know when it's ready and I will get crackin' on it - I'm keen to benchmark it to see how much overhead it adds on these small ARM devices
[13:59] <rtg_> cking, and whether it works at all :)
[13:59] <cking> rtg, that would be a bonus ;-)
[14:01] <rtg_> cking, I assume your second patch is an ABI bumper ?
[14:02] <cking> rtg_, bother, yes, i overlooked that
[14:02] <rtg_> cking, s'alright
[14:04]  * cking wonders if this bug fix is kinda academic if the saucy kernel does the trick and that's what we will be using
[14:04] <rtg_> cking, its hard to know. I've only done it for manta thus far, and have yet to try to boot it on the N10.
[14:06]  * cking tempted to forget it for now unless anyone screams for it on the raring N4 kernel
[14:07] <rtg_> cking, I'll get back to you when the N4 saucy kernel is ready
[14:07] <cking> ack
[15:48] <apw> cking, that second patch, isn't that just checking a CONFIG_* variable and therefore could we not just change the config? (for the N4 lttng)
[15:49] <cking> apw, true, but it means the N4 kernel deviates from our standard Ubuntu kernels for no reason
[15:49] <apw> hmmm
[15:50] <cking> i just wanted to re-align it because one of the earlier patches adds in features to the makefile that is not what we normally have
[16:49] <henrix> rtg_: are you rebooting gomeisa/tangerine? my session just broke and can't reconnect
[16:49] <rtg_> henrix, nope
[16:49] <henrix> hmmm
[16:49] <rtg_> I seem to have lost my connection as well
[16:55]  * rtg_ -> lunch
[16:57] <zequence> Did you change the workflow for how kernel sources are updated or something?
[16:58] <zequence> master is not containing the commits for the latest versions
[16:59] <zequence> Seems those are in master-next instead
[16:59] <zequence> hmm, wait
[16:59] <zequence> The tags are there, but where are the commits (am I just being stupid?)
[17:00] <henrix> sconklin__: you're probably still fixing the branches? ^^^
[17:01] <sconklin__> zequence: I'm going to fix the branches today, but the CVE release from last night will never appear in the linear history for the kernels, it will only be a tag
[17:03] <sconklin__> zequence: because we made the security fix on the last released kernel and not the one we had in -proposed, it's impossible to represent everything in th elinear history, including both the security release and the -proposed kernel
[17:05] <zequence> sconklin__: Ok, but once you've fixed the branches, I can just pull to get the latest version, right? I'll do that tomorrow in that case (update the -lowlatency kernels)
[17:05] <sconklin__> zequence: yes, and that will include the security fix
[17:05] <zequence> ok, thanks
[20:02]  * rtg_ -> EOD
[20:40] <infinity> psivaa: *poke*
[21:08] <FroMaster> I was provided a VMware VM that has Ubuntu 12.04.1 LTS as its base and kernel 3.2.0-30-generic. VMware only provided VMware-Tools for 3.2.0-23/3.2.0-29 not the one I have. The VM is an appliance and thus has unnecessary components removed. Trying to get the Kernel-headers & build-essentials is not possible. I'm trying to find the difference between 3.2.0-30-generic & 3.2.0-29-generic to 
[21:08] <FroMaster> see if I can upgrade the kernel and apply the vmware-tools packages via apt-get. 
[22:02] <rsalveti> apw: pushed flash-kernel support for mako, so we can enable that at the kernel package already
[22:39] <tyrog> Hi fellaz. Is there a fix for HDMI audio not working coming for Ubuntu 13.04? thanks
[22:51] <infinity> tyrog: We've had a couple of emergency security fixes get in the way of pushing that out, but the fix will be in the next SRU kernel (landing in -proposed todayish, and in -updates in a week or two).
[22:52] <infinity> tyrog: Assuming your bug is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169984
[22:52] <ubot2> Launchpad bug 1169984 in linux (Ubuntu Raring) "3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV" [High,Fix committed]
[22:59] <tyrog> infinity: so right now with -20 the fix is not included yet?
[23:01] <infinity> tyrog: It's in -20-, and backed out in -21-, and will reappear in -22-
[23:01] <infinity> tyrog: The vagaries of emergency security updates trumping long QA cycles for other bugs. :/
[23:01] <tyrog> infinity: But I tested -20 and I still dont have my hdmi audio in the sound menu
[23:02] <tyrog> and why is it being taken out from -21?
[23:02] <infinity> tyrog: Then you might, potentially, have a different bug.  Do feel free to file one ('ubuntu-bug linux') and include as much info as you can, including what you've tested.
[23:03] <infinity> tyrog: -21 is -19 with exactly one small patch on top, urgent security release.  -20 was never released (as in, didn't pass QA and other such things yet), so we couldn't base -21 on -20.
[23:04] <tyrog> infinity: From what I've seen, it will go directly from 19 to 21 for people without proposed right?
[23:05] <infinity> tyrog: Right.
[23:05] <infinity> tyrog: If you're okay with running -proposed kernels, -22 should land today/tomorrow, and will basically be a merge of -20 and -21.
[23:06] <tyrog> good, thanks :)
[23:08] <ohsix> what's the small patch/bug?