[15:58] <Daviey> zul: Are you chairing?
[15:58] <zul> no that was last week
[15:58] <Daviey> zul: Agenda says you? :P
[15:58] <hallyn> \o
[15:59] <zul> Daviey: agenda is wrong
[15:59] <jamespage> o/
[15:59] <Daviey> zul: It didn't get updated?  Do you have ACTIONS listed from last week?
[16:00] <zul> Daviey: there was no actions last week
[16:00] <smb> \o
[16:00] <Daviey> super!
[16:01] <Daviey> #startmeeting
[16:01] <meetingology> Meeting started Tue Aug 30 16:01:31 2011 UTC.  The chair is Daviey. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[16:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:01] <Daviey> #topic Review ACTION points from previous meeting
[16:02] <Daviey> None
[16:02] <Daviey> Unless anyone has anything?
[16:02] <Daviey> #Oneiric Development
[16:02] <Daviey> #topic Oneiric Development
[16:03] <Daviey> So BETA 1 release this Thursday!
[16:03] <Daviey> eep
[16:03] <zul> time flies
[16:03] <jamespage> yikes!
[16:03] <Daviey> In general, we are looking pretty good.
[16:03] <Daviey> Smoke testing of the canddiates is appreciated
[16:03]  * Ursinha is testing 
[16:03] <Daviey> Long view, issues being tracked for Oneiric . http://status.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:04] <Daviey> Some are milestoned with the ambition of being on b1.. good luck with that
[16:04] <Daviey> Any issues not present, please raise them as soon as possible and let me know about them.
[16:04] <Daviey> * Really * Please * If * a bug * needs * to * be * fixed * in Oneiric * for *server * please * tell me * if it *isn't on that * list *
[16:05] <Daviey> http://status.ubuntu.com/ubuntu-oneiric/group/topic-oneiric-server-overview.html <-- needs to be kept up to date with WI's
[16:05] <Daviey> Incoming bug count seems to be slim, but useful.
[16:05] <Daviey> Anything from anyone else?
[16:05] <Ursinha> Daviey: bugs assigned to ubuntu-server and targeted to b1, is that ok?
[16:06] <Ursinha> bug 791607
[16:06] <Daviey> Ursinha: Ones already on the list?
[16:06] <Ursinha> yes
[16:06] <Ursinha> as you said "good luck with that", I wonder if that's true or can be moved
[16:06] <Daviey> Ursinha: That is a concern, upstream eucalyptus have started to be move involved.
[16:06] <Ursinha> right
[16:06] <Daviey> The milestone was realy set to show it's importance and keep it on peoples radar.
[16:07] <Daviey> But it will not be fixed for b1.
[16:07] <Daviey> Unless we are really lucky :)
[16:07] <Ursinha> right then
[16:07] <Daviey> When B1 is pressed, i'll update all the milestones we care about for b2.
[16:07] <Daviey> Anything with anyone else?
[16:08] <Daviey> [TOPIC] Ubuntu Server Team Events
[16:08] <Daviey> (wish i knew what is up with meetingology )
[16:08] <Daviey> Any events people are attending soonish?
[16:08] <hallyn> plumber's next week
[16:09] <Daviey> Ah yes! Anyone going to Linux Plumbers.. do say hello to hallyn, and ask for 1:1 support for LXC issues.
[16:09] <Daviey> no other events?
[16:09] <zul> openstack conference and design summit coming up
[16:09] <Daviey> Week of Oct 3rd!
[16:09] <Daviey> Places still open.
[16:10] <Daviey> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:10] <Daviey> hggdh: Hello sir!
[16:11] <Daviey> I guess hggdh is afk.. will return to him in a bit.
[16:11] <Daviey> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:11] <smb> Most effort going into solving bug #832207 before oneiric release...
[16:11] <Daviey> smb: Hello!
[16:12] <smb> There is a patch for xen to make that work (for pre 2.6.39 kernels at least)....
[16:12] <smb> unfortunately without any network because the emulated nic gets no interrupts either....
[16:12] <Daviey> :/
[16:12] <smb> which is fixed by another patch recently received for testing
[16:12] <smb> ...however....
[16:13] <Daviey> smb: Upstream xen are working on the issue with you?
[16:13] <smb> Daviey, yep
[16:13] <smb> this triggers an issue with ipxe... so the boot hangs on the bios
[16:13] <hggdh> Daviey: OTP on a conflicting meeting, will be available shortly
[16:13] <Daviey> hggdh: ok, thans.
[16:14] <smb> I am able to boot by forcefully not taking any boot proms
[16:14] <smb> And Stefano said, that upstream ipxe seems to work for him as well... not tested locallly though
[16:14] <Daviey> smb: Think it's likely to be fixed by B2?
[16:14] <smb> That only leaves me with pv spinlocks hanging the boot of all 3.0 kernels in hvm mode...
[16:15] <smb> Daviey, Maybe... :-/
[16:15] <smb> Unfortunately every step seems to be into a new issue so far...
[16:15] <Daviey> smb: thanks! Just out of interest, is this on the xen devel mailing list?
[16:15] <Daviey> smb: Sounds like fun!
[16:15] <smb> Daviey, No, doing some direct mails with Stefano from Citrix
[16:16] <Daviey> ah ok, thanks
[16:16] <smb> Daviey, Endless source of joy :)
[16:16] <Daviey> heh
[16:16] <Daviey> smb: bug 790712?
[16:16] <Daviey> jamespage: Thanks for joining us :)
[16:16] <smb> Daviey, Ignored to the best of my abilities so far
[16:16] <Daviey> smb: I don't think it's been checked if that is on the B1 candidates.
[16:17] <utlemming> smb:  do you have the bug on splinlooks?
[16:17] <Daviey> hggdh: Are you able to confirm that is still valid on B1 candidates?
[16:17] <smb> utlemming, Not yet... I am pretty bad with opening those
[16:17] <hggdh> Daviey: I have not seen it again
[16:18] <smb> Daviey, hggdh I thought that I read somethign somewhere which I thought it might be related but completely blanked it now... :(
[16:18] <Daviey> hggdh: That is good, right? :)
[16:19] <smb> Oh... actually remember
[16:19] <hggdh> Daviey: not really -- we bypassed it by allocating more memory to the VMs
[16:19] <Daviey> smb / hggdh: if you see, or get reminded of it again.. lets poke more. :)
[16:19] <Daviey> hggdh: Seems like a valid work around. :)
[16:19] <hggdh> heh
[16:19] <smb> I think there was something wrong with compressed swap ...
[16:19] <hggdh> smb: please go ahead, I am interested :-)
[16:20] <apw> smb, yes there is something very wrong with compressed swap, i am trying to get it sorted in casper
[16:20] <Daviey> hallyn: bug 827798 is still minor, right?
[16:20] <hallyn> Daviey: yes
[16:20] <Daviey> good stuff
[16:20] <Daviey> Anything else for kernel?
[16:20] <smb> apw, Though that means its not fixed yet... which would amke it unrelated to the breakage not happenign anymore.
[16:21] <hallyn> Daviey: let's retarget 827798 and i'll patch it after freeze is over
[16:21] <Daviey> Do people /really/ used compressed swap?
[16:21] <smb> Anyway... No nothing more from me...
[16:21] <Daviey> hallyn: good cookies.
[16:21] <smb> Daviey, I think its used by the installer to allow smallish RAM installs
[16:21] <Daviey> smb: BTW, the care we have for powerpc flavour is sub-zero :)
[16:22] <Daviey> smb: Ah! But only for squashfs?
[16:22]  * smb does not care much even before... :)
[16:22] <Daviey> Thanks smb for the update.. appreciate it!
[16:22] <smb> Daviey, It could be completely not relevant for server install
[16:23] <Daviey> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:23] <Daviey> hggdh: Hello sir!
[16:23] <hggdh> OK
[16:23] <hggdh> still on the phone, but just hearing now ;-)
[16:23] <Daviey> hggdh: So.. QA for Beta 1.. how do we look?
[16:23] <hggdh> we need to get the ensemble and cobbler tests jotted down ASAP
[16:24] <hggdh> server tests are almost all done; we still need help on RAID1 and iSCSI
[16:24] <SpamapS> hggdh: I've got some scripts you can use as a guide.
[16:24] <Daviey> RoAkSoAx / adam_g: Do you have a spare cycle to assit hggdh in writing cobbler setup?
[16:24] <hggdh> SpamapS: perfect
[16:24] <Daviey> SpamapS: for ensemble only, right?
[16:25] <adam_g> Daviey: yeah, i can lend a hand.
[16:25] <SpamapS> hggdh: builds a chroot.. installs ensemble.. starts wp/mysql and curls for the title page.
[16:25] <Daviey> adam_g: rocking!
[16:25] <hggdh> also -- please add to http://pad.ubuntu.com/qa-server-o
[16:25] <SpamapS> hggdh: you just have to manually configure the ssh key and environments.yaml
[16:25] <Daviey> SpamapS: sounds like a good standaline.
[16:25] <Daviey> hggdh was going to work on also testing a minimal formail against cobbler for bare metal.
[16:25] <SpamapS> lp:~clint-fewbar/ensemble/jenkins-test-suite
[16:26] <RoAkSoAx> yeah and I'm still trying to figure out what's wrong in the uec0-plat test-rig as add-apt-repository does not work
[16:26] <SpamapS> misc/jenkins
[16:26] <RoAkSoAx> :)
[16:26] <Daviey> s/fromail/formula
[16:26] <Daviey> SpamapS: Can you bombared hggdh with help in getting that online?
[16:26] <SpamapS> indeed
[16:26] <Daviey> \o/
[16:26] <hggdh> SpamapS: branching now
[16:26] <Daviey> Anything else for testing?
[16:27] <SpamapS> also on the RAID1 test .. I think somebody else should do it
[16:27] <SpamapS> I did a bunch of RAID1 iterating and some fixes this last 2 weeks..
[16:27] <Daviey> Ursinha / jamepage : anything?
[16:27] <SpamapS> better that somebody untainted by that do the tests.
[16:27] <Daviey> smoser / utlemming / jamespage : Test plan for cloud images testing?
[16:27] <jamespage> Daviey: I will be working on the openstack test topologies this week
[16:28] <Daviey> jamespage: Great!  Can you try to put as much of that on the wiki as possible? ;)
[16:28] <Daviey> I don't think deploying openstack via ensemble, via cobbler is a visable QA testing this milestone.
[16:28] <Daviey> but next, i think it will be vital
[16:28] <jamespage> right
[16:28] <adam_g> jamespage: sweet, if/when you branch those openstack formulas, they now live in principia proper
[16:28] <Daviey> Who is the contact this milestone for AWS testing of the images?
[16:29] <jamespage> it will just be a 'follow these steps' for this release - we can automate it later
[16:29] <Ursinha> no sir
[16:29] <Daviey> jamespage: sounds good to me!
[16:29] <Daviey> utlemming / smoser ?
[16:29] <smoser> utlemming kicked off (i believe) another images build. we will begin test when that comes out.
[16:29] <jamespage> Daviey: I run the tests - they should publish out to jenkins.qa.ubuntu.com
[16:29] <Daviey> Beta Freeze.. what is that for eh? :)
[16:30] <smoser> i suppose i or utlemming need to get with jamespage to figure out if we can kick that off ourselves. or if we are still at his mercy to do so.
[16:30] <Daviey> utlemming: Is it safe to assume the latest that will drop on is B1 candidate?
[16:30] <jamespage> smoser: we should be able to figure it out - need to catchup with patrickmw
[16:30] <Daviey> smoser / jamespage / utlemming: Really, the jenkins testing should be more controled by QA.
[16:30] <Daviey> super
[16:31] <jamespage> Daviey: agreed - and its my problem as I've not completed the handover
[16:31] <Ursinha> +1
[16:31] <jamespage> sorry
[16:31] <smoser> that is all fine with me. i just need to push a button, or ask someone to push a button.
[16:31] <Daviey> jamespage: Oh, don;t be
[16:32] <Daviey> I hate the fact that the output of jenkins needs to be manually put into the QA tracker.
[16:32] <jamespage> :-)
[16:32] <jamespage> me to
[16:32] <Daviey> I think that could/should be automated.
[16:32] <hggdh> Daviey: you do not hate it as much as we that do it
[16:32] <Daviey> heh
[16:32] <Ursinha> did I hear automation?
[16:32] <Ursinha> is that too complex or we lack people to do so?
[16:32] <SpamapS> we control the QA code base right?
[16:33] <Daviey> hggdh / jamespage / Ursinha: you might be interested in the post-ami-to-tracker.py.. uses HTTP to 'automate'. .. not exactly an API
[16:33] <SpamapS> So we could just write an importer for jenkins data, could we not?
[16:33] <Daviey> but might have goodness that can be stolen.
[16:33] <Ursinha> Daviey: where is that?
[16:33] <Daviey> SpamapS: that is the hope :)
[16:33] <Daviey> Ursinha: lp:ubuntu-archive-tools IIRC
[16:33] <Ursinha> cool, thanks Daviey :)
[16:33] <Daviey> Maybe something that can be achieved for B2 :)
[16:34] <jamespage> well maybe
[16:34] <Daviey> If someone is going to work on that.. make sure you make it known, to avoid duplication.
[16:34] <Daviey> Moving on?
[16:34] <smoser> if i had to chose between copying data once a alpha/beta and getting automated daily test
[16:34] <smoser> i'd chose fully automated daily test
[16:35] <Daviey> true
[16:35] <Daviey> [TOPIC] Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:35] <smoser> ie, if someone is going to work on something, i'd rather tham work on getting daily tests of our ec2 images than on syncing jenkins output to iso tracker
[16:35] <Ursinha> smoser: notes
[16:35] <Ursinha> noted*
[16:35] <Daviey> NCommander: around?
[16:36] <AlanBell> oops, I broke meetingology a bit :(
[16:36] <Daviey> ogra_ .. seen NCommander ? :)
[16:36] <AlanBell> I will go fix, and reprocess this meeting, carry on as if it was working . . .
[16:36] <Daviey> AlanBell: i noticed :)
[16:36] <Daviey> Thankfully AlanBell's fail will be documented in the meeting logs for eternity.
[16:37] <Daviey> (i jest.)
[16:37]  * AlanBell makes a note to edit the logs to make it look like Daviey's fault
[16:37] <Daviey> heh
[16:37] <ogra_> Daviey, he's somewhere on the road
[16:37] <Daviey> NCommander: When you read this.. it's starting to become an issue this slot?
[16:38] <Daviey> We really need more updates on the status of ARM server.. it's like a low powered black box.
[16:38] <Daviey> Thanks ogra_
[16:38] <Daviey> [TOPIC] Weekly Updates & Questions from the Ubuntu Community
[16:39] <Daviey> kim0|holiday: I assume you are on holiday? :)
[16:39] <Daviey> Any news from the floor?
[16:39] <Daviey> [TOPIC] Open Discussion
[16:40] <zul> we have a new guy dont we?
[16:40] <Daviey> We do!
[16:40] <Daviey> rbasak: Hello sir!
[16:40] <rbasak> Hello!
[16:40]  * hallyn waves
[16:40] <Daviey> The latest addition to ~ubuntu-server team!
[16:41]  * jamespage waves as well
[16:41] <rbasak> Hi everyone!
[16:41] <adam_g> rbasak: o/
[16:41]  * Daviey notes to get rbasak to introduce himself fully next meeting.
[16:41] <Daviey> [TOPIC] Announce next meeting date and time
[16:41] <Daviey> Same time, same place, next week?
[16:42] <Daviey> Good Stuff!
[16:42] <Daviey> #endmeeting
[16:42] <meetingology> Meeting ended Tue Aug 30 16:42:04 2011 UTC.
[16:42] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-30-16.01.moin.txt
[16:43] <SpamapS> whoa..
[16:43] <SpamapS> that is.. cool
[16:49] <AlanBell> apart from failing to process nearly every command :)
[16:49] <AlanBell> reason being code added last night to allow people who are ops to close a running meeting
[16:59] <AlanBell> ok, better plan now
[16:59] <AlanBell> anyone who is an op can act as a chair for any command
[16:59] <AlanBell> so anyone can op up and step in as chair (if they can get ops)
[17:00] <bjf> #startmeeting
[17:00] <meetingology> Meeting started Tue Aug 30 17:00:02 2011 UTC.  The chair is bjf. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <bjf> ##
[17:00] <bjf> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <bjf> ##
[17:00] <cking> o/
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[17:00] <smb> \o
[17:00] <apw> o/
[17:00] <jjohansen> \o
[17:00]  * AlanBell hasn't quite released the update yet
[17:00] <bjf> # Meeting Etiquette
[17:00] <bjf> #
[17:00] <bjf> # NOTE: '..' indicates that you are finished with your input.
[17:00] <bjf> #       'o/' indicates you have something you'd like to add (wait until you are recognized)
[17:00] <bjf> #
[17:00] <ppisati> o/
[17:00] <bjf> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> Various arm kernel flavours: nothing to report.
[17:00] <ppisati> lp709245("ARM SMP scheduler performance bug"): Ming Lei has posted a patch that fixes the problem and discussion is ongoing on linux-omap@.
[17:01] <ppisati> ..
[17:01] <bjf> [TOPIC] Release Metrics and Incoming Bugs (ogasawara)
[17:01] <ogasawara> [17:01] <ogasawara> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <ogasawara> [17:01] <ogasawara>  * 39 linux kernel bugs (up 19)
[17:01] <ogasawara> [17:01] <ogasawara>  * 1 linux kernel bugs (up 1)
[17:01] <ogasawara> [17:01] <ogasawara>  * 0 oneiric linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 16 natty linux kernel bugs (down 2)
[17:01] <ogasawara>  * 3 maverick linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 7 lucid linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 0 hardy linux kernel bugs (no change 0)
[17:01] <ogasawara> [17:01] <ogasawara>  * 150 oneiric bugs (up 18)
[17:01] <ogasawara>  * 1566 natty bugs (up 35)
[17:01] <ogasawara>  * 1089 maverick bugs (down 2)
[17:01] <ogasawara>  * 959 lucid bugs (up 2)
[17:01] <ogasawara>  * 32 hardy bugs (down 1)
[17:01] <ogasawara> [17:01] <ogasawara> [17:02] <ogasawara>  * 0 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 14 natty bugs (no change 0)
[17:02] <ogasawara>  * 40 maverick bugs (no change 0)
[17:02] <ogasawara>  * 76 lucid bugs (down 1)
[17:02] <ogasawara>  * 0 hardy bugs (no change 0)
[17:02] <ogasawara> [17:02] <ogasawara>  * 6 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 435 natty bugs (no change 0)
[17:02] <ogasawara>  * 238 maverick bugs (no change 0)
[17:02] <ogasawara>  * 216 lucid bugs (no change 0)
[17:02] <ogasawara>  * 2 hardy bugs (no change 0)
[17:02] <ogasawara> [17:02] <ogasawara>  * 0 oneiric bugs (down 1)
[17:02] <ogasawara>  * 3 natty bugs (no change 0)
[17:02] <ogasawara>  * 0 maverick bugs (down 1)
[17:02] <ogasawara>  * 1 lucid bugs (no change 0)
[17:02] <ogasawara>  * 0 hardy bugs (no change 0)
[17:02] <ogasawara> ..
[17:03] <bjf> [TOPIC] Milstone Targeted Work Items
[17:03] <bjf> [LINK] http://status.ubuntu.com/ubuntu-oneiric/milestones.html
[17:03] <ogasawara> [LINK] http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team-ubuntu-11.10-beta-1.html
[17:03] <ogasawara> || apw       || other-kernel-o-bug-handling         || 2 work items||
[17:03] <ogasawara> ||           || other-kernel-o-version-and-flavours || 1 work item ||
[17:03] <ogasawara> || ppisati   || other-kernel-o-ubuntu-delta-review  || 1 work item ||
[17:03] <ogasawara> If your name is in the table above, please review your work items or bump them to Beta 2.
[17:03] <ogasawara> ..
[17:03] <bjf> [TOPIC] Status: General Oneiric (ogasawara)
[17:04] <ogasawara> Per bug 837332, we've spun a last minute upload of the kernel this morning to ensure CONFIG_EFI_VARS=y.  We've also added this config to our enforcer now.  I was a bit too strict with the enforcer check which has resulted in FTBFS for powerpc and arm.  The release team has chosen to ignore those for now and we'll get it resolved on the first upload after Beta-1.
[17:04] <ogasawara> Additionally, upstream stable v3.0.4 has been released so we'll be rebasing shortly.  We'll upload the v3.0.4 rebase as well as any queued patches on master-next this Friday after Beta-1 releases.  I would also like to remind everyone that Kernel Freeze is fast approaching, ie Thurs Sept 15.  After that, all patches are subject to our SRU policy in order to be applied.  Some important upcoming dates to keep in mind are as
[17:04] <ogasawara> follows:
[17:04] <ogasawara>  * Sept 1 - Beta 1 (2 days)
[17:04] <ogasawara>  * Sept 15 - Kernel Freeze (~2 weeks)
[17:04] <ogasawara>  * Sept 22 - Beta 2 (~3 weeks)
[17:04] <ogasawara>  * Oct 13 - Final Release (~6 weeks)
[17:04] <ogasawara> I'd also like to note that the P-series git repo was recently rebased it to v3.1-rc4.  It's available at git://kernel.ubuntu.com/ubuntu/ubuntu-p.git master-next .
[17:04] <ogasawara> ..
[17:05] <bjf> [TOPIC] Status: CVE's (apw)
[17:05] <apw> [17:05] <apw>  
[17:05] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:05] <apw>  
[17:05] <apw> Currently open CVEs for each supported branch:
[17:05] <apw>  
[17:05] <apw> || Package                                  || Open      ||
[17:05] <apw> ||                                          ||           ||
[17:05] <apw> || linux Hardy                              ||    9 (+2) ||
[17:05] <apw> || linux Lucid                              ||    6 (+2) ||
[17:05] <apw> || linux Maverick                           ||    6 (+2) ||
[17:05] <apw> || linux Natty                              ||    6 (+2) ||
[17:05] <apw> || linux Oneiric                            ||    5 (+1) ||
[17:05] <apw> || linux-ec2 Lucid                          ||    6 (+2) ||
[17:05] <apw> || linux-fsl-imx51 Lucid                    ||    6 (+2) ||
[17:05] <apw> || linux-mvl-dove Lucid                     ||    6 (+2) ||
[17:05] <apw> || linux-mvl-dove Maverick                  ||    6 (+2) ||
[17:05] <apw> || linux-ti-omap4 Maverick                  ||    6 (+2) ||
[17:05] <apw> || linux-ti-omap4 Natty                     ||    6 (+2) ||
[17:05] <apw> || linux-ti-omap4 Oneiric                   ||    5 (+2) ||
[17:05] <apw> || linux-lts-backport-maverick Lucid        ||    6 (+2) ||
[17:05] <apw> || linux-lts-backport-natty Lucid           ||    6 (+2) ||
[17:05] <apw>  
[17:05] <apw> We have a few new CVEs this week, a result of the security team cleaning house.
[17:05] <apw> ..
[17:06] <bjf> [TOPIC] Status: Stable Kernel Team (sconklin)
[17:06] <sconklin> ||== Status of kernels ==
[17:06] <sconklin> ||
[17:06] <sconklin> || We've finished the verification phase for Lucid and Maverick, which was
[17:06] <sconklin> || delayed due to time required to find regressions. Two fixes have been reverted
[17:06] <sconklin> || from those kernels due to a failure to have them verified.
[17:06] <sconklin> ||
[17:06] <sconklin> || In addition, another regression was reported in Lucid, and the patch was reverted.
[17:06] <sconklin> ||
[17:06] <sconklin> || Both Lucid and Maverick have been respun and uploaded, and the builds should
[17:06] <sconklin> || be completed tomorrow, and they will be ready to enter testing phase.
[17:06] <sconklin> ||
[17:06] <sconklin> || We have gone ahead and prepared the nect Natty kernel without waiting for the next
[17:06] <sconklin> || cycle to start for the other kernels, so that we don't pile up more stable upstream
[17:06] <sconklin> || patches than we must. This effectively decouples Natty from the kernel cadence for
[17:06] <sconklin> || the other kernels
[17:06] <sconklin> ||
[17:06] <sconklin> || * [[http://people.canonical.com/~kernel/reports/sru-report.html|Detailed Information Here]]
[17:06] <sconklin> ||
[17:06] <sconklin> || Kernel status for each series is as follows:
[17:06] <sconklin> ||
[17:06] <sconklin> ||[17:07] <sconklin> || * Released
[17:07] <sconklin> ||
[17:07] <sconklin> ||[17:07] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836914|Lucid Tracking Bug]]
[17:07] <sconklin> || * Now building in the PPA, will enter Testing phase when complete and copied to -proposed
[17:07] <sconklin> || * The following fixes were reverted due to a failure to be verified:
[17:07] <sconklin> ||   [[https://bugs.launchpad.net/ecryptfs/+bug/509180||ecryptfs sometimes seems to add trailing garbage to encrypted files]]
[17:07] <sconklin> ||   [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760||Mouse cursor dissappears with nouveau]]
[17:07] <sconklin> || * The following patch was reverted because it caused a regression:
[17:07] <sconklin> ||   [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836899||tunnels: fix netns vs proto registration ordering]]
[17:07] <sconklin> ||
[17:07] <sconklin> ||[17:07] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/837449|Maverick Tracking Bug]]
[17:07] <sconklin> || * Now building in the PPA, will enter Testing phase when complete and copied to -proposed
[17:07] <sconklin> || * The following fixes were reverted due to a failure to be verified:
[17:07] <sconklin> ||   [[https://bugs.launchpad.net/ecryptfs/+bug/509180||ecryptfs sometimes seems to add trailing garbage to encrypted files]]
[17:07] <sconklin> ||   [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/583760||Mouse cursor dissappears with nouveau]]
[17:07] <sconklin> ||
[17:07] <sconklin> ||[17:07] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836903|Natty Tracking Bug]]
[17:07] <sconklin> || * Now building in the PPA, will enter Verification phase when complete and copied to -proposed
[17:07] <sconklin> ||
[17:07] <sconklin> || Current Kernel versions are available here: http://people.canonical.com/~kernel/reports/versions.html
[17:07] <sconklin> ||
[17:07] <sconklin> ..
[17:08] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:08] <bjf> o/
[17:08] <bjf> I'll go first
[17:08] <bjf>  * I've made changes to some of the bug reports.
[17:08] <bjf>    * Bug Heat column added.
[17:08] <bjf>    * Kernel version column added. The kernel version will be prefixed with '[U]' or '[P]' if that is the version in -updates or -proposed.
[17:08] <bjf> http://people.canonical.com/~kernel/reports/1-day-new.html
[17:09] <bjf> ..
[17:09] <ogasawara> bjf: will those also be reflected in our daily bug report email?
[17:09] <bjf> ogasawara, not right now, but i was thinking about it, would you like it there as well?
[17:10] <apw> migth scap better if the [U] was a suffix
[17:10] <apw> scan
[17:10] <ogasawara> bjf: not sure I care about the updates/proposed bit, but the heat I might be interested in
[17:10] <bjf> apw, your input is noted :-)
[17:10] <bjf> ogasawara, ok
[17:11] <ogasawara> bjf: I really like your daily bug report, I primarily use that rather than LP
[17:11] <ogasawara> bjf: the email that is
[17:11]  * apw seconds that ..
[17:11] <ogasawara> ..
[17:11] <bjf> ogasawara, i wan't people to use both, the 7-day and 30-day as well, with sortable columns we should be detecting regressions quicker
[17:12] <bjf> thanks everyone
[17:12] <bjf> #endmeeting
[17:12] <meetingology> Meeting ended Tue Aug 30 17:12:34 2011 UTC.
[17:12] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-30-17.00.moin.txt
[17:12] <kamal> thanks bjf
[17:24] <AlanBell> sorry about the bot breakage
[17:24] <AlanBell> #startmeeting
[17:24] <meetingology> Meeting started Tue Aug 30 17:24:50 2011 UTC.  The chair is AlanBell. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:24] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:24] <AlanBell> #endmeeting
[17:24] <meetingology> Meeting ended Tue Aug 30 17:24:56 2011 UTC.
[17:24] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-30-17.24.moin.txt
[17:25] <AlanBell> lets use the new syntax :)
[17:25] <AlanBell> #startmeeting kernel team
[17:25] <meetingology> Meeting started Tue Aug 30 17:25:12 2011 UTC.  The chair is AlanBell. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:25] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:25] <AlanBell> #topic foo
[17:25] <AlanBell> #topic bar
[17:25] <AlanBell> someone else want to try to change the #topic please?
[17:25]  * apw notes an extra ' '
[17:26] <apw> #topic me
[17:26] <Daviey> #topic does this fail?
[17:26] <AlanBell> now try
[17:26] <Daviey> #topic does this fail?
[17:26] <apw> AlanBell, you have a spare space between topic: and the topic
[17:27] <AlanBell> #topic foo
[17:27] <AlanBell> so I do
[17:27] <Daviey> AlanBell: Would a more generic wiki page for Meetingology make sense?
[17:27] <AlanBell> yes, when I finish writing it
[17:28] <AlanBell> http://wiki.ubuntu.com/meetingology
[17:28] <AlanBell> #chair Daviey
[17:28] <meetingology> Current chairs: AlanBell Daviey
[17:28] <AlanBell> #votesrequired 2
[17:28] <meetingology> votes now need 2 to be passed
[17:28] <AlanBell> #voters Daviey AlanBell apw
[17:28] <meetingology> Current voters: AlanBell Daviey apw
[17:29] <apw> +1
[17:29] <AlanBell> #vote this house is in favour of cake
[17:29] <meetingology> Please vote on: this house is in favour of cake
[17:29] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[17:29] <AlanBell> +1
[17:29] <meetingology> +1 received from AlanBell
[17:29] <apw> +0
[17:29] <meetingology> +0 received from apw
[17:29] <AlanBell> -1 actually no
[17:29] <meetingology> -1 actually no received from AlanBell
[17:29] <Daviey> +1
[17:29] <meetingology> +1 received from Daviey
[17:29] <AlanBell> you can change your mind
[17:29] <AlanBell> #endvote
[17:29] <meetingology> Voting ended on: this house is in favour of cake
[17:29] <meetingology> Votes for:1 Votes against:1 Abstentions:1
[17:29] <meetingology> Motion denied
[17:29] <AlanBell> didn't reach the threshold
[17:30] <Daviey> AlanBell: Does it check quorum?
[17:30] <AlanBell> hmm, that is what the #votesrequired thing is for
[17:31] <AlanBell> what did you have in mind?
[17:31] <Daviey> ah, nice.. i should RTFM
[17:32] <AlanBell> normally it adds up and checks for positive/negative/zero
[17:32] <AlanBell> zero is a deadlock
[17:32] <AlanBell> or you can say how much of a positive is required (no deadlock in that situation)
[17:33] <AlanBell> #endmeeting
[17:33] <meetingology> Meeting ended Tue Aug 30 17:33:11 2011 UTC.
[17:33] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-30-17.25.moin.txt
[18:20] <bjf> #startmeeting
[18:20] <meetingology> Meeting started Tue Aug 30 18:20:47 2011 UTC.  The chair is bjf. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[18:20] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:20] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:21] <bjf> [TOPIC] ARM Status (ppisati)
[18:21] <bjf> #link https://wiki.ubuntu.com/KernelTeam/Meeting
[18:21] <bjf> #endmeeting
[18:21] <meetingology> Meeting ended Tue Aug 30 18:21:37 2011 UTC.
[18:21] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-30-18.20.moin.txt
[18:21] <bjf> AlanBell, i don't see the bot doing anything useful with "link" commands
[18:22] <bjf> AlanBell, i'm having a hard time understanding why we switched to a less functional bot
[18:38] <AlanBell> https://wiki.ubuntu.com/meetingology]
[18:38] <AlanBell> https://wiki.ubuntu.com/meetingology
[18:39] <AlanBell> bjf: because the other one broke altogether
[18:39] <AlanBell> it is more functional, but was released somewhat ahead of plan because the other one went into early terminal retirement
[18:41] <bjf> AlanBell, personally, i don't find it more functional
[18:41] <AlanBell> in what way?
[18:42] <bjf> AlanBell, I just tried #link and it didn't do anything
[18:42] <AlanBell> yeah, that would be a bug
[18:43] <AlanBell> it did note it in the summary minutes, just didn't confirm that it had caught the command
[18:43] <bjf> AlanBell, the output log is no better than the raw irc logs
[18:43] <AlanBell> in general it *should* be less chatty and not repeat stuff back to you pointlessly
[18:45] <AlanBell> the output log from your earlier meeting wouldn't be as it didn't process any commands :)
[18:45] <AlanBell> normally it should do format it nicely for pasting into moin
[18:45] <bjf> AlanBell, it "worked" last week, i didn't find the output useful (but that just might be me)
[18:45] <AlanBell> there are a few bugs in that and I am not completely happy with the output, but I am working on that
[18:46] <AlanBell> what would you like the output to do?
[18:46] <bjf> AlanBell, i already have a script for taking the output from my irc meeting and producing the moin page
[18:46] <AlanBell> ok, cool, this will do it for everyone
[18:48] <AlanBell> got an example of your script's output?
[18:48] <AlanBell> I can have multiple output writers to suit different tastes :)
[20:11] <AlanBell> hmm, seems the kernel team have a syntax all of their own that they parse
[20:14] <AlanBell> any other teams have specific formats that are post-processed by scripts and are not mootbot commands?
[20:19] <Daviey> AlanBell: Our workflow for posting the meeting mins' is via https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Team_policy (See IRC Meeting) .. suggestions welcome on how to streamline this.
[20:19] <Daviey> (Hint, we don't like the current process)
[20:19] <Daviey> Involves too much post-meeting hacking.
[20:21] <AlanBell> copy-paste-done is the target for post-meeting hackign