[00:33] <infinity> herton: So, is there a reason the bot hasn't decided that 1090123 is fit for release?
[00:33] <infinity> henrix_: ^
[00:36]  * infinity suspects it may relate to verification tasks, and gives up and just releases it.
[01:32] <herton> infinity, sorry, it's a bug I introduced in the bot today, fixed
=== chiluk is now known as chiluk_away
=== henrix_ is now known as henrix
[10:19]  * apw yawns widly
[12:42] <bambee> Hi, nvidia-current does not build with linux-image 3.5.21-generic on precise  (there is a 3.5 kernel packaged on precise)
[12:55] <xnox> replied to above ^ in #ubuntu-devel.
[12:55] <xnox> bambee: don't cross-post same message to multiple channels.
[12:57] <bambee> xnox: I just realized that this message was for the kernel team and not for the whole #ubuntu-devel channel
[13:01] <xnox> bambee: meh. it's an issue between #ubuntu-x package and #ubuntu-kernel package, therefore #ubuntu-devel is the common ground =))))
[13:05] <bambee> okay, noted
[13:32]  * henrix -> lunch
=== yofel_ is now known as yofel
=== chiluk_away is now known as chiluk
=== chiluk is now known as chiluk_away
=== chiluk_away is now known as chiluk
[14:34] <apw>  break-fix: 639b321b4d8f4e412bfbb2a4a19bfebc1e68ace4 local-2012-2372
[15:08] <apw> henrix, for the CVE where we only have a 'local' fix, i think using the title makes most sense as it will correctly catch the later application of the real fix
[15:09] <henrix> apw: ok, cool. but for 2012-5532 i guess it makes sense to use the sha1s, right?
[15:09] <henrix> apw: i'm about to commit the linux-overlay file
[15:12] <henrix> apw: ok, pushed the changes for linux-overlay
[15:13]  * henrix -> errand. back in 15mins
[15:14] <apw> henrix, yeah i think so
[15:35] <henrix> apw: about the btrfs hash collision: looks like the guy that found the issue agrees with you
[15:35] <henrix> apw: "Finally, the first described attack, i.e., make impossible the creation of a given file within a shared directory, keeps still valid."
[15:35] <apw> yeah
[15:56] <apw> henrix, ok that seems to have worked finally
[15:56] <henrix> apw: ah, cool! thanks for you help figuring this out
=== amitk is now known as amitk-afk
[16:50] <infinity> hggdh: Did you have plans to polish off regression-testing on 1087212 before the holidays, so the kernel SRU workflow can start with a clean slate in January? :)
[16:51] <infinity> hggdh: (That's the only outstanding SRU left, though no pressure if you can't get to it, or you're already on a beach somewhere ignoring me)
[17:12] <hggdh> infinity: looking it up
[17:13] <hggdh> infinity: given it is already in -proposed, I am running it now
[17:15] <hggdh> infinity: we usually do not look at the regression-testing bugs until they reach confirmed for us. So, as a rule of thumb, if you need one done before confirmed status, please ping me
[17:19]  * hggdh wishes there were beached in the Dallas area
[17:19] <hggdh> beaches
[17:19] <hggdh> well, there are lakes, and there is the mud/dirt/whatever at the water front. But that is not really a beach
[17:25] <infinity> hggdh: Ahh, yeah, true that it wasn't marked confirmed because it's still in the verification stage, but I figured a bit of parallelisation here wouldn't hurt. :)
[17:26] <hggdh> infinity: no problems for me :-)
=== chiluk is now known as chiluk_away
[18:19]  * apw looks outside, time to get out of this room
=== henrix is now known as henrix_
[19:03] <slangasek> anyone around who could talk to me about bug #1040557?
[19:03] <ubot2`> Launchpad bug 1040557 in Ubuntu CD Images "UEFI boot live-usb bricks SAMSUNG 530U3C,np700z5c laptop" [Critical,Confirmed] https://launchpad.net/bugs/1040557
[19:04] <slangasek> In talking with Samsung, it seems likely that the samsung-laptop module is triggering this; would it be possible to disable the samsung-laptop module only on systems booted with EFI?
=== chiluk_away is now known as chiluk
[19:29] <jsalisbury> apw, cking If you have a chance, can you review comment #69 in bug 1040557 ?
[19:29] <ubot2`> Launchpad bug 1040557 in Ubuntu CD Images "UEFI boot live-usb bricks SAMSUNG 530U3C,np700z5c laptop" [Critical,Confirmed] https://launchpad.net/bugs/1040557
[19:46] <bullgard4_>  /sys/devices/'LINKSYSTM:00/ exists. '~$ rgrep 'LINKSYSTM' /usr/src/linux-source-2.6.32/Documentation/ 2>/dev/null' does not produce any output. How is 'LINKSYSTM' defined?
[19:48] <bullgard4_> s/LINKSYSTM/LNXSYSTM/
[20:47] <hggdh> infinity: done, I guess now it is just waiting for Ike to finish
[20:49] <infinity> hggdh: Thanks. :)
[23:29] <achiang> jsalisbury: ping, still around?
[23:29] <jsalisbury> achiang, yes
[23:30] <achiang> jsalisbury: hey, could you take a look at https://bugs.launchpad.net/ubuntu/+source/linux-nexus7/+bug/1088424 ? sounds like something you could poke at... or maybe actually it should be ogasawara 
[23:30] <ubot2`> Launchpad bug 1088424 in linux-nexus7 (Ubuntu) "alsa midi sequencer not available on nexus 7" [Wishlist,Incomplete]
[23:30] <jsalisbury> achiang, sure I'll take a look.  ogasawara is out until the new year
[23:31] <achiang> jsalisbury: ah, ok. the real question is, did the audit of ensure the n7 Kconfig matches up with ubuntu's Kconfig ever happen. and if not, how can we make it happen? :)
[23:32] <jsalisbury> achiang, that I don't know off hand.  Maybe apw can answer that.  I believe he is in tomorrow.
[23:32] <achiang> or vanhoof ^^
[23:35] <jsalisbury> achiang, I'll keep on top of it and ping folks tomorrow when they get in
[23:36] <achiang> jsalisbury: works for me, thanks!
[23:36] <jsalisbury> achiang, np