[14:29] hello [14:30] * utkarsh2102 just waves \o [14:30] and goes back to his shell [14:30] hehe [14:30] hey [14:30] #startmeeting Weekly Main Inclusion Requests status [14:30] Meeting started at 14:30:35 UTC. The chair is cpaelzer. Information about MeetBot at https://wiki.ubuntu.com/meetingology [14:30] Available commands: action, commands, idea, info, link, nick [14:30] Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage [14:31] still all on PTO except didrocks and me? [14:31] joalif slyon sarnold jamespage ? [14:31] could be, long holidays after FF? :p [14:32] yep [14:32] well let us get going, they might show up later [14:32] right [14:32] o/ [14:32] and for steps we can get through alone we can do that already [14:32] hi joalif [14:32] #topic current component mismatches [14:32] Mission: Identify required actions and spread the load among the teams [14:32] #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg [14:32] #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg [14:32] good morning [14:33] hi sarnold [14:33] #1 is IWD [14:33] I think this is an approved MIR, still checking details ... [14:34] needed https://bugs.launchpad.net/ubuntu/+source/ell/+bug/1971738 which seems ready as well [14:34] Launchpad bug 1971738 in ell (Ubuntu) "[MIR] ell" [High, Fix Committed] [14:35] demoting wpa was needed, clarified as well [14:35] perhaps the build with lto requirement? [14:35] https://launchpad.net/ubuntu/+source/iwd/1.29-1ubuntu1 for lto [14:35] so it’s still disabled (but in the package this time, not in the global list) [14:35] which is fine [14:35] oh nice, that got the --enable-wired, too [14:35] so to me that seems ready [14:36] didrocks: do you want to work with seb128 to get with (depend iwd, promoted that, demote wpa)? [14:36] cpaelzer: yes, will do, nw! [14:36] grea [14:36] t [14:36] next is ... [14:37] well, in proposed there are plenty of pytohn-redis things and lintian again [14:37] and python-os-ken [14:37] let us sort them into actions one by one [14:37] lintian is the easiest [14:37] two known cases, no action for now [14:37] and two false positives [14:37] yes [14:38] next python-redis [14:38] new version https://launchpad.net/ubuntu/+source/python-redis/4.3.4-3 [14:38] part of the openstack tasks [14:38] pytohn-os-ken as well [14:38] this was a manual sync from debian? We did unplug automated sync, correct? [14:38] jamespage: coreycb: hey - those seem to be all yours [14:39] mark reviewed libwww-mechanize-perl and libmldbm-perl -- they're probably both good for promotion, no? [14:39] and as didrocks suggests, all seem manual syncs [14:39] oh are they sarnold, we will check that again after sorting these python things - thanks [14:39] coreycb: jamespage: that would be 4 more very last minute MIRs to get those new versions [14:40] I'll drop a msg in their channel internally to make them aware [14:40] ack [14:40] oh here you are [14:40] will you drive those jamespage? [14:40] I am - multi-meeting tasking [14:40] sorry for that [14:40] looking now [14:41] python-deprecated does not sound very promising :-), the others are python-async-timeout + python-typing-extensions + python-ncclient [14:41] I don’t see why you have any issues with the name :p [14:41] hmm, why is python-redis really only showing up on our radar today, if it was published in proposed on 2022-07-07 ? [14:42] yeah, I was about to ask that… [14:43] (I started writing the old feature-freeze warning speech but the date sure felt funny..) [14:43] Steve move 3.5.3-2 from main to universe on 2022-08-25 [14:43] moved* [14:43] maybe he moved too much [14:43] this is a pkg which is partially in main and some binaries in universe [14:43] is it shown in auto-demotions ... [14:43] which makes 4.3.4-3 still in main in proposed [14:44] so anyway, there is a mismatch (but you would expect the other way around between universe and main) [14:44] so maybe that’s the contrary, not enough demotion (not considered proposed) [14:44] I guess we need people with the knowledge of this stack [14:44] python3-redis | 3.5.3-2 | kinetic/universe | all [14:44] python3-redis | 4.3.4-3 | kinetic-proposed | all [14:45] so 3.5.3-2 was in universe, but before it was not [14:45] no, it was in main [14:45] https://launchpad.net/ubuntu/+source/python-redis/+publishinghistory [14:45] I guess jamespage / openstack as the responsible one should sort it out - probably just a mismatch before [14:46] 2021-10-15 13:50:32 CEST Published Jammy release main python 3.5.3-2 [14:46] so it was in main and got to universe due to 4.3 showing up? [14:46] Steve seems to have manually demoted it in the release pocket by the end of August [14:46] (while the new version, in main, is stuck in proposed) [14:47] the new version really depends on many more things [14:47] Depends: python3-async-timeout, python3-deprecated, python3-importlib-metadata | python3 (>> 3.8), python3-packaging, python3-typing-extensions | python3 (>> 3.8), python3:any [14:47] Depends: python3:any [14:47] so it is a real issue to get 4.3 migrating to sort these out [14:47] jamespage: coreycb: can we consider you to have a look then? [14:47] yeah, I wonder if he tried to make it move for any reasons, or if this is just a wrong correlation [14:48] but I don’t understand why we didn’t have it on our radar before (at least, before the 25th of August) [14:48] I'd also have expected to see it, at least from the day this got to main in kinetic-proposed [14:48] but not sure how much effort we should spend on analyzing this now [14:49] let me go back to libwww-mechanize-perl and libmldbm-perl instead [14:49] sarnold: that indeed LGTM now [14:49] I can move these tomorrow [14:49] \o/ [14:49] yeah, -perl are acked :) [14:49] #topic New MIRs [14:49] Mission: ensure to assign all incoming reviews for fast processing [14:50] #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:50] none [14:50] woo :) [14:50] #topic Incomplete bugs / questions [14:50] Mission: Identify required actions and spread the load among the teams [14:50] #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:50] smartcards got re-assigned [14:50] not happening right now [14:50] tuna/tuned have discussions asking for more details on the report [14:50] all fine, no action for us right now [14:51] thanks didrocks and joalif for handling these [14:52] qtr was last time, as I mentioned I told seb that we can make a one-off decision if the right aruments are provided - but so far no answer to that AFAICS [14:52] let’s see when we get some feedbacks… [14:52] #topic MIR related Security Review Queue [14:52] Mission: Check on progress, do deadlines seem doable? [14:52] #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:52] #topic MIR related Security Review Queue [14:52] Mission: Check on progress, do deadlines seem doable? [14:52] #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:52] Internal link [14:52] - ensure your teams items are prioritized among each other as you'd expect [14:52] - ensure community requests do not get stomped by teams calling for favors too much [14:52] #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 [14:52] mdevctl clearly is still missing, the rest is sort of ok to be later [14:52] sarnold: status on that? [14:53] mark has done good work getting the perl packages handled :D thanks to him; I haven't made progress on the mdevctl lately, I'm currently focused on 360s [14:53] ok, but between now and let me say next week we'd need to get mdevctl in to not mess up late Kinetic too mcuh - any chance for that? [14:53] yes [14:53] ok, looking forward to it then [14:53] thanks [14:53] #topic Any other business? [14:53] it'd take a pretty big surprise at this point :) hehe [14:53] hehe [14:53] no further topics by me today [14:54] nothing for me [14:54] nothing either [14:54] I'd really like a better idea of how the python-redis took us by surprise [14:54] we can spend the remaining 6 min on it and then close [14:54] should we poke archive admin types to get new perspectives? [14:55] like didrocks and me :-) [14:55] or is it enough to say that we'll probably learn more when jamespage [14:55] .. does the investigation? [14:56] yeah, I would wait for james first, but at first sight, I don’t see anthing happening in the archive between last week and this one [14:56] I think it isn't a lot that was missed, just afte rthe 25th of Aug it would have showed up [14:56] so why not last week [14:56] and yes, having the owning team investigate (which needs to happen anyway) seems to be the right start. [14:56] okay, cool [14:57] ok, closing for today then [14:57] thank you all [14:57] thanks cpaelzer, all :) [14:57] #endmeeting [14:57] Meeting ended at 14:57:11 UTC. Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-09-13-14.30.moin.txt [14:57] thanks cpaelzer, all :) [14:57] thanks all! === Eickmeyer is now known as NotEickmeyer === Eickmeyer4 is now known as Eickmeyer [16:31] cpaelzer: sarnold: I've moved ncclient to Suggests for now [16:49] cpaelzer: sarnold: redis needs some discussion with others on my team so I'll get back to you on that [17:13] coreycb: great, thanks :) [18:25] sarnold: cpaelzer: I've dropped redis to Suggests for python-tooz as well, it is really an optional driver. I think that was all that was holding it in main. [18:25] coreycb: woohoo, thanks :) [19:00] o/ [19:10] I guess nobody else is coming, so I'll go back to my evening now. === dbungert1 is now known as dbungert