=== Amaranth_ is now known as Amaranth === robbiew1 is now known as robbiew === Claudinux_ is now known as Claudinux === deegee_ is now known as plustwo === ogra_ is now known as ogra === jelmer_ is now known as jelmer === shadeslayer is now known as kshadeslayer === zul_ is now known as zul === Quintasan_ is now known as Quintasan === yofel_ is now known as yofel [15:57] hi ara! [15:57] hello marjo [15:59] hi ara, marjo, pitti :) [16:00] heh, gangs all arriving. [16:00] looks like we can get an on time start as the first few are here. :) [16:00] #startmeeting [16:00] Meeting started at 10:00. The chair is skaet_. [16:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:00] Thank you to everyone who helped get 10.04.2 out the door! [16:01] This meeting will focus on the SRU interlocks and hand offs, and looking at where we are, and what's needed to get back in the cadence groove again. [16:01] [TOPIC] Kernel SRU status - sconklin [16:01] New Topic: Kernel SRU status - sconklin [16:01] Current status: [16:01] Testing for ec2 kernels has not been completed, so [16:01] we held off uploading new kernels to build on [16:01] Friday. I am waiting for more information about [16:01] the ec2 failures but the last status I know is: [16:01] Lucid ec2 was thought to have a problem, but I have [16:01] been told on irc that it's OK. However, the tracking [16:01] bugs have not been updated, and until we get a definite [16:01] resolution, we'll hold off preparing th enext Lucid [16:01] kernels. [16:02] Maverick apparently does have a problem, but it turns [16:02] out that it may be a regression that appeared several [16:02] releases ago. I'm also waiting for more information [16:02] about testing results for this. If it turns out that [16:02] this is the case, we will have to decide whether to [16:02] go ahead and ship this kernel with the known bug [16:02] which is already in the field, or to hold Maverick [16:02] updates until the root cause is found. Since [16:02] Maverick ec2 kernels are a flavour built from the [16:02] master branch for Maverick (i.e. there is not a [16:02] separate ec2 source base), any hold to Maverick [16:02] must apply to all Maverick kernels other than [16:02] ARM. [16:02] I expect further updates on the ec2 kernels today. [16:02] Source packages have been prepared for upload for [16:02] Dapper, Hardy, and most of Karmic, and are ready [16:02] for building on the kernel PPA. We will wrap up [16:02] the rest of the Karmic packages today, and wait [16:02] to proceed until we know about Lucid and Maverick [16:02] ec2. [16:02] .. [16:02] o/ [16:03] go ara === hakimsheriff_ is now known as hakimsheriff [16:03] when are you taking the go-no go decision? who is doing the further testing on those? [16:04] I'm awaiting a status report from Stefan Bader about the ec2 kernels, should have it very soon and then will circulate that by email. He's testing right now [16:04] o/ [16:05] sconklin: please let me know once the decision has been made [16:05] .. [16:05] vanhoof: Will do. [16:05] sconklin, OK, thanks. Please update the tracking bugs as well, there are people subscribed that will be interested [16:05] sconklin: can you list the explicit tracking bugs that we should all be following? [16:05] .. [16:05] .. [16:06] I'm not sure of the bugs releted to the specific failures in ec2. [16:06] The master tracking bugs are all listed here: http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html [16:06] skaet: QA team is tracking this one for Maverick: [16:06] bug 725089 might be one, that's the bug we found during our testing: [16:06] Launchpad bug 725089 in linux (Ubuntu) "QRT test-kernel-security causes kernel panic on EC2 AMD64 image" [High,New] https://launchpad.net/bugs/725089 [16:06] .. [16:07] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/725089 [16:07] Ubuntu bug 725089 in linux (Ubuntu) "QRT test-kernel-security causes kernel panic on EC2 AMD64 image" [High,New] [16:07] o/ [16:08] sconklin: that bug is assigned to jjohansen, is he the correct assignee? [16:08] marjo: Yes [16:08] sconklin: the wiki pages has a lot of bugs listed, and it isn't clear to me on it which ones the status tracking are going on in. [16:08] sconklin: ack [16:09] which specific one for maverick and lucid should I be looking at for this cycle? [16:09] skaet_: you can tell from the bug title: [16:09] linux: 2.6.32-29.58 -proposed tracker [16:09] for example. That's the master tracker for the -proposed kernel [16:09] skaet_, if you look at the Maverick section, the one with the big red X icon next to it is the tracking bug which has a failure on it [16:10] 723335 linux: 2.6.35-27.48 -proposed tracker [16:10] 716532 linux: 2.6.35-27.47 -proposed tracker [16:10] I think that th etracking bugs for ec2 should have been set to verification-failed, but they weren't [16:10] 709352 linux: 2.6.35-26.45 -proposed tracker [16:11] there are mulitple proposed trackers, which should be used, and when? [16:12] skaet, you match the version in the title with the version in proposed [16:12] which is just above the bugs for that kernel on the same page [16:14] sconklin, bjf - will work with you offline then on the subject. I do see now, but think if I'm confused, others probably are as well. [16:14] any other questions? [16:15] [TOPIC] HW certification - ara [16:15] New Topic: HW certification - ara [16:15] hello again :) [16:15] :) [16:15] Our testing results for both Maverick and Lucid are going very well. As usual the reports can be found at [16:15] [LINK] http://people.canonical.com/~hwcert/sru-testing/current/ [16:15] LINK received: http://people.canonical.com/~hwcert/sru-testing/current/ [16:15] There are some desktops that are misbehaving, and we are troubleshooting them now, but nothing indicates so far that those could be kernel regressions. [16:15] o/ [16:15] Anyway, we will be updating the tracking bugs today, with all this information. But so far, thumbs up from us. [16:16] Also, tomorrow I won't be able to attend the Kernel meeting, sconklin, but the tracking bugs will be updated from us by then. [16:16] .. [16:16] ara: thx, looking forward to it [16:16] ara: ack [16:16] brendand: go [16:16] re: misbehaving desktops, they are behaving better now :) [16:17] ara and brendand, thanks! [16:17] [TOPIC] QA status - marjo [16:17] New Topic: QA status - marjo [16:17] hi folks [16:18] * Hardy testing done [16:18] https://wiki.ubuntu.com/QATeam/KernelSRU-hardy-2.6.24-28.84 [16:18] * Lucid and Maverick testing [16:18] - Lucid completed. lucid https://wiki.ubuntu.com/QATeam/KernelSRU-lucid-2.6.32-29.58 [16:18] - Maverick – regression found https://wiki.ubuntu.com/QATeam/KernelSRU-maverick-2.6.35-27.48 [16:18] - Bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/725089 assigned to jjohansen [16:18] .. [16:18] Ubuntu bug 725089 in linux (Ubuntu) "QRT test-kernel-security causes kernel panic on EC2 AMD64 image" [High,New] [16:19] Thanks marjo [16:19] o/ [16:19] skaet_ go ahead?! [16:19] how is this week going to work with alpha3 coming out for your team in terms of the new maverick kernel showing up? [16:20] skaet_ will be challenging :) [16:20] marjo: ack [16:20] any other questions? [16:20] skaet_ hggdh will be most affected, i.e. server ISO testing [16:21] marjo, you are doing iso testing this week ? [16:21] bjf, yes, alpha 3 comes out on March 3rd. [16:21] bjf: yes, natty alpha 3 is due this thursday [16:22] marjo, next week will be the week for qa regression on a new maverick [16:22] bjf: you seem surprised? [16:22] marjo, not at all surprised [16:22] bjf: yes, we will be available again for SRU kernel testing next week (after alpha3 is out) [16:23] marjo, then i don't see where the conflict is between iso testing and maverick -proposed testing [16:23] [TOPIC] general SRU status - pitti [16:23] New Topic: general SRU status - pitti [16:23] nothign really noteworthy here, as we don't have a coming deadline for a point release [16:23] :) [16:24] how are the SRU validation backlogs doing? [16:24] lucid still looks okay, as we flushed it for .2 [16:25] we have some 3 or 4 proposed packages which are very old [16:25] * skaet_ nods [16:25] (but that isn't unusual either) [16:25] I usually give a warning for them in the bugs after half a year, and kill them from -proposed after another month [16:26] ok, wasn't sure of the pattern, and some did look a bit old. [16:26] but that affects stuff like eclipse in lucid, not core things like eglibc [16:26] thanks pitti. [16:26] ..? [16:27] .. [16:27] thanks, sorry was commenting in the flow. [16:27] any other questions? [16:27] [TOPIC] OEM priorities - vanhoof [16:27] New Topic: OEM priorities - vanhoof [16:28] heh [16:28] :) [16:28] news to me [16:28] current -proposed, or next cycle? [16:28] next cycle [16:28] was the though, but if you've got concerns right now, feel free to raise. [16:29] we may have an interesting i915 patch, which needs a bit more testing, and then proper review ... that is the most pressing thing on my plate at the moment [16:29] I'll know more once we get a bit more testing done [16:29] as for the current -proposed, we're in good shape, just monitoring the release as it holds a few key bug fixes within it [16:29] .. [16:30] thanks vanhoof! questions? [16:30] [TOPIC] Support priorities - martins [16:30] New Topic: Support priorities - martins [16:30] just sent you a long list [16:30] but for now, the status of the likewise open [16:31] need to fix my id, this is martins [16:31] likewise open? [16:31] https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/534629 [16:31] Ubuntu bug 534629 in likewise-open (Ubuntu Lucid) "AssumeDefaultDomain does not work" [Undecided,New] [16:32] yes, looks like it is commited [16:33] I just need to understand if it will go into the next point release [16:33] make sense? [16:33] Guest78155, can we get its priorities set so it gets into the right focus queues? [16:34] skaet_: sure I will have it adjusted [16:34] thanks! in addition to importance, please make sure its targetted to milestone 10.04.3. [16:35] skaet_: I have a few others that I will want to cover with you off line, that is the one that I am tracking now [16:35] skaet_: sure will do [16:35] Guest78155, sounds good. Will work with you on it off line. [16:35] thanks for letting us know which is on your hot list. [16:36] any other questions? [16:36] [TOPIC] New business, last chance for general questions? - all [16:36] skaet_: not now, I am good [16:36] New Topic: New business, last chance for general questions? - all [16:36] o/ [16:36] ara: go [16:37] in the StableReleaseCadence documentation the tag documented for tracking bugs is kernel-tracking-bug, but lately they have been tagged as kernel-release-tracking-bug [16:37] which one is the correct one? [16:37] sconklin, bjf ^^ ? [16:37] ara, kernel-release-tracking-bug, i'll update the doc [16:37] bjf, thanks :) [16:38] * skaet_ looks around for any other questions? [16:38] Thanks sconklin, bjf, marjo, ara, pitti, vanhoof, martins. [16:38] #endmeeting [16:38] Meeting finished at 10:38. [16:39] see ya skaet_ [16:39] thanks skaet_! [16:39] skaet: thx [16:40] thanks again, will put out minutes for this meeting, and get an agenda present out for the next one. [16:40] minutes will be tomorrow though. === dholbach_ is now known as dholbach === Craig_Dem_ is now known as Craig_Dem === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk [18:11] o/ [18:11] o/ [18:11] * sbeattie waves [18:12] hello [18:12] \o [18:12] \o [18:13] alrighty, let's get started [18:13] #startmeeting [18:13] Meeting started at 12:13. The chair is jdstrand. [18:13] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:13] The meeting agenda can be found at: [18:13] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:13] LINK received: https://wiki.ubuntu.com/SecurityTeam/Meeting [18:13] [TOPIC] Review of any previous action items [18:13] New Topic: Review of any previous action items [18:13] there aren't any ACTION items from last week, but I did want to follow up with sbeattie regarding openjdk [18:14] sbeattie: are you getting the help needed from doko for the update? === Ursinha-afk is now known as Ursinha [18:15] jdstrand: we're poking at it, yes; though as I mentioned elsewhere, I'm somewhat inclined to release the openjdk-6 packages I have, that built everywhere except ppc/karmic, and work with doko to resolve the build failure there and the 6b18 arm build failures. [18:16] sbeattie: that sounds reasonable [18:16] but I can poke a little harder at doko's hack first. [18:17] sbeattie: how severe are the vulns? specifically, is it worth haing the supported arch' users wait on ppc? [18:17] s/haing/having/ [18:18] jdstrand: one of the vulns is the magic large number DoS (similar issue that php5 experienced), there's at least one security manager bypass issue. [18:18] * jdstrand nods [18:19] fyi, chromium wants to put a floor on the minimum version of openjdk of 1.9.7, and expects to do that with the chromium 10 release. [18:19] I'm inclined to skip ppc this time [18:19] I'd really like to get fixes out to the supported arch users. [18:19] eek [18:19] micahg: ^ [18:19] :( [18:19] kees: that... will be a problem on arm. [18:19] jdstrand: actually, not an issue, lucid+ will have that with sbeattie's updates [18:19] sbeattie: I suspect arm will have lots of problems beyond just that :) [18:19] sbeattie: ack [18:20] (assuming I ever release something :-( ) [18:20] micahg: ah, good [18:20] sbeattie: I think we've got at least one more release before chromium 10 [18:20] sbeattie: I appreciate all the time and effort you've put into this [18:20] * jdstrand hugs sbeattie [18:21] anyway, it came up with a conversation I was having with chris evans [18:21] sbeattie: is there anything that can be added to https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures so that it would be easier next time? eg, so that we don't lose knowledge, etc [18:21] kees: is chris evans the google chromium security guy? [18:21] * jdstrand can't remember off-hand [18:22] jdstrand: yes, I can document how to put together the orig tarball, though that's not been the source of the issue with this update. [18:22] sbeattie: perhaps added to QRT/notest_testing if that makes more sense [18:23] sbeattie: ok. I think that would be a good idea [18:23] sbeattie: whenever you get a chance [18:23] jdstrand: no, that's... someone else. who's name I'm blanking on. this is http://scarybeastsecurity.blogspot.com/ [18:23] jdstrand: will do. (feel free to add it as an action item) [18:23] kees: ah right. duh [18:24] [ACTION] sbeattie to update https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures and/or QRT for openjdk tarball generation, build instructions, etc [18:24] ACTION received: sbeattie to update https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures and/or QRT for openjdk tarball generation, build instructions, etc [18:24] sbeattie: thanks [18:24] [TOPIC] Weekly stand-up report [18:24] New Topic: Weekly stand-up report [18:24] I'll go first [18:24] I'm in the happy place this week [18:25] I've got archive-admin work for alpha3 [18:25] some more libvirt sponsoring [18:25] tbird and chromium testing on amd64 [18:25] QRT updates for apparmor and libvirt [18:25] more investigation of changes auditing [18:25] and investigate a reported ufw logging issue [18:25] basically a bunch of random stuff :) [18:26] I'll pick up an update if I've got time, but I am not optimistic this week [18:26] that's it from me [18:26] kees: you're up [18:26] okay, spent a while working on upstreaming lkml things, adding more qrt tests for them, docs, etc. [18:26] this week I'm on triage. [18:27] that's really about it from me. [18:28] kees: is that s/spent/spend/? [18:28] jdstrand: I was reporting last week, yes. spent [18:28] ah [18:29] k [18:29] jdstrand: this week I'd like to work on gcc testsuite updates but I always say that. [18:29] ok [18:29] mdeslaur: you're next [18:30] I'm currently publishing samba, clamav and fuse [18:30] and then will work on ffmpeg, and some more from the list [18:31] I have an embargoed issue or two to look at [18:31] and will do some iso testing this week [18:31] that's about it! [18:31] sbeattie: tag, you're it [18:33] I'm on community this week; I was on triage last week; I fell a bit behind on bug triage (sorry kees!) so will try to help catch up on that this week. [18:33] jdstrand: evan martin is the guy from UDS. [18:33] ah yes [18:33] micahg: you might try to get in contact with him ^ [18:33] sbeattie: no worries :) [18:33] micahg: I was unsuccessful [18:34] jdstrand: ACK [18:34] micahg: well, I may have contacted him, I don't know. He never contacted me back :) [18:34] I have the whole openjdk issue (already discussed) and a logwatch update underway [18:35] * jdstrand notes that sbeattie got apparmor 2.6 released and uploaded to natty last week [18:35] I also released the upstream apparmor 2.6.0 tarball, merged that into natty (with jdstrand's review and sponsorship), but I need to formally announce it. [18:35] hehe [18:35] jdstrand: heh [18:36] sbeattie: I didn't think you were going to mention it! [18:36] :) [18:36] I also need to do a similar release for 2.5.2. [18:36] I think that's it for me. [18:37] sbeattie: fyi, the binaries haven't hit the archive cause an archive admin other than me needs to deNEW it (hung on the new python-libapparmor) [18:37] * sbeattie should probably schedule an upstream apparmor meeting. [18:37] jdstrand: oh, okay. do we think they'll get approved by alpha 3? [18:37] sbeattie: would you mind poking an AA today so it can get deNEWed in time for alpha3? [18:38] jdstrand: sure, can do. [18:38] sbeattie: well, the should be, but I want to make sure they are [18:38] sbeattie: thanks! [18:38] I'm pretty excited about the python bindings [18:38] alpha3 freeze is in 4.5 hours, so I would suggest that happen sooner rather than later if you want it in [18:38] micahg: well, it is already uploaded from 4 days ago, so the aa *should* do it [18:39] but yeah [18:39] sooner than lator [18:39] jdstrand: me too! Especially given the last minute tweaking I had to do to get them to work at all. [18:39] heh [18:41] if sbeattie doesn't have any more, micahg, you're up [18:41] yep, all done. [18:41] Chromium/Firefox/Thunderbird updates [18:41] upgrading to natty [18:42] still have a few setup items to do [18:43] I think that's it [18:43] cool [18:43] * micahg also needs to get up to speed on webkit [18:45] great, mdeslaur can brain-dump on you [18:45] that sounded kinda wrong [18:45] anyhoo [18:45] [TOPIC] Miscellaneous and Questions [18:45] New Topic: Miscellaneous and Questions [18:45] does anyone have any other questions or items to discuss? [18:46] nope! [18:46] * sbeattie eyes jjohansen nervously. [18:47] hehe, problem solved boring technical paper to follow [18:47] :) [18:47] jjohansen: heh, cool. Technical papers are good. [18:47] jjohansen: mentioned ealier. do you think we should have an apparmor upstream meeting this week? [18:47] yeah, it might be a good idea [18:48] start planning for 2.7/3.0 [18:48] cool, we can do that in #apparmor [18:48] (schedule it that is) [18:48] yep [18:49] ok [18:49] thanks kees, mdeslaur, sbeattie, micahg and jjohansen! [18:49] #endmeeting [18:49] Meeting finished at 12:49. [18:49] thanks jdstrand! [18:50] jdstrand: thank you! [18:50] sure thing :) [18:50] thanks jdstrand [18:50] thanks! [18:50] :) [19:04] geser: is the dmb meeting tonight, as mentioned on te agenda? [19:05] kklimonda: yes (if we get quorum) [19:05] \o [19:05] * stgraber waves [19:05] o/ [19:06] kklimonda: sup [19:07] bdrung_, cody-somerville, persia, maco: DMB meeting [19:08] * cody-somerville is here. [19:08] hi [19:09] o/ [19:11] if I didn't miscount, then we are quorate === Ursinha is now known as Ursinha-lunch [19:11] Laney: around? [19:11] i can only stay for a little whil... at what point is the meeting postponed? [19:12] any volunteers for chair? [19:12] maco: Iain mailed the DMB list that he can't today [19:12] o/ [19:12] oh ok [19:12] im still not on that list [19:12] o/ i couldn't make it earlier [19:14] #startmeeting [19:14] Meeting started at 13:14. The chair is geser. [19:14] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [19:14] * cody-somerville has a nose bleed, afk. [19:14] [TOPIC] Review of previous action items [19:14] New Topic: Review of previous action items [19:14] * Emmet Hikory to organise the selection process for DMB renewal [19:15] the voting is done [19:15] but I don't know how far Emmet is with organizing the take-over of the DMB mailing list (will try asking him) [19:16] and I don't remember seeing an official announcement of the new DMB (will ask him about it too or do it myself) [19:16] anything else regarding the new DMB? [19:17] [TOPIC] Administrative Matters [19:17] New Topic: Administrative Matters [19:17] * Review progress of probationary period of Marco Rodrigues [19:18] as cody-somerville went afk we have to defer it for later [19:18] [TOPIC] MOTU Application: Sylvestre Ledru [19:18] New Topic: MOTU Application: Sylvestre Ledru [19:19] is Sylvestre Ledru here? [19:21] ok, looks like we have to defer it to e-mail [19:22] [TOPIC] core-dev application: Dave Walker [19:22] New Topic: core-dev application: Dave Walker [19:22] [LINK] https://wiki.ubuntu.com/DaveWalker/DeveloperApplication [19:22] LINK received: https://wiki.ubuntu.com/DaveWalker/DeveloperApplication [19:22] o/ [19:23] a first question was already done during the last meeting [19:23] Yes [19:23] I was interviewed in the last meeting [19:24] [LINK] http://irclogs.ubuntu.com/2011/02/14/%23ubuntu-meeting.html#t12:28 [19:24] LINK received: http://irclogs.ubuntu.com/2011/02/14/%23ubuntu-meeting.html#t12:28 [19:24] i have no questions === bdrung_ is now known as bdrung [19:25] someone have any questions? or are all still reading? [19:25] * cody-somerville is reading. [19:26] * stgraber is reading the log [19:26] Daviey, What upload permissions do you already have? [19:27] cody-somerville, mythbuntu-dev [19:27] ah, right. [19:27] last timei polled [19:27] http://erk.daviey.com/ubuntu-archive-access.txt [19:27] LINK received: http://erk.daviey.com/ubuntu-archive-access.txt [19:29] need to keep the cadbury eggs away? [19:29] eek. [19:29] ok, done reading the log [19:31] done reading [19:31] any questions or are we ready for voting? [19:32] Daviey, Becoming a Ubuntu Core Developer is more than just about upload rights - Its a leadership position. What are the most important values and ethics you demonstrate as a leader? Give me an example of these in practice. [19:32] cody-somerville, Good question. [19:32] It's about taking responsibility for your actions... thinking of other teams [19:33] That is, don't upload something before speaking with others it might cause woe to. [19:33] If you break something, ,make sure you notify people if needed... fix it [19:33] does this also apply to MOTU? [19:33] or give someone else enough information to fix it themselves [19:34] geser, yes.. because Universe isn't just MOTU :) [19:34] but equally, some packages have people who are essentially maintainers.. it would be rude and potentially damaging to not at least speak to them first [19:34]