[16:00] <Daviey> utlemming: Are you happy to chair?
[16:00] <utlemming> Daviey: sure
[16:01] <smb> \o
[16:02] <adam_g> o/
[16:02] <Daviey> utlemming: Are you getting my pm's?
[16:02] <zul> helo
[16:03] <Ursinha> o/
[16:03] <hallyn> \o
[16:03] <utlemming> #startmeeting
[16:03] <MootBot> Meeting started at 11:03. The chair is utlemming.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:04] <RoAkSoAx> o/
[16:04] <utlemming> [TOPIC] follow up from last meeting
[16:04] <MootBot> New Topic:  follow up from last meeting
[16:04] <utlemming> sommer, j1mc: to look at doc presentation (continued x 2)
[16:04] <utlemming> What is the status on the doc presentation?
[16:05] <utlemming> And it looks like neither are in...so
[16:05] <utlemming> [ACTION] sommer and j1mc to look at doc presentation (continued x 3)
[16:05] <MootBot> ACTION received:  sommer and j1mc to look at doc presentation (continued x 3)
[16:06] <utlemming> [TOPIC] Oneiric Development
[16:06] <MootBot> New Topic:  Oneiric Development
[16:06] <utlemming> Anyone have any topics here?
[16:07] <Daviey> o/
[16:07] <Daviey> Full cycle tracking: - http://status.ubuntu.com/ubuntu-oneiric/group/topic-oneiric-server-overview.html
[16:07] <Daviey> We seem to be pretty much on target, with:
[16:07] <Daviey> Bugs currently being tracked for Oneiric Release: - http://people.ubuntu.com/~davewalker/release-bugs.html
[16:07] <Daviey> If there is a bug you are aware of, or currently working on that isn't on that list - please can you raise it here, or with me afterwards.  Thanks.
[16:07] <Daviey> Sync's/Merges: - http://people.ubuntu.com/~davewalker/server-sid-new.html (We are doing ok!  But please be conservative!)
[16:08] <Daviey> (boot experience Clint is currently working hard on)
[16:08] <Daviey> LXC is expected to catch up at the LXC sprint.
[16:08] <Daviey> Anything else to note?
[16:08] <hallyn> conservative?
[16:08] <hallyn> meaning don't do any more synca than we feel we really need to?
[16:09]  * hallyn confused
[16:10] <utlemming> Daviey: can you clarify for hallyn?
[16:11] <Daviey> hallyn: We just need to start stabilising
[16:11] <Daviey> We can still break stuff, but there is added presure to resolve.
[16:11] <hallyn> Daviey: oh, i was loking at it a bit differently...
[16:11] <hallyn> figuring we should sync to the last possible minute in this cycle,
[16:11] <hallyn> and be extra-conservative in 12.04
[16:11] <zul> agreed
[16:12] <hallyn> was particularly hoping not to sync libvirt at all during 12.04 cycle if possible
[16:12] <Daviey> hallyn: Well we /can/ do that.. but be more aware of issues it might cause.
[16:12]  * hallyn nods
[16:12] <Daviey> (hallyn, note that next cycle may be syncing from debian testing, rather than unstable)
[16:12] <hallyn> ah
[16:13] <Daviey> hallyn: I wonder if we can reduce our delta regarding libvirt?
[16:13] <hallyn> Daviey: that's not the issue.  (well, it's a bear, but not the issue ;)
[16:13] <Daviey> That seems to be moving quite fast in Debian, and regular sync would be easier if a smaller delta.
[16:14] <hallyn> it's moving fast upstream.
[16:14] <hallyn> too fast, imo, to safely track during lts cycle.
[16:16] <Daviey> hallyn: agreed, we'll discuss that at UDS
[16:16] <hallyn> cool
[16:17] <jdstrand> fwiw, it does move very fast
[16:17] <jdstrand> (imo)
[16:17] <Daviey> jdstrand: We'll nab you for a session regarding core component versioning session at UDS btw :)
[16:17] <Daviey> utlemming: I think we can move on.
[16:17] <utlemming> [TOPIC] Ubuntu Server Team Events
[16:17] <MootBot> New Topic:  Ubuntu Server Team Events
[16:17] <jdstrand> Daviey: cool
[16:17]  * jdstrand quiets down
[16:18] <utlemming> Do we have any events this week?
[16:19] <utlemming> SpamapS (Clint Byrum) will be speaking at OSCON July 28
[16:19] <utlemming> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:19] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[16:20] <hggdh> any questions for me?
[16:20] <hggdh> otherwise...
[16:20] <hggdh> ..
[16:21] <utlemming> hggdh: we'll take silence as no questions
[16:21] <Daviey> hggdh: None at the moment!
[16:21] <utlemming> [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> Hi
[16:21] <smb> Not think there so much updates this week
[16:21] <Daviey> one mo
[16:22] <smb> Found some missing deps for the xen build which zul is taking care of
[16:22] <smb> Daviey, yes?
[16:22] <Daviey> smb / utlemming: Any news on bug #791850 ?
[16:22] <utlemming> Daviey: beat me to the punch there...
[16:23] <smb> Daviey, Not so much from my side, I was using the comment of Amazon looking to provide data as a SEP field
[16:23] <utlemming> There has been some AWS forum activity going with Oneiric -- so we might need to spend some time there. Amazon reports that the instance dies almost immediately.
[16:23] <Daviey> utlemming: I assigned it to you, purely as the point of contact - as you were talking to Amazon about it.
[16:24] <adam_g> i've got a question regarding Bug #799630 and similar, where DKMS packages are updated against backported kernels and fail. is this kinda stuff supported, especially on LTS?
[16:24] <utlemming> Yes, I've talked with Amazon a couple of times, but haven't made any in roads there yet.
[16:24] <Daviey> utlemming: ok.. what can we do to progress this?
[16:25] <Daviey> adam_g: dkms should not build a kernel module if it notices the kernel has a >= to what is in the dkms payload.
[16:25] <utlemming> I'll work with smb on this -- we'll likely need to get a dump on this or repro this in house
[16:26] <Daviey> utlemming: sounds good!
[16:26] <utlemming> [ACTION] smb and utlemming to work on Bug #791850
[16:26] <MootBot> ACTION received:  smb and utlemming to work on Bug #791850
[16:26] <smb> adam_g, I guess at least for LTS and when providing backported kernels I think it should be taken care of
[16:27] <adam_g> Daviey: so that mentioned bug looks more like a packaging issue than anything else?
[16:27] <RoAkSoAx> adam_g: yes it does, though you'd also have to start updating user-space tools to match the kernel module
[16:27] <Daviey> adam_g: can't comment really, first time i've looked at it
[16:27] <Daviey> We'll take it out of meeting.
[16:27] <utlemming> [ACTION] Daviey and adam_g to address Bug #791850
[16:28] <MootBot> ACTION received:  Daviey and adam_g to address Bug #791850
[16:28] <utlemming> Any other topics for smb?
[16:28] <smb> Ok. Otherwise I also don't have more.
[16:28] <adam_g> drbd is one example, but there are other modules that we maintaind out-of-tree and later merged mainline, but in doing so caused out of tree modules to fail to build against later kernels
[16:28] <Daviey> smb: thanks!
[16:28] <Daviey> adam_g: Yeah, that sounds like a dkms bug, as it should not build.
[16:29] <Daviey> Thankfully, the dkms upstream is a ubuntu developer - we'll jump on him if we get blocked. :)
[16:29] <adam_g> Daviey: ok great, ill be happy to look at it with you later
[16:29] <smb> Daviey, just note that in some cases you only have the dkms module
[16:30] <Daviey> yah
[16:30] <utlemming> [TOPIC] Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:30] <MootBot> New Topic:  Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:31] <utlemming> NCommander: you're up
[16:33] <utlemming> Okay, moving on
[16:33] <utlemming> [TOPIC] Weekly Updates & Questions from the Ubuntu Community
[16:33] <MootBot> New Topic:  Weekly Updates & Questions from the Ubuntu Community
[16:34] <utlemming> Any questions or comments to or from our community?
[16:34] <utlemming> Moving on then
[16:34] <utlemming> [TOPIC] Open Discussion
[16:34] <MootBot> New Topic:  Open Discussion
[16:35] <Daviey> I have nothing to raise.
[16:35]  * NCommander is here now (sorry, TASP call)
[16:36] <utlemming> NCommander: glad to have you join
[16:36] <utlemming> Any updates for us?
[16:36] <NCommander> Unattended installation with preseeds is now know to work on pandaboard which should help satisfy the requirements of ensebmle
[16:37] <NCommander> In addition, heavy QA efforts are underway to make sure common sets of server packages work properly on ARM (such as kerberous, ruby-on-rails, etc.)
[16:37] <NCommander> any help with QA testing of any sort would be greatly appericated
[16:37] <Daviey> NCommander: Is there docs on using uboot to PXE boot?
[16:38] <Daviey> NCommander: Where is the QA effort being co-ordinated?
[16:38] <NCommander> Daviey: more like a loose collection of notes, GrueMaster is the expert on this
[16:38] <NCommander> Daviey: on two specs in LP
[16:38] <Daviey> NCommander: I wonder if you'd be able to ask GrueMaster to document this?
[16:38]  * NCommander tries to get the links
[16:39] <NCommander> Daviey: he probably has it documented, I just haven't been around to poke him about it
[16:39] <NCommander> https://blueprints.launchpad.net/ubuntu/+spec/server-o-arm-image-validation
[16:39] <NCommander> https://blueprints.launchpad.net/ubuntu/+spec/server-o-arm-image-qa
[16:39] <hallyn> wiki.ubuntu.com/ArmServer ?
[16:39] <NCommander> hallyn: there's a landing page on the wiki but I don't have a link handy
[16:40] <hallyn> ah ok
[16:40] <Daviey> NCommander: This probably needs to be better vocalised.
[16:40] <NCommander> Daviey: the QA bits?
[16:40] <Daviey> NCommander: both parts :)
[16:40] <NCommander> I'll make a posting on my blog about it, though I'm unsure how many people actually read it :-(
[16:41] <Daviey> NCommander: We'll all read it :)
[16:41] <Daviey> it will be well recieved. :)
[16:41] <Daviey> Thanks NCommander !
[16:41] <NCommander> np
[16:43] <utlemming> [TOPIC] Announce next meeting date and time
[16:43] <MootBot> New Topic:  Announce next meeting date and time
[16:43] <utlemming> Tuesday 2011-08-02 at 1600 UTC here in #ubuntu-meeting
[16:43] <utlemming> Thank you everyone and have a good week
[16:43] <utlemming> #endmeeting
[16:43] <MootBot> Meeting finished at 11:43.
[16:44] <Daviey> thanks utlemming
[16:44] <utlemming> :)
[16:59] <ppisati> o/
[17:00] <smb> \o
[17:00] <bjf> #
[17:00] <bjf> # lets "get 'er done"!
[17:00] <bjf> #
[17:00] <bjf> #startmeeting
[17:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <bjf> ##
[17:00] <bjf> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <bjf> ##
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[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] ARM Status (ppisati)
[17:00] <MootBot> New Topic:  ARM Status (ppisati)
[17:00] <ppisati> Oneiric/ti-omap4: finally pushed out the first oneiric 3.0 + TI BSP kernel (3.0.0-1200.2), and there's already a BSP update in the pipe.
[17:00] <ppisati> Oneiric/tegra: forward ported/triaged around ~600 patches from 2.6.38 to 3.0 - basically video/ and arch/arm/mach-tegra/, plus some glue functions here and there. The kernel doesn't compile yet.
[17:00] <ppisati> ..
[17:01] <bjf> [TOPIC] Release Metrics and Incoming Bugs (ogasawara)
[17:01] <MootBot> New 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] <MootBot> LINK received:  http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <ogasawara> [17:01] <ogasawara>  * 26 linux kernel bugs (up 6)
[17:01] <ogasawara> [17:01] <ogasawara>  * 2 linux kernel bugs (up 2)
[17:01] <ogasawara> [17:01] <ogasawara>  * 0 oneiric linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 22 natty linux kernel bugs (down 1)
[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>  * 65 oneiric bugs (up 3)
[17:01] <ogasawara>  * 1425 natty bugs (up 5)
[17:01] <ogasawara>  * 1092 maverick bugs (down 11)
[17:01] <ogasawara>  * 927 lucid bugs (down 41)
[17:01] <ogasawara>  * 32 hardy bugs (down 1)
[17:01] <ogasawara> [17:01] <ogasawara> [17:01] <ogasawara>  * 0 oneiric bugs (no change 0)
[17:01] <ogasawara>  * 12 natty bugs (up 6)
[17:01] <ogasawara>  * 41 maverick bugs (down 2)
[17:01] <ogasawara>  * 74 lucid bugs (down 8)
[17:01] <ogasawara>  * 0 hardy bugs (no change 0)
[17:01] <ogasawara> [17:01] <ogasawara>  * 1 oneiric bugs (up 1)
[17:01] <ogasawara>  * 440 natty bugs (down 4)
[17:02] <ogasawara>  * 242 maverick bugs (no change 0)
[17:02] <ogasawara>  * 208 lucid bugs (down 9)
[17:02] <ogasawara>  * 2 hardy bugs (no change 0)
[17:02] <ogasawara> [17:02] <ogasawara>  * 0 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 2 natty bugs (no change 0)
[17:02] <ogasawara>  * 1 maverick bugs (down 1)
[17:02] <ogasawara>  * 0 lucid bugs (no change 0)
[17:02] <ogasawara>  * 0 hardy bugs (no change 0)
[17:02] <ogasawara> ..
[17:02] <bjf> [TOPIC] Blueprints: Oneiric Delta Review (ogasawara)
[17:02] <MootBot> New Topic:  Blueprints: Oneiric Delta Review (ogasawara)
[17:02] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-ubuntu-delta-review
[17:02] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/other-kernel-o-ubuntu-delta-review
[17:02] <ogasawara> apw, lag, rsalveti: you have work items to review your set of Ubuntu patches.  I've pushed these out to Alpha-3 for you.  Please take a moment to review when you have a chance. See https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview for your specific set of patches.  Note, these are the only remaining work items for this blueprint.
[17:02] <ogasawara> ..
[17:02] <bjf> [TOPIC] Status: General Oneiric (ogasawara)
[17:02] <MootBot> New Topic:  Status: General Oneiric (ogasawara)
[17:03] <ogasawara> Last week we uploaded the 3.0.0-7.8 kernel.  This most notably enabled overlayfs as well as rebased to upstream v3.0 final.  Alpha-3 is next Thurs, Aug 4th.  I intend to upload our final Alpha-3 this Friday, July 29th.  If there are any patches that need to land for Alpha-3, get them sent to the kt-ml asap.
[17:03] <ogasawara> ..
[17:03] <bjf> [TOPIC] Status: CVE's (apw)
[17:03] <MootBot> New Topic:  Status: CVE's (apw)
[17:03] <apw> [17:03] <apw> After hitting 0 CVEs open on all branches but Hardy at the start of the week we have seen, one CVE has resurface and 8 new ones have been added.  Luckily a large number of the new CVEs are already fixed in Lucid and later.
[17:03] <apw> [LINK] http://people.canonical.com/~apw/cve/pkg/CVE-linux.txt
[17:03] <MootBot> LINK received:  http://people.canonical.com/~apw/cve/pkg/CVE-linux.txt
[17:03] <apw> Currently open CVEs for each supported branch:
[17:03] <apw> || Package                                  || Open ||
[17:03] <apw> ||                                          ||      ||
[17:03] <apw> || linux Hardy                              ||   12 ||
[17:03] <apw> || linux Lucid                              ||    3 ||
[17:03] <apw> || linux Maverick                           ||    3 ||
[17:03] <apw> || linux Natty                              ||    3 ||
[17:04] <apw> || linux Oneiric                            ||    2 ||
[17:04] <apw> || linux-ec2 Lucid                          ||    3 ||
[17:04] <apw> || linux-fsl-imx51 Lucid                    ||    9 ||
[17:04] <apw> || linux-mvl-dove Lucid                     ||    3 ||
[17:04] <apw> || linux-mvl-dove Maverick                  ||    3 ||
[17:04] <apw> || linux-ti-omap4 Maverick                  ||    9 ||
[17:04] <apw> || linux-ti-omap4 Natty                     ||    3 ||
[17:04] <apw> || linux-ti-omap4 Oneiric                   ||    2 ||
[17:04] <apw> || linux-lts-backport-maverick Lucid        ||    3 ||
[17:04] <apw> || linux-lts-backport-natty Lucid           ||    3 ||
[17:04] <apw> ..
[17:04] <bjf> [TOPIC] Status: Stable Kernel Team (sconklin)
[17:04] <MootBot> New Topic:  Status: Stable Kernel Team (sconklin)
[17:04] <sconklin> ||== Status of kernels ==
[17:04] <sconklin> ||
[17:04] <sconklin> || This is kernel verifiation,
[17:04] <sconklin> || Kernel status for each series is as follows:
[17:04] <sconklin> ||
[17:04] <sconklin> || * [[http://people.canonical.com/~kernel/reports/sru-report.html|Detailed Information Here]]
[17:04] <sconklin> ||
[17:04] <sconklin> ||[17:04] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/812360|Hardy Tracking Bug]]
[17:04] <sconklin> || * A new kernel is in -proposed, ready for  QA (early)
[17:04] <sconklin> ||
[17:04] <sconklin> ||[17:05] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/813507|Lucid Tracking Bug]]
[17:05] <sconklin> || * A new kernel was built to include one additional patch, and has completed testing
[17:05] <sconklin> ||   It is ready to be published
[17:05] <sconklin> ||
[17:05] <sconklin> ||[17:05] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/808934|Maverick Tracking Bug]]
[17:05] <sconklin> || * Kernel in -proposed from the last cycle is awaiting regression testing.
[17:05] <sconklin> ||
[17:05] <sconklin> ||[17:05] <sconklin> || * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811180|Natty Tracking Bug]]
[17:05] <sconklin> || * Verification has begun for this kernel, with two bugs remaining to be verified
[17:05] <sconklin> ||
[17:05] <sconklin> ..
[17:05] <bjf> [TOPIC] Security & bugfix kernels - Natty/Maverick/Lucid/Hardy (sconklin)
[17:05] <MootBot> New Topic:  Security & bugfix kernels - Natty/Maverick/Lucid/Hardy (sconklin)
[17:05] <sconklin> ||
[17:05] <sconklin> || Current Kernel versions are always available here: http://people.canonical.com/~kernel/reports/versions.html
[17:05] <sconklin> ||
[17:05] <sconklin> || Package                                    || Upd/Sec              || Proposed             ||  TiP || Verified ||
[17:05] <sconklin> ||                                            ||                      ||                      ||      ||          ||
[17:05] <sconklin> || hardy    linux                             || 2.6.24-29.91         || 2.6.24-29.92         ||    0 ||        0 ||
[17:05] <sconklin> || lucid    linux-meta-lts-backport-maverick  || 2.6.35.25.36         || 2.6.35.30.38         ||    0 ||        0 ||
[17:05] <sconklin> || ---      linux-lts-backport-maverick       || 2.6.35-25.44~lucid1  || 2.6.35-30.56~lucid1  ||   22 ||       22 ||
[17:05] <sconklin> || ---      linux-firmware                    || 1.34.7               || 1.34.10              ||    0 ||        0 ||
[17:05] <sconklin> || ---      linux                             || 2.6.32-33.70         || 2.6.32-33.71         ||    0 ||        0 ||
[17:05] <sconklin> || maverick linux-firmware                    || 1.38.6               || 1.38.8               ||    1 ||        0 ||
[17:06] <sconklin> || ---      linux                             || 2.6.35-30.54         || 2.6.35-30.56         ||    1 ||        1 ||
[17:06] <sconklin> || natty    linux-meta-ti-omap4               ||                      || 2.6.38.1209.7        ||    0 ||        0 ||
[17:06] <sconklin> || ---      linux-backports-modules-2.6.38    || 2.6.38-10.6          || 2.6.38-11.7          ||    0 ||        0 ||
[17:06] <sconklin> || ---      linux-firmware                    ||                      || 1.52.1               ||    0 ||        0 ||
[17:06] <sconklin> || ---      linux                             || 2.6.38-10.46         || 2.6.38-11.47         ||   18 ||       16 ||
[17:06] <sconklin> || ---      linux-ti-omap4                    ||                      || 2.6.38-1209.13       ||   10 ||       10 ||
[17:06] <sconklin> || ---      linux-meta                        || 2.6.38.10.25         || 2.6.38.11.26         ||    0 ||        0 ||
[17:06] <sconklin> ||
[17:06] <sconklin> ..
[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:06] <bjf> thanks everyone
[17:06] <bjf> #endmeeting
[17:06] <MootBot> Meeting finished at 12:06.
[17:06] <sconklin> thanks
[17:06] <kamal> thanks bjf
[17:07] <apw> bjf thanks