== Meeting information == * #ubuntu-meeting: Weekly Main Inclusion Requests status meeting, started by cpaelzer, 06 Apr at 14:30 — 14:45 UTC. * Full logs at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-04-06-14.30.log.html == Meeting summary == === current component mismatches === Discussion started by cpaelzer at 14:32. * ''LINK:'' https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg (cpaelzer, 14:32) * ''LINK:'' https://launchpad.net/ubuntu/+source/cinder/2:18.0.0~b1-0ubuntu2 (sarnold, 14:34) * ''LINK:'' https://launchpad.net/ubuntu/+source/cinder/2:18.0.0~b1-0ubuntu2 (cpaelzer, 14:34) === Any other business? === Discussion started by cpaelzer at 14:35. * ''LINK:'' https://wiki.ubuntu.com/ToolChain/LTO (cpaelzer, 14:38) == People present (lines said) == * cpaelzer (35) * doko (9) * sarnold (8) * meetingology (2) * ddstreet (1) * icey (1) == Full log == 14:30 #startmeeting Weekly Main Inclusion Requests status 14:30 Meeting started at 14:30:03 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 sarnold: jamespage: didrocks: ddstreet: doko: ping MIR-party people 14:30 o/ 14:31 good morning 14:31 extra ping for jamespage as the only interestign bit seems to be coud archive related 14:31 getting started 14:31 Using the agreed "fast path" of our meeting I anted to let you know that 14:32 action-items, component-mismatches, new MIRs and incomplete MIRs all have no new entries and can be skipped today 14:32 the one thing worth to bring up is 14:32 #topic current component mismatches 14:32 #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg 14:32 o/ 14:33 There we see cinder <-> python-boto* 14:33 I pinged icey about that last week 14:34 doko: cpaelzer: I believe that coreycb uploaded a change to resolve that yesterday 14:34 https://launchpad.net/ubuntu/+source/cinder/2:18.0.0~b1-0ubuntu2 14:34 https://launchpad.net/ubuntu/+source/cinder/2:18.0.0~b1-0ubuntu2 14:34 ok 14:35 that seems to be on the way to be resolved then 14:35 Which is great 14:35 that leads to 14:35 #topic Any other business? 14:35 so what's up? 14:35 one thing 14:35 @sarnold are you planning ahead security reviews in 21.10 cycle or is it to early to bother about that? 14:35 doko: what is it? 14:36 cpaelzer: heh, we're still working on reviews from N cycles in the past.. 14:36 I'd like to add a requirement that a package in main must not be on the lto-disabled list, but the fix, or the work-around should be directly in the package 14:37 so you'd want the lto-disable in the package and not in the list 14:37 sounds reasonable to me to enforce maintainer-awareness 14:37 any reasons opinions against that suggestion? 14:37 what's involved in a maintainer opting into the lto-disable in their package? 14:38 https://wiki.ubuntu.com/ToolChain/LTO 14:38 for universe? just uploading a new lto-disabled-list package 14:38 export DEB_BUILD_MAINT_OPTIONS=optimize=-lto 14:39 nice docs doko :) 14:40 so agreed? 14:41 yeah, I think this is a good idea 14:41 +1 - I'm already writing the text for it 14:41 sarnold: I would suggest doing the disablement for hirsute security uploads as well, if you find something that doesn't build/work with lto 14:41 doko: ack, thanks, I'll pass it along 14:42 but filing a bug report would be appreciated 14:42 3/3 votes for that change 14:42 no more people here and it seems rather non controversial 14:42 adding the change to the wiki ... 14:43 ta 14:44 done 14:44 to review template and the explanations 14:44 anything else ? 14:44 nothing from me 14:45 ok and doko said one (=1) thing which we handled 14:45 closing this early giving you back some time 14:45 thanks @all 14:45 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)