== Meeting information == * #ubuntu-meeting: Weekly Main Inclusion Requests status meeting, started by slyon, 02 Apr at 14:35 — 15:15 UTC. * Full logs at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-04-02-14.35.log.html == Meeting summary == === current component mismatches === Discussion started by slyon at 14:35. * ''LINK:'' https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg (slyon, 14:35) * ''LINK:'' https://people.canonical.com/~ubuntu-archive/component-mismatches.svg (slyon, 14:35) === New MIRs === Discussion started by slyon at 14:41. * ''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, 14:41) === Incomplete bugs / questions === Discussion started by slyon at 14:42. * ''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, 14:42) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/16 is also to be double-checked by cpaelzer (please update the case once you have some time), to confirm the requirements are good (slyon, 14:45) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781 (slyon, 14:46) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099 (slyon, 14:46) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/aom/+bug/2004442 (slyon, 14:46) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916 (slyon, 14:46) === Process/Documentation improvements === Discussion started by slyon at 14:47. * ''LINK:'' https://github.com/canonical/ubuntu-mir/pulls (slyon, 14:47) * ''LINK:'' https://github.com/canonical/ubuntu-mir/issues (slyon, 14:47) === MIR related Security Review Queue === Discussion started by slyon at 14:48. * ''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, 14:48) * ''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 (slyon, 14:48) * ''LINK:'' https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 (slyon, 14:48) === Any other business? === Discussion started by slyon at 14:50. * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813 (cpaelzer, 14:58) == People present (lines said) == * slyon (78) * cpaelzer (54) * sarnold (18) * eslerm_ (15) * jbicha (6) * dviererbe (6) * meetingology (2) * ravikant_ (1) == Full log == 14:35 #startmeeting Weekly Main Inclusion Requests status 14:35 Meeting started at 14:35:34 UTC. The chair is slyon. Information about MeetBot at https://wiki.ubuntu.com/meetingology 14:35 Available commands: action, commands, idea, info, link, nick 14:35 #topic current component mismatches 14:35 Mission: Identify required actions and spread the load among the teams 14:35 #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg 14:35 #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg 14:36 *boom* 14:36 oh my 14:36 I guess we should ignore that for today. I did some investigation ealier, and it's mostly due to missing binaries in the archive, cause by the mass-rebuild 14:37 then falling back to an alternative dependency, that is not in main 14:37 ahhhhhh 14:37 -proposed might be roughly correct though 14:37 hey, thanks for starting 14:37 gnome-remote-desktop -> freerdp2 should be double checked, as we want it to use freerdp3 instead 14:38 jbicha: -proposed is even worse 14:38 how is that worse? :) 14:38 I'm not sure where those new rust-* trees/roots come from, but would blame the state of the archive, too 14:38 gnome-remote-desktop does depend on freerdp3 in -proposed but failed to build on armhf & may need AA help 14:38 thanks jbicha, that will resolve the mismatch on freerdp2 then once it migrates 14:39 what kind of AA help do you expect there? 14:39 sarnold: ah sorry! I mixed up my -release and -proposed tabs :) 14:39 slyon: every single week I think we ought to switch the order of the two links and every single week I do nothing about it :) 14:39 we may want to remove gnome-remote-desktop on armhf 14:39 abseil -> googletest and glib2.0 -> sysprof should be checked by the desktop team (cc didrocks, jbicha) 14:39 oh removing armhf was already done so I guess that will clear up on xz-utils migrates 14:40 I'm working through glib -> sysprof either by reverting or by demoting libglib2.0-dev to universe (like we did with other sysprof-using libraries) 14:40 Desktop plans to do a MIR for sysprof for the 24.10 cycle 14:40 I updated the *trace* and bpf* cases today and would love to get cpaelzer's input on bpf*, to see if we can drop some of the MIR required TODOs to Recommended TODOs. (but more on that later) 14:40 ok, so no dependency now - but re-added in 24.10 - sounds good and matches what I expected 14:40 thank you slyon :) 14:41 #topic New MIRs 14:41 Mission: ensure to assign all incoming reviews for fast processing 14:41 #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:41 any volunteers for bug #2060035 14:41 I could take it myself, probably. 14:42 let's do this 14:42 #topic Incomplete bugs / questions 14:42 Mission: Identify required actions and spread the load among the teams 14:42 #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:43 tracking update on #2051925 (still WIP) 14:43 bug 2051925 14:43 same for trace-cmd 14:43 bug 2023531 > Therefore, the final requirement for the .NET MIR should be fulfilled. 14:44 slyon: I'm too distracted still :-/ will read the bpf and trace cases in a bit 14:44 thanks! 14:44 So bug 2052813 and bug 2052809 TBD by cpaelzer 14:45 next one bug 2023531 14:45 If there are any questions for dotnet. I am here o/ 14:45 https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/16 is also to be double-checked by cpaelzer (please update the case once you have some time), to confirm the requirements are good 14:46 that's it for updates, I guess 14:46 I moved quite a few to "In Progress" this morning: 14:46 https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781 14:46 https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099 14:46 https://bugs.launchpad.net/ubuntu/+source/aom/+bug/2004442 14:46 https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916 14:46 (Just FYI) 14:46 so those are good 14:47 #topic Process/Documentation improvements 14:47 Mission: Review pending process/documentation pull-requests or issues 14:47 #link https://github.com/canonical/ubuntu-mir/pulls 14:47 #link https://github.com/canonical/ubuntu-mir/issues 14:48 no updates AFAICT 14:48 #topic MIR related Security Review Queue 14:48 Mission: Check on progress, do deadlines seem doable? 14:48 Some clients can only work with one, some with the other escaping - the URLs point to the same place. 14:48 #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:48 #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:48 Internal link 14:48 #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 14:48 sarnold: 14:48 this looks very clean! 14:48 it *is* very clean :D 14:49 \o/ 14:49 eslerm_ has done an excellent job helping many reviewers to help us get to this state :) I'm feeling really good. <3 14:49 wow nearly empty board 14:49 and there isn't too much in the pipeline. 14:49 Much appreciated, kudos! 14:49 But I guess the secirty team is busy with other stuff these days :) 14:50 #topic Any other business? 14:50 the remaining items on Security's jira board are blocked 14:50 eslerm_: did you already reach out to the corresponding team to help unblocking it? 14:51 one is blocked by security 14:51 the other we have spoken to desktop about 14:51 so, we weren't exactly clear in our "must be assigned to security team before beta freeze" if it was the specific date or the specific milestone .. and perhaps beta freeze has moved around due to the recent fun 14:52 in any event, MIRs beyond beta freeze that need security team ACK will also need a conversation with the security engineering director 14:52 I think that's all I had 14:53 thanks for clarifying. This might or might not affect https://launchpad.net/bugs/2060035 – depending on what I find on the MIR review. CC seb128 ^ 14:53 slyon: read and updated bug 2023531 - it is indeed ready to go now AFAICS 14:53 the msgraph mir says it targets 24.04.1 14:54 thx cpaelzer! cc dviererbe ^ 14:54 eslerm_: good. that should give some buffer 14:54 Do we have anything else? 14:54 slyon: I'm ok on build time tests being impossible on bpftrace - with autopkgtests added that should be ok 14:55 not that I feel to be the one that has to decide alone, but I think it is ok 14:55 Do I have to open an MIR bug for dotnet8? 14:55 cpaelzer: I agree. As we need a specific kernel, that we cannot guarantee on the builders 14:55 yep 14:55 it would be nice to sort out which bpf binaries make it to the default installation, lots of duplication between packages 14:56 eslerm_: that is on https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813 14:57 eslerm_: I think it will only pull in one of them, and IMHO should be the smallest (there are pre-linked and some that have way more dependencies) 14:57 But I haven't done this myself, so I can't tell you what exactly it would pull atm 14:57 I cannot find my conversation about fdk-aac-free, I'll speak to desktop in case I did not :( 14:57 thanks cpaelzer 14:57 but we have seen it in the mismatches, so it is there isn't it 14:57 slyon: https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2052809 seems to be ready then 14:58 cpaelzer: ACK. I'll update the case 14:58 what about bpfcc? 14:58 alreaedy done 14:58 cool! 14:58 still reading on this one 14:58 https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813 14:58 personally, I would make the bpftrace binaries non-executable examples 14:58 and I personally think that'd vastly detract from the value of the package :) 14:59 there are two packages in the bpfcc source package which duplicate binary functionality as well 14:59 I think we should have the examples executable 14:59 it is about making people aware of a whole new world of things they could get 14:59 eslerm_: are you concerned about something in particular? 14:59 the duplicated functionality in the bpfcc package feels pretty unfortunate :( some of them seem to work and others don't :( it'd be nice if the not-working-at-release ones would be removed.. 15:00 slyon: symbols have been looked at, the rest is done or impossible 15:00 that is usually the amount we strong-require 15:00 cpaelzer: so that can be promoted? 15:00 I'd be ok to give it a pass, you are subscribed and might even add c++filt based symbsoils in the past 15:00 it just feels redundant to have execsnoop, execsnoop-bpfcc, and execsnoop.bt all installed by default (and many similar cases) 15:00 again, you are all entitled to make that call - but I think yes this is ok'ishj 15:01 we might want to mention the "do not install all tools" that we discussed above 15:01 eslerm_: yeah, not all of them for sure 15:01 eslerm_: that is what I meant with just the set without dependencies 15:01 eslerm_: whichever that was 15:02 I trust that it will be implemented well :) 15:02 never trust :-) 15:02 but thanks 15:03 OK. I'll update the bpfcc case after the meeing then. 15:03 cpaelzer: May I also ask you to have a look at https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916/comments/22 15:03 Do you want those #MISSING: symbols dropped? IMO it should be fine as-is. Upstream is aware and want's to drop it anyway 15:04 #MISSING is fine unless it keeps adding more and more and more of them 15:04 but we can also wait for didrocks opinion on this ^ as he was the original reviewer 15:04 ok 15:04 you'd usually expect some cleanup every release or so 15:05 distro release or package "release"? 15:05 distro release 15:05 ack 15:06 like not each upload, but one of these usual "once every while" housekeeping tasks 15:07 I guess that should be all for today... 15:07 thanks all! o/ 15:07 thanks for doing a final triage-review of all the bpf mirs slyon 15:07 slyon: do you know which bpf tools are the small ones? 15:07 thanks all o/ 15:07 cpaelzer: I don't know, but will check back with ravikant_ 15:08 ok found it 15:08 the dependency is 15:08 1. seeds changed to depend on ubuntu-kernel-accessories 15:08 2. that depends on 15:08 Recommends: bpfcc-tools, bpftrace 15:08 I think that should actually be libbpf-tools 15:08 which is the small one as in 15:09 " 15:09 112 This package provides the tools from bpfcc-tools but written in a portable 15:09 113 fashion using BTF and libbpf hence the installation footprint will be smaller 15:09 114 compared to bpfcc-tools. 15:09 " 15:10 I'll ping Robie who was coordinating a lot 15:10 you ping ravikant_ 15:10 and together they will probably ask kernel to update the dependency or tell us why it needs to be the bigger one 15:10 sounds like a plan! 15:11 Repeating this question, because I am not sure if the answer was meant for me. Do I have to open an MIR bug for dotnet8? or is this included with the dotnet6 MIR? 15:11 oh right . 15:11 dviererbe: you'd want to open one, but refer to the existing dotnet6 15:11 ack 15:11 dviererbe: and then spell out what is the same and what is different 15:11 thanks all! I am meeting Robie in 30 mins. 15:11 dviererbe: so it should exist, but should be a fast path for both sides 15:11 awesome ravikant_ 15:11 .. imho opening a new one would make sense; perhaps sometday it'll be as auto-pilot as postgres, but at least the first few it feels like it's worth having an eye on it 15:12 okay, thanks 15:12 (we can all dream of someday being as good as postgres :) 15:13 Can I close the meeting now? 15:13 (sorry for running over again!) 15:13 I think so, but I thought so a few minutes ago, too, hehe 15:15 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)