[12:36] <EtienneG> hey guys!  Quick q.: when is the next SRU for lucid scheduled?
[12:43] <herton> EtienneG: if everything goes well, current one will probably released next week, once testing finishes (current SRU being tracked in bug 871899)
[12:43] <ubot2> Launchpad bug 871899 in kernel-sru-workflow "linux: 2.6.32-35.78 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/871899
[12:43] <herton> the next one I think will be prepared right after UDS
[12:44] <EtienneG> herton, cool stuff, thanks herton!
[12:45] <EtienneG> herton, do we have a calendar, or a report, or somesuch to track these?  I'll bookmark it and refer t it in the future.
[12:46] <herton> EtienneG: we have a report of all SRUs in progress here: http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[12:46] <herton> we also have a calendar, but it's not always reliable, because of regressions etc. it may offset sometimes
[12:47] <herton> usually each SRU cycle is each 3 weeks
[12:48] <EtienneG> herton, yeah, I understand the cadence is three weeks but likely to slip due to regression.  At least, if I can track what the *plan*, it is already a start!  :)
[12:53] <herton> EtienneG: we have an internal google calendar with the likely schedule, but it's not public I think
[12:58] <herton> s/it's not/nothing
[13:21] <hggdh> herton: btw, did you see my comment on bug 872660?
[13:21] <ubot2> Launchpad bug 872660 in kernel-sru-workflow/regression-testing "linux-lts-backport-maverick: 2.6.35-30.61~lucid1 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/872660
[13:21] <herton> hggdh: yep, https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-maverick/+bug/872660/comments/5
[13:21] <ubot2> Launchpad bug 872660 in kernel-sru-workflow/regression-testing "linux-lts-backport-maverick: 2.6.35-30.61~lucid1 -proposed tracker" [Undecided,In progress]
[13:23] <hggdh> herton: I agree, but I needed it. I cannot decide for the kernel team
[13:24] <herton> hggdh: sure, no problem. This warning shouldn't hold the update
[13:25] <hggdh> herton: all yours to promote to updates
[13:26] <herton> ack
[13:26] <hggdh> now, for the next
[13:42]  * ogasawara back in 20
[13:53] <herton> ppisati: on next fsl-imx51 update, you will be able to use verify-release-ready from kteam-tools to check for common problems like missing tracking bug etc., before pushing. The same is true for all other arm branches, except mvl-dove from maverick, as the script doesn't like the lucid version being used, I'll take a look if it's feasible to fix
[13:58] <herton> ops, in fact on mvl-dove from maverick it doesn't like the missing abi files
[13:59] <ogra_> lucid is dead for armel
[13:59] <ogra_> EOL message should have gone out last week (sadly it wasnt yet), dont put work into lucid distro stuff
[14:00] <herton> ogra_: true for lucid mvl-dove, but maverick mvl-dove should still be updated from what I got
[14:01] <ogra_> herton, i was more referring to fsl-imx51
[14:01] <ogra_> dove exists in maverick, but to my knowledge we never supported a kernel for it
[14:01] <ogra_> (in maverick that is)
[14:05] <herton> ogra_: good news, once official word gets out
[14:05] <ogra_> yeah, i was promised the announcement for last friday ... i'll hunt down kate today
[14:28] <gentoo_drummer> I used the command line installation since i hate unity and installed xfce. the system is incredible fast, even quicker than my debian and i was wondering if someone could tell me how can i get the default ubuntu font rendering
[14:29] <gentoo_drummer> any ideas guys/
[14:29] <gentoo_drummer> ?
[14:31] <ogra_> and you expect the kernel team to know that ? thats brave :)
[14:32] <gentoo_drummer> :P
[14:32] <ogra_> try #ubuntu-desktop ;)
[14:32] <gentoo_drummer> well.. i assume that kernel team tweks with things
[14:32]  * ogra_ guesses they are to understaffed to have time for that :)
[14:37] <ppisati> herton: cool, thanks! :)
[14:43] <hggdh> herton: do we have a backport from Oneiric?
[14:44] <ogra_> herton, so i just talked to kate ... the actual 18 months for lucid are only over on the 29th so EOL announcement for lucid will go out then, but please dont do any kernel work on lucid arm kernels anymore, would be wasted time
[14:45] <herton> hggdh: yes, tracked in bug 878811
[14:45] <ubot2> Launchpad bug 878811 in linux-lts-backport-oneiric "linux-lts-backport-oneiric: 3.0.0-13.21~lucid1 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/878811
[14:45] <herton> ok
[14:46] <hggdh> herton: it does not show up on http://people.canonical.com/~kernel/reports/sru-report.html ?
[14:48] <herton> hggdh: no, I don't know why, bjf ^
[14:48] <hggdh> herton: since I already have lucid loaded, I will go ahead and do 878811 also; of course, may redo if verification fails
[14:48] <herton> hggdh: ok. http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html lists it though
[14:49] <bjf> herton, hggdh, will look into it
[15:07] <ogra_> herton, so i also just confirmed again, there was never a dove kernel in maverick, if there is thats a big mistake and its definitely not supported by any of us (or you)
[15:09] <herton> hmm ok
[15:09] <herton> going to lunch, bbl
[15:20] <bjf> ogra_: that is quite amusing since we did ship a mvl-dve maverick kernel (2.6.32 based) and have been supporting it since release
[15:21] <ogra_> bjf, yes, we never should have done that, that kernel was for NCommanders tests and should have been removed from the archive before release day
[15:21] <ogra_> bjf, wrt dove in maverick we only support the userspace
[15:21] <bjf> pgraner: ^ nice eh?
[15:22] <ogra_> (sorry, i didnt even know that kernel exists, i (nor anyone else but NCommander) wasnt involved in dove after lucid)
[15:23] <ogra_> the more intresting question is, is there a way to remove it from a released archive ....
[15:23] <ogra_> if its there now, i guess it should see security maintenance at least, would be good to avoid that
[15:24] <bjf> ogra_: we work on it every 3 weeks
[15:24] <ogra_> ugh
[15:24] <ogra_> what a waste of manpower
[16:05] <hggdh> herton, bjf: bug 879516, I am failing this kernel
[16:08] <bjf> hggdh: any reason that bug is private ?
[16:08] <hggdh> bjf: a security test failed
[16:08] <hggdh> bjf: you should have access, I subscribed the kernel team
[16:09] <hggdh> bjf: I will move straight ahead to the Oneiric proposed kernel now, and check it
[16:20] <bjf> herton, hggdh, the lts-backport-oneiric tracking bug is not on the sru-report because the tracking bug was not added to the changelog
[16:21] <hggdh> bjf: ah, thank you
[16:23] <herton> bjf: ack, I thought it could be this, since we weren't able to create the bug report earlier
[16:24] <herton> and put in the changelog
[17:54] <hggdh> herton: jj found the issue on the oneiric backport to be a test case failure; as such, I am tagging it -passed
[17:56] <cnd> bjf, do you know who does the wiki gardening for the kernel team?
[17:57] <cnd> I'm wondering how to create a table with borders
[17:57] <bjf> cnd we've let it go to weeds
[17:57] <cnd> urg
[17:58] <bjf> cnd there's a moin style/syntax help page that explains it
[17:58] <bjf> i think
[17:58] <cnd> I can't find anything on borders though
[17:58] <cnd> and the ubuntu wiki by default doesn't show borders
[17:58] <cnd> which makes it hard to read tables
[17:58] <cnd> oh wait, I can check the release schedule page
[17:58] <cnd> that has borders
[17:59] <cnd> or not
[18:28] <herton> hggdh: ok, cool
[19:54] <tathi> I just reformatted an old ubuntu box and installed 11.10, and while it installed the rt61pci driver automatically, my wireless card isn't picking up the router's SSID.
[19:54] <tathi> (connect to hidden network works fine, as do all other computers in the house)
[19:54] <tathi> Should I be reporting this as a bug?
[19:55] <ohsix> how long did you wait for the ap to show up
[19:56] <tathi> It took me probably 15-20 minutes to figure out how to get it up, find the SSID from another box, and all that.
[19:57] <tathi> So long enough, I think.
[19:57] <ohsix> there are a few moving parts, and unless something is very broken it's not the kernel or the driver
[19:57] <tathi> Hrm.
[19:57] <ohsix> nm-tool can display what networkmanager sees, the applet might have its own criteria for displaying stuff
[19:58] <tathi> Any other suggestions?  It worked fine under Ubuntu 9.04 this morning, then I spent an hour or so reinstalling.  Didn't move the computer, so the hardware should still be fine.
[19:59] <tathi> What applet?
[20:00] <ohsix> that fancy thing on your desktop that actually shows a list of things to connect to is just a small part of it
[20:00] <tathi> Ah.  I was mostly poking around with command-line tools, though I didn't change anything.
[20:01] <tathi> lspci, iwlist, lshw, that sort of thing.
[20:01] <ohsix> nm-tool should pretty much tell you all you need to know, delete the connection for the ap you're trying to accessing, disable networking, reenable; check and see if nm-tool shows the ap you're interested about
[20:02] <tathi> I'll try that.  Thanks!
[20:10] <tathi> Nope, same thing.
[20:18] <tathi> Well, I suppose I could pull the card and test it on another computer in case it randomly broke at the same time I upgraded the software...
[20:19] <tathi> Seems odd that it can connect fine though.
[20:20] <ohsix> same thing what? nm-tool doesn't list the ap?
[20:20] <tathi> right.
[20:20] <tathi> If it's connected, it lists the normal stuff.
[20:21] <tathi> Disconnect, and it still lists the ap.
[20:21] <ohsix> what driver was it again?
[20:21] <tathi> disable networking and delete entry, enable it again and still no ap.
[20:21] <tathi> rt61pci
[20:23] <ohsix> can you post the output of dmesg to a pastebin
[20:25] <tathi> grr...don't have xclip.  yeah, hang on.
[20:27] <tathi> http://pastebin.com/ebpjssCs
[20:28] <tathi> Is this the right place to ask this?  I could go find someone else to bother... :)
[20:30] <ohsix> well, #linux-wireless