=== doko_ is now known as doko === jodh` is now known as jodh [15:05] !dmb-ping [15:05] bdrung, ScottK, Laney, micahg, barry, tumbleweed, stgraber: DMB ping [15:05] * barry waves [15:06] * bdrung_work waves [15:06] * stgraber waves [15:06] if ScottK doesn't turn up, I guess I'm chairing [15:06] we're quorate [15:06] shall we start and he can take over if he turns up? [15:06] do we have anything? [15:07] that's a fair question [15:07] I saw ari moved his application [15:07] wgrant, if we don't move that to email [15:08] I didn't look at it yet, as promised [15:08] o/ [15:10] if you guys want to though, try and rustle him up [15:11] Laney implied that we wouldn't take that application today [15:11] but I wouldn't be against making an exception in this case [15:14] so I did my action item [15:14] I'll remove that from the agenda [15:15] the only other thing I want to say is to urge the rest of you to spend some time on the email applications [15:16] * tumbleweed promises to [15:18] you all have a DMB hour right now ;-) [15:19] this is true [15:50] amusingly, the meeting is actually in 10 minutes :P [15:50] no wait [15:50] my calendar is wrong WTF [15:51] http://fridge.ubuntu.com/calendars/ friiiiiiiidge [15:52] hrm, it was right in my calendar [15:52] fridge was wrong for me [15:52] yes, that too [15:53] aah, I copied it to my calendar while it was still right [15:53] then somebody changed the fridge [16:08] tumbleweed, Laney, micahg-work: DST changes make the fridge change. poke me at #ubuntu-news and I'll get it fixed now :) [16:32] \o [16:32] hi! [16:32] #startmeeting [16:32] Meeting started Mon Jan 13 16:32:21 2014 UTC. The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:32] 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:32] The meeting agenda can be found at: [16:32] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [16:32] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [16:32] I'll go first [16:32] hi! [16:32] I'm on triage this week [16:33] I'm working on several updates: openjdk-7 will either go out today or tomorrow. unfortunately, upstream dropped some arm assembly bits so the update wil regress on performance for arm [16:34] I'll do an SRU if they add them back, but I'm not particularly worried at this point because even with the assembly bits, the performance is not great [16:34] nothing much we can do about that [16:34] (ie, I don't think there is much performance sensitive openjdk arm out there) [16:34] yeah [16:35] I'm also working on openstack. I got slowed down a bit last week cause I had to start writing patches [16:35] I've also got work items as time allows [16:35] mdeslaur: you're up [16:35] I'm on community this week [16:35] I'm currently testing some updates [16:35] I'll be releasing memcached this afternoon [16:36] and have a couple more lined up, and will continue going down the list, etc. [16:36] that's it! [16:36] sbeattie: you're yp [16:36] I'm on apparmor this week [16:36] I need to do a bit more prep before discussing the userspace dfa stuff with jjohansen [16:37] I also need to do a bit of prep before the upstream meeting this week. [16:37] as well as continue the ongoing testing work and review of patches [16:37] that's it for me, tyhicks? [16:38] I'm preparing an apparmor trusty upload right now with dbus eavesdropping policy support and a stack of parser improvements from sbeattie and jjohansen [16:38] after that, I'll go back to kdbus [16:39] I need to triage a couple ecryptfs bugs this week [16:39] I've got a few other work items that I sprinkle in as time permits, but I'm not sure what I'll get to [16:39] that's it for me [16:39] jjohansen: you're up [16:42] I'm working on apparmor again this week. I've got some dfa test coordination with sbeattie, some upstream meeting prep to do, a bug to look at (sorry need to did the # back out), and more revisions on the ipc and stacking work [16:43] thats it for me [16:44] sarnold: your up [16:45] I'm in the happy place this week, though I've got some leftover bits of community that I didn't finish last week that I'll get to this week -- typo3-src, wireshark, and libotr2 updates [16:46] I've also got a MIR for beanstalk, currently that's blocking progress elsewhere, so that'll be a top priority this week [16:46] sarnold: fyi, currently it ftbfs according to foundations) [16:46] if there's time left over it'd be nice to get caught up on apparmorpatches again [16:46] jdstrand: oh that could complicate things :) thanks [16:47] I think it got reassigned to the server team [16:47] anyhoo, it's all in the bug [16:47] anyway I think that's it for me, chrisccoulson? [16:48] i'm working on oxide this week ;) [16:48] i've uploaded builds here now - https://launchpad.net/~phablet-team/+archive/ppa, although there's a couple of problems with these [16:48] (all builds crash if the egl libs aren't installed, and there's another runtime link error with the arm build) [16:49] should be fixed by http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/305 though [16:49] chrisccoulson: oh, both? [16:49] jdstrand, both issues? i'm currently working on the other one [16:49] chrisccoulson: ie, after r305 is built, then we'll have armhf builds? [16:50] I see [16:50] jdstrand, hopefully. i'm pretty determined to have a working arm build by tomorrow :) [16:50] that would be awesome :) [16:50] and then i shall be able to carry on with my other tasks [16:50] oh, i spent friday afternoon investigating bug 1267893. that was fun ;) [16:50] bug 1267893 in Oxide "Shutdown crash due to possible mesa race at startup" [Critical,Triaged] https://launchpad.net/bugs/1267893 [16:51] i think that's me done [16:52] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [16:52] The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. [16:52] See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. [16:52] http://people.canonical.com/~ubuntu-security/cve/pkg/ircd-hybrid.html [16:52] http://people.canonical.com/~ubuntu-security/cve/pkg/dcraw.html [16:52] http://people.canonical.com/~ubuntu-security/cve/pkg/znc.html [16:52] http://people.canonical.com/~ubuntu-security/cve/pkg/libtar.html [16:52] http://people.canonical.com/~ubuntu-security/cve/pkg/python-virtualenv.html [16:52] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [16:53] So, now that we've settled in after being away for the holidays, I was curious about the status of our major work [16:54] chrisccoulson: based on what you just said, it sounds like we'll have armhf builds this week (awesome). That should unblock that work for everyone, correct? can you comment on when you think benchmarking, CI and uploads to Ubuntu will happen? [16:56] * jdstrand notes that feature freeze is Feb 20th, and our oxide and apparmor work fall under that [16:57] * jjohansen runs screaming back to bed [17:00] ok, we'll come back to chrisccoulson later [17:01] oh, sorry, i was talking in another channel [17:01] armhf builds this week - yes [17:01] uploads to ubuntu - i'm waiting on qt5.2 landing for that [17:02] CI - i need to respond to an email for that actually :) [17:02] and benchmarking can start whenever i guess [17:03] chrisccoulson: once the armhf builds work-- can you run the benchmarks on armhf for oxide and qtwebkit and send them to the the phablet list? (phablet because the builds aren't in a public ppa yet) [17:04] jdstrand, sure, no problem [17:04] chrisccoulson: the test-oxide click package has the links to some identified benchmark testsuites from conversations from months ago [17:04] so I think it is just a matter of installing that and clicking on the links [17:04] chrisccoulson: thanks [17:05] [ACTION] chrisccoulson to benchmark oxide and qtwebkit once armhf builds work [17:05] ACTION: chrisccoulson to benchmark oxide and qtwebkit once armhf builds work [17:05] [ACTION] chrisccoulson to send results of benchmarks to list [17:05] ACTION: chrisccoulson to send results of benchmarks to list [17:06] tyhicks: as for apparmor and the emulator-- your apparmor upload you are preparing-- is that all that is needed to turn on apparmor in the emulator? [17:06] jdstrand: yes, that should be all that is needed [17:07] (obviously, there will be one other upload to remove the apparmor=0 from the boot args) [17:07] yeah [17:07] thanks [17:08] tyhicks: what is the status of the yama work? [17:09] jdstrand: the work itself is all done - I have been trying to find a way to run the autopilot tests with yama enabled [17:09] jdstrand: I saw an email to the phone list last week that said that the autopilot tests now pass in the emulator, so that's promising [17:10] tyhicks: you might coordinate with xnox (he has been working on emulator working with autopilot) and perhaps sergiusens and/or the qa team [17:10] yeah [17:11] tyhicks: you mentioned the kdbus investigation will be picked up again this week. I'm guessing there isn't anything new to report since the last meeting on it? [17:12] jdstrand: no, nothing really new at the moment [17:12] ack [17:14] jjohansen, sbeattie: I've seen lots of patches on different apparmor related items (which is great! the parser improvements in particular are going to really help the emulator work) but I'm not clear on the status of ipc and stacking. aiui from previous meetings, ipc should land first, with stacking later. [17:14] jjohansen, sbeattie: I know sbeattie is working on testing, etc to support jjohansen's work-- how are we on ipc? on stacking? [17:15] jdstrand: they are in the your machine will die in a firey oops state atm [17:15] (for the feature and its testing) [17:17] jdstrand: I am trying to get something up to a ppa this week but, there is no point if you can't even boot it [17:17] jjohansen: ok. so, are these just bugs (that granted, may take some time to fix) or is it more than that? (eg, design, implementation, etc to be done) [17:18] there is design iteration and some implementation to be done [17:18] ok. ack on not uploading broken stuff to the ppa [17:18] thanks for the updates [17:19] Does anyone have any other questions or items to discuss? [17:23] mdeslaur, sbeattie, tyhicks, jjohansen, sarnold, ChrisCoulson: thanks! [17:23] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [17:23] Meeting ended Mon Jan 13 17:23:56 2014 UTC. [17:23] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-01-13-16.32.moin.txt [17:23] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-01-13-16.32.html [17:23] thanks jdstrand [17:23] thanks jdstrand! [17:23] thanks! [17:24] thanks jdstran [17:24] thanks, jdstrand === fire is now known as hack === Guest87464 is now known as ayan