== Meeting information == * #ubuntu-meeting: Weekly Main Inclusion Requests status meeting, started by slyon, 21 Mar at 15:30 — 15:53 UTC. * Full logs at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-03-21-15.30.log.html == Meeting summary == === current component mismatches === Discussion started by slyon at 15:31. * ''LINK:'' https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg (slyon, 15:31) * ''LINK:'' https://people.canonical.com/~ubuntu-archive/component-mismatches.svg (slyon, 15:31) === New MIRs === Discussion started by slyon at 15:37. * ''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 (slyon, 15:37) === Incomplete bugs / questions === Discussion started by slyon at 15:37. * ''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 (slyon, 15:37) === MIR related Security Review Queue === Discussion started by slyon at 15:41. * ''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 (slyon, 15:41) * ''LINK:'' https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 (slyon, 15:41) === Any other business? === Discussion started by slyon at 15:45. * ''LINK:'' https://github.com/canonical/ubuntu-mir/blob/75a487a44c91728e6c35338ed78b57f978bfeea6/README.md?plain=1#L159 (eslerm, 15:46) == People present (lines said) == * slyon (57) * sarnold (16) * eslerm (14) * didrocks (9) * joalif (3) * meetingology (2) * dviererbe (2) * jamespage (1) == Full log == 15:30 #startmeeting Weekly Main Inclusion Requests status 15:30 Meeting started at 15:30:55 UTC. The chair is slyon. Information about MeetBot at https://wiki.ubuntu.com/meetingology 15:30 Available commands: action, commands, idea, info, link, nick 15:30 Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage eslerm 15:31 #topic current component mismatches 15:31 Mission: Identify required actions and spread the load among the teams 15:31 #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg 15:31 #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg 15:31 o/ 15:31 hello 15:32 c-m is looking pretty good. inetutils is with joalif for MIR review (what's status on this?) and I've just reviewed a fix for the broken autopkgtests today 15:32 the fix is ready for sponorship, but pending FFe 15:32 mosh has been taken over by rbasak to fix the remaining blockers 15:32 slyon I didn't get the chance to work on it last week, I;ll do it this week (promise) 15:32 thanks joalif! 15:32 c-m-p: 15:33 this is looking much cleaner! 15:33 does ipmitool need to stay on that list? "ipmitool repository has been locked, and its maintainer suspended, by GitHub" - https://lwn.net/Articles/926101/ 15:33 we (foundations) were able to drop two *-perl dependencies of devscripts and I just uploaded ndctl earlier today to drop two additional deps/mismatches 15:34 eslerm: this is a fair point.. I think we should further disucss this during AOB 15:35 we definitely should have another conversation with the maas team to see if there's a good alternative that we can invest in to push it over the line 15:35 for *cups we're pending security review IIRC and python-inflect is with the OpenStack team 15:35 sarnold: is maas the only user? 15:36 slyon: probably not, but the supported-maas seed is how this is on our radar every week :) 15:36 sarnold: could you or eslerm reach out to the MAAS team to clarify this? 15:36 sure 15:36 ACK. Maybe we should create a bug report which can be shared with the MAAS team, and also subscribe ~ubuntu-archive, to bringt it to the AAs attention? 15:37 #topic New MIRs 15:37 Mission: ensure to assign all incoming reviews for fast processing 15:37 #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 15:37 nothing \o/ 15:37 #topic Incomplete bugs / questions 15:37 Mission: Identify required actions and spread the load among the teams 15:37 #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 15:38 bug #2001699 -> tracking update 15:38 bug #2007710 -> seems ready for promotion. didrocks could you double check and update the bug status accordingly? 15:38 slyon: we need the FFe 15:38 before doing the promotion 15:38 but yeah, I’ll change the status after checking 15:39 didrocks: thanks! Please also mention the FFe in the comments as I think I couldn't find anything about it there 15:39 well, it’s the distro regular process at this point (for the thing that will start pulling it) 15:40 didrocks: well... actually it looks like it already migrated. So maybe FFe is already done? 15:40 but happy to write it down 15:40 the thing pulling it should have the FFe 15:40 anyway, thanks for taking care! 15:40 being either a seed/metapackage change or a dep 15:40 I see. makes sense 15:40 no other recent (past 2 weeks) updates on that list 15:41 #topic MIR related Security Review Queue 15:41 Mission: Check on progress, do deadlines seem doable? 15:41 #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 15:41 Internal link 15:41 - ensure your teams items are prioritized among each other as you'd expect 15:41 - ensure community requests do not get stomped by teams calling for favors too much 15:41 #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 15:41 sarnold: what's the update you have for us today? 15:42 I'm seeing progress on x265 15:43 we requested volunteers a few times for cups mirs, I have a 1x1 today where I can raise this again 15:43 alas not much progress on duktape or kea (sorry christian, when reading the logs, I've still got your dissaproving picture over my monitor) -- escalations atop escalations 15:43 right! there have been some discussions regarding x265 vs libde265. but it seems like they are not fit for the reverse purpose (encoder vs decoder). Foundations is currently trying to clarify this with upstream libde265 15:44 we do still intend to put more time on MIRs nearer the end of the month, but there's no denying that resources are currently elsewhere 15:44 yeah.. we'll probably also need some cycles for inetutils[-telnet] once MIR review is done by joalif ... 15:44 that's good to hear, I'm not working on x265, but theres A LOT of assembly :) 15:45 eslerm: oh good :) you're the new assembly expert! :) 15:45 as unfortunately this already got seeded and the previous netkit-telnet got dropped from the archive (Debian & Ubuntu) 15:45 hehe :) 15:45 sorry David :pray: 15:45 okay. moving on. 15:45 #topic Any other business? 15:46 https://github.com/canonical/ubuntu-mir/blob/75a487a44c91728e6c35338ed78b57f978bfeea6/README.md?plain=1#L159 15:46 nothing 15:46 I approved bug #2003549 today after all the required TODOs got resolved, cc athos 15:46 I added a comment and subscriptions on https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1978144 15:46 I'd like to change the MIR process to require one LP bug # per MIR request 15:47 when multiple MIRs are on a single LP page, it breaks security tooling and is generally confusing 15:47 I think that's a good idea; I'd love to see us move to something like the kernel team's tracking bugs 15:47 I can make a PR to describe this, but wanted to highlight the issue here 15:47 the downside of course is that it'd require new tooling to make a change that drastic 15:48 eslerm: no objections against this from my side... it's sometimes easier/quicker to have multiple (small) packages on the same LP bug (like all those *-perl deps), but having individual bugs is the cleaner approach 15:48 this change is nice and small, addresses problems we're having with jira right now, and doesn't require tooling changes 15:48 eslerm: do you mind creating a PR on github to update that part of the section and we can have the discussion in the PR review? 15:48 can do 15:48 thank you 15:48 it is more work for bug filers :/ but I think the clarity gain is worth it 15:49 thanks eslerm! Then we should be able to find consensus on the next MIR meeting 15:49 (or, at least, I'm assuming I'm not the only one who has trouble figuring out which of N packages is referred to when reading comments within an omnibus bug) 15:49 \o/ 15:50 I asked cpaelzer to enable the Issues section. I promised to respond to issues and redirect them here if the authors doesn't do it. I have PR adding a Contributing section to the Readme: https://github.com/canonical/ubuntu-mir/pull/13 15:50 I don’t have strong opinions from my side, so the easiest for you is fine by me :) 15:51 ^ reads well to me 15:51 dviererbe: I like it 15:51 dviererbe: I also like it. 15:51 Thank you :) 15:52 thanks slyon, all :) 15:52 Could everybody please add their review (+1/-1) on the pending PRs: https://github.com/canonical/ubuntu-mir/pulls 15:52 so we can get those landed soon? 15:52 slyon: heh, we should add that as a recurring section in the meeting agenda 15:52 sarnold: ACK. I'll create a PR to update the meeting script :) 15:52 \o/ 15:53 I guess that's all for today. 15:53 thanks folks! 15:53 thanks slyon, all o/ 15:53 thanks slyon, all :) 15:53 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)