[12:50] hmm nothing [12:50] yay I misread my clock by 2h, ignore the noise :-) [13:18] cpaelzer: you are allowed to be confused only next week :) [13:22] glad to know that didrocks [13:22] I'll stop for now ... [13:28] thanks for making me smile didrocks :-) [13:29] :p [13:59] * ddstreet grabs coffee before mtg o/ [14:00] o/ [14:00] hey [14:00] jamespage: doko: didrocks: sarnold: joeubuntu: ping [14:02] hey cpaelzer ! [14:02] hi [14:02] ok lets get this party started then ... [14:02] #startmeeting Weekly Main Inclusion Requests status [14:02] Meeting started Tue Mar 24 14:02:44 2020 UTC. The chair is cpaelzer. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [14:02] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Main Inclusion Requests status Meeting | Current topic: [14:02] #topic Review of previous action items === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Main Inclusion Requests status Meeting | Current topic: Review of previous action items [14:03] I had the action from Frankfurt sprint to reork the wiki (you all should have got a mail) [14:03] There is a suggested new page https://wiki.ubuntu.com/MainInclusionProcessNEW [14:03] #link https://wiki.ubuntu.com/MainInclusionProcessNEW [14:03] That unifies the old chaos of everal places (harder to find and unsure where to look at) [14:03] #link https://wiki.ubuntu.com/MIRTeam [14:04] #link https://wiki.ubuntu.com/MainInclusionProcess [14:04] #link https://wiki.ubuntu.com/UbuntuMainInclusionRequirements [14:04] in addition to merging those I have added the review-templates that I've shown in frankfurt [14:04] is anyone against using the new page? [14:05] Once we agree I can do the changes to replace one of the existing pages and have the others refer to it [14:05] thx for working on that, I have a couple of remarks on the page and unsure how we should fix them [14:05] for instance, there is a discrepancy between how we give a MIR to the security team and the diagram below [14:05] the text is: [14:05] didrocks: the content is mostly the same as before - are your remarks new issues or already bad before my sugegsted change? [14:05] " * They might also delegate portions of the review to other teams, assign it to them, and set it to Incomplete; common cases are getting a thorough security review from the security team " [14:06] -> the diagram shows only "new" as a valid status though [14:06] good morning [14:06] cpaelzer: I think this was pre-existing, but as we consolidate in one page now, it’s more visible :) [14:06] yes didrocks [14:07] in recent times we really only kept incomplete if the bug-reporter had to come back later with tasks [14:07] (it’s minor, the rest is really really good) [14:07] the security Team was fine to pick the tasks in state "new" as well as long as they are assigned [14:07] ok, I’ll update the diagram to match this [14:07] na [14:07] didrocks: lets change the text [14:07] let’s set on incomplete [14:07] yep [14:07] the diagram is the simpler version [14:07] ack [14:07] one less state change [14:08] hmm, the process is "hidden" after the review description ... maybe should be moved up [14:09] we use incomplete for a placeholder bug, missing subscriber, missing stuff in the MIR [14:09] doko: we can makd #4 to become 3.1 would that work better for you? [14:09] doko: yes incomplete is "please comeback once XXX is fulfilled" [14:09] which can be subscribers, or "please add a test" or "needs new version" and such [14:10] doko: I'll move the process states up that is a good suggestion [14:10] I would make 4 -> 2 [14:11] like an overview before the detail then [14:11] sure that can work as well [14:11] yes [14:11] done [14:12] the state chare has incomplete the way we use it [14:12] it is state #7 [14:12] it is missing in the long text thou [14:13] I'll add at "Filing a MIR bug" as 4.2 [14:15] done [14:15] anything else that anyone wants to change immediately [14:15] it is - after all - a wiki so you can do that at any time [14:16] but I know that this probably is the one time we really read and modify it [14:16] for quite a while [14:16] so is everyone ok now? [14:16] FYI - the one URL that will stay (=the page this unified content will take over) is https://wiki.ubuntu.com/MainInclusionProcess === didrocks999 is now known as didrocks [14:17] and the other two will be come blank referrals (not sure if the wiki allows auto-referral but a link will do as well) [14:19] I'd be bold and consider silence = yes [14:19] cpaelzer: heh, good plan :) [14:19] last remarks to hold me back before we go on with the agenda? [14:19] I really like the new page [14:19] and removing two others is excellent value :) [14:19] thanks sarnold [14:19] for me, +1 :) [14:19] we realized when introducing ddstreet that we did ourselve not know on which page it was - so the task became obvious :-) [14:20] ok lets go on then [14:20] #topic current component mismatches === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Main Inclusion Requests status Meeting | Current topic: current component mismatches [14:20] #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg [14:20] #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg [14:21] geoip2 is ready for promotion [14:21] doko: could you do that right away? [14:21] sure [14:21] the bug is linked in the svg as usual [14:21] FYI that was the long tail of a geoip -> geoip2 change triggered by the last bind9 updates [14:22] other things worth to mention are libfido2 / libcbor which are worked on [14:22] more interesting for this section of the agenda might be the totally new bits [14:22] doko: I know you asked xnox about the seed change with python-is-... is the "what-is-python" related? [14:24] perl don't hurt me [14:25] don't hurt me, no more [14:25] yeah, I'm +0 thats we need that in main ... [14:25] do you know who is driving that? [14:26] xnox. I don't care if it's in main or not [14:26] ok he will let us know if he needs anything [14:26] he knows the people and the process [14:26] if we decide to do something abotu it it might be wrong [14:26] he will know better [14:26] next weould be apport depending on terminator [14:27] does anyone know more about that? [14:29] that is from binary apport-gtk [14:29] recent uploads by bdmurray [14:30] for now highlighting him is all that comes to mind, I'd expect him to file a MIR if one is need on this [14:30] other opinions? [14:30] I think let’s wait for bdmurray to see his reason, but terminator in main doesn’t really make much sense to me [14:30] doko: are you filing MIRs once you see them in mismatches usually - or are you pinging the uploaders? [14:30] didrocks: maybe it is an unintended pickup of the dependency, the changelog doesn't mention it [14:31] I think so [14:31] ok next agenda item [14:31] cpaelzer: I think it may be unrelated to apport itself though -- at least on my lists, apport-gtk Depends: on x-terminal-emulator [14:31] open MIR to assign to us [14:31] sarnold: yes on my focal it has x-terminal-emulator as well [14:31] cpaelzer: this may be a bug in whatever tool generates the svg, I don't know why terminator specifically was chosen to satisfy this dependency, nor why it recently changed [14:32] sarnold: it has "Provides: x-terminal-emulator" [14:33] apport should have a real package as the first alternative [14:33] doko: ahhhhh [14:33] yep it directly lists it in depnds [14:34] bdmurray: ^^ would you fix that in apport? [14:34] doko: can you carry that to him in whatever the next team meeting is for you? [14:34] on my big pile of unpacked packages, terminator is only ever mentioned in code, likely as a fallback option http://paste.ubuntu.com/p/jK7CgH5JWS/ [14:34] #topic New MIRs === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Main Inclusion Requests status Meeting | Current topic: New MIRs [14:35] #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir [14:36] cpaelzer: the foundations team has a trello card to fix component-mismatches iirc [14:36] ok thanks bdmurray [14:36] I'll make sure cbor goes forward [14:36] I already did a review and have an open MP I need to review [14:37] to check if it fulfills my needs for 2new version" [14:37] it also is assigned to security [14:37] so no need to add further people to that [14:37] the other two are [14:37] https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1867813 [14:37] Launchpad bug 1867813 in linux-firmware-raspi2 (Ubuntu) "[MIR] linux-firmware-raspi2 to restricted" [High,New] [14:37] https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/1868572 [14:37] Launchpad bug 1868572 in lxd-agent-loader (Ubuntu) "[MIR] lxd-agent-loader" [Undecided,New] [14:38] anyone feeling like picking either of them? [14:38] for the security part, I think I'd just like to give the binary package a quick re-review after it enters -proposed or similar, just to make sure the usual sanity checks are done [14:38] it seems security has already looked at lxd-agent-loader and it is a trivial package [14:38] sarnold: ack, that comment was for libcbor right? [14:38] cpaelzer: yes [14:39] I'll do lxd-agent-loader somewhen today or tomorrow [14:39] anyone willing to take https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1867813 plese ? [14:39] Launchpad bug 1867813 in linux-firmware-raspi2 (Ubuntu) "[MIR] linux-firmware-raspi2 to restricted" [High,New] [14:41] i would, but i already took lp #1868154 and lp #1868159 and don't want to take too many since i'm new to the process [14:41] Launchpad bug 1868154 in realmd (Ubuntu) "[MIR] realmd" [Undecided,New] https://launchpad.net/bugs/1868154 [14:41] Launchpad bug 1868159 in adcli (Ubuntu) "[MIR] adcli" [Undecided,New] https://launchpad.net/bugs/1868159 [14:42] agreed ddstreet [14:42] anyone else? [14:43] doko: this seems to be a foundations-case anyway - would you be able to give this one a look? [14:44] I mean 1867813 [14:45] it seems everone is busy or unwilling :-/ doko since it is from sil2100 you probably are the closest member anyway - so he will bother you first :-) [14:46] we can wait for an answer int he last section of the meeting [14:46] lets go on for now [14:46] #topic Incomplete bugs / questions === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Main Inclusion Requests status Meeting | Current topic: Incomplete bugs / questions [14:46] #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:46] ugh, not sure how to review that. I'll ask lucascz [14:46] thanks doko [14:47] openstack team seems to work on https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1864666 but it is still incomplete and got mentioned to be for 20.10 now [14:47] Launchpad bug 1864666 in python-octavia-lib (Ubuntu) "[MIR] python-octavia-lib, ovn-octavia-provider" [Medium,Incomplete] [14:47] no action on that [14:47] for https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1835114 I know that rbalint is waiting on rharper [14:47] Launchpad bug 1835114 in ec2-instance-connect (Ubuntu) "[MIR] ec2-instance-connect" [Undecided,Incomplete] [14:47] neither of the recent incomplete bugs is "for us" [14:47] #topic Any other business? === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice | Weekly Main Inclusion Requests status Meeting | Current topic: Any other business? [14:48] this was long already, anything else by any of you? [14:48] nothing from me [14:48] ddstreet: I know you wanted second opinions on some reviews - is that ready for discussion? [14:49] for lp #1864667 [14:49] Launchpad bug 1864667 in neutron (Ubuntu) "[MIR] neutron-ovn-metadata-agent" [Undecided,In progress] https://launchpad.net/bugs/1864667 [14:49] i started review, but as it's a binary pkg from a src already in main, i noted as such, and changed to 'In Progress' waiting for AA to handle it [14:49] is that correct procedure? [14:50] i haven't got to the other 2 i took for review yet [14:50] yeah, I usuaully do a quick sanity check but other than that new binaries on src-in-main does not need a new MIR [14:50] do i need to subscribe any other person/team to the bug, or will an AA see it and handle it? [14:51] i.e. putting the new binary pkg into main [14:51] TBH I don#t see that in mismatches [14:51] root@f:~# apt-cache policy neutron-ovn-metadata-agent [14:51] I think that requires Fix Committed, from https://wiki.ubuntu.com/MainInclusionProcessNEW [14:51] neutron-ovn-metadata-agent: [14:51] i think the binary pkg is still stuck in focal-proposed [14:51] Installed: (none) [14:51] Candidate: 2:16.0.0~b2~git2020020712.d5b33ffc77-0ubuntu2 [14:51] Version table: [14:51] 2:16.0.0~b2~git2020020712.d5b33ffc77-0ubuntu2 500 [14:51] 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages [14:51] 500 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages [14:51] it is already done [14:52] I thnik this bug is useless extra effort [14:52] ok well it's still good knowledge for me :) [14:52] so it should be fix committed? [14:52] well, it is more like "invalid" [14:52] ah since no action needed, got it [14:52] heh I would have thought Fix Released, since it's "resolved by an AA" :) [14:52] * doko leaves the meeting, have to run for an appointment [14:53] cu doko [14:53] doko o/ [14:53] ok i'll put it into 'fix released' just to avoid confusion about whether it belongs in main or not [14:53] ddstreet: I updated the bug [14:53] bye doko [14:53] coreycb: will come back if needed [14:53] ah ok thnx cpaelzer :) [14:53] ok we are done then ... [14:53] anything else? [14:53] 10 [14:54] 5 [14:54] 3 [14:54] 2 [14:54] 1 [14:54] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | be nice [14:54] Meeting ended Tue Mar 24 14:54:08 2020 UTC. [14:54] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-03-24-14.02.moin.txt [14:54] thanks to everyone [14:54] thanks cpaelzer, all [14:54] I know this was a long one [14:54] thnx! bye o/ [14:54] cpaelzer: I like the logarythmic countdown :) [14:54] cpaelzer: I think neutron-ovn-metadata-agent should be ok now, fixed it yesterday. [14:54] sarnold: sort of reverse fibonacci due to all the rabbits dying of a virus [14:55] thx :) [14:58] lol === vorlon` is now known as vorlon