[03:00] <bryceh> apw, you about by chance?
[03:01] <bryceh> apw, ok will email
[09:40] <apw> cking, hey morning ... you got any aarandale h/w with external monitor ports ?
[09:41] <cking> apw, lemme check my inventory
[09:41]  * cking rummages around
[09:42] <cking> apw, no, afraid not
[09:43] <apw> cking, shame, ok ... i wonder who if anyone does these days, i am hearing reports that external monitors are not working on those chipsets
[09:44] <cking> hrm, best ping the guys in lexington
[09:45] <apw> cking, yep, will do, you are just a little better aligned timewise
[09:46] <cking> unfortunately I've sent quite a bit of kit back lately
[09:46] <apw> that or drown in the stuff
[09:46] <apw> i sh
[09:47] <apw> i should have got you to send me a sample of aarrandale, and a sample of ironlake
[10:15]  * apw goes get some breaky
[10:34] <cking> apw, perhaps you should ask lexington to ship you some kit
[10:37] <apw> cking, might be a plan
[10:44] <eagles0513875_> hey apw  :) got ur msg with an updated kernel going to try and confirm sru kernel update fixes the issue which i hope it does. atm dealing with a crashing netowork manager which seems lots of people are having that issue as well
[10:46] <apw> ta
[10:47] <eagles0513875_> ?
[10:47] <apw> ta == thanks
[10:47] <eagles0513875_> ahh  ok guessing ur up in the uk apw 
[10:47] <apw> based in the uk yes
[10:48] <eagles0513875_> nice nice :) 
[10:48] <eagles0513875_> isnt canonical up there as well
[10:58] <apw> eagles0513875_, sort of, canonical is mostly distributed, but there is an office in the uk
[10:59] <eagles0513875_> im wondering if they would support a game distro version of ubuntu
[10:59] <eagles0513875_> honestly doubt it though
[11:00] <apw> not really sure what support would mean, there are a number of vairiants, kubtuntu, ubuntustudio etc who at least get CDs spun etc
[11:01] <eagles0513875_> ya but those people that i have spoken to why not create a meta package
[11:01] <eagles0513875_> the problem wiht meta package is the amount of stuff that is still avialable in the repos 
[11:01] <eagles0513875_> i want to provide repos with specific software geared towards this particular market
[11:02] <apw> why would you want to stop people also installing other things?
[11:02] <eagles0513875_> to help them save time hunting for what they are looking for
[11:05] <amitk> eagles0513875_: while you're welcome to do that and provide your own repos and so forth that mirror only certain packages, why restrict your potential users?
[11:06] <eagles0513875_> amitk: im trying ot target a niche market which has yet to be exploited in the linux world
[11:12] <apw> eagles0513875_, making it easy to find the s/w you want/need is good, restricting me so its hard to use the machine for other things seems wrong
[11:16] <amitk> yeah, I wouldn't use such a software system, but then I suspect we don't fall into eagles0513875_ 's target audience :)
[11:18] <eagles0513875_> humm 
[11:18] <eagles0513875_> amitk: what other software would you install besides games on a game distro 
[11:19] <apw> whatever i wanted to
[11:19] <eagles0513875_> you got me thinking if i do anythign i might rework the repositories
[11:19] <apw> are you trying to make a ps3, else let me use my machine for what i want to 
[11:21] <amitk> eagles0513875_: that is like asking the original WRTG54 router hackers what they could want besides the buggy Linksys firmware :)
[11:22] <eagles0513875_> hehe
[11:26] <apw> amitk, nicly put
[11:27] <eagles0513875_> amitk:  apw  im still in the brain storming stage
[11:28] <apw> i feel erring on the side of openness will win you more adopters
[11:28] <apw> and likely should mean that you cna leverage the existing infrastructure at low effort from yourself
[11:28] <apw> win all round
[11:28] <eagles0513875_> ya i see where your coming from 
[11:28] <apw> behaving like m$ will not win you friends
[11:29] <eagles0513875_> i guess i can create non gaming repos which users can enable if they want to install other software 
[11:29] <eagles0513875_> or just enable all my repos and leave a very basic desktop environment
[11:29] <eagles0513875_> im still in brain storm stage atm 
[11:30] <eagles0513875_> apw: guessing best place ot start would be with the installer and kernel?
[11:32]  * apw is sligntly unsure where you think you are going
[11:32] <apw> why is a dekstop env no good for gaming, works for windows
[11:33] <eagles0513875_> im not saying its not but where should one start putting this together 
[11:33] <eagles0513875_> at the kernel installer level 
[11:34] <eagles0513875_> or desktop environment etc
[11:34] <eagles0513875_> apologies i might not have made that very clear 
[11:34] <apw> i would ask that question on #ubuntu-devel, i suspect you need to put together a seed for the collection you need
[11:34] <apw> which i think is basically a big meta-package which pulls in all the things you definatly want, and the rest comes via dependancies
[11:36] <amitk> eagles0513875_: start with ubuntu-server which is probably the minimum seed at present, uninstall the server bits, add desktop bits you need. That should be the starting point for your own seed
[12:01] <Kano> hi, why is no rfcom in .39 kernel?
[12:04] <Kano> would be good if rc4 has it enabled...
[12:08] <apw> Kano, no idea
[12:09] <Kano> it was in .38
[12:10] <apw> Kano, what driver are you missing
[12:10] <apw> and from what kernel
[12:12] <Kano> .39 mainline, RFCOMM
[12:12] <Kano> for bt connections
[12:13] <Kano> maybe more are missing, but this is definitely not there..
[12:13] <apw> the config for it is turned on, which driver .ko is missng
[12:13] <Kano> well i wanted to modprobe rfcomm, it is not there
[12:13] <Kano> it is not in the final config too
[12:14] <Kano> http://www.gentoo.de/doc/de/bluetooth-guide.xml
[12:14] <Kano> grep -i rfcomm /boot/config-2.6.39-*
[12:14] <Kano> no output
[12:15] <Kano> i could not even connect a bt mouse
[12:16] <Kano> but thats noother module most likely
[12:18] <apw> Kano, bluetooth is known broken in lots of ways in early 39-rc
[12:18] <Kano> because it is not even enabled?
[12:18] <apw> no cause it is broken
[12:19] <Kano> without a module it can not work
[12:19] <apw> not in our builds, in generall
[12:19] <Kano> i use your build
[12:19] <Kano> the mainline ones
[12:19] <apw> and those come with no guarentees even to boot
[12:20] <Kano> they boot, they are good for benchmarking oss drivers, but bt modules are missing
[12:25] <apw> ogasawara, are you building oneric anywhere?
[12:42] <apw> Kano, might be fixed for -rc4, won't know till it builds
[12:43] <Kano> ok
[13:59] <ogasawara> apw: I'm not building oneiric anywhere, I didn't plan to until the archive officially opened.  Anyone wanting to run an oneiric kernel at this point has to be savy enough to build on their own.
[14:04] <tgardner> ogasawara, we could be uploading as a daily build into the natty pocket for now
[14:08] <ogasawara> tgardner: to the kernel-ppa?
[14:08] <tgardner> ogasawara, I suppose. it doesn't make a lot of difference. the archive will be open in a few weeks anyways.
[14:09] <ogasawara> tgardner: I assumed that would then override the tip builds of the current natty tree.  meh, I'm indifferent as I don't think there are a heck of a lot of oneiric consumers anyways.
[14:10] <ogasawara> for the ones that do exist, I've been building them a kernel when asked.  so far I've only had 1 request.
[14:10] <tgardner> ogasawara, I was gonna start trying out on some of my servers, but I can do the builds myself. are you about to rebase for -rc4 ?
[14:10] <ogasawara> tgardner: yep, gonna do the rebase right now
[14:10] <ogasawara> tgardner: I'll ping ya when I've got it pushed
[14:10] <tgardner> ogasawara, thanks
[14:14] <apw> ogasawara, the tip builds are in pre-proposed
[14:14] <apw> the kernel-ppa/ppa only has natty backports to lucid
[14:14] <apw> i think tgardner did natty in there before upload to the archive
[14:15] <ogasawara> apw: ah, that'd make sense then.  I'll upload the -rc4 rebase to there then.
[14:15] <apw> you get to find out that none of the d-i stuff works and fix it before the archive chews on it :)
[14:16] <ogasawara> that'll be fun
[14:18] <tgardner> bjf, sconklin-gone: linux-lts-backport-maverick has been baking in -proposed for 4 weeks. any chance of getting it promoted?
[14:23] <tgardner> apw, https://launchpad.net/ubuntu/+source/gcc-4.5 uploaded 24 hours ago. is this gonna scrog dkms packages?
[14:25] <apw> tgardner, i think it might, let me see if any are complete and then i can test
[14:25] <apw> its about time we knew for sure if dkms cares
[14:26] <tgardner> apw, yeah, I've never been sure just how naive the version test is.
[14:26] <apw>   * For Linaro based builds, do not turn on -fshrink-wrap by default on armel
[14:26] <apw> so that means that new code that shat all over us is now disabled for all architectures
[14:26] <apw> wtf
[14:27] <tgardner> sounds like a failed experiment
[14:27] <apw> tgardner, grrr
[14:28] <tgardner> apw, good thing its close to beer thirty for you lest you pop  a gasket :)
[14:30] <cking> what does -shrink-wrap do - it's some kind of ARM function epilogue optimisation isn't it?
[14:34] <sforshee> can someone accept my nominations on bug 745304 ?
[14:34] <ubot2> Launchpad bug 745304 in linux "Graphics corruption after hibernate with Intel GMA 3150 chipset" [Medium,In progress] https://launchpad.net/bugs/745304
[14:36] <tgardner> sforshee, done
[14:36] <sforshee> tgardner, thanks!
[14:36] <tgardner> what library does one link against for a cc program, e.g., g++ evil-clock-test.cc -lc -o evil-clock-test
[14:37] <apw> tgardner, -lc is the the standard c lib, you also get impliciltly linked against libgcc
[14:39] <tgardner> apw, here we go: g++ evil-clock-test.cc -lc -lpthread -lrt -o evil-clock-test
[15:14] <apw> smb, can you remember what used to go wrong, and thus who complained when the compilers in -security and -updates didn't match and we shoved kernels out ?
[15:15] <apw> i rememeber bugs filed for it in the past
[15:15]  * apw notes that dkms doesn't seem to care in my experience
 smb, can you remember what used to go wrong, and thus who complained when the compilers in -security and -updates didn't match and we shoved kernels out ?
 i rememeber bugs filed for it in the past
