[03:19] <infinity> zequence: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1187230
[03:19] <ubot2> Ubuntu bug 1187230 in Kernel SRU Workflow "linux-lowlatency: <version to be filled> -proposed tracker" [Medium,In progress]
[03:19] <infinity> ikepanhc: https://bugs.launchpad.net/ubuntu/+source/linux-armadaxp/+bug/1187229
[03:20] <ubot2> Ubuntu bug 1187229 in Kernel SRU Workflow "linux-armadaxp: <version to be filled> -proposed tracker" [Medium,In progress]
[03:20] <ikepanhc> infinity: for precise? you will have it today
[03:20] <infinity> ikepanhc: \o/
[07:36] <Guest85775> Dear All,
[07:37] <Guest85775> I have a question about adding a new wireless command to 
[07:37] <Guest85775> kernel 
[07:37] <Guest85775> specifically one of depreciated commands
[07:38] <Guest85775> What is the safest way to do this?
[07:39] <apw> i don't think we know what you mean by a 'deprecated wireless command'
[07:39] <Guest85775> sorry
[07:40] <Guest85775> I mean iwspy
[07:42] <Guest85775> I can not get any outputs other than errors
[07:44] <Guest85775> the errors: http://pastebin.com/krdNpPqJ
[07:54] <apw> Guest85775, when did it last work
[07:55] <Guest85775> This morning 
[07:56] <Guest85775> oo sorry 
[07:56] <Guest85775> it does not work yet
[07:56] <Guest85775> and I realized that is has been removed from the kernel
[07:57] <apw> well it is not removed from raring's kernel, which kernel did it last work for you
[07:58] <Guest85775> http://tinyurl.com/kernel-remove
[07:59] <Guest85775> see above link
[07:59] <Guest85775> uname -a out put is 3.8.0-19-generic
[08:00] <apw> oh then that is even dumber as they removed the 'connection' to ispy but the rest of the code is there
[08:00] <apw> so ... that implies the numbers wern't valid anyhow, so i don't suppose connecting
[08:00] <apw> it back up is going to help any, what number are you trying to find with ispy
[08:01] <Guest85775> I have several nodes in adhoc mode 
[08:01] <Guest85775> I got their mac addresses with ifconfig -a 
[08:02] <Guest85775> when I type iwspy eth1 + 0c:1c:6c:0c:3c:86
[08:02] <Guest85775> with one of MAC add.s or IP adress 
[08:02] <Guest85775> it generates errors
[08:02] <apw> what did it do before
[08:03] <Guest85775> nothing same errors 
[08:03] <apw> when it worked, in older releases, what did give you
[08:03] <apw> what infoirmation are you running it for
[08:03] <Guest85775> ok. 
[08:03] <Guest85775> I find a forum post to see its output 
[08:03] <apw> as the upstream wireless people are saying it was producing rubbish
[08:04] <Guest85775> https://forum.openwrt.org/viewtopic.php?id=12889&p=2
[08:04] <Guest85775> There is a out put for this command and I am trying to get similar outputs
[08:06] <Guest85775> to be more specific I need signal levels of each nodes in the ad hoc network
[08:07] <apw> hmm, well iwspy on mac80211 devices has been gone so long you have near no hope of restoring that, we don't support a kernel old enough to even have it still
[08:08] <apw> it was removed in 2008
[08:08] <Guest85775> OK. So is there any way to get similar output by any bash commands ?
[08:09] <apw> that i know of, sorry i have no idea, i have never setup an adhoc network
[08:10] <apw> though do they not appear in iwlist <interface> scanning
[08:10] <Guest85775> no
[08:10] <apw> as you can see ad hoc networks in network manager
[08:10] <Guest85775> I have found 
[08:10] <Guest85775> sudo iw dev eth1 scan
[08:11] <Guest85775> command yet it behaves strange 
[08:11] <Guest85775> since it collects completely diffent mac addresses, I mean other than our machines
[08:14] <apw> presumably it is seeing everything in your area
[08:14] <Guest85775> anyway, based on my first question, is there a way to integrate iwpsy command to my current kernel?
[08:15] <Guest85775> if yes how?
[08:15] <apw> that functionality was declared dead and unsupported for the majority of cards back in 2008, i think that is a dead end
[08:16] <apw> and they did that saying in 2008 that it wasn't working for a long time
[08:16] <Guest85775> ouch, it really hurts
[08:19] <Guest85775> apw, thanks for your answers.
[08:19] <apw> np
[09:00] <infinity> ppisati: You have two new rebases awaiting your attention, BTW.
[09:00] <infinity> ppisati: #1186475 and #1187228
[09:01] <infinity> smb: And #1186479 for you, if you missed it. :)
[09:02] <smb> infinity, maybe you noticed the additional version number :)
[09:03] <infinity> smb: Oh, hah, that was only 40m ago, the workflow report hadn't picked up the title change yet.  Ignore me.
[09:04] <smb> infinity, Oh well it was only a tad ago... Btw, the saucy xen update to 4.2.2 would not need tech-board involvement, yet... lalala
[09:07]  * smb looks sadly at the smoke cloud which is now in the place infinity was just seconds ago...
[09:10] <infinity> smb: I got distracted by a lively conversation on #debian-devel
[09:10] <infinity> smb: Remind me about Xen at your EOD (which should be vaguely when I'm getting up)
[09:10] <infinity> smb: s/Remind/Pester/
[09:11] <smb> infinity, Its just what usually happens when you mention reviewing Xen packages to anybody. Just was abusing you a bit.
[09:12] <smb> infinity, Will try to remember... sometimes hard after sitting through irc meetings :--P
[09:13] <infinity> smb: I found the best way to deal with that was to transfer to a team that doesn't have IRC meetings.
[09:13] <ppisati> infinity: i did a rebase last week, but i was never 'imported'
[09:13] <smb> There is such a thing?
[09:14] <infinity> ppisati: Yeah, we skipped your update from last week, as we guaged the impact on omap4 to be not worth the process.  This week's is new. :)
[09:14] <smb> Guess I need to think about begging to move to release...
[09:15] <smb> Actually our own team meeting is just noticeable by the irc window getting hot (if open) from the friction
[09:15] <infinity> You rub your IRC window?
[09:15] <infinity> Kinky.
[09:16] <smb> infinity, More the text rushing by rubs against it. ;)
[09:16] <infinity> Also kinky.  I think?
[09:16] <infinity> If you're into that sort of thing.
[09:17] <infinity> Anyhow.  I should wander off and try to nap.
[09:17] <smb> I would not be completely sure either... Have a good nap!
[10:05]  * apw giggles at infinity
[12:01] <apw> [DEFAULT]
[12:01] <apw> default_host_main = UNKNOWN
[12:01] <apw> smb, ^^ i have that at the top of my .dput.rc
[12:54] <infinity> cking: Can you verify your SRU for bug #1180394 ?
[12:54] <ubot2> Launchpad bug 1180394 in linux-nexus4 (Ubuntu Raring) "ubuntu-nexus4, lttng-modules-dkms won't build with current kernel" [Undecided,Fix committed] https://launchpad.net/bugs/1180394
[12:56] <cking> infinity, sure will do
[12:56] <infinity> cking: Shiny, thanks.
[14:39] <cking> infinity, after some wrestling with the N4, it's verified 
[14:39] <infinity> cking: Danke.
[15:40] <jsalisbury> **
[15:40] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:40] <jsalisbury> **
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Meeting starting now
[17:00] <jsalisbury> ##
[17:16] <bjf> Number of commits applied since release -  lucid : 3362; precise : 3173; quantal : 2014; raring : 317
[17:19] <smb> bjf, I think I see kamal work to "improve" the r-numbers... :)
[17:19] <bjf> indeed
[19:35]  * apw manages to get -rc4 to boot ... yay
[20:49] <zequence> infinity: precise is uploaded to PPA and seems to be building fine
[20:50] <zequence> I'm still using this same machine for building, but will set up another soon