[16:33] <jdstrand> hi!
[16:33] <tyhicks> hello
[16:33] <jdstrand> #startmeeting
[16:33] <meetingology> Meeting started Mon Nov  4 16:34:17 2013 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:33] <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:33] <jdstrand> The meeting agenda can be found at:
[16:33] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:33] <jdstrand> [TOPIC] Announcements
[16:34] <jdstrand> Thanks to the following individuals:
[16:34] <jdstrand> Christian Biamont (christianbiamont) provided a debdiff for precise for xml-security-c (LP: #1192874)
[16:34] <jdstrand> Felix Geyer (debfx) provided debdiffs for precise-raring for libapache2-mod-fcgid (LP: #1238242)
[16:34] <jdstrand> Felix Geyer (debfx) provided debdiffs for precise-raring for ejabberd (LP: #1239307)
[16:34] <jdstrand> christianbiamont, debfx: Your work is very much appreciated and will keep Ubuntu users secure. Great job! :)
[16:34] <jdstrand> [TOPIC] Weekly stand-up report
[16:34] <chrisccoulson> hi!
[16:34] <jdstrand> I'll go first
[16:35] <jdstrand> I'm on triage this week
[16:35] <jdstrand> I've got quite a few things to catch up on from being at the sprint last week
[16:35] <jdstrand> also I need to process/communicate outcomes from sprint next week
[16:36] <jdstrand> in general, there shouldn't be any surprises for our team
[16:36] <jdstrand> nothing major was added to our plans for 14.04 and 14.10
[16:37] <jdstrand> I will be doing a click-apaprmor upload to sponsor a fix for cjwatson. I'm getting some CI testing going around click-apparmor which is why I haven't updated it yet
[16:37] <jdstrand> I hope to have that today or tomorrow at the latest
[16:38] <jdstrand> I know tyhicks wants me to sponsor an apparmor upload
[16:38] <jdstrand> I think that's it for me
[16:38] <jdstrand> mdeslaur: you're up
[16:38] <mdeslaur> hi! I'm on community this week
[16:38] <mdeslaur> I'm currently pushing out libav updates
[16:38] <mdeslaur> FYI, the libav and ffmpeg codebases have diverged to the point of it being unreasonable to track both using the same set of CVEs
[16:39] <mdeslaur> as such, I've updated the CVEs in the tracker
[16:39] <jdstrand> oh, interesting
[16:39] <jdstrand> mdeslaur: updated as in, updated the boilerplate?
[16:39] <mdeslaur> jdstrand: as in added README.libav, killing the boilerplate, and marking existing cves as ignored or not-affected for libav
[16:40] <jdstrand> cool
[16:40] <mdeslaur> we shouldn't track ffmpeg CVEs as affecting libav
[16:40] <jdstrand> I noticed libav is now in universe in trusty
[16:40] <sarnold> does kurt agree?
[16:41] <mdeslaur> tomorrow I'm off, and further down this week, I plan on finishing my merges and picking up some more updates
[16:41] <mdeslaur> sarnold: no idea
[16:41] <mdeslaur> sarnold: but the CVE descriptions never had "libav" in them
[16:42] <mdeslaur> and I can't track vulnerabilities/commits across them
[16:42] <mdeslaur> and libav is commiting a whole slew of independant security fixes now without asking for CVEs
[16:43] <mdeslaur> anyway, that's it from me
[16:43] <mdeslaur> sbeattie: you're up
[16:44] <mdeslaur> hrm, sbeattie seems to be MIA
[16:45] <tyhicks> I'll go
[16:45] <tyhicks> I'll wrap up a pending apparmor upload today and hand it off to jdstrand (thanks!)
[16:45] <tyhicks> Then I need to look into an ecryptfs/apparmor kernel bug that I hit last week
[16:45] <tyhicks> I also have some merges that I need to do
[16:46] <tyhicks> oh, and I need to look at enabling yama on the mobile kernels
[16:46] <tyhicks> that's it for me
[16:46] <tyhicks> jjohansen: you're up
[16:47] <tyhicks> sarnold: lets go to you
[16:48] <sarnold> hehe
[16:48] <sarnold> it appears I'm in my happy place again this week \o/
[16:49] <sarnold> I've been getting the hang of both canonistack and smo ser's virtual maas deployment scripts with an eye towards being able to do some maas update testing
[16:49] <sarnold> I've prepared new versions of the maas updates for release hopefully this week -- it depends if the -proposed updates have moved into the -updates queue yet or not.
[16:50] <mdeslaur> sarnold: \o/
[16:50] <sarnold> (bigjools had finished the last verification-needed test last week, so I hope the automated framework moved them through by now)
[16:50] <sarnold> mdeslaur: yeah, it'll be nice to finally cross these two off the list :)
[16:51] <jdstrand> which two?
[16:52] <sarnold> unfortunately smo ser's older script isn't his preferred testing method, and I had trouble getting the newer script to work, but I think his older script will work well enough for a starting point for documenting how the whole thing works..
[16:52] <sarnold> jdstrand: CVE-2013-1057 and CVE-2013-1058
[16:52] <jdstrand> ah, two CVEs, yes (I thought you were talking about source packages)
[16:52] <sarnold> ah :)
[16:53] <sarnold> once this is done I may do another MIR or pick up an update, depending upon mdeslaur's preference :)
[16:53]  * mdeslaur consults magic 8 ball
[16:53] <sarnold> chrisccoulson: your turn :)
[16:54] <chrisccoulson> chromium is up to date now (had mozilla updates last week as well)
[16:54] <sarnold> \o/
[16:54] <jdstrand> \o/
[16:54] <mdeslaur> chrisccoulson: woot!
[16:54] <chrisccoulson> this week i shall be helping get people up and running with oxide
[16:56] <mdeslaur> \o/
[16:56] <chrisccoulson> i'm currently trying to improve the workflow for maintaining the chromium patches in oxide. there were various issues at the end of last week
[16:56] <jdstrand> interesting
[16:56] <chrisccoulson> other than that, i'll be back on to the usual again :)
[16:56] <jdstrand> chrisccoulson: so, oxide made a big splash last week-- you should be getting the help now
[16:56] <chrisccoulson> jdstrand, excellent, thanks
[16:57] <chrisccoulson> jdstrand, you did a presentation didn't you?
[16:57] <jdstrand> I did
[16:58] <chrisccoulson> jdstrand,  how did that go?
[16:59] <jdstrand> chrisccoulson: well-- most everyone realized it was the plan of record
[16:59] <jdstrand> chrisccoulson: phonedations had a number of questions cause we hadn't brought them into the loop before that (though they were in the meeting in april and saw the emails on it stating it was the plan)
[17:00] <jdstrand> chrisccoulson: they've done quite a bit of work on qtwebkit to make sure it works well on armhf
[17:00] <chrisccoulson> ah, ok. although i can't imagine it working that well, with no jit ;)
[17:01] <jdstrand> chrisccoulson: and I imagine they will also start helping out soon (eg rsalveti). but like I said elsewhere-- getting you the armhf hardware and you can do some benchmarks marks to give to them
[17:01] <jdstrand> yeah, I don't have the details. you and rsalveti should definitely talk at some point though
[17:01] <chrisccoulson> yeah, that's cool
[17:01] <jdstrand> I want to update/form a new bp for oxide for this cycle
[17:02] <jdstrand> we can talk more about that this week
[17:02] <jdstrand> oh, yes, that is another thing I have to do-- work with mdeslaur and all of you on bps for vUDS
[17:03] <jdstrand> I don't know that we'll have an oxide session-- I think the work is known. we'll discuss later
[17:03] <jdstrand> chrisccoulson: did you have any other questions or anything else to report?
[17:03] <chrisccoulson> jdstrand, no, i think that's me done
[17:04] <jdstrand> [TOPIC] Highlighted packages
[17:04] <jdstrand> 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.
[17:04] <jdstrand> 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.
[17:04] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/openjpa.html
[17:04] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/flightgear.html
[17:04] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/sanlock.html
[17:04] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/rawstudio.html
[17:04] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/lighttpd.html
[17:04] <jdstrand> [TOPIC] Miscellaneous and Questions
[17:04] <jdstrand> Does anyone have any other questions or items to discuss?
[17:05] <jdstrand> mdeslaur, tyhicks, sarnold, chrisccoulson: thanks!
[17:05] <jdstrand> #endmeeting
[17:05] <meetingology> Meeting ended Mon Nov  4 17:06:23 2013 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-04-16.34.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-04-16.34.html
[17:06] <mdeslaur> thanks jdstrand!
[17:06] <tyhicks> thanks!
[17:07] <sarnold> thanks jdstrand :)
[19:02] <tumbleweed> !dmb-ping
[19:02]  * stgraber waves
[19:02] <tumbleweed> (not that it looks like we need a meeting)
[19:02]  * barry waves
[19:02] <barry> no utlemming again this time afaict
[19:03] <ScottK> o/
[19:03] <tumbleweed> he does appear to be on freenode, just not in here
[19:04] <utlemming> hi, I'm here
[19:04] <barry> awesome!
[19:05] <barry> bdrung: you're chairing today, if you're around
[19:10]  * bdrung comes around
[19:10] <bdrung> #startmeeting
[19:10] <meetingology> Meeting started Mon Nov  4 19:10:55 2013 UTC.  The chair is bdrung. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:10] <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
[19:11] <bdrung> no previous action items. let's begin with our applications.
[19:12] <bdrung> #topic Per Package Uploader Applications
[19:13] <bdrung> #subtopic Ben Howard applying for PPU for walinuxagent  and hv-kvp-daemon-init
[19:13] <bdrung> #link https://wiki.ubuntu.com/utlemming/PPUApplication
[19:13] <bdrung> utlemming: welcome. can you introduce yourself?
[19:13] <utlemming> hi, I'
[19:13] <utlemming> I'm Ben Howard and I spend my days in the cloud
[19:14] <utlemming> I rather enjoy working on Ubuntu and maintain those two packages, working with sponsors
[19:14] <utlemming> and I build the Cloud Images for Ubuntu
[19:15] <stgraber> so just a few random questions to get started ;)
[19:15] <stgraber> are you subscribed to ubuntu-devel-announce?
[19:16] <utlemming> er, I am not...but will be shortly :)
[19:16] <stgraber> good :)
[19:16] <utlemming> and done
[19:19] <stgraber> (sorry, trying to think about some clever questions, and failing at the moment ;))
[19:21] <stgraber> so those two packages are Azure specific, right? are there equivalents for other cloud platforms that you'll end up maintaining? or is Azure special in that regard?
[19:22] <utlemming> indeed, they are specific to Azure. The other package that I do a lot of work on is cloud-init. However, I lean on Scott Moser for that.
[19:22] <utlemming> there are no other packages at this time that I maintain as part of cloud work....and I would like to keep it that way. The goal is to put all that stuff into Cloud-init.
[19:24] <tumbleweed> utlemming: is walinuxagent something that we want to get into Debian too?
[19:25] <utlemming> tumbleweed: yes, and there is a version in Debian called waagent. However, I have been unssuccesful in working with the debian maintainer.
[19:26] <tumbleweed> oh, it's the same thing
[19:26] <utlemming> tumbleweed: our version, however, is much cleaner as we've made cloud-init to handle the majority of the work. So we do carry a delta.
[19:26] <tumbleweed> yeah, that's unfortunate
[19:27] <utlemming> tumbleweed: that said, I have worked with MS to get some our changes upstreamed, including carrying our init scripts and packaging to make maintance easier.
[19:28] <tumbleweed> does it make sense for ubuntu to have both walinuxagent and waagent? shouldn't we be dropping one or rebasing onto debian's package?
[19:29] <bdrung> at least the package name should be the same
[19:29] <utlemming> bdrung: if you look at the debian logs, they used our early version of the package to create waagent
[19:30] <barry> utlemming: can you go into any detail about the debian maintainer issues?
[19:31] <utlemming> barry: we introduced the intial version of the walinuxagent ~ 12.04 time frame, while walinuxagent was still having a lot of issues. I worked with MS to get those straigtened out. The Debian guys decided to package it, and introduced waagent based on our packaging. In the 12.10 and then 13.04 I reached out asking about merging the packages and removing the differences, which fell on deaf ears.
[19:33] <barry> utlemming: did they just not respond?  are the orig maintainers still interested in maintaining the package in debian?
[19:33] <tumbleweed> on a related topic, are you aware of the (fairly low traffic) debian-cloud list?
[19:33] <utlemming> barry: no response. I haven't followed up in while -- I intend on following up on that latter
[19:34] <utlemming> tumbleweed: yes, I am and I am on it
[19:34] <utlemming> tumbleweed: I even hang out on their IRC channel
[19:34] <barry> utlemming: cool
[19:34] <tumbleweed> ok. hopefully we can solve this some day
[19:34] <tumbleweed> but in the meantime, shouldn't we rename our walinuxagent source package? or remove waagent in Ubuntu?
[19:36] <utlemming> tumbleweed: that is a great question. waagent today exists as MS's originally saw it, while walinuxagent now requires cloud-init and uses cloud-init to behave like a cloud instance.
[19:36] <barry> tumbleweed: maybe schedule that for later in trusty if the issue can't be resolved in debian?
[19:36] <utlemming> tumbleweed: for cloud-images, we want them to behave like cloud-images and so we use walinuxagent + cloud-init.
[19:37] <stgraber> if our changes are a relatively clean set on top of upstream, then applying those on waagent instead (and killing walinuxagent) would make more sense
[19:37] <stgraber> if we've diverged to the point where we heavily change the upstream source tarball, then a separate source name isn't entirely unreasonable
[19:37] <utlemming> I can agree with that position. Mostly our changes are configuration changes.
[19:37] <stgraber> but we should then blacklist and remove waagent from the archive
[19:38] <bdrung> it depends what name is preferred. waagent or walinuxagent?
[19:38] <stgraber> well, whatever Debian uses is usually best, if only for dependencies
[19:38] <infinity> Am I fashionably late?
[19:38] <stgraber> infinity: no, just late ;)
[19:38] <utlemming> I would probably blacklist waagent, simply because it is a dangerous package. Part of packaging is to prevent it from hosing a system on installation.
[19:38] <infinity> ScottK asked me to pop in and repeat something I told him in private.
[19:38] <infinity> 12:19 <ScottK> Is utlemming ready for PPU rights for the Azure stuff?
[19:38] <infinity> 12:25 <infinity> I don't think I've had to fix any of his uploads for a while now, so probably.  As long as he's saying the right things about being sane and getting reviews.
[19:38] <infinity> So, there.   My work here is done. :)
[19:39] <ScottK> Thanks.
[19:39] <tumbleweed> thanks infinity
[19:39] <bdrung> maybe it would be good to file a bug against waagent in the BTS to ask for an opinion. either we should adopt the Debian name or Debian should adopt Ubuntu's name.
[19:39] <utlemming> I can take that as a work item for this cycle
[19:40] <bdrung> depending on the outcome, one of the two source package should be removed (and all needed changed applied to the remaining source package)
[19:41] <stgraber> oh, I guess I should also publicly state this since I've only done so in private to the board. I've been doing a fair amount of SRU review mostly of walinuxagent and haven't seen any problem with those so far. utlemming does a good job of getting all the right bits SRUed where it matters and keeping track of the state of Ubuntu Server on Azure.
[19:43] <bdrung> #vote Should Ben Howard get upload rights for walinuxagent and hv-kvp-daemon-init and get Ubuntu membership?
[19:43] <meetingology> Please vote on: Should Ben Howard get upload rights for walinuxagent and hv-kvp-daemon-init and get Ubuntu membership?
[19:43] <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)
[19:43] <stgraber> +1
[19:43] <meetingology> +1 received from stgraber
[19:43] <tumbleweed> +1
[19:43] <meetingology> +1 received from tumbleweed
[19:43] <barry> +1
[19:43] <meetingology> +1 received from barry
[19:43] <bdrung> +1
[19:43] <meetingology> +1 received from bdrung
[19:44] <infinity> utlemming: Congrats.
[19:44] <utlemming> :)
[19:44] <ScottK> +1
[19:44] <meetingology> +1 received from ScottK
[19:44] <bdrung> #endvote
[19:44] <meetingology> Voting ended on: Should Ben Howard get upload rights for walinuxagent and hv-kvp-daemon-init and get Ubuntu membership?
[19:44] <meetingology> Votes for:5 Votes against:0 Abstentions:0
[19:44] <meetingology> Motion carried
[19:45] <bdrung> utlemming: congrats.
[19:45] <stgraber> utlemming: so normally I'd grant you those rights immediatel,y however since I've expired from the technical board and no new board has been elected since, it'll take a little while.
[19:45] <stgraber> utlemming: I'll have to poke the Launchpad folks to figure out whether someone can cowboy the ACL in there for me ;)
[19:46] <utlemming> ack, sounds good
[19:47] <bdrung> utlemming: I consider having PPU + Ubuntu Membership to be more than Ubuntu Contributing Developer (which just grants recognition and Ubuntu membership). do you still want to become Ubuntu Contributing Developer?
[19:47] <utlemming> er, I think that PPU + Ubuntu Membership is fine
[19:48] <utlemming> I'll work towards MOTU next
[19:49] <bdrung> #topic Any other business
[19:49] <bdrung> anything else to discuss?
[19:50] <stgraber> nothing here
[19:50] <tumbleweed> nor here
[19:50] <barry> same
[19:50] <bdrung> okay.
[19:51] <bdrung> micahg will be the next chair (following our list)
[19:51] <bdrung> thanks for coming.
[19:51] <bdrung> #endmeeting
[19:51] <meetingology> Meeting ended Mon Nov  4 19:51:40 2013 UTC.
[19:51] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-04-19.10.moin.txt
[19:51] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-04-19.10.html
[19:51] <barry> thanks bdrung
[19:51] <bdrung> you're welcome.