[15:15] <tgardner> apw, you were able to load a dkms created module?
[15:16] <apw> tgardner, i believe so yes, just confirming i have the right compiler
[15:16] <ogasawara> tgardner: oneiric -rc4 rebase pushed.  my test builds are finishing up but look good so far.
[15:17] <tgardner> ogasawara, what did you do about the kexec patch ?
[15:17] <ogasawara> tgardner: I dropped it, an official fix was in -rc4
[15:17] <tgardner> ogasawara, good, thats pretty much what I did though I didn't really research it much
[15:18] <eagles0513875> hey apw
[15:18] <bjf> ##
[15:18] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:18] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[15:18] <bjf> ##
[15:20] <apw> eagles0513875, yes
[15:20] <eagles0513875> still havent tested yet waiting on network manager fix :( 
[15:31] <apw> tgardner, did i see you installing vmware recently?  how does that carry its kernel modules (if any)
[15:32] <tgardner> apw, builds 'em on the fly
[15:33] <apw> tgardner, do you have that setup on a natty machine, wonder if we can test if that cares
[15:33] <tgardner> apw, I don't. Its a lucid host. lemme think about what I might test it on.
[15:36] <tgardner> bjf, did you ever get any feedback from the LP dudes on what happened to bug emails ?
[15:37] <bjf> tgardner, i've not raised the issue with them
[15:38]  * ogasawara back in 20
[15:38] <tgardner> bjf, ok, I'm gonna tilt at the windmill.
[15:38] <bjf> where at ?
[15:38] <tgardner> that windmill*
[15:39] <bjf> email or irc ?
[15:39] <jjohansen> apw, tgardner: I have vmware here, I can test on natty
[15:39] <tgardner> I'll get on their irc channel.
[15:40] <tgardner> jjohansen, its the compiler version that apw wants tested. what happens to vmware modules after the compiler has been updated, but the kernel hasn't
[15:40] <bjf> tgardner, they've been pretty responsive on #launchpad
[15:40] <tgardner> bjf, a'int nobody there. do they hang o some other channel?
[15:41] <jjohansen> tgardner: ok
[15:41] <bjf> tgardner, on freenode
[15:42] <tgardner> jjohansen, we're wanting to make sure vmware can load its modules after having been compiled with aq different compiler version then the kernel.
[15:42] <tgardner> bjf, ah, thats more like it
[15:43] <jjohansen> tgardner: I have a maverick kernel on a natty box, I can test against that kernel
[15:44] <tgardner> jjohansen, I don't think that'll trigger the scenario we're worried about.
[15:45] <jjohansen> tgardner: hrmm, okay.  I also have earlier natty kernels I can test again
[15:46] <apw> yeah an older kernel  whcih was built with a different comp should show the issue if any
[15:47] <tgardner> jjohansen, the version skew I'm worried about is because the natty kernel thats going out in the release was built with gcc 4.5.2-8ubuntu3, but the version of the compiler in the archive will be 4.5.2-8ubuntu4. will vmware recompile actually be able to load their modules given the version skew.
[15:48] <jjohansen> tgardner: ah, got it.  Okay will test that one
[15:50] <sconklin> smb: would you like the lucid ec2 package in our PPA copied to -proposed?
[15:50] <smb> sconklin, yes please! :)
[15:51]  * smb thought he had written some mail to the sru-list about that...
[15:52] <sconklin> tgardner: pitti says he's holding off copying the lts-backports-maverick package because there's been no feedback on the bug https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-maverick/+bug/737728
[15:52] <ubot2> Launchpad bug 737728 in linux-meta-lts-backport-maverick "linux-lts-backport-maverick: 2.6.35-28.50~lucid1 -proposed tracker" [Undecided,Fix committed]
[15:54] <bjf> tgardner, maybe you should light a fire under the QA mgr. ? :-P
[15:56] <tgardner> sconklin, aren't the LTS backports a regular part of their test cycle ?
[15:56] <bjf> tgardner, they are, but due to natty testing they have no cycles for stable
[15:56] <sconklin> tgardner: -ENOCLUE
[15:56] <tgardner> bjf, gotta be careful about hassling the Q/A manager. he's got a big stick.
[15:57] <smb>  /o\
[15:57] <tgardner> maybe some of that stuff will shake out this week.
[17:11] <bjf> ogasawara, JFo I seem to recall there is a wiki page that tried to explain how to make changes to apport, do either of you remember such a page? (am i dreaming?)
[17:12] <ogasawara> bjf: I vaguely remember, let me see if I can find it
[17:13] <ogasawara> bjf: https://wiki.ubuntu.com/Apport this is what I remember
[17:14] <tgardner> JFo, what are the URLs you use to report the latest new bugs?
[17:14] <bjf> ogasawara, thanks, was thinking there was one that talked specifically about kernel package hooks
[17:19] <ogasawara> bjf: hrm, I don't remember such a page but that doesn't mean it doesn't exist.  /me tried searching but didn't find anything
[17:19] <bjf> ogasawara, thanks, i'll try to write one up
[17:25] <apw> jjohansen, how did the vmware testing go?
[17:26] <skaet> apw, ping?
[17:26] <apw> pong
[17:27] <skaet> am a bit concerned about subtle interactions from that recent compiler change.
[17:27] <jjohansen> apw: I haven't been able to successfully build the modules yet.  They need to be patched, /me is trying to update vmware but not having much luck finding the account login yet
[17:27] <apw> jjohansen, tgardner may have the info
[17:27] <apw> skaet, well in theory its only affects armel
[17:27] <apw> or are you saying you feel armel needs rebuilding
[17:28] <jjohansen> apw: err its a personal account, /me just got in
[17:28] <apw> ih dih
[17:28] <apw> oh doh
[17:28] <skaet> apw,  patch seems localized to armel.    Concern is on the rebuilding of kernel for armel.
[17:29] <apw> skaet, do we have any information as to the nature of the failure?
[17:29] <skaet> do you have access to that test that broke things before when they switched over, and are you convinced that that case will still work, with this new default.   I'm worrying about subtle implications of the prolog code not being where expected.
[17:30] <tgardner> why don't we just avoid the 'noid and do a no-change upload?
[17:30] <apw> all our breakage was due to bugs in the implementaiton which lead to it being switched back off for non-armel
[17:30] <apw> cirtainly we could upload and rebuild, its 24 hours turn round
[17:31] <apw> tgardner, i wonder if we would want to put anything in there with it, the ath9k patch or the bluetooth one which is worrying cnd
[17:31] <tgardner> apw, neither of those patches are particularly risky.
[17:32] <skaet> apw,  re armel default switch, don't know there will be a failure or not.   just a bit worried, about something breaking that will be very hard to track down with this change, so late in the release.
[17:32] <tgardner> its up to you.
[17:32] <apw> well the safest safest course is a no change rebuild, to get the latest compiler
[17:32] <JFo> bjf, I remember the one ogasawara posted
[17:32]  * JFo scrolls down
[17:32] <apw> and if you have time in your schedule we can cirtainly do that
[17:33] <bjf> JFo, thanks
[17:33] <JFo> tgardner, you mean the incoming bugs numbers?
[17:33] <JFo> or just new status bugs?
[17:33] <apw> skaet, what do you think about pulling in some fixes
[17:33] <tgardner> JFo, the new bugs in the last 24 hours, etc
[17:34] <JFo> hmmm, I have been using the reports bjf wrote for that
[17:34] <JFo> what I report is the change in the overall number
[17:34] <tgardner> JFo, right, thats what I want.
[17:34] <JFo> tgardner, I use https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=natty+kernel-natty&field.tags_combinator=ANY
[17:34] <skaet> apw,  not thrilled,  but pragmatic.   What will improve, and what's the risk?   
[17:34] <JFo> and change the tag per release
[17:35] <JFo> then I do what we have currently versus what there was
[17:35] <JFo> there isn't much to it
[17:35] <JFo> is that what you wanted tgardner?
[17:35] <tgardner> JFo, I think its bjf's report that I want.
[17:35] <JFo> ok one sec...
[17:36] <JFo> tgardner, http://people.canonical.com/~kernel/reports/1-day-new.html
[17:36] <tgardner> JFo, ah, thanks.
[17:36] <JFo> no problem
[17:38] <smb> jjohansen, So I think it is done more or less. It even boots. I am thrilled. :)
[17:38] <jjohansen> smb: nice
[17:47] <sconklin> http://www.ndpsoftware.com/git-cheatsheet.html
[17:47]  * JFo bookmarks
[17:48] <JFo> that is pretty cool
[17:49] <apw> skaet, ok there are a couple of fixes which we could consider
[17:49] <apw> there is an ath9k panic which triggers on connecting to a WPA2 access point
[17:50] <jjohansen> apw: I couldn't trigger it in my testing
[17:50] <apw> there is a fix for some bluetooth devices which only work for 3s and then stop
[17:50] <bjf> ##
[17:50] <bjf> ## Kernel team meeting in 10 minutes
[17:50] <bjf> ##
[17:50] <jjohansen> apw: that is ath9k
[17:50] <apw> jjohansen, ok so perhaps that one is not as wide spread and we can leave it till later
[17:50] <jjohansen> apw, tgardner: vmware is running here now
[17:51] <tgardner> jjohansen, and its fine with compiler version skew ?
[17:51] <jjohansen> tgardner: actually haven't tested that, yet.  Had problems getting it running and had to update, do to compile failures
[17:52] <jjohansen> tgardner: the 7.1.4 package didn't seem to compile the modules which means they existed for my current kernel
[17:52] <jjohansen> that or I missed it compiling them
[17:53] <tgardner> jjohansen, I think you just missed them  getting compiled. I assume you installed VMware from scratch?
[17:53] <jjohansen> tgardner: yep fresh install
[17:53] <jjohansen> I am looking in its logs now
[17:54] <jjohansen> tgardner: so it built them
[17:54] <jjohansen> so it is working
[17:54] <anonymity> hello
[17:55] <tgardner> jjohansen, right. so the next step is to make sure you've booted the kernel from the archive, and that gcc is updated to the next version beyond what was used to build the kernel. then remove and reinstall VMware.
[17:55] <jjohansen> apw: re ath9k yeah I think its safe to leave it to later
[17:56] <jjohansen> tgardner: is there a version beyound gcc-4.5 4.5.2-8ubuntu4
[17:57] <tgardner> jjohansen, thats the version that was uplaoded 28 hours ago.
[17:58] <tgardner> jjohansen, /proc/version should have  gcc-4.5 4.5.2-8ubuntu3 for the archive kernel
[17:58] <bjf> JFo, just noticed you have a workitem "update apport-hooks verbage" which is POSTPONED, does the work i did on apprt constitute a DONE for that ?
[17:59] <JFo> indeed, I put it postponed pending the outcome of that
[17:59] <JFo> is that bug solved?
[17:59] <jjohansen> tgardner: yep it does.  vmware built modules and is running with
[17:59] <jjohansen> Linux version 2.6.38-8-generic (buildd@allspice) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu3) ) #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011
[17:59] <jjohansen> gcc-4.5        4.5.2-8ubuntu4
[18:00] <jjohansen> so the skew doesn't seem to be a problem
[18:01] <tgardner> jjohansen, hmm. Its insmod that does the version comparison I think. Guess I'll have to look in the source to see how it does it.
[18:06] <cking> bjf, that meeting was rather swift today
[18:06] <JFo> bjf, do you have that apport bug number handy?
[18:06] <bjf> JFo, that merge has been accepted and pitti uploaded a apport package with the change in it so i think you can mark it done
[18:06]  * JFo can't seem to find it 
[18:06] <JFo> sweet
[18:06] <JFo> will do
[18:07] <tgardner> cking, so swift that I completely missed it.
[18:09] <cking> just way too efficient
[18:10] <JFo> bjf, blueprint adjusted
[18:10]  * smb waits until the instant meeting notes are available before the meeting
[18:10] <JFo> heh
[18:22] <JFo> going to step away for a bit and eat something... back soon
[18:23] <apw> bjf, sorry was so terse on the meeting, was on the phone to kate about the compiler change
[18:24] <bjf> apw, np, was bugging me more that you were taking so long :-P
[18:25] <apw> i know, typing is so slow
[18:44]  * tgardner --> lunch
[18:46]  * apw drops for an hour-ish ... will be back to do the upload -- pending the decision
[18:58]  * cking --> back later
[19:18] <skaet> apw,  hold off on doing the upload to rebuild.  We'll go with the kernel we have for now unless we find a specific bug.   Most of the ecosystem is already known to work with this kernel.   We've been existing with some applications compiled with the flag, and some without for quite a while. 
[19:31] <Kano32> apw: the only diff is CONFIG_HIBERNATE_CALLBACKS=y with rc4 kernel
[19:31] <Kano32> still no bt
[19:57] <JFo> ogasawara, want to start on these release team bugs?
[19:57] <ogasawara> JFo: sure
[19:57] <JFo> I'm still going through to weed out the ones we don't have to look at
[19:57] <JFo> want to mumble?
[19:57] <ogasawara> sure
[19:58] <JFo> https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/634487
[19:58] <ubot2> Launchpad bug 634487 in linux "t1.micro instance hangs when installing java" [High,Confirmed]
[19:58] <tgardner> JFo, I asked upstream whats going on with the dev_watchdog timeout on natty. there are a couple hundred dups as far as I can tell.
[19:58] <JFo> yeah, tons
[19:58] <JFo> any idea what is causing it?
[19:59] <tgardner> JFo, not yet
[19:59] <JFo> ok, thanks for the head's up
[19:59] <JFo> :)
[19:59] <apw> skaet, ok will do
[20:00] <skaet> apw,  or not do, in this case actually.  ;)
[20:01] <apw> skaet, ok will not do :)
[20:27] <JFo> ogasawara, ok, I only have a handfull I'll follow up on tomorrow
[20:27] <ogasawara> JFo: ack
[20:37] <JFo> so bjf I have about 355 bug mails in the last 24 hrs
[20:38] <bjf> JFo, i have 33
[20:38] <JFo> hmmmm
[20:38] <bjf> JFo, only one of them is from a "NEW" bug
[20:38] <JFo> interesting
[20:39] <JFo> I have no clue what could have changed
[20:39] <JFo> I see at least 50 NEW bugs
[20:39] <bjf> that's what i'd expect to see also
[20:40] <JFo> plus a metric ton of updates
[20:42] <JFo> frankly, I'm baffled
[20:45] <ogasawara> JFo: not that I know what you guys are talking about, but I see you're subscribed to get bugmail for every bug against the linux kernel package, I don't see bjf subscribed though
[20:45] <bjf> ogasawara, am i not via the canonical-kernel-team ?
[20:46] <JFo> well, that is likely it
[20:46] <ogasawara> bjf: I don't think the canonical-kernel-team is subscribed
[20:46] <JFo> bjf, I don't think the kernel team gets ALL bug mail
[20:46] <ogasawara> bjf: so you wouldn't inherit a subscription
[20:46] <JFo> just the ones the team is subbed ot assigned
[20:46] <JFo> or*
[20:46] <bjf> ogasawara, but then I don't understand why i'm getting the bug email that i am getting
[20:48] <ogasawara> bjf: likely a combo of bugs being assigned to the canonical-kernel-team, bug's which you've specifically subscribed to, or bugs which your a member of a team which is subscribed to the bug
[20:49] <ogasawara> bjf: https://launchpad.net/ubuntu/+source/linux/+subscribe
[20:49] <ogasawara> bjf: ^^ if you want to see all changes to public bugs against the linux package
[20:50] <bjf> ogasawara, sure, i could do that, however what tgardner and i have been talking about is that recently our bug mail has dropped by a great deal with no action on our part
[20:51] <bjf> ogasawara, and we are wondering why
[20:51] <ogasawara> bjf: hrm, no idea there
[20:51] <bjf> ogasawara, is it because the canonical-kernel-team was subscribed to all linux email and it no longer is, or is that some other reason... we just don't know
[20:52] <bjf> bug 625364
[20:52] <ubot2> Launchpad bug 625364 in pm-utils "lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails" [Undecided,Confirmed] https://launchpad.net/bugs/625364
[20:52] <ogasawara> bjf: I don't think the ckt was ever subscribed to get all linux bug mail, so I think it's some other reason
[20:53] <bjf> i got the last comment from jfo on that bug, but I'm still trying to figure out why
[20:53] <JFo> likely it was because ckt was assigned?
[20:53]  * JFo guesses
[20:54] <bjf> ah brad->canonical kernel team->ubuntu bug control->ubuntu bugs
[20:54] <tgardner> ogasawara, I think the most telling change in behavior is that I've stopped getting project email.
[20:55] <bjf> so by that trail, anything that "Canonical Kernel Team", "Ubuntu Bug Control" or "Ubuntu Bugs" is subscribed to, i should be getting email from
[20:55] <bjf> that would seem like a few bugs
[20:57]  * bjf believes that ogasawara is now sorry she said anything
[20:57] <ogasawara> heh
[20:58]  * ogasawara is actually wondering if that is true, ie ckt is indirectly subscribed to all ubuntu bugs?
[20:58]  * JFo has hidden
[20:58] <JFo> :)
[21:00] <bjf> Canonical Kernel Team is a member of ubuntu-bugcontrol
[21:01] <bjf> Ubuntu Bug Control is a member of Ubuntu Bugs
[21:02] <tgardner> bjf, the ubuntu-bugs project page says you should be subscribed to https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs if you wanna see them all.
[21:05] <tgardner> bjf, maybe bdmurray could answer some of these questions.
[21:05] <bjf> tgardner, so being a member of a team does not automatically get you all the email for bugs that team is subscribed to
[21:05] <tgardner> bjf, you find a reference for that somewhere?
[21:06] <bjf> tgardner, no, just extrapolating from the comments on the Ubuntu Bugs team page
[21:07] <bjf> tgardner, it's not what I expected, that's for sure
[21:07] <tgardner> bjf, so, does that mean you have to subscribe to every team's mailing list?
[21:07] <bjf> tgardner, that just doesn't make sense
[21:08] <tgardner> bjf, yeah, I don't want to be on the Ubuntu Bug Control team list, most of which isn't relevant to me.
[21:10] <bdmurray> Is there a question I can answer?
[21:11] <bjf> tgardner, i have the attention of lifeless on #launchpad
[21:16] <tgardner> bdmurray, bjf and I were just wondering why the volume of email has dropped so drastically in the last couple of weeks.
[21:20] <bdmurray> tgardner: and you are complaining? ;-)  the thing that would probably help the most is knowing a bug you aren't getting email for and think you should be
[21:26] <tgardner> bdmurray, any bugs against the linux source package for example. I _used_ to get them because I'm in the canonical-kernel-team which is indirectly a member of a bunch of other teams.
[21:28] <bjf> tgardner, is bug 759176 an example ? (it's private but it had a comment added just yesterday)
[21:28] <bjf> tgardner, we are a subteam of one of the teams that is subscribed
[21:30] <tgardner> bjf, yep, I never received anything about it
[21:31] <bjf> bdmurray, ^
[21:35] <bdmurray> IIRC kernel-bugs used to be subscribed to all linux bug reports and had the mailing list set to kernel-bugs@lists.ubuntu.com.  However, this is not what is currently set.
[21:35] <bdmurray> It looks like it changed around 11/2010.
[21:41] <bjf> tgardner, lifeless is asking me to file a bug against launchpad and he will have someone look at it
[21:42] <tgardner> bjf, yep, been lurking
[21:42] <bjf> tgardner, cool
[21:42] <tgardner> bjf, I'm EOD, catch you tomorrow.
[21:43] <bjf> tgardner, l8r
[21:44] <bdmurray> bjf: I can't see that sample bug
[21:44] <bjf> bdmurray, i'll subscribe you if you like
[21:44] <bdmurray> bjf: when did this slow down happen?
[21:45] <bjf> bdmurray, approx. 2 weeks ago
[21:46] <bdmurray> bjf: do you have a bug mail from 2 weeks ago I could look at?
[21:47] <bjf> bdmurray, i'll look but I keep my bug email pretty much cleaned up, it kind of gets out of hand if I don't
[21:55]  * ogasawara back on later
[21:58] <bjf> bdmurray, i found one and have forwarded the email to you
[23:57] <pmcenery> Any chance of this fix making it into natty? https://bugzilla.kernel.org/show_bug.cgi?id=31232
[23:57] <ubot2> bugzilla.kernel.org bug 31232 in IPV6 "/proc/sys/net/ipv6 has two neigh folders" [Low,New]
[23:58] <pmcenery> Bacially anything that does sysctl in an LXC container never completes.