[01:29] <achiang> what is the process for requesting a backport into currently shipping kernel? say i have a patch i'd like to see in karmic...
[01:30] <achiang> hm, and i guess i'd want to see it backported to lucid too, since /subject says it's based on .32
[01:30] <achiang> http://bugzilla.kernel.org/show_bug.cgi?id=15064
[01:30] <ubot3> bugzilla.kernel.org bug 15064 in Config-Processors "no deep C-states on core-i7, thus no turbo" [Normal,Resolved: code_fix] 
[01:32] <achiang> without that patch, lots of folks are experiencing issues on the new batch of Intel Core i7 laptops
[01:32] <crimsun> achiang: is it in a .32.x point release?
[01:35] <achiang> crimsun: hm, no. we did not mark it for -stable
[01:35] <achiang> crimsun: i mean, linus hasn't even pulled it yet, but even after he does, we didn't tag it with -stable, so it won't get picked back up by gregkh
[01:36] <crimsun> I suppose the most straightforward way is to file a bug affecting linux and get it into a point release
[01:37] <achiang> crimsun: you mean a launchpad bug?
[01:37] <crimsun> yes, https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
[01:39] <achiang> crimsun: reading the KernelTeam homepage to try and find the policy; do ubuntu only backport patches in the -stable trees?
[01:41] <crimsun> achiang: I'm unfamiliar with the precise SRU policy/policies for each Ubuntu release; smb/rtg/apw would be best to ping on that.
[01:46] <dhillon-v10> ogasawara: ping regarding glibc changed in the lucid kernel
[01:49] <JFo> dhillon-v10, can you elaborate for the channel at large? perhaps someone here can help you.
[01:51] <JFo> and I am also not sure what you mean about glibc changing in the kernel... it isn't in the kernel
[01:57] <dhillon-v10> JFo: hi there, sorry for the delay, a friend of fine and a lot of other people are experiencing this problem: when they use kvm with lucid images it breaks kvm, that's because of a commit made upstream to glibc which changed all calls that previously pointed to about() to free() now
[01:57] <dhillon-v10> JFo: and free() returns an aborting signal breaking kvm
[01:58] <dhillon-v10> JFo: I have a fix for it, but its a dirty hack, it involves adding a line to /etc/profile
[02:11] <cooloney> dhillon-v10: that looks like an glibc issue
[02:12] <dhillon-v10> cooloney: yup :) I read a conversation on LKML where they made this change to glibc so I was wondering how do I go about fixing it
[02:25] <cooloney> dhillon-v10: is there any bug tracker on launchpad for this issue, maybe we can help that. 
[02:25] <cooloney> dhillon-v10: i guess ogasawara is going to sleep now.
[02:27] <dhillon-v10> cooloney: ahh right, sorry ogasawara, I will get you the link in a sec.
[17:51] <less1> Hi, I am sure if this is right place to ask this question.  I am working on ubuntu booting over http.  I have working prototype up at http://www.etherboot.org/share/pravin/UbuntuNet/  Can someone guide where can I get more feedback about this?
[18:13] <JFo> less1, you are looking for #ubuntu
[18:14] <JFo> someone in there should be able to help or at least point you in the right direction. :)
[18:14] <less1> JFo: thanks.. I will check it out.
[18:15] <JFo> certainly
[23:30] <crimsun> bjf: hi, some questions about the git packaging of cod alsa: firstly, is there supposed to be a metapackage in debian/control.d/flavour-control.stub? linux-alsa-driver-modules-PKGVER-ABINUM-FLAVOUR doesn't do anything useful, so I guess it's supposed to be renamed and a proper Depends added?
[23:31] <crimsun> bjf: I can push those changes for alsa-driver-cod-{karmic,lucid}.git to my tree on zinc
[23:40] <bjf> crimsun, I tried to just take the LBM packaging and reuse it, but I may have messed it up, I'm pretty green w.r.t. packaging
[23:40] <bjf> crimsun, I'd welcome any changes you have