/srv/irclogs.ubuntu.com/2023/06/20/#ubuntu-meeting.txt

=== Guest277 is now known as ogra
=== ogra is now known as Guest711
=== Guest711 is now known as ogra
cpaelzerhiho, getting this started early as we ran over last time14:29
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:30
meetingologyMeeting started at 14:30:17 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:30
meetingologyAvailable commands: action, commands, idea, info, link, nick14:30
eslermhello o/14:30
didrockso/14:30
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )14:31
cpaelzerhi everyone14:31
slyono/14:31
cpaelzer#topic current component mismatches14:31
cpaelzerMission: Identify required actions and spread the load among the teams14:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:31
slyonoh lovely *-perl14:32
cpaelzeryou missed it last week slyon14:32
joalifo/14:32
cpaelzerbryce is on the big tree out of spamassassin14:32
cpaelzerwe haven't settled on a solution yet14:32
sarnoldgood morning14:32
slyonhaha, OK. I guess I'll investigate libio-compress-brotli-perl14:32
cpaelzerslyon: you might, but IIRC matt mentioned that Steve looked at it already14:33
slyonok. I'll check back with them14:33
cpaelzerslyon: so ensure to not do redundant work14:33
cpaelzerruby-rack is stuck intentionally for now, kanashiro[m] is on that14:34
cpaelzereverything else is known and ok14:34
cpaelzerno action here14:34
cpaelzer#topic New MIRs14:35
cpaelzerMission: ensure to assign all incoming reviews for fast processing14:35
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:35
cpaelzerfirst of all14:35
cpaelzerthe easy cases14:35
cpaelzerglibmm, gtkmm, cairomm are just source uploads of the same we had14:36
cpaelzerso those get usually a fast sanity check if they are really the same14:36
cpaelzerjoalif: did one of them - and we said if this worked out as expected we will distribute the others and expect them to be quick checks14:37
joalifit was fairly simple14:37
joalifthe source code didnt have extensive changes14:37
cpaelzerjoalif: and was it, as expected, just the same as before14:37
cpaelzergood14:37
cpaelzerthanks14:37
cpaelzerso today let us hand out the other three14:38
cpaelzerbut with a low effort expectation14:38
joalifi can have one of them14:38
cpaelzerI'm happy to take glibmm14:38
slyonjoalif: which one was the one you handled, could you share the LP reference, so we can use it as a template?14:38
cpaelzerjoalif:  for another - gtkmm then14:38
cpaelzerslyon: cairomm ok?14:38
slyonsure!14:38
didrocksI can take 2 or have 1 and then, next week another one14:38
joalifslyon: https://bugs.launchpad.net/ubuntu/+source/pangomm2.48/+bug/202026714:38
-ubottu:#ubuntu-meeting- Launchpad bug 2020267 in pangomm2.48 (Ubuntu) "[MIR] pangomm2.48" [Undecided, In Progress]14:38
slyonthx14:38
cpaelzerthe last one is https://bugs.launchpad.net/ubuntu/+source/libhttp-cookiejar-perl/+bug/202424514:39
-ubottu:#ubuntu-meeting- Launchpad bug 2024245 in libhttp-cookiejar-perl (Ubuntu) "[MIR] libhttp-cookiejar-perl" [Undecided, New]14:39
cpaelzerthat might have been the one Matt informed me about14:39
didrockssounds like good Friday’s material then14:39
didrocksperl :p14:39
didrockshappy to take it14:39
cpaelzerindeed it is14:39
didrockswell "happy…" it’s perl14:39
cpaelzerso slyon the other one is new and for you14:39
didrocksbut you know what I mean :p14:39
slyonack14:39
cpaelzerassigned didrocks14:39
cpaelzerthank you all14:40
cpaelzerlet us look at the incomplete14:40
cpaelzer#topic Incomplete bugs / questions14:40
cpaelzerMission: Identify required actions and spread the load among the teams14:40
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:40
cpaelzerduktape I looked at14:40
cpaelzerthey did what we asked14:40
cpaelzerand committed to do some more later (out of the recommended set)14:40
cpaelzerthis is ready to promote, but waits for the newly added tests to run on infra once14:41
cpaelzerincomplete until then14:41
sarnoldyay new tests :)14:41
cpaelzeryou should be happy14:41
cpaelzerthe other updates have been present last week14:41
cpaelzerso that is fine14:41
cpaelzer#topic Process/Documentation improvements14:42
cpaelzerMission: Review pending process/documentation pull-requests or issues14:42
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls14:42
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues14:42
seb128https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/1997560 also needs to be re-reviewed please14:42
-ubottu:#ubuntu-meeting- Launchpad bug 1997560 in libcamera (Ubuntu) "[MIR] libcamera" [Undecided, New]14:42
cpaelzerdo not mind pull #17 and issue #22 - I haven't found time yet14:42
cpaelzerhi seb128, thanks for the ping - having a look14:42
cpaelzerslyon: that is your case, can you do that re-check?14:43
seb128thx, I expect that's for slyon since he did the first review14:43
cpaelzerPR 23 I have requested some changes to make it more useful - waiting on dviererbe14:43
cpaelzerthat leaves the potentially longer open discussions14:43
slyonseb128: cpaelzer: I'll be looking into libcamera and comment on the bug report14:43
cpaelzerthanks slyon14:43
seb128slyon, thanks14:43
cpaelzerboth by seth asking for reflection on how we work14:44
cpaelzerhttps://github.com/canonical/ubuntu-mir/issues/2414:44
-ubottu:#ubuntu-meeting- Issue 24 in canonical/ubuntu-mir "More team members" [Open]14:44
cpaelzeron this, while we are all busy - I do not yet see a real shortage14:44
cpaelzerwe generally get things adressed in a timely manner14:44
cpaelzerand the thought of more work is mostly around re-reviews which we already throttled by suggesting to fill into a constant 1-per-week load14:45
cpaelzerso that would be fine14:45
cpaelzerfurthermore the team composition is meant to be a bit "one of each" for foundation, desktop, server, seg, ...14:45
cpaelzerso adding would be ... duplicating?14:45
cpaelzerI see no need for either yet14:45
cpaelzerthe real question in there - for now - I think is "How do we add more?"14:46
cpaelzerthis isn't defined14:46
cpaelzerso far it has been a team discussion and team decision14:46
cpaelzerthis isn't a place you'd "apply" for unless you got pushed that way by a manager right?14:46
didrocksyes, it’s mostly cooptation, and a lot of ubuntu teams are like this14:46
sarnoldor just sort of volunteered by team mates? :) (hello eslerm, dviererbe :)14:47
cpaelzerI know that generally such a question "How do we add more?" in a similar "weakly defined" way is being worked on. As others like SRU and archive admins are like it14:47
cpaelzeryes you might be pulled in like eslerm and dviererbe14:47
=== coreycb_ is now known as coreycb
slyonI think I saw a similar discussion on the TB mailing list..14:47
cpaelzerbut remember that in theory they are good friends but no members, if it ever comes to voting and qorum and such14:47
cpaelzerslyon: yes that is what i mean14:48
cpaelzerlet them sort it out for an example team14:48
slyonthat is more about Ubuntu, which MIR is not necessarily part of (this is more of Canonical), but we could use the same process, once defined14:48
cpaelzerif there is a best practice out of that we might juts pick it up14:48
cpaelzeris that a sufficien state for now sarnold?14:48
sarnoldwe've had a few very small meetings, that raised the question.. and if we intend to get through the 2300-ish packages in main in a decade, we might need more help?14:48
cpaelzersarnold: I'd want to bother about that if/once we ever conclude on really being able to do re-reviews as a company14:49
cpaelzerwe will start slow with the capacity we have, see if the teams can at all follow up14:49
cpaelzerand once proven worthwhile we can think about expanding14:49
sarnoldcpaelzer: okay, so leavaing that aside, you feel like the work is otherwise reasonable enough and not yet cause for concern?14:49
cpaelzeryes14:49
cpaelzeronly the security side of things sometimes stalls :-)14:50
cpaelzerbut this got better since you sarnold have eslerm as buddy14:50
sarnoldand occasional meetings with two or three team members showing up is also no cause for concern?14:50
sarnoldcpaelzer: and much help from others :)14:50
cpaelzerindeed14:50
cpaelzersarnold: it hasn't been blocking us that we attend as we are available (like no PTO coverage)14:50
cpaelzerif it would be, I'd consider it - but since it worked fine - why make things more ocmplex14:51
sarnoldcool, thanks for the discussion; and I'm glad to hear the larger question is being asked elsewhere, too14:51
cpaelzerindeed14:51
cpaelzersarnold: would you mind copy&paste and self-close your issue?14:51
sarnoldcpaelzer: good idea14:51
cpaelzermy time runs out soon with a hard stop and a conflict14:51
cpaelzertrying to present the next case14:51
cpaelzerbut mind the time14:52
cpaelzerhttps://github.com/canonical/ubuntu-mir/issues/2614:52
-ubottu:#ubuntu-meeting- Issue 26 in canonical/ubuntu-mir "Decide if we get enough value from c++ symbols tracking to keep doing it" [Open]14:52
cpaelzerfiled by sarnold but brought up by seb12814:52
cpaelzerI can tell you how I feel, and you please tell me what you think - ok?14:52
cpaelzerI've seen cases where - with some effort - C++ symbols were made useful14:52
cpaelzerdue to that I like to ask the teams to give it a shot14:52
cpaelzerand I've seen cases14:52
seb128the libcamera MIR which is ready for re-review mentioned earlier sort of collide with that (though they are now bumping the soname with every version which might be enough for us to get away with it)14:53
cpaelzerwhere they have tried and based on that came back to explain well why it won#t work int his case14:53
cpaelzerseb128: that is a trick to get out, but yeah perma soname bump is avoiding that too14:53
cpaelzerso in my mind maybe we should extend the explanation in the RULE lines14:53
cpaelzerto explain that people should have a reasonable look14:53
slyondid we have precedence for such soname bumping in the past?14:54
cpaelzermaybe with a hint where it worked well14:54
sarnolddoes that mean a new libcameraN every release?14:54
seb128sarnold, yes14:54
slyonI mean.. it avoids the issue that .symobls is trying to fix, so should be acceptable from the MIR perspective?14:54
cpaelzerslyon: yes, dpdk does that for example14:54
cpaelzeronce every year14:54
cpaelzerand it was much nicer14:54
cpaelzerbut14:54
cpaelzerwe still do symbols tracking there14:54
sarnoldare we proposing bumping sonames out of cadence with upstream?14:55
cpaelzerand it cought errors a few times14:55
slyonyes, that means some extra libcameraN transitions, but I guess there are not (yet?) too many reverse dependencies14:55
cpaelzere.g. on supposed stable updates14:55
cpaelzerso even if soname gets bumped each time, for SRUs symbols tracking is helpful14:55
cpaelzerreal life experience14:55
cpaelzerwhich in turn means "so bumps each time" is no reason to say "we won't do symbols tracking"14:56
cpaelzerI consider a proper, "this is what I tried, this is why it fails and this is why it is feasible" statement the right way14:56
slyonok. So this ^ might be a problem for the libcamera MIR, seb12814:56
cpaelzerI'd not want to give a too easy option to pass on symbols, but also I acknowledge that symbols isn't a strict requirement14:57
cpaelzerdoes that make sense?14:57
seb128slyon, I will follow up with a comment stating that14:57
slyonthanks14:57
didrocksI think this is in line and solidify what we were asking for C++ libs, no? Just more official (give it a shot at least, try it, and assess with the result, but start with trying it)14:57
slyoncpaelzer: yes that makes sense. especially the SRU argument is very valid!14:57
seb128I still think the experience is expensive and broken14:58
cpaelzermaybe your libs really are different than ours14:58
seb128there is no decent way to deal with the cross arch difference14:58
cpaelzeras it was said multiple times, that might be fine - but it depends on the code seb12814:58
seb128like libcamera which synced from Debian had around 190 lines of symbols diff14:58
cpaelzerone package might have that issue, explain and demonstrate14:59
cpaelzerand get an ack to be without symbols14:59
seb128right14:59
cpaelzeranother package might work well14:59
seb128long term I still think that as a project we should aim at doing better14:59
cpaelzerwhich is better than saying "yo do not need to bother about symbols"14:59
seb128also symbols don't really cover abi, they wouldn't catch a change in a structure definition14:59
cpaelzerI agree to "as a project we should aim at doing better", i Just have no great option and time to work on yet14:59
seb128I'm +1 with the 'give it a try be be allowed to explained why it doesn't work for this project'15:00
cpaelzergreat15:00
cpaelzermy next double concurrent meeting has started15:00
didrockssame here15:00
sarnoldhappy meeting15:00
seb128we were also playing with the alternative option of 'enforce the symbol on amd64, at least it's manageable and better than not having it'15:00
cpaelzerwould someone be ok to convert this into a PR to mention it more clearly in the RULES section?15:01
cpaelzerthat would indeed be better if you can get it to work15:01
eslermat next meeting, I would like to discuss the status of LP#199381915:01
-ubottu:#ubuntu-meeting- Launchpad bug 1993819 in dh-cargo (Ubuntu) "MIR: cargo, dh-cargo" [High, In Progress] https://launchpad.net/bugs/199381915:01
seb128it's still tedious, but it's on one arch and be handled locally so probably an acceptable tradeoff for the extra safety15:02
cpaelzereslerm: I've given it a bump to be sure we see it15:02
eslermthanks15:02
cpaelzeryep15:02
sarnoldseb128: is this something you're actively experimenting with? or an idea being kicked around?15:02
cpaelzerseb128: would you mind to throw a PR to https://github.com/canonical/ubuntu-mir15:02
cpaelzerthat way you can ensure the suggested change matches what you'd like15:02
cpaelzerand we can check if it matches what we thought to be the outcome of this meeting15:03
seb128cpaelzer, I can do that yet15:03
cpaelzerthanks15:03
seb128np!15:03
cpaelzerwe are over I know15:03
cpaelzerso let us hope to be quick and easy on the last two agenda items15:03
cpaelzer#topic MIR related Security Review Queue15:03
cpaelzerMission: Check on progress, do deadlines seem doable?15:03
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.15:03
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-mir15:03
cpaelzer#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-mir15:03
cpaelzerInternal link15:03
cpaelzer- ensure your teams items are prioritized among each other as you'd expect15:03
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much15:03
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:03
cpaelzerthat looked good recently15:03
sarnoldthere's progress on many MIRs simultaneously :) it's a fun place to be15:03
cpaelzerindeed sarnold15:04
cpaelzercargo will be discussed next week as eslerm requested15:04
cpaelzerbut overall that security queue LGTM15:04
cpaelzeryou even slowly but surely get to those libheif related packages15:05
cpaelzergreat15:05
cpaelzerI'd bve happy and go on ...15:05
cpaelzer#topic Any other business?15:05
sarnoldnone here15:05
cpaelzernone here either15:05
slyonnothing15:05
joalifnothing15:05
eslermsame :)15:05
cpaelzerthese meetings start to run over more often, which isn't too bad as it shows how active and approachable we are. If it is too often we can push more discussions to e.g. GH issues15:06
cpaelzerI'd close it out, thank you all15:06
sarnoldthanks cpaelzer, all :)15:06
cpaelzer#endmeeting15:06
meetingologyMeeting ended at 15:06:20 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-06-20-14.30.moin.txt15:06
joalifthanks cpaelzer, all :)15:06
seb128thanks and sorry for contributing to the longer meettings!15:06
seb128sarnold, we were desktop-discussing doing the symbols enforcing on amd64 for the gtkmm packages, basically just overriding dh_makeshlibs in debian/rules with different -c level on amd64 and !15:06
eslermthanks, bye all o/15:06
slyonthanks, bye!15:06
sarnoldseb128: awesome; that sounds like a really nice middle-ground to get much of the value of the checks and if it is easier to work with, so much the better15:07
seb128one thing that would also help probably there is to have a reference documentation of how to do symbols for c++ libraries15:08
sarnoldyes15:08
sarnoldevery single time this comes up my head spins trying to keep track of which pieces are documented where, and it never seems like it's at the right level for my needs15:09
=== Mr_Pan_ is now known as Mr_Pan
=== klebers_ is now known as klebers
=== adrien_ is now known as adrien

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