14:34 #startmeeting Weekly Main Inclusion Requests status 14:34 Meeting started at 14:34:03 UTC. The chair is cpaelzer. Information about MeetBot at https://wiki.ubuntu.com/meetingology 14:34 Available commands: action, commands, idea, info, link, nick 14:34 Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe ) 14:34 o/ 14:34 #topic current component mismatches 14:34 Mission: Identify required actions and spread the load among the teams 14:34 #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg 14:34 #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg 14:35 jamespage: that is still the set of openstack cases 14:35 jamespage: you can be happy that we are so far away from any freeze, so it isn't urgent 14:35 but I kind of get deja-vu seeing it every week 14:35 cpaelzer: IIRC it was delegated to some people from his team. 14:35 I have volunteers to work the MIR for those - I will raise them and assign so its clear 14:35 I thought so as well, but expected to have bugs by now then 14:35 perfect 14:35 Maybe a dummy LP bug should be created and linked, so that we don't have to go over that every week 14:36 let me throw you two bugs then jamespage 14:36 and you can assign as you go with them 14:36 thanks - I'll push them out accordingly 14:36 uh 14:36 they exist 14:36 but are not picked up 14:36 that'll just change the section of the meeting, no? :) 14:36 checking ... 14:36 https://bugs.launchpad.net/ubuntu/+source/python-typeguard/+bug/2068033 14:36 https://bugs.launchpad.net/ubuntu/+source/typeshed/+bug/2068035 14:37 I supposed ~ubuntu-mir needs to be subscribed? 14:37 yep, done by now 14:37 sarnold: yeah, but if it's a bug stating "TBD", we can just skip over it without thinking about it :) 14:37 nothing else in this list for today 14:38 exactly @slyon 14:38 We had wsdd come into the queue earlier, but I grabbed and handled it as seb128 asked for this to go to security asap 14:38 which it is by now 14:38 #topic New MIRs 14:38 Mission: ensure to assign all incoming reviews for fast processing 14:38 #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir 14:38 none 14:38 \o/ 14:38 #topic Incomplete bugs / questions 14:38 Mission: Identify required actions and spread the load among the teams 14:39 #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir 14:39 last update was on https://bugs.launchpad.net/ubuntu/+source/libpanel/+bug/2066272 which was a review done 14:39 nothing else that is super recent 14:39 * slyon is afraid that things are feeling too calm this (early) cycle 14:39 hehe 14:39 AFAICS many teams do more 24.04.x work, so it won't show here for oracular 14:39 but in e.g. increased SRU activity 14:39 but that is gut feeling, not data 14:40 yeah libpanel has some TODOs for jbicha 14:40 yep 14:40 wsdd also had some needs (as expected) 14:40 but ok in general 14:40 tests not running properly, otherwise LGTM 14:40 #topic Process/Documentation improvements 14:40 Mission: Review pending process/documentation pull-requests or issues 14:40 #link https://github.com/canonical/ubuntu-mir/pulls 14:40 #link https://github.com/canonical/ubuntu-mir/issues 14:40 https://github.com/canonical/ubuntu-mir/pull/60 tries to address https://github.com/canonical/ubuntu-mir/issues/59 14:41 have a look, if we can get 1-2 +1 I can merge right away 14:42 +1 14:42 Thanks, anyone still reading or should I merge (this is a fairly calm change, just clarifying better) 14:43 +1 14:43 thanks, merged 14:43 #topic MIR related Security Review Queue 14:43 Mission: Check on progress, do deadlines seem doable? 14:43 Some clients can only work with one, some with the other escaping - the URLs point to the same place. 14:44 #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir 14:44 #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=[MIR]&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir 14:44 Internal link 14:44 - ensure your teams items are prioritized among each other as you'd expect 14:44 - ensure community requests do not get stomped by teams calling for favors too much 14:44 #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 14:44 sarnold: did you see wsdd come in already? 14:44 cpaelzer: I added it a few seconds ago 14:44 (thanks to your hint) 14:44 sarnold: There's also bug #2069308 as of today, which should go to security review already, as the requested changes are fairly simple packaging things 14:45 hunh i'm not sure I knew xterm wasn't in main, heh 14:46 this one is in https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir but not yet in the jira board 14:46 so, due to turnover, we won't have the throughput that we did last cycle; I'll try to find some assistance but things are feeling tight 14:46 so much for things being too calm 14:46 aye, a bit more calm would be just the thing :) 14:46 and indeed the backlog starts to front-load 14:46 yay for that 14:47 5 waiting to be grabbed 14:47 do you need help in raising a concern, or is it not that bad yet? 14:47 I guess the xdg-terminal-exec can be handled with lower priority. They didn't mention a specific deadline IIRC 14:47 not that bad yet, holidays have also interrupted the regular communication channels 14:47 ok 14:48 let us watch that if that means 4 weeks for review (not nice but ok) or 12 weeks (a problem I guess) 14:48 for now, leaving this in the hands of sarnold 14:48 #topic Any other business? 14:49 just a small bit .. 14:49 sil2100 and myself were wondering about pulseaudio this morning.. 14:49 slyon: what is the status of pulseaudio that you wondered about? 14:49 src:pulseaudio is in main, but most binaries have been dropped, somehow they are still being pulled in images, which leaves us in a strange situation. 14:49 I miagine sarnold is typing more than a small bit as it still goes on 14:50 sometimes questions are floating in space about "hey one of our partners wants such-and-such included, how do we do it?" -- while our giant pile of TODOs is well-suited for our review needs, it feels like a poor fit for "how do I get something included into ubuntu" or "how do I get a new package supported by canonical" 14:50 Does anybody know if we still need pulseaudio in main at all? or what's happening here? CC jbicha, didrocks 14:50 slyon: we definitely need some pulseaudio stuff in main, it's being handled (hopefully today) 14:51 jbicha: oh, good to know! So binaries were demoted by accident? 14:51 I haven't been able to find any logs that explain how some binaries got demoted everywhere but on armhf 14:51 does anyone else see a need for a more packager-oriented guide? or is the current review documentation sufficient for the task, if not ideal? 14:52 sarnold: I wonder if this could be one section of the new packaging-guide? cc dviererbe 14:52 jbicha: thanks, we'll wait for what you find then 14:52 sarnold: I wanted to write the same 14:52 I don't intend for us to solve this today ;) but I just thought I'd put the idea out there, to see if anyone else sees this, or may see this over the course of the cycle 14:52 also I believe pulseaudio did not show up on component-mismatches because the binaries were still in main on armhf 14:52 sarnold: I agree that having a higher level overview would be good. 14:52 sarnold: but not so much in re-writing the same to have redundancy and mismatches. More to write an intro for those not knowing much about it referring to our page for the gritty details 14:52 which then references the ubuntu-mir template with all the specific TODOs 14:53 exactly 14:53 slyon: might be able to carry that into the backlog of the packaging guide which is in the Foundations Jira? 14:53 there are many stories about what could be written about, this would be one more 14:53 a "new packaging guide" sounds like an excellent place to put this :) 14:53 or dviererbe? 14:54 I'll reach out to dviererbe, trying to get that into some backlog :) 14:54 I tend to stumble over these conversations in places where the question may be overlooked entirely 14:54 thanks 14:54 and hanging it on osmething like a new packaging guide feels likely to reach the right audience 14:54 thanks 14:54 correct 14:54 any other AOB? 14:54 nothing else 14:55 nothing 14:55 nothing from me either 14:55 jbicha: joalif: jamespage: last chance to add something else ... :-) 14:55 nothing from me, thanks 14:56 nothing from me 14:56 ok a countdown from the https://oeis.org/ to close it out 14:56 42 14:56 14 14:56 5 14:56 2 14:56 1 14:56 1 14:57 see you all 14:57 yay a return to an old tradition :D 14:57 indeed 14:57 thanks cpaelzer, all 14:57 #endmeeting