=== cpete1 is now known as cpete === mIk3_09 is now known as mIk3_08 [15:01] o/ [15:01] o/ [15:01] o/ [15:01] \o [15:02] o/ [15:02] o/ [15:02] o/ [15:02] #startmeeting Weekly Ubuntu Foundations team [15:02] Meeting started at 15:02:59 UTC. The chair is bdrung. Information about MeetBot at https://wiki.ubuntu.com/meetingology [15:03] Available commands: action, commands, idea, info, link, nick [15:03] #topic Lightning rounds [15:03] #link https://discourse.ubuntu.com/t/foundations-team-updates-thursday-14-sep-2023/38635 [15:04] With the -security pocket fix will that end up in the jammy version of the snap? [15:04] o/ [15:04] ogayot: ^^ [15:05] bdmurray: when the snap is promoted to latest/stable, it should [15:05] bdmurray, looking at https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/450971 - jq will be much better at parsing json and spitting out what you want [15:06] bdrung: Yes, see the line above. We are just sorting out issues installing jq in the charms... [15:06] or a more specific channel if there is one for jammy - but the intention is indeed to have a refresh available for jammy [15:06] I just don't want to have to think about this in February [15:06] \o [15:07] zhsj: I love OCaml :) [15:07] waveform: Started filling out release notes for mantic - yeah \o/ [15:08] adrien: 😯😯 [15:11] zhsj: if that's about the ocaml thing, it's oddly popular among French programmers, because it's widely used as a teaching language. [15:12] I wish discourse would tell me the bug title on mouseover [15:16] all finished reading? [15:17] zhsj: I don't have much time to checkout that and debug it but overall the debian ocaml team is very good; I'd be surprised this isn't already noticed and planned [15:19] adrien: same error in debian, and liquidsoap has been removed testing. Debian bug #1042099 [15:19] -ubottu:#ubuntu-meeting- Debian bug 1042099 in src:liquidsoap "liquidsoap FTBFS: Error: This expression has type ... but an expression was expected of type" [Serious, Open] https://bugs.debian.org/1042099 [15:20] actually it's no longer problem for nbs, as it has been removed from mantic-release. i'm just on an old nbs.html when i did the work [15:22] upils: discourse pointedly reminds me to say welcome :) [15:22] thanks :) [15:22] zhsj, you mentioned https://code.launchpad.net/~zhsj/ubuntu/+source/libevent/+git/libevent/+merge/451102 which is not sponsored yet but it does not appear on https://reports.qa.ubuntu.com/reports/sponsoring/ [15:23] bdrung: he pinged us directly in -devel [15:23] upils: could be helpful if you give us a realname mapping in your IRC client and discourse profile [15:24] zhsj: unfortunately the debian release schedule is not the same as ours :'( I'd need to checkout the sources and build myself which I can maybe do tomorrow [15:25] adrien: awesome [15:27] #topic Release incoming bugs [15:27] #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-mm-incoming-bug-tasks.html#foundations-bugs [15:27] bug #2034986 [15:28] -ubottu:#ubuntu-meeting- Bug 2034986 in ubuntu-release-upgrader (Ubuntu) "some text became unreadable during a distribution upgrade" [Critical, Confirmed] https://launchpad.net/bugs/2034986 [15:28] vorlon suggested I report that [15:28] \o/ [15:29] longstanding issue where fonts go wonky after things are upgraded on disk [15:29] my 10,000ft suspicion is that it's triggered by the update to the system fontconfig cache [15:29] but I don't really *know*; I just know that it's a recurring issue [15:30] I have seen such behaviour on upgrade in the past as well [15:31] if we can put some time into investigating it this cycle, that will serve us for 24.04 [15:31] because if it happens on 23.04->23.10 it will also happen on 22.04->24.04 [15:33] I agree that we will expect that bug to appear on 22.04->24.04 [15:33] I also agree it should be sorted [15:34] ok let's take it \o/ [15:36] next: bug #2033440 [15:36] -ubottu:#ubuntu-meeting- Bug 2033440 in ubuntu-meta (Ubuntu Mantic) "ubuntu-desktop: unnecessary hard 'Depends: pipewire-audio'" [Undecided, New] https://launchpad.net/bugs/2033440 [15:36] that's a desktop team decision [15:36] also, it's targeted to mantic [15:36] so the tag should be cleared [15:37] also I would wontfix it if it were me [15:37] it targets lunar and mantic. [15:38] leaving it for the desktop team (ubuntu-meta is in their list as well) [15:38] ok there's ambiguity about whether removing the tag drops it from the desktop team's incoming queue [15:39] next: bug #2034759 [15:39] -ubottu:#ubuntu-meeting- Bug 2034759 in livecd-rootfs (Ubuntu) "riscv64 and generic preinstalled images use default ubuntu:ubuntu user where no other images do" [Undecided, New] https://launchpad.net/bugs/2034759 [15:40] there was clarification that they set a default l/p but disable ssh password authentication [15:41] and in fact I thought riscv64 was worse that pi but it was the other way around :) [15:41] +1 on that. I'd love us using ubuntu-image for riscv64 images too [15:42] anyway I think this is not actionable for mantic [15:42] because "make riscv64 as good as pi" was what I meant and there's nothing to be done [15:43] I'm fine to just close it invalid [15:43] Would like to revisit this for nn though [15:44] sil2100: I think we need to sink with local-optimum before we could commit to anything [15:44] sink? [15:44] sync [15:45] Let's do that :) I might forget though..! [15:45] it's basically only solvable if we integrate console-conf (or equivalent) + give users a good UX for preseeding [15:45] which is out of scope for livecd-rootfs [15:45] I should add some context in that bug (the livecd-rootfs bits haven't been used on the pi for a loooong time now; our defaults for that have been set in the cloud-init seed) [15:46] waveform: it's all in the raspi-settings package, right? [15:46] waveform: please do [15:46] bdmurray: next? [15:46] eh [15:46] bdrung: next? [15:46] Ah, I guess in the gadget..? [15:46] no -- most of the hacks from livecd-rootfs migrated there, but the initial authentication settings have been in the cloud-init seed (from the gadget) for yonks [15:47] next: bug #2034986 [15:47] -ubottu:#ubuntu-meeting- Bug 2034986 in ubuntu-release-upgrader (Ubuntu Mantic) "some text became unreadable during a distribution upgrade" [Critical, Confirmed] https://launchpad.net/bugs/2034986 [15:47] We talked about that. [15:48] yes [15:48] #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ll-incoming-bug-tasks.html#foundations-bugs [15:48] nothing there for us [15:49] but there are three under unknown [15:49] for timidity, virtualbox, and marco [15:50] we can take that out of band and follow up with the taggers that they're following a process that won't work for them [15:50] #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-jj-incoming-bug-tasks.html#foundations-bugs [15:50] (I'll do that) [15:51] bug #1990798 [15:51] heh, one is tagged champagne [15:51] -ubottu:#ubuntu-meeting- Bug 1990798 in ubuntu-release-upgrader (Ubuntu) "do-release-upgrade fails if ESM enabled" [Critical, Incomplete] https://launchpad.net/bugs/1990798 [15:52] it is incomplete and with pro team, skip [15:53] #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs [15:53] nothing for foundation, but 13 in unknown category [15:53] #topic Team proposed-migration report [15:53] #link https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs [15:54] * bdrung hands over the baton to vorlon [15:54] I can probably take one proposed-migration [15:54] s390-tools*: MIR. schopin, is this still on your todo? [15:54] There aren't that many to take :) [15:54] vorlon: yes :) [15:55] ginggs isn't here to make cards for us, but maybe you want to make one manually for tracking if you don't already have one? [15:55] llvm-toolchain-15 is "just" waiting for a riscv64 build, nothing to do [15:55] I might actually have several -_- [15:55] haha [15:55] glibc is blocking linux-raspi-meta, I'll take a look at that [15:55] done [15:55] bdrung: [15:56] #topic AOB [15:56] zsh 5.9-5 FTBFS on i386. Someone could look at that. [15:57] any volunteers? [15:57] I can take a look [15:57] undefined reference to `fmod' [15:57] (probably another fp math issue?) [15:57] ah, doko pushed an update to strace but I'm surprised he didn't hit the same build issue as I did [16:00] Speak now or forever hold your peace. [16:00] adrien: the changelog entry says: "New upstream version, fixing FTBFS". So maybe he did? [16:01] 3 [16:01] 2 [16:01] 1 [16:01] #endmeeting [16:01] Meeting ended at 16:01:31 UTC. Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-09-14-15.02.moin.txt [16:01] ogayot: the ftbfs was "expected" for all arches due to the new kernel and I think that's what he's refering to but then I also had a build issue specifically for arm64 (which I had on LP builders and pi4) === rs20095 is now known as rs2009