/srv/irclogs.ubuntu.com/2022/06/28/#ubuntu-meeting.txt

=== JanC_ is now known as JanC
cpaelzerlate just a bit14:31
sarnoldgood morning14:31
joalifo/14:31
didrockshey14:31
slyonheyho o/14:32
cpaelzerok getting ready ...14:33
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:33
meetingologyMeeting started at 14:33:09 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:33
meetingologyAvailable commands: action, commands, idea, info, link, nick14:33
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage14:33
cpaelzermost of you are here already, just me being slightly late due to head to head meetings - sorry :-/14:33
cpaelzer#topic current component mismatches14:33
cpaelzerMission: Identify required actions and spread the load among the teams14:33
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:33
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:33
cpaelzerlet us see what this week has new for us14:33
cpaelzernothing in non-proposed14:34
cpaelzerbut a lintian explosion in -proposed14:34
slyonugh lintian... they're adding new dependencies quicker than we can process them :)14:34
slyonlintian got a new maintainer upstream and I think there was a big re-organization of the code14:34
sarnoldor.... hooray for more automated checking :) (I hope)14:34
cpaelzerwhich is all great, but paingul14:34
cpaelzerslyon: a question, is there a strong resaon it needs to be in main14:34
slyonI'll check those new dependencies. and assign them out within foundations, as needed14:34
cpaelzerslyon: it does not have to be as a build-dependency14:34
didrocksperlpainful even :p14:35
slyoncpaelzer: yeah.. we had that discussion during the Frankfurt sprint. But there were some strong opinions about keeping it in main14:35
slyonI can lookup the details if you want to14:35
cpaelzerok, then you said it right -sort out the MIRs on your end and file them14:35
cpaelzerjust wanted to ask to be sure14:35
cpaelzerthe rest are known false positives14:36
cpaelzeror cases waiting for review14:36
sarnoldopenwsman?14:36
cpaelzersarnold: that whole maas seed thing is there forver and not changing14:36
cpaelzerit is aphilospohopy questions, someone decided to declare a seed as maas uses those, but no one stepped up owning and promoting the packages14:37
sarnoldaha. it felt vaguely familiar but I didn't see openwsman in /lastlog. this should do for another few months then.. heh14:37
cpaelzerit is a very special case of false positives14:37
cpaelzerTBH all cases that are up are in the security queue14:37
cpaelzerso you can clear this view a lot sarnold :-P14:37
cpaelzer#topic New MIRs14:38
cpaelzerMission: ensure to assign all incoming reviews for fast processing14:38
cpaelzer#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-mir14:38
cpaelzernone14:38
didrocks\o/14:38
cpaelzerreally, I thought I have seen one in my inbox this week14:38
cpaelzerlet me see if it shows up in incomplete14:38
cpaelzer#topic Incomplete bugs / questions14:38
cpaelzerMission: Identify required actions and spread the load among the teams14:38
cpaelzer#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-mir14:38
cpaelzera few updates on those14:39
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/197814414:39
ubottuLaunchpad bug 1978144 in ipmitool (Ubuntu) "[MIR] ipmitool" [Undecided, Incomplete]14:39
cpaelzerwas reviewsed by joalif14:39
cpaelzerlooks good a few todos for the team, soon to be handled14:39
cpaelzerwe can assign this to security already IMHO14:39
cpaelzeras we usually do14:39
joalifso this needs sec review14:39
cpaelzerLena will add the test details while that is hanging in the sec queue14:40
joalifbut I didn't know if i shoudl assign it to them before the todos are done14:40
cpaelzeryes joalif, I assigned security now14:40
joalifah ok14:40
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/libisofs/+bug/197795914:40
ubottuLaunchpad bug 1977959 in libisofs (Ubuntu) "[MIR] libisoburn, libburn, libisofs" [Undecided, Incomplete]14:40
cpaelzerthis goes on between slyon and alexghiti14:40
didrocksI think slyon kept in sync with his time14:40
didrocksteam*14:40
slyonactually:14:40
cpaelzer?14:41
slyonthis is a question for didrocks:14:41
slyonabout the .symbols file14:41
didrocks(I agree about the no additional delta if we can’t get it sponsored to debian)14:41
didrocksif that was your question :p14:41
slyonI think we do not want to block on this here. as they're using the "-V" parameter14:41
didrocksyeah, I agree, but can we try to get them in debian still?14:42
slyoni.e. dh_makeshlibs -V14:42
slyonYes, I feel like it should be sent to Debian, but no need to inroduce a Ubuntu delta, right?14:42
cpaelzerack14:42
didrocksright, this is what I just wrote ^14:42
slyonok, thanks for clarification14:42
cpaelzerThen we have https://bugs.launchpad.net/ubuntu/+source/gsasl/+bug/197286614:43
slyonI will talk to Alex, he's out currently, though14:43
ubottuLaunchpad bug 1972866 in gsasl (Ubuntu) "[MIR] gsasl" [Undecided, Incomplete]14:43
didrocksslyon: just to ensure this is done, forwarded, but ack then. I’ll let you finish syncing with your team14:43
didrocksgood :)14:43
cpaelzerthis goes on in discussion - so far mostly about nothing yet testing it AFAICS14:43
cpaelzernothing to act for us right now14:43
cpaelzer#topic MIR related Security Review Queue14:43
slyonshould this be set to "New"+security?14:43
cpaelzerMission: Check on progress, do deadlines seem doable?14:43
cpaelzer#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-mir14:43
cpaelzerInternal link14:43
cpaelzer- ensure your teams items are prioritized among each other as you'd expect14:44
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much14:44
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:44
slyonI think foundations' part is done on gsasl14:44
cpaelzeryes slyon14:44
slyonwill do cpaelzer14:44
cpaelzerset14:44
slyonthx14:44
cpaelzerI could ask, but I ask the same thing every week sarnold - so I'm not asking this week14:44
cpaelzerbut the list is huge again :-/14:44
* cpaelzer hugs sarnold for review-pain14:45
cpaelzerDoes anyone have other teams inout on the security queue or its handling atm?14:45
cpaelzers/inout/input/14:45
cpaelzerI guess that is a "no by timeout"14:46
sarnoldthere was little progress last week due to a security sprint, which was excellent -- and I expect little this week, as most of my colleagues are on vacation this week and much of next week; however, we had good discussions on performing MIRs, the new folks who have taken some are keen, and I'm still feeling happy thoughts :)14:46
cpaelzeroh great14:46
cpaelzerso it seems we can hope that this isn't just on your shoulds soon then14:46
sarnoldyes14:46
cpaelzergreat14:46
cpaelzer#topic Any other business?14:46
sarnoldnone here14:47
cpaelzerI have a heads up on https://bugs.launchpad.net/ubuntu/+source/mdevctl/+bug/194239414:47
ubottuLaunchpad bug 1942394 in mdevctl (Ubuntu) "[MIR] mdevctl 1.0.0 (rust switch)" [Undecided, Incomplete]14:47
cpaelzerthis ties into the rust rules that we have discussed a while ago14:47
cpaelzerhttps://github.com/cpaelzer/ubuntu-mir/pull/3/files14:47
ubottuPull 3 in cpaelzer/ubuntu-mir "Add rust rules" [Open]14:47
cpaelzerI will soon have to rebase and re-propose that to land it14:47
cpaelzerbecause we have it almost ready in the form that was suggested14:47
cpaelzerthere are things which we need to reconsider14:47
cpaelzerfor example cargo.lock isn't yet done by the dh_cargo tooling, until it exists one can not provide it14:48
cpaelzerthere are fallbacks in our proposed ruling which we will use14:48
cpaelzerso far just an FYI so you know it comes14:48
cpaelzerand sadly the wiki has become immutable again14:48
slyonnice, thanks14:48
cpaelzernothing else from my side14:48
slyonI have once question wrt my last comment on https://bugs.launchpad.net/ubuntu/+source/lerc/+bug/197755114:49
ubottuLaunchpad bug 1977551 in lerc (Ubuntu) "[MIR] lerc" [Undecided, New]14:49
slyondo we require the build to fail on .symbols file changes?14:49
cpaelzeron breaking symbols change IIRC yes14:49
slyonthe MIR rules state that symbols tracking needs to be in place14:49
cpaelzernot on just adding new symbols14:49
slyonlerc is tracking symbols, but ignoring the changes during build14:49
slyon(only to be checked manually)14:49
sarnoldcargo.lock missing from dh_cargo :( -- do we need to ask our rust experts to help push that over the finish line?14:49
* didrocks likes to use level 4 as discussed the other days, but it’s more a personal preference on package I used to maintain directly14:50
cpaelzersarnold: (rust) yes, but I'd decouple the MIR rules and any ongoing package from that. Once it exists it shall be used, but until it does we can't require it14:50
didrocksI think though that yeah, only on removing symbols (even if adding symbols can break in C++)14:50
slyondidrocks: ACK, thanks for your input on this one! maybe we don't need to be as strict in the generic rules.14:50
slyonBut I'll ask seb to introduce a delta to make the build fail on symbols changes14:51
cpaelzerslyon: it should fail on removing a symbol - if it does that it is ok IMHO14:51
sarnoldcpaelzer: I'm afraid if we go down that path we'll eventually have a dozen packages in, and no support, and no incentive to get it done..14:51
cpaelzersarnold: and if we don't we can't update more and more waiting on the dh_cargo feature to exist14:51
slyoncpaelzer: I agree on this. So we need to patch lerc, as the maintainers do not want this, due to it being too much work for C++ libraries with lots of generated symbols names14:51
slyonthat might change on toolchain changes14:52
cpaelzerslyon: I'm really only having a soft opinion here - I do not maintain much C++14:52
cpaelzerit feels odd to add delta just for that14:52
slyonhmm14:52
didrocksif you want to be scared on how you can break the ABI in C++: https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B14:52
didrocksand you see that removing symbols is not the only way to break it :p14:53
didrocks(but I think good enough for most of the cases)14:53
cpaelzersarnold: (rust) so yes, let us hard-request that from dh-cargo asap - but allow some way to make progress in between14:53
sarnoldcpaelzer: (rust) yes, that can make sense -- but I'm really only comfortable allowing the first if we also have a resourced plan to get to a better dh_cargo situation14:54
slyon(c++ symbols) IMO it makes sense to rather be on the safe side and check/adopt .symbols after toolchain changes, rather than missing a ABI break14:54
cpaelzerack14:55
cpaelzerthat is the way to go then slyon14:55
slyonthanks. nothing else from my side14:55
cpaelzerok, that sounds like a wrap then14:56
sarnoldthanks cpaelzer, all :)14:56
cpaelzerthank you all14:56
cpaelzer#endmeeting14:56
meetingologyMeeting ended at 14:56:57 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-06-28-14.33.moin.txt14:56
didrocksthanks cpaelzer, all!14:57
slyonthanks all!14:57
joalifthanks all14:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!