[16:01] <smoser> o/
[16:01] <ttx> o/
[16:01] <RoAkSoAx> o/
[16:01] <SpamapS> aaaaaand compiz crashed
[16:01] <hallyn> \o
[16:02] <ttx> SpamapS: not enjoying dog food so much ?
[16:02] <hallyn> i was actually just enjoying compiz on my other laptop.  thought desktop was looking nice
[16:02] <smoser> so, it appears that https://wiki.ubuntu.com/ServerTeam/Meeting was not updated
[16:02] <smoser> or, if it was , then we dont have a meeting today
[16:03] <smoser> #startmeeting
[16:03] <MootBot> Meeting started at 10:03. The chair is smoser.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <smoser> ok.
[16:03] <jamespage> o/
[16:03] <smoser> so, i think the link above is good except for the 'next meeting' note.
[16:03] <smoser> we'll go off that agenda
[16:03]  * robbiew needs to take a call...a few of them actually...so only lurking
[16:04] <smoser> [TOPIC] Review ACTION points from previous meeting
[16:04] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:04] <robbiew> so don't ask me about Natty Development Status
[16:04] <smoser>  * Everyone - ISO testing.
[16:04] <smoser> I got through all of the ec2 testing, and found enough bugs to have something to do for beta
[16:05] <smoser> and http://iso.qa.ubuntu.com/qatracker/build/ubuntuserver/all seems to indicate that we got through all the tests.
[16:05] <smoser> so, good work on that.
[16:05] <smoser> [TOPIC] natty development
[16:05] <MootBot> New Topic:  natty development
[16:05] <smoser> robbiew, says he doesn't have anything here.
[16:05] <smoser> does anyone else ?
[16:06] <SpamapS> hallyn: you have a potential FFe to propose, right?
[16:06] <hallyn> hm.  yes, potentially for spice
[16:06] <hallyn> though I'm still skiddish about it
[16:07] <Daviey> It probably makes sense for hallyn to investigate what needs doing, and propose a FFe if you think so hallyn
[16:07] <hallyn> yup
[16:07] <Daviey> We can't ack a FFe anyway :)
[16:07] <smoser> Beta is March 24.
[16:07] <Daviey> taht is aaaaaaaaaaages
[16:07] <hallyn> :)
[16:07] <smoser> Make sure (this is s a reminder for me) that if you've got things that you expect you'll get fixed, please open bugs, and target them
[16:07] <smoser> so they wont just get lost
[16:07] <SpamapS> I just want to bring it up for greater discussion that the FFe would be against qemu-kvm.
[16:08] <SpamapS> So, if and when its time to propose the FFe, people should take notice and be ready. :)
[16:08] <smoser> anything else here ?
[16:08] <hallyn> SpamapS: there *will* be a request to upload 0.14.0 of qemu-kvm
[16:08] <hallyn> but that's not with spice
[16:09] <SpamapS> smoser: I've had targetted bugs removed from the target because they weren't considered release blockers...
[16:09] <SpamapS> Which is , I guess, the general use case for targetting bugs.
[16:09] <smoser> yeah, but you should at least have the bugs open. and you can let other people decide if the are or are not milestonable
[16:09] <Daviey> so, like last cycle - we have some super secret tags to add to bugs we care about.
[16:10] <Daviey> server-nrs for bugs we need to work on.
[16:10] <smoser> nrs ?
[16:10] <Daviey> smoser, that is the secret sauce.
[16:10] <SpamapS> that sounds funny if you say it... serverners
[16:11] <SpamapS> next cycle will be even better.. serverors
[16:11] <smoser> what is nrs ?
[16:11] <Daviey> smoser, Natty Release Server
[16:11] <SpamapS> Do those get pulled into the wiki page automatically?
[16:11] <smoser> ah, redundancy built in
[16:11] <smoser> well done
[16:11] <Daviey> smoser, The alternative being server-nro - Natty Release Other
[16:12] <smoser> so.
[16:12] <Daviey> smoser, Other is not server teams area of work, but stuff we care about.
[16:12]  * smoser has some things to tag with that.
[16:12] <Daviey> (ttx's awesome workflow)
[16:12] <smoser> is that documented somewhere other than right above ? it is new to me, but that does not mean a lot.
[16:13] <Daviey> smoser, No, it's not documented
[16:13] <smoser> ok. moving on.
[16:13] <smoser> unless someone has something else, or wants to step up to give more info there and document it somewhere appropriate...
[16:13] <smoser> [TOPIC] Ubuntu Server Team Events
[16:13] <MootBot> New Topic:  Ubuntu Server Team Events
[16:14] <smoser>  * UKUUG Spring Conference - 22-24 March, ttx attending, talking OpenStack (and Ubuntu Server).
[16:14] <smoser> anything else ?
[16:14] <hallyn> http://www.froscon.de/
[16:14] <MootBot> LINK received:  http://www.froscon.de/
[16:14] <SpamapS> MySQL UC coming up April 16
[16:14] <hallyn> It's not certain, but there's talk of a containers development mini-conf there
[16:15] <SpamapS> I'll be at the MySQL UC in Santa Clara, giving a talk on Drizzle and Natty
[16:15] <hallyn> (aug 20-21 in Germany)
[16:15] <Daviey> smoser, nack.
[16:15] <SpamapS> Aug?
[16:15] <smoser> fair enough.
[16:16] <smoser> moving on
[16:16] <smoser> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:16] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[16:16]  * smoser has something for hggdh if he is here
[16:16] <hggdh> yes?
[16:16] <hggdh> :-)
[16:17] <smoser> where do we stand with hardy on ec2 ?
[16:17] <smoser> as i recall some of your tests failed
[16:17] <hggdh> there is a new kernel for hardy in proposed, and we will test it in a few
[16:17] <smoser> but failed both with original hardy (released EC2) and the proposed.
[16:18] <hggdh> some of the failures we found on ec2 were due to differences in kernel patches; I am told they were expected, and should not show up again
[16:18] <smoser> hggdh, and you're going to test, and I assume avoid the tests that hang in both existing and proposed.
[16:18] <hggdh> (i.e., the tests have been updated to consider these differences)
[16:19] <smoser> ah. ok.
[16:19] <smb> The security regression tests were always failing on hardy. At least some of them
[16:19] <smoser> well, anyway you look at it, usre space was causing kernel crash.
[16:19] <smoser> thats not correct
[16:19] <smoser> user space
[16:19] <hggdh> indeed. But all I can do is point out the issues
[16:19] <smoser> anyone else have anything for hggdh ?
[16:20] <hggdh> the decision to accept/reject, in these cases, is not mine
[16:20] <smoser> hggdh, you have anything else ?
[16:20] <smoser> otherwise, moving on
[16:21] <hggdh> no, not from here
[16:21] <smoser> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:21] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (smb)
[16:21] <smb> I am not sure exactly what I did last week
[16:21] <smb> This week started to look at some patches for Lucid-ec2 and found that there could be dragons
[16:22] <smoser> anyone have anything for smb ? i do not.
[16:22] <smb> smb, Sent a note to you and John with some more details
[16:22] <smb> errr make that smoser
[16:22] <smoser> smoser, i got your email
[16:22] <smoser> :)
[16:22]  * smb is talking to himself again
[16:22] <smoser> k.
[16:22] <smoser> moving on
[16:22] <SpamapS> smb I noticed some more people with lockups when using gigabit + NFS ..
[16:22] <smoser> whoops.
[16:22] <smoser> going back
[16:23] <smb> SpamapS, I wished I could replicate them
[16:23] <SpamapS> bug 661294
[16:23] <SpamapS> smb: right, I think that a new development is that there are some reports of non-NFS high speed transfers causing the same thing
[16:23] <smb> I am currently trying at least to verify the sending large files patch in Hardy and maybe in Maverick
[16:24] <SpamapS> smb: and a full lspci for the affected servers. Just wondering if its still on your radar.
[16:24] <smb> Then there has been something that could affect people doing nfs from within kvm
[16:24] <smb> SpamapS, "It is full of stars!"
[16:25] <smb> SpamapS, IOW yes, though there is a lot there
[16:26] <SpamapS> Ok, just wondering because a few close associates have been affected and are sort of at a loss since they can't go from hardy to lucid for fear of locking up their machines or having to run at 100Mbit.
[16:26] <SpamapS> we should mvoe on
[16:26] <smb> It sounded like a race of some sort, but then i tried
[16:27] <smb> and would receive gigs of files on 1000Gbit
[16:27] <smoser> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[16:27] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[16:27] <smoser> sommer is not here.
[16:27] <smoser> anyone else want to talk about documentation ?
[16:27] <Daviey> (thanks smb)
[16:27] <Daviey> Well... we have had a recent question of translatins
[16:27] <Daviey> translations.
[16:28] <RoAkSoAx> I hope things are going great with you.
[16:28] <SpamapS> I'll be working a lot on upstart docs.
[16:28] <Daviey> We talked about it at UDS, and i hoped it might have been something that sommer was going to drive
[16:28]  * RoAkSoAx will start working on updated Cluster Docs
[16:28] <Daviey> Sadly, he's had other commitments
[16:28] <Daviey> RoAkSoAx, Do you want to take the action of talking with the wider docs team? :)
[16:29] <Daviey> If not, i will.
[16:29] <RoAkSoAx> Daviey: it's all yours :)
[16:29] <Daviey> "thanks"
[16:29] <RoAkSoAx> hehe
[16:29] <smoser> [ACTION] Daviey to talk with wider docs team regarding translations
[16:29] <MootBot> ACTION received:  Daviey to talk with wider docs team regarding translations
[16:30] <smoser> [TOPIC] Weekly Updates & Questions from the Ubuntu Community
[16:30] <MootBot> New Topic:  Weekly Updates & Questions from the Ubuntu Community
[16:30] <smoser> anyone have anything here?
[16:30] <smoser> ok. moving on
[16:30] <smoser> [TOPIC] Open Discussion
[16:30] <MootBot> New Topic:  Open Discussion
[16:31] <smoser> anyone have anythign for open discussion ?
[16:31] <SpamapS> hah wow you waited a whole 15 seconds for the community ;)
[16:31] <SpamapS> I think thats supposed to be the Community Team
[16:31] <RoAkSoAx> SpamapS: nope, it was agreed to remove the "Community Team"
[16:31] <smoser> agenda needs fixing.
[16:32] <smoser> oh?
[16:32] <RoAkSoAx> and change it "The Ubuntu Community"
[16:32] <Daviey> No, RoAkSoAx is correct
[16:32] <smoser> ah.
[16:32] <Daviey> I had one more thing.... but i've lost it.
[16:32] <smoser> so, anything there ? we can go back... but IMO this qualifies as "open discussion" just as well as community team.
[16:32] <SpamapS> ahh
[16:32] <SpamapS> ahh ok
[16:32] <Daviey> Oooo.. That was it janimo is my hero of the week.
[16:33] <Daviey> That is all.
[16:33] <RoAkSoAx> smoser: that's what I said but the decision to have "The Community Team" was preferred
[16:33] <smoser> yeah.
[16:33] <smoser> k. for open discussion, if someone wants some udev fun
[16:33] <smoser> bug 712026
[16:33] <Daviey> (janimo has apparently fixed the axis2c FTBFS bug that was causing us so much upset)
[16:34] <hallyn> also bug 727342 - debian doesn't have the fix we need yet
[16:34] <hallyn> and judging by dupes, there are a lot of people wanting it fixed
[16:35] <smoser> the udev bug above raises its head a small percentage of time on i386 instances on ec2. resulting in (i think) dead udev, and thus either network devices coming up, or at least loss of their events.. it is fixed with a reboot.
[16:35] <hallyn> its fixed in upstream git, but not any upstream release.  I can push a temp fix that'll make it work for us, but I suspect debian will not take it and will want to wait for an upstream release
[16:35] <hallyn> (emailed them and asked).  that is all
[16:37] <SpamapS> smoser: so, the problem is the net-device-added event sometimes fails ?
[16:37] <smoser> that is what i was suspecting
[16:37] <smoser> but all i really have is output http://launchpadlibrarian.net/63369945/hung.txt
[16:38] <SpamapS> udevd-work[126]: open /dev/null failed: No such file or directory
[16:38] <SpamapS> interesting
[16:38] <SpamapS> smoser: we should discuss in #ubuntu-cloud later
[16:38] <smoser> we can chat more on that offline SpamapS if you're interested, it is somethign that really needs fixing before beta as I suspect that it is a more general issue, and that i've only been lucky so far on i386
[16:39] <SpamapS> yeah probably
[16:39] <RoAkSoAx> hallyn: not always, just take the upstream fix and forward it to debian. Once they import a new upstream release they will drop the patch and we can sync
[16:39] <SpamapS> some new race
[16:39] <smoser> SpamapS, bug 712034 is related
[16:39] <smoser> (covering the error messages, but most of the time udev doesn't croak)
[16:39] <SpamapS> smoser: I think you should release us!
[16:40] <smoser> [TOPIC] Announce next meeting date and time
[16:40] <MootBot> New Topic:  Announce next meeting date and time
[16:40] <smoser>         Tuesday, March 15 2011 16:00 UTC
[16:40] <Daviey> rocking.
[16:40] <smoser> nothing more to see here folks
[16:40] <smoser> be on your way
[16:40] <smoser> #endmeeting
[16:40] <MootBot> Meeting finished at 10:40.
[16:59] <JFo> \o/
[16:59] <ppisati> o/
[16:59] <jjohansen> \o
[16:59] <herton> o/
[16:59] <cking> \o
[17:00] <sforshee> o/
[17:00]  * pgraner o/
[17:00] <bjf> #startmeeting
[17:00] <MootBot> Meeting started at 11:00. The chair is bjf.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <apw> o/
[17:00] <sconklin> o\
[17:00] <tgardner> 0/
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[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] <bjf> [TOPIC] Release Metrics (JFo)
[17:00] <MootBot> New Topic:  Release Metrics (JFo)
[17:00] <JFo> Release Meeting Bugs (14 bugs, 9 Blueprints)
[17:00] <JFo> [17:00] <JFo>  * 6 linux kernel bugs (up 1)
[17:00] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:00] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:00] <JFo> [17:00] <JFo>  * 19 linux kernel bugs (down 1)
[17:00] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:01] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:01] <JFo> [17:01] <JFo>  * 7 blueprints (Including HWE Blueprints)
[17:01] <JFo> [17:01] <JFo>  * 69 Linux Bugs (up 9)
[17:01] <JFo> [17:01] <JFo>  * 94 Linux Bugs (no change)
[17:01] <JFo> [17:01] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[17:01] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[17:01] <JFo> ..
[17:01] <bjf> [TOPIC] Blueprints: Natty Bug Handling (JFo)
[17:01] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:01] <MootBot> New Topic:  Blueprints: Natty Bug Handling (JFo)
[17:01] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:01] <JFo> nothing to report today
[17:01] <JFo> ..
[17:01] <bjf> [TOPIC] Status: General Natty (apw)
[17:01] <MootBot> New Topic:  Status: General Natty (apw)
[17:01] <apw> The natty kernel is now at v2.6.38-6.33 (v2.6.38-rc8 based).  We are currently concentrating on bug squashing for Natty.  One area of concern is an interaction between vesafb and drmfb during boot, in some cases we are triggering gpu hangs; we are looking at vesafb load to slightly later in boot when drm has not shown up.  We are expecting v2.6.38 final next week.
[17:01] <apw> ..
[17:01] <bjf> [TOPIC] Status: Ecryptfs (jj)
[17:01] <MootBot> New Topic:  Status: Ecryptfs (jj)
[17:02] <jjohansen> postponed for natty.  xattr version still waiting for review, hope to get the version with names stored in the ecryptfs header out today
[17:02] <jjohansen> ..
[17:02] <bjf> [TOPIC] Status: Stable Kernel Team (sconklin / bjf)
[17:02] <MootBot> New Topic:  Status: Stable Kernel Team (sconklin / bjf)
[17:02] <sconklin> ||
[17:02] <sconklin> || We have completed verification phase for the current cycle, and entered
[17:02] <sconklin> || the testing phase: https://wiki.ubuntu.com/Kernel/StableReleaseCadence
[17:02] <sconklin> ||
[17:02] <sconklin> ..
[17:02] <bjf> [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:02] <MootBot> New Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:02] <sconklin> ||
[17:02] <sconklin> || We have completed verification phase for the current cycle, and entered
[17:02] <sconklin> || the testing phase: https://wiki.ubuntu.com/Kernel/StableReleaseCadence
[17:02] <sconklin> ||
[17:03] <apw> ?
[17:03] <tgardner> beer tard....
[17:03] <sconklin> || Package                                    || Upd/Sec              || Proposed             ||  TiP || Verified ||
[17:03] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:03] <sconklin> || dapper   linux-source-2.6.15               || 2.6.15-55.93         || 2.6.15-57.94         ||    0 ||        0 ||
[17:03] <sconklin> || ---      linux-meta                        || 2.6.15.56            || 2.6.15.57            ||    0 ||        0 ||
[17:03] <sconklin> || ---      linux-backports-modules-2.6.15    || 2.6.15-55.13         || 2.6.15-57.15         ||    0 ||        0 ||
[17:03] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:03] <sconklin> || hardy    linux-restricted-modules-2.6.24   || 2.6.24.18-28.7       ||                      ||      ||          ||
[17:03] <sconklin> || ---      linux-ubuntu-modules-2.6.24       || 2.6.24-28.47         ||                      ||      ||          ||
[17:03] <sconklin> || ---      linux-meta                        || 2.6.24.28.30         || 2.6.24.29.31         ||    0 ||        0 ||
[17:03] <sconklin> || ---      linux                             || 2.6.24-28.86         || 2.6.24-29.87         ||    1 ||        1 ||
[17:03] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:03] <sconklin> || karmic   linux-ec2                         || 2.6.31-307.27        || 2.6.31-308.28        ||    0 ||        0 ||
[17:03] <sconklin> || ---      linux-ports-meta                  || 2.6.31.22.18         || 2.6.31.23.19         ||    0 ||        0 ||
[17:03] <sconklin> || ---      linux-mvl-dove                    || 2.6.31-214.32        ||                      ||      ||          ||
[17:03] <sconklin> || ---      linux-meta-mvl-dove               || 2.6.31.214.13        ||                      ||      ||          ||
[17:03] <sconklin> || ---      linux                             || 2.6.31-22.73         || 2.6.31-23.74         ||    0 ||        0 ||
[17:03] <sconklin> || ---      linux-fsl-imx51                   || 2.6.31-112.30        ||                      ||      ||          ||
[17:03] <sconklin> || ---      linux-meta-fsl-imx51              || 2.6.31.112.10        ||                      ||      ||          ||
[17:03] <sconklin> || ---      linux-backports-modules-2.6.31    || 2.6.31-22.24         || 2.6.31-23.25         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-meta                        || 2.6.31.22.35         || 2.6.31.23.36         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-meta-ec2                    || 2.6.31.307.6         || 2.6.31.308.7         ||    0 ||        0 ||
[17:04] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:04] <sconklin> || lucid    linux-ec2                         || 2.6.32-314.27        || 2.6.32-314.27        ||    3 ||        3 ||
[17:04] <sconklin> || ---      linux-meta-mvl-dove               || 2.6.32.209.12        || 2.6.32.214.15        ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-ports-meta                  || 2.6.32.29.22         || 2.6.32.30.23         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-mvl-dove                    || 2.6.32-211.27        || 2.6.32-214.30        ||   20 ||       20 ||
[17:04] <sconklin> || ---      linux-meta-lts-backport-maverick  || 2.6.35.25.36         ||                      ||      ||          ||
[17:04] <sconklin> || ---      linux-lts-backport-maverick       || 2.6.35-25.44~lucid1  ||                      ||      ||          ||
[17:04] <sconklin> || ---      linux-backports-modules-2.6.32    || 2.6.32-29.28         || 2.6.32-30.29         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux                             || 2.6.32-29.58         || 2.6.32-30.59         ||    2 ||        2 ||
[17:04] <sconklin> || ---      linux-fsl-imx51                   || 2.6.31-608.22        ||                      ||      ||          ||
[17:04] <sconklin> || ---      linux-meta-fsl-imx51              || 2.6.31.608.9         ||                      ||      ||          ||
[17:04] <sconklin> || ---      linux-meta                        || 2.6.32.29.35         || 2.6.32.30.36         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-meta-ec2                    || 2.6.32.314.15        || 2.6.32.314.15        ||    0 ||        0 ||
[17:04] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:04] <sconklin> || maverick linux-meta-ti-omap4               || 2.6.35.903.6         ||                      ||      ||          ||
[17:04] <sconklin> || ---      linux-ports-meta                  || 2.6.35.27.21         || 2.6.35.28.21         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-mvl-dove                    ||                      || 2.6.32-414.30        ||    9 ||        9 ||
[17:04] <sconklin> || ---      linux-meta-mvl-dove               ||                      || 2.6.32.414.4         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-firmware                    || 1.38.4               || 1.38.5               ||    1 ||        1 ||
[17:04] <sconklin> || ---      linux                             || 2.6.35-27.48         || 2.6.35-28.49         ||    4 ||        4 ||
[17:04] <sconklin> || ---      linux-backports-modules-2.6.35    || 2.6.35-27.18         || 2.6.35-28.19         ||    0 ||        0 ||
[17:04] <sconklin> || ---      linux-ti-omap4                    || 2.6.35-903.21        ||                      ||      ||          ||
[17:04] <sconklin> || ---      linux-meta                        || 2.6.35.27.35         || 2.6.35.28.36         ||    0 ||        0 ||
[17:04] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:04] <sconklin> ..
[17:04] <bjf> [TOPIC] Status: HW Cert. Team  (ara)
[17:04] <MootBot> New Topic:  Status: HW Cert. Team  (ara)
[17:04] <ara> hello!
[17:05] <ara> In the HW certification team, we will start testing the -proposed kernels for Maverick and Lucid tomorrow or early Thursday. We expect to finish testing no later than March 16th (probably a lot earlier!)
[17:05] <ara> ..
[17:05] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[17:05] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[17:05] <JFo> Incoming Bugs
[17:05] <JFo>  225 Natty Bugs (up 43)
[17:05] <JFo>  1200 Maverick Bugs (up 17)
[17:05] <JFo>  1031 Lucid Bugs (up 6)
[17:05] <JFo> Current regression stats (broken down by release):
[17:05] <JFo> [17:05] <JFo>   * 40 maverick bugs (no change)
[17:05] <JFo>   * 76 lucid bugs (up 1)
[17:05] <JFo>   * 7 karmic bugs (no change)
[17:05] <JFo>   * 0 hardy bugs (no change)
[17:05] <JFo> [17:05] <JFo>   * 94 natty bugs (up 21)
[17:05] <JFo>   * 236 maverick bugs (down 1)
[17:05] <JFo>   * 221 lucid bugs (up 4)
[17:05] <JFo>   * 38 karmic bugs (no change)
[17:05] <JFo>   * 2 hardy bugs (no change)
[17:05] <JFo> [17:06] <JFo>   * 1 natty bugs (up 1)
[17:06] <JFo>   * 0 maverick bugs (no change)
[17:06] <JFo>   * 0 lucid bugs (no change)
[17:06] <JFo>   * 0 karmic bug (no change)
[17:06] <JFo> ..
[17:06] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[17:06] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[17:06] <JFo> Today is the bug day. We are covering bugs in the New status.
[17:06] <JFo> ..
[17:06] <bjf> [TOPIC] Triage Status (JFo)
[17:06] <MootBot> New Topic:  Triage Status (JFo)
[17:06] <JFo> nothing to report.
[17:06] <JFo> ..
[17:06] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:06] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:07] <bjf> thanks everyone
[17:07] <bjf> #endmeeting
[17:07] <MootBot> Meeting finished at 11:07.
[17:07] <JFo> thanks bjf
[17:07] <JFo> now that's gotta be a record
[17:07] <cking> blink and you miss it
[17:07] <apw> i blame steve
[17:07] <JFo> heh
[17:25] <ppisati> Nafallo:
[17:25] <ppisati> ops
[18:00] <jdstrand> o/
[18:00] <jjohansen> \o
[18:01] <micahg> o/
[18:01] <sbeattie> \o
[18:02] <jdstrand> we'll wait a couple more minutes for the other guys
[18:05] <jdstrand> alright, well let's get started
[18:05] <jdstrand> #startmeeting
[18:05] <MootBot> Meeting started at 12:05. The chair is jdstrand.
[18:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:05] <jdstrand> The meeting agenda can be found at:
[18:05] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:05] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:05] <jdstrand> [TOPIC] Review of any previous action items
[18:05] <MootBot> New Topic:  Review of any previous action items
[18:06] <jdstrand> there is one from last week: sbeattie to update SecurityTeam/UpdateProcedures and/or QRT for openjdk tarball generation, build instructions, etc
[18:06] <sbeattie> jdstrand: bah, didn't get to it. sorry.
[18:06] <jdstrand> no worries. aiui, you are still embroiled in that anyway :)
[18:06] <sbeattie> yes
[18:08] <jdstrand> sbeattie: perhaps just do it after the publication. that way you'll have everything
[18:08] <sbeattie> jdstrand: sure.
[18:08] <jdstrand> [TOPIC] Weekly stand-up report
[18:08] <MootBot> New Topic:  Weekly stand-up report
[18:08] <jdstrand> I'll go first
[18:08] <jdstrand> I am on triage this week
[18:09] <jdstrand> I think I am going to look at the schroot/dbus issue. I haven't looked at it at all yet, but need it for an upload
[18:09] <jdstrand> I hope to fix a couple things with ufw
[18:09] <jdstrand> (minor)
[18:09] <jdstrand> and do some QRT updates for apparmor and libvirt
[18:09] <jdstrand> I still would like to investigate changes auditing, since I didn't get to it last week
[18:10] <jdstrand> beyond that, I'd also like to pick up an update
[18:10] <jdstrand> (sounds like a busy week)
[18:10] <jdstrand> :)
[18:10] <jdstrand> kees: you're up
[18:10] <kees> okay, am on community this week
[18:10] <kees> I've been poking around with qrt updates
[18:11] <kees> mostly for subtle kernel features, and chasing corner-cases that hggdh keeps finding. :)
[18:11]  * sbeattie hugs hggdh 
[18:11] <kees> this week I'm going to try to finish my copy_*_user audit in the kernel so I can move on to other areas to audit
[18:11] <kees> that's it for now
[18:12] <jdstrand> kees: thanks
[18:12] <jdstrand> mdeslaur: you're up
[18:12]  * hggdh is a master in finding weird situations...
[18:12]  * kees hugs hggdh
[18:12] <mdeslaur> I'm in the happy place this week
[18:13] <mdeslaur> I published tiff and avahi updates yesterday
[18:13] <mdeslaur> and finally did a gnome-screensaver SRU
[18:13] <mdeslaur> I'll be off for a week starting tomorrow, so today I've been doing some triage
[18:13] <mdeslaur> that's it from me!
[18:14] <mdeslaur> sbeattie: you're next
[18:14] <highvoltage> yay happy places
[18:14] <sbeattie> hehe
[18:14] <mdeslaur> :)
[18:14] <sbeattie> I'm also in the happy place this week.
[18:14] <sbeattie> Last week I released an update for openjdk/non-arm
[18:15] <sbeattie> I'm still working on openjdk/arm packages, maverick built, and lucid is still building.
[18:15] <sbeattie> for lucid, I'll be pushing a no-change-rebuild of binutils and gcj-4.4 from lucid-updates along with it.
[18:16] <sbeattie> they're in the security-proposed ppa.
[18:16] <sbeattie> I'm still poking at karmic.
[18:16] <sbeattie> though I may release the lucid and maverick packages while sorting out karmic
[18:17] <sbeattie> apparmor: I pushed a 2.5.2 official release tarball to launchpad yesterday.
[18:17] <jdstrand> nice
[18:17] <sbeattie> need to do some wiki work and announce it.
[18:18] <sbeattie> otherwise, I'll try to pick up another update this week.
[18:18] <sbeattie> That's it for me.
[18:18] <jdstrand> sbeattie: thanks
[18:18] <jdstrand> micahg: you're up
[18:19]  * micahg is perpetually in the happy place
[18:19] <sbeattie> micahg: \o/
[18:19] <jdstrand> that will change soon, not to worry :)
[18:19] <micahg> I have a chromium update this week
[18:19] <micahg> I'm going to start on the webkit update for karmic-maverick
[18:19]  * jdstrand hugs micahg 
[18:20]  * micahg hugs jdstrand
[18:20] <mdeslaur> \o/
[18:20] <micahg> I think that's enough for me :)
[18:20] <jdstrand> micahg: thanks
[18:20] <jdstrand> [TOPIC] Miscellaneous and Questions
[18:20] <MootBot> New Topic:  Miscellaneous and Questions
[18:20] <jdstrand> congratulations to micahg for getting his first (and second) USNs out
[18:21] <jdstrand> beyond that, I don't have anything
[18:21] <jdstrand> jjohansen: is there anything you'd like to bring up?
[18:22] <jjohansen> jdstrand: /me still needs to coord with sbeattie for the 2.6 release
[18:22] <jjohansen> we already have some bugs against it
[18:22]  * jdstrand nods
[18:22] <sbeattie> jjohansen: right, nice finds.
[18:22] <jjohansen> other than that, nothing I can think of
[18:23] <jdstrand> does anyone have any other questions or items to discuss?
[18:23] <sbeattie> do we want an apparmor meeting tomorrow?
[18:23] <jjohansen> sbeattie: blame chromium
[18:23] <jjohansen> hrmm is there anything to discuss at this point?
[18:23] <jdstrand> I don't personally have anything
[18:23] <sbeattie> jjohansen: don't think so, but I thought I'd ask.
[18:24]  * sbeattie still needs to read jjohansen's dfa posts
[18:24]  * jjohansen could discuss vague ideas about integrating some cgroups control into profile resource control but I don't think a meetings the right place for that
[18:25] <jjohansen> or sbeattie could just wait for the longer version tech paper, because I have just moved forward at this point
[18:25]  * kees enjoyed the dfa posts; I just don't have much to say about them. :)
[18:25] <sbeattie> heh
[18:25] <jjohansen> its kernel vars for n+1
[18:26]  * jjohansen is going to hold off on hfa, backrefs and counting constraints and try to get the rest done
[18:26] <jdstrand> cool
[18:27]  * jdstrand looks forward to @{pid} :)
[18:27]  * jjohansen looks forward to a faster compiler
[18:28] <jdstrand> heh
[18:28] <jdstrand> alright, thanks everyone!
[18:28] <jdstrand> #endmeeting
[18:28] <MootBot> Meeting finished at 12:28.
[18:29] <sbeattie> thanks!
[18:29] <micahg> thanks jdstrand
[18:29] <jdstrand> sure :)
[18:31] <mdeslaur> thanks jdstrand
[23:39] <NRWlion> hey guys
[23:45] <MrChrisDruif> Hai NRWlion :)
[23:47] <jledbetter> Salutations
[23:48] <NRWlion> MrChrisDruif, you again ;)
[23:48] <NRWlion> satue jledbetter
[23:48] <MrChrisDruif> Yeah, you'll find me everywhere :P
[23:48] <NRWlion> MrChrisDruif, that sounds like a life threatening ;)
[23:49] <MrChrisDruif> Meh....more in a friendly way :)
[23:59] <cprofitt> #startmeeting
[23:59] <MootBot> Meeting started at 17:59. The chair is cprofitt.
[23:59] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[23:59] <cprofitt> Welcome to the Beginners Team meeting