15:04 #startmeeting Weekly Ubuntu Foundations team 15:04 Meeting started at 15:04:02 UTC. The chair is bdrung. Information about MeetBot at https://wiki.ubuntu.com/meetingology 15:04 Available commands: action, commands, idea, info, link, nick 15:04 #topic Lightning rounds 15:04 #link https://discourse.ubuntu.com/t/foundations-team-updates-thursday-8-jun-2023/36137/5 15:05 I give everybody time to read and ask questions. 15:10 o/ 15:13 "footgun" 15:14 I give everyone one more minute for reading. 15:17 #topic Release incoming bugs 15:17 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-mm-incoming-bug-tasks.html#foundations-bugs 15:17 nothing there 15:17 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ll-incoming-bug-tasks.html#foundations-bugs 15:18 https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/2008430 15:20 sounds like something we should take and resolve 15:20 though I thought all the non-PEP-440 packages were fixed by lunar? 15:21 Yes but basically the point made by the last comment is that non-distro packages that don't respect PEP440 will break apt-daemon, even if they're unrelated. 15:21 all lunar packages (except for drslib) should have PEP-440 compliant versions. 15:21 ok 15:22 anyway, +1 for us taking this, we do rather rely on aptdaemon not exploding 15:22 * bdrung agrees 15:23 targetted the bug to lunar 15:24 tagged foundations-todo and subscribed foundations-bugs 15:24 next: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2012698 15:25 desktop 15:25 so leaving that untouched 15:25 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-jj-incoming-bug-tasks.html#foundations-bugs 15:26 https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2019203 15:27 is this the same as the regression we saw in mysql in mantic-proposed from the security update? 15:27 it is 15:27 Oh, I subscribed it, but then danilogondolfo looked into it and AFAICT the conclusion was that it wasn't a glibc issue. 15:27 I didn't get around to update the status. 15:28 I helped investigating the problem. Apparently the kernel doesn't expose information about cache line sizes on armhf and the code relied on that to allocate memory 15:29 allocate cache-line-size aligned memory* 15:32 I'll mark the glibc status as Invalid then, and add the kernel in the loop. 15:32 thanks 15:32 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs 15:33 nothing for us (unless there is something in "unknown") 15:33 #topic Team proposed-migration report 15:33 #link https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs 15:34 that list is short. Enjoy it before Debian unfreezes... 15:34 indeed 15:35 fwupd continues to be stuck there 15:35 there's been discussion on the bug w/ the Debian maintainer but I haven't analyzed it 15:35 he asserts that there are flaky tests and different behavior across the autopkgtest runners 15:36 vorlon: There is a LP bug for it: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2021908 and it does not seem to be flaky...? 15:36 liushuyu: that's the bug Mario repliedto 15:36 liushuyu: will you continue to drive this one for the next week, or do you need to hand it off? 15:37 vorlon: I can take a look after finishing the armhf time_t stuff. It looks like the upstream did not gate the network tests correctly 15:37 ok 15:37 that leaves just python-apt needing an assignee 15:38 any volunteers? 15:38 Even if you turn off the network tests, some of them will still run 15:38 o/ 15:38 python-apt: schopin: 15:38 thanks 15:38 bdrung: back to you 15:38 #topic AOB 15:39 I'll be out next Wed/Thu 15:39 I'm OOO monday 15:44 #endmeeting