/srv/irclogs.ubuntu.com/2024/08/20/#ubuntu-meeting.txt

=== Bashing-om is now known as Guest1212
=== Bashing-1m is now known as Bashing-om
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
jbichao/14:30
slyono/14:30
jamespageo/14:30
slyonc_paelzer is out today, so let me run the meeting...14:31
slyon#startmeeting Weekly Main Inclusion Requests status14:31
meetingologyMeeting started at 14:31:10 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:31
meetingologyAvailable commands: action, commands, idea, info, link, nick14:31
sarnoldgood morning14:31
slyonPing for MIR meeting - didrocks joalif slyon sarnold c_paelzer jamespage ( eslerm dviererbe )14:31
slyon#topic current component mismatches14:31
slyonMission: Identify required actions and spread the load among the teams14:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:31
dviererbeo/14:31
slyon dkms vs gcc-13 is new and for the kernel team to look into14:32
SkiaHi! If you have any questions regarding the MIR for `retry`, let me know, I'm around :-)14:32
slyonx11-utils vs luit is new (only a Recommends, so we might be able to just drop/dowgrade it to Suggests), it's for the desktop team, so I'd like to ask didrocks for investigation14:32
slyonthe other ones seem to be known/in-progress. Thanks jamespage for getting all the openstack MIRs started!14:33
slyon#topic New MIRs14:33
slyonMission: ensure to assign all incoming reviews for fast processing14:33
slyon#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:33
jamespageI have a question in those for later14:33
slyonko14:33
slyonok*14:33
slyonI'll take a look at bug #2066272 after the meeting (CC jbicha), to verify if my requirement was met14:34
-ubottu:#ubuntu-meeting- Bug 2066272 in libpanel (Ubuntu) "[MIR] libpanel" [Undecided, New] https://launchpad.net/bugs/206627214:34
slyonbug #207378314:35
-ubottu:#ubuntu-meeting- Bug 2073783 in exfatprogs (Ubuntu) "[MIR] exfatprogs" [Undecided, New] https://launchpad.net/bugs/207378314:35
=== pushkarnk1 is now known as pushkarnk
slyonthis is new and for the desktop team, I can probably take it for review14:36
slyonbug #207638114:36
-ubottu:#ubuntu-meeting- Bug 2076381 in retry (Ubuntu) "[MIR] retry" [Undecided, New] https://launchpad.net/bugs/207638114:36
slyonThis is also new and for canonical-ubuntu-qa (related to foundations). joalif do you have capacity to take that?14:37
sarnolddoes canonical-ubuntu-qa have sufficient capacity to take on new ownership?14:38
slyonSkia: ^ ?14:38
Skiayes, this would be part of what we already do in maintaining autopkgtest14:38
sarnoldack, thanks14:39
slyonI see no other MIR bugs assigned to joalif, currently. So I'm passing it to her. Please unassign yourself if you feel like you can't handle it.14:39
SkiaPlease note that the MIR also concern Jammy and Noble14:39
Skiabecause of the SRU exception for autopkgtest14:39
sarnoldthanks for pointing it out :) 700 lines of hopefully-good-quality C is probably no real risk for previous release support14:40
slyonSkia: we've been doing retroactive MIRs in the past. The versions are very close (v1.0.4 & v1.0.5) so I don't see an issue with that14:40
Skiaokay, good to hear14:40
slyonwe'd usually first handle devel/oracular, and then double-check the delta to the LTS14:40
slyonSkia: you might need to poke us about it from time to time, as it might fall through the reporting cracks when it's resolved for devel/oracular ;-)14:41
slyon#topic Incomplete bugs / questions14:41
slyonMission: Identify required actions and spread the load among the teams14:41
slyon#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:41
sarnold.. and I don't know what the actual mechanism is to get it published to main in the previous releases.14:42
Skiaslyon: noted :-)14:42
slyonsarnold: it's usually the normal MIR + (potential) security review. Then poking an AA to get it promoted14:42
sarnoldslyon: is a new upload necessary?14:42
slyonsarnold: I don't think so, as long as the MIR review doesn't find any issues. Otherwise, we'd need an SRU before being able to promote it14:43
slyonbug #2072620 is the only bug with recent updates14:43
-ubottu:#ubuntu-meeting- Bug 2072620 in referencing (Ubuntu) "[MIR] referencing" [Undecided, Incomplete] https://launchpad.net/bugs/207262014:43
slyon^ tracking update from jamespage. Is this the bug you wanted to talk about?14:44
jamespageactually its bug 207262114:44
-ubottu:#ubuntu-meeting- Bug 2072621 in rpds-py (Ubuntu) "[MIR] rpds-py" [Undecided, In Progress] https://launchpad.net/bugs/207262114:44
slyonokay. Let's wait for AOB then..14:44
jamespagereferencing just needs a bit of work to get a test suite running - working with python modules team in debian for that14:44
slyonACK, thanks for the update. Moving on.14:44
slyon#topic Process/Documentation improvements14:44
sarnoldslyon: hmm, is there an easy way to find the packages that "are in main" but don't have a new upload since the move, and thus only have .../universe/... paths on the archives?14:44
slyonMission: Review pending process/documentation pull-requests or issues14:44
slyon#link https://github.com/canonical/ubuntu-mir/pulls14:45
slyon#link https://github.com/canonical/ubuntu-mir/issues14:45
sarnoldoh wow you're really on top of things today :D14:45
slyonsarnold: I don't know... We don't need new uploads when moving things from universe->main in devel. So I'd assume the AA tooling taking care of everything.14:46
slyon(sorry, I want to save some time for AOB :P)14:46
sarnold*nod*14:47
slyonI merged https://github.com/canonical/ubuntu-mir/pull/62 earlier today. Thanks for everybody who reviewed!14:47
-ubottu:#ubuntu-meeting- Pull 62 in canonical/ubuntu-mir "Clarify exotic hardware requirements" [Merged]14:47
slyonI created https://github.com/canonical/ubuntu-mir/pull/64 earlier today, addressing a valid issue reported by eslerm (thanks!)14:47
-ubottu:#ubuntu-meeting- Pull 64 in canonical/ubuntu-mir "exceptions: copy OEM document" [Open]14:47
slyonPlease everybody take a look at ^ and give your comments on GitHub, so we can get it landed soon.14:48
slyon#topic MIR related Security Review Queue14:48
slyonMission: Check on progress, do deadlines seem doable?14:48
slyonSome clients can only work with one, some with the other escaping - the URLs point to the same place.14:48
slyon#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:48
slyon#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-mir14:48
slyonInternal link14:48
slyon#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:48
slyonsarnold: what's the status on your side?14:48
jbichaI'm curious about whether the Security team thinks it is likely for libimobiledevice-glue to complete its Security Review before 24.10 is released14:48
jbichaThis isn't to bump its priority (same priority as several other desktop pkgs), but because it is part of an incomplete transition we inherited from Debian autosync.14:48
jbichaSo if it lands for 24.10, we can leave things as they are. If it is unlikely to land, then we could work to undo the transition for 24.10 and redo it next cycle.14:48
joalifslyon: I was at another meeting, I'll take care of the MIR14:48
slyonthx joalif!14:49
jbicha(you could also look into it and get back to me about it)14:50
slyonI see a bunch of security review piling up, especially for the desktop team.14:50
sarnoldheh yeah i'll have ot do that :( the included copies of crypto code is slightly worrying14:50
sarnoldso much :(14:50
slyonmaybe c_paelzer can help raising severity for getting new security reviewers once he's back from PTO..14:51
slyonBut they'd also need to be trained first :(14:51
sarnoldwe did make some progress on sysprof, but otherwise it's a real challenge to get time from folks due to deadlines from $elsewhere14:51
slyonACK. So jbicha please coordinate with sarnold directly when you need to shuffle the desktop security review priority/order.14:52
slyon#topic Any other business?14:52
slyonjamespage: wanted to talk about bug #207262114:52
-ubottu:#ubuntu-meeting- Bug 2072621 in rpds-py (Ubuntu) "[MIR] rpds-py" [Undecided, In Progress] https://launchpad.net/bugs/207262114:52
jbichanothing else from me :)14:52
jamespageah yes14:52
jamespageso...14:52
jamespagepackage is a python wrapper around rust (similar to python-crytography)14:53
jamespageI was trying to figure out how this fits into the agreed standards for Rust packages - am I reading the rules right in that the Rust dependencies should be vendored into the package?14:54
=== pushkarnk1 is now known as pushkarnk
sarnoldyes14:54
jamespageso to confirm that's different from static linking from rust packages via BD's14:55
slyonyes, that's been common practice for the Rust ecosystem. Because non-venored dependencies have been unfeasible for now (although it would be nicer/prefered)14:55
jamespageok I was looking for prior art to follow - python-cryptography is similar14:56
sarnoldis that newly rustic?14:57
jamespagerpds-py? its in the dependency chain for jsonschema updates coming from debian14:57
sarnoldI wonder if that started doing rust after it was in main, and perhaps never got real attention to it after a transition14:57
jamespagereplacement for pyrsistent which is in main (but scheduled for demoition)14:57
slyonIf the dependency tree is small enough, it would still be nicer to do static linking from rust packages BD's, but we might not have all the correct verions in the archive and it might need lots of additional MIR paperwork for each of the BDs. So vendoring it all into the python package is the more streamlined approach14:58
sarnoldsorry, I meant the python-cryptography -- I'm curious if it actually serves as a good example of what we decided on14:58
jamespageit did switch once in main yes14:58
jamespageits small14:58
jamespagehttps://www.irccloud.com/pastebin/nivxTBBl/14:58
jamespagethat does pull in a load of other librust-*-dev packages14:59
slyon^ that's the problem14:59
jamespageinfact more than a few - loads15:00
jamespageok so I need to vendor in what's needed15:00
slyonwe'd need to work through the whole tree of librust-*-dev packages, doing MIRs. Which was deemed infeasible in the past.15:00
slyonACK. Vendoring is the way forward here.15:00
sarnolddid we have a nice discussion somewhere of the best way to approach that problem?15:01
slyonjamespage: there's been some discussion about how to best trim the set of vendored dependnecies to a minimum, I think this is the starting point: https://github.com/canonical/ubuntu-mir/issues/5115:01
-ubottu:#ubuntu-meeting- Issue 51 in canonical/ubuntu-mir "cargo vendor adds unnecessary crates" [Closed]15:01
jamespagethanks for all of the pointers :)15:02
slyonDo we have anything else for AOB?15:02
sarnoldnothing here15:02
slyon3.2.115:03
slyonthanks all! o/15:03
sarnoldthanks slyon, all :)15:03
slyon#endmeeting15:03
meetingologyMeeting ended at 15:03:26 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-08-20-14.31.moin.txt15:03
jamespagethanks slyon15:03
slyonjbicha: thanks for working on libpanel! MIR +1, https://bugs.launchpad.net/ubuntu/+source/libpanel/+bug/2066272/comments/515:10
-ubottu:#ubuntu-meeting- Launchpad bug 2066272 in libpanel (Ubuntu) "[MIR] libpanel" [Undecided, In Progress]15:10
slyonfeel free to get the dependency in or get it seeded.15:11

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