/srv/irclogs.ubuntu.com/2022/02/01/#ubuntu-meeting.txt

=== slyon_ is now known as slyon
=== jchittum_ is now known as jchittum
=== Kilos- is now known as Kilos
cpaelzerhiho15:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:30
meetingologyMeeting started at 15:30:22 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:30
meetingologyAvailable commands: action, commands, idea, info, link, nick15:30
cpaelzerping slyon, didrocks, sarnold, joalif, jamespage for MIR meeting15:30
didrockshey15:30
joalifo/15:30
jamespageo/15:30
cpaelzer#topic Review of previous action items15:30
cpaelzerlast week we landed a few wiki updates (done)15:30
cpaelzeradn we assigned a few MIR reviews15:30
cpaelzerI've just seen didrocks complete his a few hours ago15:31
cpaelzerand I did mine last wednesday15:31
didrocks*many* hours ago, hem hem :)15:31
slyono/15:31
cpaelzerIIRC there was one more for joalif with guidance by jamespage if needed - did that complete as well?15:31
joalifI'm working on mine, i'm about to finish it15:31
slyonI completed mine as well (set to incomplete)15:31
cpaelzerand we had something I forgot assigned to slyon, maybe not a review - /me checks logs15:31
cpaelzerah ok15:31
cpaelzergreat then15:31
cpaelzerso notihng toally stuck and forgotten15:31
cpaelzergreat15:32
cpaelzerlet us look at this weeks news then15:32
cpaelzer#topic current component mismatches15:32
sarnoldgood morning15:32
cpaelzerMission: Identify required actions and spread the load among the teams15:32
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:32
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:32
cpaelzernon-proposed looks like all-known15:32
cpaelzerlibreoffice-epiphany sounds familiar, but not of recently15:33
cpaelzerdidrocks: thinse LO is desktop, do you remember?15:33
cpaelzers/thinse/since/15:33
didrocksI don’t remember we had it on the list, I’ll look at it15:34
cpaelzerwanted to write "that" and changed my mind to 2since" => thinse :-)15:34
cpaelzerthanks for having a look15:34
cpaelzerthe rest is mostly known15:34
cpaelzermesa/postgresql-14 -> llvm-toolchain-13 really "just" waits for promotion of llvm-toolchain-1315:34
slyonack15:34
cpaelzermclemenceau:  has asked doko to have a look15:34
cpaelzerbut nothing happened for quite a while, probably busy by many other things15:35
cpaelzerslyon: do you know if doko is available enough these days to rely on him, or should we make his life easier asking another AA to promote it?15:35
slyonhe is only available a few days a week, so if it just needs promotion, we might need another AA to move it forward quicker15:36
slyons/might need/might ask/15:36
cpaelzerfoundations agrees to own it and IIRC they subscribed15:36
cpaelzerlet me check15:36
slyonyes we agreed to own LLVM. but apparently the llvm-toolchain-13 package is not yet subscribed :-/15:37
cpaelzerfoundations-bugs is not yet subscribed AFAICS15:37
cpaelzerso not "just promoting it"15:37
slyonlet me check back with doko then during our next team meeting15:38
cpaelzeryou already do the work and maintenance, we just need to correct the subscription and then promote it15:38
cpaelzerno need for a complex case, but it would unblock a lot of rather complex things in -proposed15:38
cpaelzerso I'd like to give this a  +1 in prio15:38
cpaelzerthanks slyon for carrying it to the team15:38
cpaelzerdoesn't have to be doko to handle it AFAICT15:39
cpaelzerok, enough of mismatches for today15:39
cpaelzer#topic New MIRs15:39
sarnoldpython-vitrage?15:39
cpaelzersarnold: while new it has a bug assigned per the color15:39
jamespageI'll take that its openstack related15:39
cpaelzerthanks jamespage15:39
cpaelzerhttps://bugs.launchpad.net/cloud-archive/+bug/189393515:40
ubottuLaunchpad bug 1893935 in python-vitrageclient (Ubuntu Jammy) "[MIR] python3-vitrageclient" [High, Triaged]15:40
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/twitter-bootstrap3/+bug/166715015:40
ubottuLaunchpad bug 1667150 in twitter-bootstrap3 (Ubuntu) "[MIR] twitter-bootstrap3" [High, Won't Fix]15:40
slyonthat was marked wontfix in 2019..15:40
sarnoldcomment #9 suggests the JS is just for docs15:40
cpaelzerthe latter can be painful doing much more than needed in one package and having plenty of dependencies (from my look at it for mailman3 back in the day)15:40
sarnoldI don't know how we mark those15:40
jamespageit will be15:40
cpaelzerso be careful when reviewing those jamespage15:40
cpaelzermaybe you can cut twitter-bootstrap3 and only need the python-vitrageclient15:41
cpaelzershould be much easier overall15:41
jamespageack15:41
cpaelzerok, trying again to go on with the agenda :-) Thanks for bringing it up though - was worth the discussion15:41
cpaelzer#topic New MIRs15:41
cpaelzerMission: ensure to assign all incoming reviews for fast processing15:42
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-mir15:42
cpaelzer"only one bug" but a complex one and two tasks15:42
cpaelzerstep #1 - I'd suggest we do assign two people (one per task) to split the load15:42
cpaelzeranyone feeling less than 1255 busy these days that could have a look?15:42
cpaelzer125%15:42
didrocksI am 214% this week (approximately), but if this can wait another week, I’m happy reviewing something like cargo15:43
didrockswell, by some definition of "happy" :)15:43
cpaelzerthere are quite some "TODO" left open in the bug description15:44
cpaelzerare we sure this is even meant to be ready for review?15:44
joalifsame for me, however I am happy to review whatever (right now I cannot judge the complexity of a review )15:44
slyonI've been told its ready. I think the mwhudson opinion has been clarified in the comments and an autopkgtest has been proposed in Debian15:45
cpaelzerok15:45
cpaelzerI do not really see the time either, but since I'm involved in drafting the rust rules I'll take rustc15:45
didrocksagreed that description should be updated first to address/remove TODOs15:45
cpaelzerbut for cargo at least I'd want someone else to do it15:45
sarnoldhmm, he mentions devendoring llvm.. I thought the rust folks had pretty significant changes in their llvm15:46
cpaelzerschopin: could you carry https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1957932/comments/1 into an update of the bug description please?15:46
ubottuLaunchpad bug 1957932 in rustc (Ubuntu) "[MIR] rustc, cargo" [Critical, New]15:46
cpaelzerI think for rustc I'm gonna do a first level reivew asking for detailed plans on llvm but also things like dh-cargo and others that came up while drafting the MIR rules for it15:48
cpaelzerlooking for a cargo volunteer15:48
cpaelzerIf no one says yes it will be didrocks with the acknowledgement to do it next week and a big credit for next "looking for volunteers" round :-)15:49
sarnoldhehe15:49
cpaelzerok that will be it15:49
didrocks(beers in Franfurt :p)15:49
cpaelzerwe have to get through our content to not miss other bits ...15:49
cpaelzer#topic Incomplete bugs / questions15:49
cpaelzerMission: discuss the recent activity to identify any follow up action15:49
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-mir15:49
cpaelzerI have pinged ahasenack on FRR, thanks didrocks for the review15:50
didrocksyw!15:50
cpaelzerSince it was a security-team request to please change quagga->frr I hope we can still get a fast-pass on an security ack15:50
cpaelzerthe other things you asked on the bug seem fine and ahasenack is great at resolving those15:51
cpaelzereverything else is older15:51
cpaelzerv4l2-relayd15:51
slyonthat one is back to the reporter15:51
cpaelzeroh I see, long list of todos15:52
cpaelzerthanks15:52
slyonI assembled a list of TODOs that needs improvement15:52
cpaelzer#topic MIR related Security Review Queue15:52
cpaelzerMission: Check on progress, do deadlines seem doable?15:52
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:52
cpaelzersarnold: any news that will raise our mood on this?15:52
sarnoldonly slightly, python-cheroot is still in progress, no progress on adsys15:53
cpaelzerI see foundations and Desktop have updated their deadlines/milestones15:53
slyon\o/15:53
cpaelzer10 Packages (+FRR/libyang2 that we know of + potentially a bit more over the next few weeks)15:53
sarnoldhaving these milestones, and the launchpad config to see them :), is pretty fantastic15:53
slyonyeah... the Rust/Cargo MIR is one of them..15:54
slyon(once assigned to security)15:54
cpaelzerif we look at feature freeze or even beta that means from now on we will need like 3-4 per week done to go on15:54
cpaelzerjust to size the focus and priority correctly15:54
cpaelzer@sarnold15:54
sarnoldwell, I *was* feeling optimstic..15:55
cpaelzeror you shut down security for a week at the last possible time and all do just reviews - but then no time is left, so no findings allowed :-)15:55
cpaelzerPlease be optimistic, but I just wanted to make clear what velocity you need to get it done - so you can scream for more people in the team meetings that you have15:56
cpaelzerand by that we get to15:56
cpaelzer#topic Any other business?15:56
sarnoldnothing from me15:56
cpaelzernothing from me15:56
joalifnothing15:56
didrocksnothing either15:56
slyonnothing here15:56
cpaelzerok then, closing for today ... just in time15:57
cpaelzerthank you all15:57
cpaelzer#endmeeting15:57
meetingologyMeeting ended at 15:57:07 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-02-01-15.30.moin.txt15:57
sarnoldthanks cpaelzer, all :)15:57
slyonthank you all!15:57
joalifthanks all, bye15:57
didrocksthank you all :)15:57
seb128arg, I had a question but missed the meeting15:57
seb128already, next week15:57
seb128alright15:57
cpaelzerif it can wait seb128, then yes next week15:57
cpaelzerotherwise use the full ping list (see the meeting start) and ask it now15:58
cpaelzerwon#t be in the log though15:58
seb128I will ask anyway in case it's easy reply15:58
seb128but I will ask officially next week otherwise15:58
cpaelzerok15:58
seb128is it possible to MIR a trivial binary package from a complex source?15:58
seb128or would that be better split in a new source somehow?15:58
seb128asking because we would like to preinstall steam-devices which is a bunch of udev rules but built from the steam source15:59
seb128(ideally those rules wouldn't be needed and be included in systemd or something standard, I will investigate that possibility first)15:59
cpaelzerseb128: "better" split it, but sometimes the effort of the split - the related Debian Delta and all that is just too painful16:05
cpaelzerseb128: therefore if CAN be done to just promote one binary16:05
cpaelzerseb128: it depends a bit if the source between "to be promoted" and "to stay behind" is rather clear split in the archive or not16:06
cpaelzerimagine two small .c files to build binaries and a gigantinc shared C file -> bad case16:06
cpaelzerseb128: but two separate subdirectories and the to-be-promoted binary just coming from one -> good csae16:06
seb128in this case it's steam and on the side a small binary with udev rules16:06
seb128so that's the easy case probably16:07
didrocksI’m afraid that after some years, we go with what we hear often ("the source is in main, so promoting the binary doesn’t need a full MIR review")16:07
seb128the alternative would be to create a new source with the rules, but then we need a delta to remove the binary from steam and create a new package and keep it updated16:07
didrocks(even if the initial MIR ack was "only for this binary package)16:07
cpaelzerthe problem is what didrocks outlined that later on someone can come by and say "from the same source, please promote"16:08
seb128right16:08
cpaelzerbut for that we have these two lines in the template for reviewers16:08
cpaelzerto at least document it in the MIR clearly16:08
cpaelzerTODO: List of specific binary packages to be promoted to main: <TBD>16:08
seb128anyway it's post your meeting, I didn't meant to drag you into a late discussion16:08
cpaelzerTODO: Specific binary packages built, but NOT to be promoted to main: <TBD>16:08
seb128I will raise it again at the next meeting16:08
seb128thanks for the replies!16:08
didrocksyeah, we need to ensure AA look for the MIR bug before doing any AA work16:08
didrocksfood for thoughts for next week :)16:09
seb128or we should explicitly blacklist the other binaries16:09
cpaelzer^^ this16:09
seb128we have some list of things that should not be promoted irrc16:09
seb128with things like ffmpeg codecs on it16:09
seb128just to make sure they don't get pulled in by mistake16:09
seb128but then the list might get outdated with new binaries from the source created after the promotion...16:10
cpaelzerI think that only matters to avoid auto-inclusion, if there is an explicit seed or dependency added it would still get in IIRC16:10
seb128we maybe should create a promotion blacklist16:10
seb128or system to avoid promoting other binaries from a source16:10
seb128cpaelzer, oh, while I'm talking to you, did you see https://github.com/cpaelzer/ubuntu-mir/pull/5 and is that the right way to suggest such changes? or should I rather bring that up to the next meeting as well?16:12
ubottuPull 5 in cpaelzer/ubuntu-mir "Tweak TBD placeholders" [Open]16:12
cpaelzerseb128: that PR plus pinging in the meeting is the recommended way16:13
cpaelzerthere are no notifications set up at all16:13
cpaelzerso we will miss it until there is a ping16:13
seb128k, I will ping next week :)16:13
ahasenackon the topic of promoting specific binaries, nginx comes to mind16:20
ahasenackwhen it was MIRed, there was one binary package that was explicitly stated to NOT be promoted to main16:20
ahasenackbecause its source was in debian/*, not part of upstream, and that was not reviewed in the MIR16:20
schopincpaelzer: ACK on the rust MIR comment/description thing16:44
=== genii is now known as genii-core

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