== Meeting information == * #ubuntu-meeting: Weekly Ubuntu Foundations team meeting, started by juliank, 07 Nov at 16:02 — 17:07 UTC. * Full logs at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-11-07-16.02.log.html == Meeting summary == === Lightning rounds === Discussion started by juliank at 16:02. === Release incoming bugs === Discussion started by juliank at 16:03. * ''LINK:'' http://reports.qa.ubuntu.com/rls-mgr/rls-pp-incoming-bug-tasks.html#foundations-bugs (juliank, 16:03) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2086104 (mkukri, 16:03) * ''LINK:'' http://reports.qa.ubuntu.com/rls-mgr/rls-oo-incoming-bug-tasks.html#foundations-bugs (juliank, 16:21) * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2083131 (liushuyu, 16:26) * ''LINK:'' http://reports.qa.ubuntu.com/rls-mgr/rls-nn-incoming-bug-tasks.html#foundations-bugs (juliank, 16:28) * ''LINK:'' http://reports.qa.ubuntu.com/rls-mgr/rls-jj-incoming-bug-tasks.html#foundations-bugs (juliank, 16:48) * ''LINK:'' http://reports.qa.ubuntu.com/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs (juliank, 16:54) === Team proposed-migration report === Discussion started by juliank at 16:54. * ''LINK:'' https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs (juliank, 16:54) === AOB === Discussion started by juliank at 16:55. == People present (lines said) == * juliank (79) * schopin (15) * enr0n (8) * ravikant_ (7) * andersson123 (5) * slyon (5) * mkukri (3) * meetingology (2) * liushuyu (2) * adrien (1) * uralt (1) * r41k0u (1) * bdrung (1) == Full log == 16:02 #startmeeting Weekly Ubuntu Foundations team 16:02 Meeting started at 16:02:22 UTC. The chair is juliank. Information about MeetBot at https://wiki.ubuntu.com/meetingology 16:02 Available commands: action, commands, idea, info, link, nick 16:02 #topic Lightning rounds 16:02 We skip today 16:03 #topic Release incoming bugs 16:03 o/ 16:03 #link http://reports.qa.ubuntu.com/rls-mgr/rls-pp-incoming-bug-tasks.html#foundations-bugs 16:03 o/ 16:03 bug 2083942 16:03 \o (half around only) 16:03 o/ 16:03 https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2086104 16:04 we are still talking about bug 2083942 16:04 :D 16:04 should we tag it todo? 16:04 enr0n: I think we should tag this todo 16:05 bug 2085070 seems for schopin 16:05 Well, anyone who wants to do an SRU can take it too :) 16:06 schopin: yes ^ 16:06 who needs/wants to do an SRU? 16:06 But yes clearly it needs to be tagged. 16:06 schopin: Well yes I just want you to drive and judge whether that's correct 16:07 We do not ship a glusterd 16:07 andersson123 wants to do an STU 16:07 We don't? Oh well :P 16:07 SRU* 16:07 Ah ok glusterfs-server 16:07 enr0n I can take this up 16:07 apt search didn't pop anything up 16:08 I can take one at another time since Mate is volunteering :) 16:08 r41k0u spoke first (and in the correct place too) 16:08 Well ok then 16:09 bug 2085142 16:09 this isn't anything we can do I suppose 16:10 We can file a ticket with IS 16:12 I have filed a ticket with IS 16:12 Any volunteer to drive this? 16:12 If IS tells me it's not their task I can circle back 16:13 I guess Julian volunteered then :) 16:13 I'll keep it as incoming for a week 16:13 To force me to check next week 16:13 bug 2015538 16:13 That one again.. 16:13 Should we move this to qq now 16:13 we still need somebody to do the upstream gdm work 16:14 as long as that work doesn't get done, we can't move forward 16:14 maybe we should drop the tag until somebody (some team) picks up that work? 16:15 Just pushing it forward each cycle for consideration seems sensible to me 16:15 I fear that if we do nothing will ever happen. 16:15 (do drop the tag I mean) 16:21 liushuyu: the implementation is at https://github.com/bus1/dbus-broker/pull/321/files 16:21 #link http://reports.qa.ubuntu.com/rls-mgr/rls-oo-incoming-bug-tasks.html#foundations-bugs 16:22 bug 2085157 16:22 I already started working on it. So please tag it. 16:23 tagged 16:23 bug 2085548 16:26 https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2083131 16:26 I left a comment on the first bug 16:27 And I'll tag the second one as todo I guess 16:28 #link http://reports.qa.ubuntu.com/rls-mgr/rls-nn-incoming-bug-tasks.html#foundations-bugs 16:28 bug 2041518 16:28 that one was with desktop 16:29 bug 2085314 16:29 enr0n: 16:29 looking 16:29 There's a fix upstream to cherry pick 16:30 Reproducer for SRU may be tricky 16:30 maybe valgrind would pick up the overflow? 16:31 Either way we can upload it and convince SRU team that we can't reproduce it but upstream says it fixes it or something? 16:31 it looks like there is a somewhat reliable repro on the bug report. I will give it a shot and tag this for SRU if so 16:31 something something micro release exceptions for systemd 16:32 heh 16:32 bug 2060676 16:32 does systemd *do* microreleases? 16:32 yes 16:32 yes 16:32 schopin: yes 16:32 lol3 16:32 This sounds like a won't fix? 16:33 Oh well Debian has a fix 16:33 Last time I looked at it I couldn't figure out where it came from 16:33 let's do it I guess, this is weird auditing 16:34 bug 2078596 16:34 This is about broken command-not-found data 16:35 We have no straightforward way to fix it as the release pocket is frozen 16:35 re the shadow bug, it's fairly low priority, I'm not sure we'd want to risk an SRU just for this? 16:35 schopin: I'd rather fix it now before it comes back in from very annoyed customers via support 16:36 heh, at least they'd feel they get their money's worth? 16:36 These get to security-relevant logs and can flare up auditing things 16:38 I can take ! 16:39 I volunteer ... Katniss style 16:39 andersson123: the command-not-found issue or the shadow thing? 16:39 whichever is simplest :) 16:39 * schopin imagines andersson123 with a long braid. 16:40 command-not-found requires inventing a new mechanism in command-not-found to have fixups 16:40 and infrastructure changes 16:40 andersson123: shadow is simpler. 16:40 Shadow then please (my fav hedgehog) 16:41 Yay delegation \o/ 16:42 is this related? 2066199 16:42 bug 2066199 16:42 This would fix that one instance for sure 16:42 But I think it's worth fixing the general case 16:43 We need to do a one-off hack to command-not-found in to ignore everything not actually published in noble 16:43 as we can't fix the noble data 16:46 bug 2078579 16:48 #link http://reports.qa.ubuntu.com/rls-mgr/rls-jj-incoming-bug-tasks.html#foundations-bugs 16:48 sorry I missed bug 2086506 16:52 I'll go look at my discussions about this a couple months ago and then I'll come back to this next week 16:53 bug 2085951 16:53 update-notifier seems to miss a Depends: python3-debian 16:53 in jammy and below 16:54 #link http://reports.qa.ubuntu.com/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs 16:54 empty 16:54 #topic Team proposed-migration report 16:54 #link https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs 16:55 ginggs said this is too much in flux and we should do it next week after everything got retried 16:55 We are also running out of time anyway 16:55 #topic AOB 16:55 if we are going to tag 2085951, should we also add an assignee? 16:55 otherwise it's gonna get lost in the ether 16:55 juliank: can you triage this bug https://bugs.launchpad.net/ubuntu/+source/libzstd/+bug/2086543 16:55 Ah yes, who wants to add a dependency? 16:56 mkukri wanted to do an SRU I think? 16:57 took it 16:59 ravikant_: I think static libraries are not supposed to be built with fPIC so this is correct? 16:59 But it's a tool chain question 16:59 at least -fPIE maybe? or otherwise you cannot link them into pies 17:07 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)