16:02 #startmeeting Weekly Ubuntu Foundations team 16:02 Meeting started at 16:02:10 UTC. The chair is juliank. Information about MeetBot at https://wiki.ubuntu.com/meetingology 16:02 o/ 16:02 Available commands: action, commands, idea, info, link, nick 16:02 #topic Lightning rounds 16:02 #link https://discourse.ubuntu.com/t/foundations-team-updates-thursday-2025-02-06/ 16:02 no matrix yet? 16:02 next month 16:03 We don't have a proper solution for publicly logging channels, and that's kind of the point of us having the meeting here in the first place ;) 16:03 \o 16:04 schopin: makes sense 16:05 * schopin can't remember the last time he'd posted a status report with actual links in it! 16:06 My commits will have to do 16:06 Also I just found a bug, brb 16:07 schopin, "maths is hard" :) 16:07 I knew you'd notice it ;) 16:08 auto a = std::move(b); 16:08 f(b); // no error 16:08 so annoying :D 16:09 Imagine spending an hour or so figuring out that oh no actually the code did nothing because the vector you were iterating over was moved away two lines above :D 16:11 #topic Release incoming bugs 16:11 #link http://reports.qa.ubuntu.com/rls-mgr/rls-pp-incoming-bug-tasks.html#foundations-bugs 16:11 enr0n, I am interested in your EOL upgrade support work (since you said something about distro-info) 16:11 ah just untagged by enr0n 16:12 #link http://reports.qa.ubuntu.com/rls-mgr/rls-oo-incoming-bug-tasks.html#foundations-bugs 16:12 bug 2096914 16:12 bdrung: I am no longer using that approach, since distro-info-data on e.g. kinetic was too old to have noble 16:12 So now it's back to statically defining upgrade paths, but in a way that's easier to keep track of IMO 16:14 the tags seem wrong? 16:14 regression-release seems awkward 16:15 that bug is a bit of a mess, none of the comments make _any_ sense 16:15 Skia: ^ 16:16 ack 16:16 let me look 16:16 comment #2 talks about a patch that introduces the issue which causes a FTBFS if anything 16:16 comment #4 has an rsync without ipv6 16:16 comment #5 claims rsync from debian, 3.3, is actually 3.4 16:17 oh, yeah, the rsync bug. I had hoped that server maybe would like to look at this 16:17 that's seems to be a build configuration issue 16:17 oh it's shared custody? 16:17 yes 16:18 It's a shared package, and the bug is a regression in a security update 16:18 Cue the 3 spidermen meme 16:18 XD 16:18 I can confirm Debian rsync package says 3.3 but rsync --version says 3.4 16:19 wth 16:19 let the other spidermen deal with it 16:19 No updates on the nn bugs 16:19 what's the process to get the Security team to look at it? 16:19 (bug 1888347, bug 2088268) 16:20 schopin: The security uploader has been subscribed to the bug? 16:21 but it's been 7 days 16:21 ¯\_(ツ)_/¯ 16:22 I subscribed the team 16:22 does anyone know why the patch linked (about reconfigure) has been added? 16:22 shrug 16:22 #topic Team proposed-migration report 16:22 #link https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs 16:22 I just see SECURITY UPDATE in the changelog, my mind goes blank afterwards. 16:22 heh 16:23 17 packages needing attention, 36 packages not yet considered late 16:23 and tired joalif 16:23 um 16:23 tired juliank 16:23 :D 16:24 recap: libgit2 is with schopin, vim with mwhudson, libpng1.6 vs gtk4 with uralt , xxhash with rkratky 16:24 numpy is with PS6 outage 16:25 I've retried all the regressions from this morning already, queue is still burning, will do again tomorrow 16:26 lapack enr0n 16:26 ack 16:27 systemd enr0n :D 16:28 ncurses: ginggs 16:29 dhcpcd : levihackerman 16:30 Leaving gcc and binutils 16:30 and that's all 16:30 #topic AOB 16:32 Noble .2 next week! :-) 16:33 If you wanted something in .2 and you haven't been pinged by the release team yet, it's probably too late :P 16:34 #endmeeting