/srv/irclogs.ubuntu.com/2012/10/01/#ubuntu-meeting.txt

=== bazhang_ is now known as bazhang
=== philballew_ is now known as philballew
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== mmrazik is now known as mmrazik|lunch
=== mmrazik|lunch is now known as mmrazik
=== Quintasan_ is now known as Quintasan
=== doko_ is now known as doko
=== mmrazik is now known as mmrazik|otp
=== mmrazik|otp is now known as mmrazik
=== Quintasan_ is now known as Quintasan
=== philballew_ is now known as philballew
jdstrandhi!18:03
mdeslaur\o18:03
mdeslauro/18:03
mdeslaur\o18:03
jdstrandmdeslaur is eager to start, clearly :)18:04
jdstrand#startmeeting18:04
meetingologyMeeting started Mon Oct  1 18:04:29 2012 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.18:04
meetingologyAvailable 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 #votesrequired18:04
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting18:04
jdstrand[TOPIC] Weekly stand-up report18:04
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
jdstrandI'll go first18:04
jdstrandI'm in the happy place this week18:05
jdstrandI've been working on some lightdm apparmor fixes this morning for 12.10, and am almost done18:05
jdstrandI've got some pending updates that I am working on18:05
jdstrandthat's it from me18:05
jdstrandmdeslaur: you're up18:06
mdeslaurI just released software-properties updates18:06
mdeslaurand I have qemu-kvm and devscripts updates to test18:06
mdeslaurI'm on triage this week18:06
mdeslaurand I'm on community too18:06
mdeslaurwednesday, I have patch piloting18:06
mdeslaurand after that, I'll pick something else to poke at18:06
mdeslaurthat's it for me18:07
mdeslaursbeattie: you're up18:07
sbeattieI'm finally finishing up glibc testing, that will go out later today18:07
sbeattieAfter that, I'm moving on to apparmor stuff18:07
sbeattiewill pick up jjohansen's coredump testcase patch for quantal18:08
sbeattiethat's pretty much it for me.18:08
sbeattietyhicks: you're up (since micahg's off)18:08
tyhicksI have a libgssglue update to test and publish18:09
tyhicksI also need to attach a fix to the openssl bug I opened a couple weeks ago18:09
tyhicksIt isn't getting any attention upstream18:09
tyhicksBut there's two plausible, simple fixes for it18:09
* tyhicks will be sure to have that ready by at least mdeslaur's patch piloting on wednesday18:10
mdeslaurhrm :P18:10
tyhicksThen I'll be starting on apparmor stuff when I get the green light from jjohansen18:10
tyhicksmdeslaur: you're welcome ;)18:10
tyhicksjjohansen: that's it, you're up18:10
jdstrandheh18:10
jjohansentyhicks: green light18:10
tyhicksoh, nice! :)18:11
jjohansenSo I am dumping some docs, on tyhicks and sbeattie18:11
jjohansenand getting them moving on some apparmor items18:11
jjohansenI still have some fixing of the dbus parser patch so it works with 2.8 that I a plan to finish up today18:12
jjohansenI have a yama qrt failure to finish looking into18:12
jjohansenand more apparmor debugging18:12
jjohansenof the kernel.18:13
jjohansenI also need to push the current set of bug fixes upstream for 3.7 release window18:13
jjohansensarnold: your up18:14
jjohansenoh and I guess this is a short week for me I am off friday18:15
sarnoldI think I've got my buildenvironment and testenvironment all built; this week we'll find what I missed and hopefully get around to fixing some packages. :)18:15
sarnoldI'm also going to be paying attention to the community role, woo.18:15
sarnoldjdstrand: you're up18:15
jdstrand[TOPIC] Highlighted packages18:17
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
jdstrandThe 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.18:17
jdstrandSee 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.18:17
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/smsclient.html18:17
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/libyaml-libyaml-perl.html18:17
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/libdbd-pg-perl.html18:17
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/mcrypt.html18:17
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/otrs2.html18:17
jdstrand[TOPIC] Miscellaneous and Questions18:17
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
jdstrandThere are a lot of merge opportunities for packages listed in http://people.canonical.com/~ubuntu-security/d2u/. Performing these updates is a great way to help Ubuntu and bolster your developer application.18:17
jdstrandmdeslaur (or possibly jjohansen): I see some 'high' kernel CVEs. what is the status of those?18:18
jjohansenjdstrand: oh, hrmm I haven't checked this morning yet18:18
mdeslaurjjohansen: it's been at high for a while now18:19
mdeslaurCVE-2012-352018:19
ubottu** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-3520)18:19
mdeslaurit's in the -proposed kernel, so should be out soon18:21
mdeslaurjdstrand: ^18:21
jjohansenjdstrand, mdeslaur: yep18:21
jdstrandmdeslaur: awesome, thanks18:22
jdstrandDoes anyone have any other questions or items to discuss?18:22
sarnoldjdstrand: wrt the lightdm, one of our users was looking for a way to allow the guest profile to launch chromium-browser but not have the lightdm profile itself known about all the exceptions to its profile18:23
sarnoldjdstrand: this seemed like a reasonable idea to me, I've got a feeling that an #include <lightdm.d> may be useful for handling future cases similar to chromium-browser18:24
sarnolds/itself known/itself know/18:24
jdstrandsarnold: yeah-- I saw the bug. I am doing something similar18:25
jdstrandlightdm.d would be good, but I'd like to get upstream consensus on our .d directories. in the meantime, I have split out all of the lightdm rules into abstractions/lightdm. the guest and remote sessions can use that18:26
sarnoldjdstrand: cool :) (he wanted to pick up a bug he thought he could handle, but the nuances of named profile transitions are subtle enough that I think it makes sense for you to work on that one full-speed-ahead. But I did like his idea of isolating exceptions in their own pile of included files.18:26
jdstrandcause right now the freerdp and uccsconfigure profiles are profile copies18:26
jdstrandthen I am adding a separate lightdm_chromium-browser abstraction that will itself include the lightdm abstraction18:27
jdstrandbug it will have the additional rules to get chromium running18:27
sarnoldaha, that sounds good. :) Thanks18:27
jdstrandso we achieve the same. if we need another special-cased profile, then we can add the lightdm.d dir18:28
jdstrand#endmeeting18:32
=== 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
meetingologyMeeting ended Mon Oct  1 18:32:52 2012 UTC.18:32
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-01-18.04.moin.txt18:32
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-01-18.04.html18:32
sbeattiejdstrand: thanks!18:33
jdstrandmdeslaur, sbeattie, tyhicks, jjohansen, sarnold: thanks!18:33
mdeslaurthanks jdstrand!18:33
sarnoldthanks jdstrand :)18:33
jjohansenjdstrand: thanks18:33
=== yofel_ is now known as yofel
kees\o19:55
* stgraber waves19:56
brycehhiho19:56
pittibonne nuit mes amis19:57
cjwatsonHi19:57
cjwatsonDo we have a non-trivial agenda?19:58
pitti"New/MIR processing for new nvidia-experimental-NNN packages: bryce19:58
pitti["19:58
pittiAFAICS19:58
pitti(at first sight that sounds more like an operational problem though rather than policy)19:59
bryceh(it's a small point of clarification needed from last week's discussion, hopefully quick)19:59
keespitti: you can't trick me! you're not french! :)20:00
pittikees: j'apprends le français maintenant20:01
pittikees: c'est la faute de seb128 et duolingo.com :)20:01
keeshaha20:01
mdzhi20:02
pittiwho's chairing today? cjwatson chaired last time, so kees now?20:02
pittihey mdz20:02
keessure, I'm happy to do it.20:02
kees#startmeeting20:02
meetingologyMeeting started Mon Oct  1 20:02:25 2012 UTC.  The chair is kees. Information about MeetBot at http://wiki.ubuntu.com/meetingology.20:02
meetingologyAvailable 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 #votesrequired20:02
keeslooks like no action review20:02
keesso, let's move right along...20:02
kees[topic] New/MIR processing for new nvidia-experimental-NNN packages: bryce20:03
=== meetingology changed the topic of #ubuntu-meeting to: New/MIR processing for new nvidia-experimental-NNN packages: bryce
cjwatsonThere was one action but I did it20:03
cjwatson(Followed up to the lists)20:03
brycehthanks again for the new policy regarding the experimental drivers.20:03
keescool, saw that just now.20:03
keesbryceh: sure! seems like a good plan.20:03
brycehthe issue is that I think there was some uncertainty by reviewers on what that means, so in practice it has not been speeding things up very much.20:04
cjwatsonHave you actually had pushback, or is it just that all the reviewers are busy?20:04
pittinew processing seems to be rather simple to me, I guess these drivers look all alike?20:04
brycehbut the specific issue I need help with is when we get a new beta driver, it needs to go through several steps:  New review, MIR, then SRU20:04
cjwatsonThere's enough overlap between -sru and -release that release timing can cause issues20:04
pittiI don't see much purpose in an explicit MIR20:05
brycehwhat i'm finding is that while each review is quick, it can take several days to catch someone's attention and do the review.20:05
pittiwe don't usually do that for other cases either (libfoo2 vs. libfoo3 or so)20:05
brycehcjwatson, busy/vacation/offline yeah20:05
* soren stumbles in20:05
sorenSorry I'm late.20:05
pittiI had expected the cycle to be "upload to -proposed queue" and u-sru NEWs it into -restricted20:06
pittihey soren20:06
brycehanyway, currently it appears I need to go to three separate individuals to do the review steps.  It would be nice if one person (the SRU admin, ala RAOF) could handle all approvals in one go.20:06
cjwatsonSo, RAOF has technical access to do both NEW and SRU (normally he'd only process the UNAPPROVED queue, but there's nothing actually stopping him from doing NEW for a stable series and in this case it seems reasonable)20:07
cjwatsonI think then all we would need to do is agree that he has a class-action MIR?20:07
keesseems fine to me. I think that was the original intent, yes?20:08
cjwatsoni.e. that the "main" (well, restricted) review for the mainline nvidia/fglrx drivers covers these variants too20:08
cjwatsonDoes the package need to go into the development series as well as part of this?20:08
brycehcjwatson, yes we will always have the development series updated too.20:09
keesgood, yeah. I would have expected that to be happening.20:09
brycehalthough technically they're probably orthogonal since we move them back to nvidia-current on upgrade20:09
bryceher, move people back20:09
cjwatsonThat's a problem because in general -sru does not have any queue admin access to the development series20:10
cjwatsonIf the person you were dealing with were in -archive then this wouldn't be a problem though20:10
cjwatsonAnd actually RAOF is - not fully trained I think but he's expressed an interest in that and it's just waiting for me to get round to it20:10
cjwatsonIf I'm thinking of the right person20:10
pittibut I guess the time-sensitive part is actually precise-proposed?20:11
stgraberhaving RAOF do both the AA work for the current dev release and the SRU review would make sense as he's probably the one person who's the most clue about the package anyway20:11
brycehpitti, that's correct20:11
pittii. e. if the equivalent dev release NEWing takes some days longer, that's not a big deal?20:11
brycehhaving it in quantal is really only important in order to proceed with doing the SRU20:12
pittiif it helps archive/SRU folks, I wouldn't mind to extend the MRE with some verbiage about delegating the SRU NEWing for nvidia-* to ubuntu-sru20:12
brycehpitti, yeah, if we could do the precise-proposed and quantal as two separate processes then if getting it into quantal takes a while longer, that'd be ok20:12
pittiwe've had wholly new drivers SRUed without any dev release counterpart20:13
cjwatsonI think NEW authorisation where necessary for SRUs is implicit in the general delegation to -sru20:13
cjwatsonPersonally20:13
pittiit doesn't happen often (fortunately!), so I guess there's some uncertainty involved20:14
brycehok, thanks, yes it may be just that it needed some extra clarification what was permitted.  thanks20:15
keesdo we have a specific action to take out of this? update documentation?20:16
brycehkees, I have been documenting the process at https://wiki.ubuntu.com/X/DriverUpdates and will make sure it's clearly stated and referenced on that page20:17
keesbryceh: okay, that sounds good to me.20:17
cjwatsonYep, we don't seem to have any dissent here20:18
keesbryceh: did this cover everything for you?20:19
brycehkees, yes thank you!20:19
keescool20:19
kees[topic] Scan the mailing list archive for anything we missed (standing item)20:19
=== meetingology changed the topic of #ubuntu-meeting to: Scan the mailing list archive for anything we missed (standing item)
keesI don't see anything outstanding on the list. anyone see anything I'm not?20:20
pittineither do I20:20
sorenNope.20:20
stgrabernope20:21
kees[topic] Check up on community bugs (standing item)20:21
=== meetingology changed the topic of #ubuntu-meeting to: Check up on community bugs (standing item)
pittiI changed my mutt config to show  TB mail in a different color now, and nothing jumps at me :)20:21
keeswe have https://bugs.launchpad.net/ubuntu-community/+bug/174375 still showing, but it looks like we should unassign TB from it, based on discussion.20:21
ubottuLaunchpad bug 174375 in ubuntu-community "Distribution drivers permissions may need redesign" [Medium,Confirmed]20:21
kees(or mark it fix-released)20:22
keeswhat do others think?20:22
pittiI'd close it now20:23
pittiif there are specific issues left, they should get more focussed bugs20:24
cjwatsonYeah, let's close it.  We don't gain much from it at this point.20:24
keesdone.20:24
pittibut "may need redesign" sounds like a dead horse now20:24
kees[topic] Other business20:24
=== meetingology changed the topic of #ubuntu-meeting to: Other business
keesanything else we need to go over before picking the next chair?20:24
cjwatsonAs a point of reference, ~ubuntu-release now has queue admin access and still contains ~ubuntu-release-nominators (though that was mostly oversight), and to the best of my knowledge there's been zero abuse.20:24
pitti"There are currently no open bugs." \o/20:24
cjwatsonProbably because it's not exactly something you can run into by accident.20:24
keespitti: :)20:24
cjwatson(And if we cared, we could invert the team structure as I suggested, but I don't think I really care.)20:25
kees[topic] Select a chair for the next meeting20:26
=== meetingology changed the topic of #ubuntu-meeting to: Select a chair for the next meeting
keesokay, who's next?20:26
pittithat would be me, I think20:26
sorenI won't be able to make it.20:26
keesmdz, no?20:26
pittiOct 15 sounds ok20:26
stgraberyeah, as long as there's no abuse, status quo is fine. I'd still love to have that audit trail implemented though :)20:26
mdzI'm available October 15th I think20:27
pittiI'm going in the order at https://launchpad.net/~techboard/+members20:27
keesah!20:27
pittibut I don't mind much20:27
mdzbut pitti's suggestion is fine too ;-)20:27
pittiI'm just less sure about Oct 29, with UDS and such20:27
cjwatsonOct 15 is fine by me20:27
keesokay, we'll do first-name then, not nick. pitti it is20:27
mdzoct 29 is no problem for me20:27
cjwatsonOct 29 will be, er, either 2200 or 2300 at UDS (haven't looked up DST)20:28
pittiwelcome to my world :)20:28
cjwatsonWhich I doubt I can make20:28
pitti220020:28
cjwatson(My family will be with me so I don't think I'll be doing lots of late-night hacking)20:28
pittiassuming that we readjust back to winter time20:28
stgraberyeah, the UDS meeting seems rather unlikely to happen as we'll likely be busy with other things20:29
keesnice and quick meeting, just under 30 min. :)20:29
kees#endmeeting20:29
=== 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
meetingologyMeeting ended Mon Oct  1 20:29:46 2012 UTC.20:29
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-01-20.02.moin.txt20:29
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-01-20.02.html20:29
pittimerci kees, à demain!20:30
keeshehe20:30

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!