=== john-cabaj1 is now known as john-cabaj
[00:48] <sarnold> tsimonq2, arraybolt3, awesome followup email, thanks :)
[00:50] <tsimonq2> <3
[01:02] <duflu> e-shell
[01:04] <duflu> ^ no keyboard focus stealing prevention
[01:13] <sarnold> iShell
[04:46] -queuebot:#ubuntu-release- New binary: binutils [arm64] (plucky-proposed/main) [2.43.90.20250122-2ubuntu1] (core, i386-whitelist)
[04:50] -queuebot:#ubuntu-release- New: accepted binutils [arm64] (plucky-proposed) [2.43.90.20250122-2ubuntu1]
[04:50] -queuebot:#ubuntu-release- New: accepted haskell-xml-conduit-writer [arm64] (plucky-proposed) [0.1.1.5-1]
[04:50] -queuebot:#ubuntu-release- New: accepted haskell-xml-conduit-writer [ppc64el] (plucky-proposed) [0.1.1.5-1]
[04:50] -queuebot:#ubuntu-release- New: accepted haskell-xml-conduit-writer [s390x] (plucky-proposed) [0.1.1.5-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [amd64] (plucky-proposed) [2.30.50+ds-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [ppc64el] (plucky-proposed) [2.30.50+ds-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [s390x] (plucky-proposed) [2.30.50+ds-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [arm64] (plucky-proposed) [2.30.50+ds-2]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [ppc64el] (plucky-proposed) [2.30.50+ds-2]
[04:50] -queuebot:#ubuntu-release- New: accepted vimium [amd64] (plucky-proposed) [2.1.2-1]
[04:50] -queuebot:#ubuntu-release- New: accepted haskell-xml-conduit-writer [amd64] (plucky-proposed) [0.1.1.5-1]
[04:50] -queuebot:#ubuntu-release- New: accepted haskell-xml-conduit-writer [riscv64] (plucky-proposed) [0.1.1.5-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [arm64] (plucky-proposed) [2.30.50+ds-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [amd64] (plucky-proposed) [2.30.50+ds-2]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [s390x] (plucky-proposed) [2.30.50+ds-2]
[04:50] -queuebot:#ubuntu-release- New: accepted haskell-xml-conduit-writer [armhf] (plucky-proposed) [0.1.1.5-1]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [riscv64] (plucky-proposed) [2.30.50+ds-1]
[04:50] -queuebot:#ubuntu-release- New: accepted node-ace-code [amd64] (plucky-proposed) [1.35.4+~cs1.7.37-2]
[04:50] -queuebot:#ubuntu-release- New: accepted sdl2-compat [armhf] (plucky-proposed) [2.30.50+ds-2]
=== woky is now known as 082ABEWVI
[05:02] -queuebot:#ubuntu-release- Unapproved: openldap (oracular-proposed/main) [2.6.8+dfsg-1~exp4ubuntu1 => 2.6.8+dfsg-1~exp4ubuntu1.1] (i386-whitelist, ubuntu-server)
[05:02] -queuebot:#ubuntu-release- Unapproved: openldap (noble-proposed/main) [2.6.7+dfsg-1~exp1ubuntu8.1 => 2.6.7+dfsg-1~exp1ubuntu8.2] (i386-whitelist, ubuntu-server)
[05:05] -queuebot:#ubuntu-release- New binary: binutils [i386] (plucky-proposed/main) [2.43.90.20250122-2ubuntu1] (core, i386-whitelist)
[05:06] -queuebot:#ubuntu-release- Unapproved: openldap (jammy-proposed/main) [2.5.18+dfsg-0ubuntu0.22.04.2 => 2.5.18+dfsg-0ubuntu0.22.04.3] (i386-whitelist, ubuntu-server)
[05:07] -queuebot:#ubuntu-release- New: accepted binutils [i386] (plucky-proposed) [2.43.90.20250122-2ubuntu1]
[05:11] -queuebot:#ubuntu-release- New binary: binutils [amd64] (plucky-proposed/main) [2.43.90.20250122-2ubuntu1] (core, i386-whitelist)
[05:13] -queuebot:#ubuntu-release- New: accepted binutils [amd64] (plucky-proposed) [2.43.90.20250122-2ubuntu1]
[05:32] -queuebot:#ubuntu-release- New binary: gittuf [amd64] (plucky-proposed/none) [0.8.0-1] (no packageset)
[05:37] -queuebot:#ubuntu-release- New binary: gittuf [arm64] (plucky-proposed/none) [0.8.0-1] (no packageset)
[05:37] -queuebot:#ubuntu-release- New binary: gittuf [armhf] (plucky-proposed/none) [0.8.0-1] (no packageset)
[06:01] -queuebot:#ubuntu-release- New binary: gittuf [ppc64el] (plucky-proposed/universe) [0.8.0-1] (no packageset)
[07:13] <didrocks> paride: utkarsh2102: it seems that there is a potential testbed/infra issue on https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/plucky/amd64: both 25.04.8 (which used to pass) and 25.04.9 are failing on "2202s rm: cannot remove '/adt/tmp.0M71ZpzlvK/ubuntu::/chroot': Device or resource busy". As the diff https://launchpadlibrarian.net/772085181/livecd-rootfs_25.04.8_25.04.9.diff.gz is
[07:13] <didrocks> clearly not related to the test issue and pass on non amd64 arch, can we whitelist it for now?
[08:24] <paride> didrocks, hi! looking
[08:28] <paride> didrocks, I agree it's unrelated. There is already a migration-reference/0 run queued, that should reset the test status
[08:32] <Skia> I am not sure the link to this discussion has been posted here, but it would be interesting for people to know: https://lists.ubuntu.com/archives/ubuntu-devel/2025-January/043224.html
[08:32] <Skia> TL;DR: a move to Matrix seems well engaged
[08:41] <paride> didrocks, interestingly, livecd-rootfs seems to be the only package with that failure mode
[08:41] <paride> from a search performed like this: ./retry-autopkgtest-regressions --log-regex  "chroot': Device or resource busy"
[08:41] <RikMills> livefs where thunderbird snap is seeded are failing
[08:42] <paride> RikMills, indeed
[08:43] <paride> there are probably lingering mounts left behind
[09:04] <zhsj> ubuntu-sru: another ping for https://bugs.launchpad.net/ubuntu/+source/golang-1.23/+bug/2085834 and it's in focal new queue, https://launchpad.net/ubuntu/focal/+queue?queue_state=0&queue_text=golang
[09:04] -ubottu:#ubuntu-release- Launchpad bug 2085834 in golang-1.23 (Ubuntu Focal) "[SRU] backport golang-1.23 to focal" [Undecided, In Progress]
[09:13] -queuebot:#ubuntu-release- Unapproved: gnome-shell (noble-proposed/main) [46.0-0ubuntu6~24.04.6 => 46.0-0ubuntu6~24.04.7] (desktop-extra, mozilla, ubuntu-desktop)
[10:11] <ginggs> paride, didrocks: my migration-reference/0 of livecd-rootfs passed :-/
[10:13] <Skia> ginggs: was it run in the same datacenter? bos03 vs lcy02? Look for those in the logs
[10:13] <Skia> The technically have different images for the testbeds, although they should be built with the same scripts.
[10:39] <ginggs> Skia: it looks like my migration-reference, and j.bicha's last attempt were both run in bos03, although about 12 hours apart
[10:39] <Skia> okay, then likely on the same testbed
[10:41] <ginggs> i have re-triggered with the same trigger as j.bicha (livecd-rootfs/25.04.9) in case it is different now
[10:41] <Skia> :+1:
[11:27] <RikMills> ubuntu-release ubuntu-sru: We have a plasma bugfix to upload for Noble. LP: #2093184
[11:27] -ubottu:#ubuntu-release- Launchpad bug 2093184 in plasma-desktop (Ubuntu) "[SRU] tracking bug for plasma LTS 5.27.12 bugfix updates for Noble" [Undecided, Confirmed] https://launchpad.net/bugs/2093184
[11:28] <RikMills> given timing of 24.04.2 I will make sure this is done ASAP
[11:44] -queuebot:#ubuntu-release- Unapproved: breeze (noble-proposed/universe) [4:5.27.11-0ubuntu3 => 4:5.27.12-0ubuntu0.1] (kubuntu)
[11:45] -queuebot:#ubuntu-release- Unapproved: breeze-gtk (noble-proposed/universe) [5.27.11-0ubuntu2 => 5.27.12-0ubuntu0.1] (kubuntu)
[11:50] -queuebot:#ubuntu-release- Unapproved: kde-cli-tools (noble-proposed/universe) [4:5.27.11-0ubuntu2 => 4:5.27.12-0ubuntu0.1] (kubuntu)
[11:55] -queuebot:#ubuntu-release- Unapproved: kde-gtk-config (noble-proposed/universe) [4:5.27.11-0ubuntu2 => 4:5.27.12-0ubuntu0.1] (kubuntu)
[11:58] -queuebot:#ubuntu-release- Unapproved: kinfocenter (noble-proposed/universe) [4:5.27.11-0ubuntu3 => 4:5.27.12-0ubuntu0.1] (kubuntu)
[12:01] -queuebot:#ubuntu-release- Unapproved: plasma-desktop (noble-proposed/universe) [4:5.27.11-0ubuntu2 => 4:5.27.12-0ubuntu0.1] (kubuntu)
[12:03] -queuebot:#ubuntu-release- Unapproved: plasma-discover (noble-proposed/universe) [5.27.11-0ubuntu2 => 5.27.12-0ubuntu0.1] (kubuntu)
[12:06] -queuebot:#ubuntu-release- Unapproved: plasma-workspace (noble-proposed/universe) [4:5.27.11-0ubuntu4.2 => 4:5.27.12-0ubuntu0.1] (kubuntu)
[12:10] <RikMills> ubuntu-sru: please accept for noble ^^
[12:11] <RikMills> that way we can hopefully have 10 days in proposed and 10 days in the release pocket before 24.04.2
[12:42] -queuebot:#ubuntu-release- New binary: gittuf [riscv64] (plucky-proposed/universe) [0.8.0-1] (no packageset)
[13:04] <ginggs> didrocks: livecd-rootfs autopkgtests look happy now and 25.04.9 has migrated
[13:11] <didrocks> ginggs: yeah, I saw that! Thanks :)
[13:13] -queuebot:#ubuntu-release- New: accepted gittuf [amd64] (plucky-proposed) [0.8.0-1]
[13:13] -queuebot:#ubuntu-release- New: accepted gittuf [armhf] (plucky-proposed) [0.8.0-1]
[13:13] -queuebot:#ubuntu-release- New: accepted gittuf [riscv64] (plucky-proposed) [0.8.0-1]
[13:13] -queuebot:#ubuntu-release- New: accepted gittuf [arm64] (plucky-proposed) [0.8.0-1]
[13:14] -queuebot:#ubuntu-release- New: accepted gittuf [ppc64el] (plucky-proposed) [0.8.0-1]
[13:15] <LocutusOfBorg> sergiodj, hello, I'm stealing sssd merge
[13:15] <LocutusOfBorg> I wanted to reintroduce faketime on armhf
=== falcojr9 is now known as falcojr
[13:56] -queuebot:#ubuntu-release- Unapproved: malcontent (oracular-proposed/main) [0.12.0-1.1ubuntu1 => 0.12.0-1.1ubuntu1.1] (ubuntu-budgie, ubuntu-desktop, xubuntu)
[13:59] -queuebot:#ubuntu-release- Unapproved: malcontent (noble-proposed/main) [0.11.1-1ubuntu1 => 0.11.1-1ubuntu1.1] (ubuntu-budgie, xubuntu)
[14:35] -queuebot:#ubuntu-release- Unapproved: wsl-setup (noble-proposed/main) [0.5.4~24.04 => 0.5.8~24.04] (no packageset)
[14:39] -queuebot:#ubuntu-release- Unapproved: rejected wsl-setup [source] (noble-proposed) [0.5.8~24.04]
[14:39] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (noble-proposed/main) [24.04.82 => 24.04.83] (desktop-core, i386-whitelist)
[14:41] -queuebot:#ubuntu-release- Unapproved: wsl-setup (noble-proposed/main) [0.5.4~24.04 => 0.5.8~24.04] (no packageset)
[15:14] <RikMills> ubuntu-sru: please accept plasma 5.27.12 packages for noble so we can get them in for 24.04.2
[15:40] <schopin> LocutusOfBorg: has faketime been fixed? Because last I checked it really didn't play nice with t64
[15:48] -queuebot:#ubuntu-release- Unapproved: flash-kernel (oracular-proposed/main) [3.107ubuntu13~24.10.1 => 3.107ubuntu13~24.10.2] (core)
[15:56] -queuebot:#ubuntu-release- Unapproved: flash-kernel (noble-proposed/main) [3.107ubuntu13~24.04.1 => 3.107ubuntu13~24.04.2] (core)
[16:01] <sergiodj> LocutusOfBorg: sure, go for it
[16:02] <sergiodj> but beware of what schopin said (which is also my experience)
=== nljhnamtjjlobywl is now known as dywpylwizaspxkvx
=== dywpylwizaspxkvx is now known as georgiag
[17:07] <LocutusOfBorg> sergiodj, schopin https://autopkgtest.ubuntu.com/packages/s/sssd/plucky/armhf :)
[17:07] <LocutusOfBorg> looks like it is!
[18:16] <apw> /
[19:52] <liushuyu> Hi, can someone from the SRU team take a look at https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2082636? Thanks!
[19:53] -ubottu:#ubuntu-release- Launchpad bug 2082636 in dpkg (Ubuntu Noble) "[SRU] dpkg: backport frame-pointer enabling mechanism for Rust" [Undecided, Fix Committed]
[20:12] <tsimonq2> ubuntu-release: Simple FYI, Qt 6.8.2 has been pushed by a week: https://lists.qt-project.org/pipermail/releasing/2025-January/003040.html
[20:12] <tsimonq2> I'll adjust the release schedule accordingly.
[20:15] <tsimonq2> FTR: the plan is to release 25.04 with Qt 6.8.3, and 25.10 with the 6.9 series (nice)
[20:31] <tsimonq2> jbicha: ^^^ This won't interfere with the GNOME beta scheduled for the week after, right?
[20:43] <RikMills> ubuntu-sru: please accept plasma 5.27.12 packages for noble so we can get them in for 24.04.2
[20:49] <tsimonq2> ubuntu-release, ubuntu-archive: Semi-*LOUD* ping. The Thunderbird snap currently breaks the Kubuntu ISO. Besides completely removing this from the seed or patching livecd-rootfs, we have *no* ability to patch the Thunderbird snap to fix the issue at hand. See the latest livefs failure for Kubuntu.
=== arraybolt3_ is now known as arraybolt3
[20:50] <tsimonq2> Full disclaimer, I'm very grumpy about this. I saw this coming from a mile away, it just took Murphy's Law to actually make it happen.
[20:50] <seb128> tsimonq2, what would help and be constructive is to describe the issue rather than having a rant...
[20:50] <tsimonq2> https://launchpadlibrarian.net/772298416/buildlog_ubuntu_plucky_amd64_kubuntu_BUILDING.txt.gz
[20:51] <mwhudson> tsimonq2: (having not looked at the failure) is this kubuntu only because only kubuntu seeds thunderbird or
[20:51] <tsimonq2> taskrunner.go:299: Change 1 task (Mount snap "thunderbird" (609)) failed: installation not allowed by "dot-thunderbird" plug rule of interface "personal-files" for "thunderbird" snap
[20:51] <tsimonq2> cannot preseed: installation not allowed by "dot-thunderbird" plug rule of interface "personal-files" for "thunderbird" snap
[20:51] <tsimonq2> unmounting: /tmp/snapd-preseed
[20:51] <tsimonq2> mwhudson: Anything that seeds Thunderbird.
[20:52] <tsimonq2> seb128: I've said what I've needed to say, I don't plan on ranting further than I already have. :P
[20:52] <seb128> tsimonq2, so it's a bug in the devel serie, those happens, is that a reason to have a go at snaps this wya?
[20:52] <arraybolt3> seb128: The problem is not "those happen", the problem is no one has access to fix it despite policy saying Core Devs should have access to fix it.
[20:52] <seb128> I'm not planning to help just because I don't consider that a constructive way to bring up an issue
[20:52] <tsimonq2> ^
[20:52] <arraybolt3> And this is a problem *now*, we have plasma testing to do *now*.
[20:53] <arraybolt3> seb128: I didn't see anything untoward in tsimonq2's message, he sent one message saying he was frustrated and that was it?
[20:53] <seb128> arraybolt3, starting by Semi-*LOUD* seriously?
[20:53] <seb128> how is that remotly constructive
[20:54] <arraybolt3> um, this is an active channel, some pings are more important than others?
[20:54] <arraybolt3> I ping -release and -archive every so often for far less critical things.
[20:54] <arraybolt3> That wasn't frustration, it's just trying to get attention for something of high urgency.
[20:54] <seb128> I would be fine with a ping, not with a 'I'm going to start by warning I'm shouting at you about the fact that you are using snaps
[20:55] <seb128> it didn't feel constructive sorru
[20:55] <seb128> 'we have *no* ability to patch the Thunderbird snap to fix the issue at hand'
[20:55] <seb128> you have people who are around and can land a fix for you (e.g me) so that's not the problem
[20:55] <arraybolt3> Regardless of whether it felt constructive, the fact remains that this is of very high importance, since it's potentially going to interfere with Kubuntu's ability to release in a good state.
[20:55] <seb128> do you have a fix?
[20:55] <arraybolt3> tsimonq2: ^ ?
[20:56] <seb128> we are not even at feature freeze come on
[20:56] <seb128> your expectations of a devel cycle are off..
[20:56] <seb128> bugs happen, we fix them
[20:56] <seb128> I don't see how that's putting any release at risk
[20:57] <seb128> it's just overstating the problem
[20:57] <arraybolt3> This is probably a discussion best had elsewhere, but suffice to say Plasma testing takes time, Kubuntu devs know the schedule, we know how long we need to do things and when something is threatening that. Assuming good faith on tsimonq2's part and understanding his level of skill, I don't think he would say "this is a big problem" unless it was.
[20:57] <arraybolt3> quoting him from Matrix, "I guess we have to remove the Thunderbird snap, unless someone can fix it, like, right now. We need to test the new Plasma. It's blocking work from getting done."
[20:58] <seb128> welcome on a devel serie
[20:58] <arraybolt3> he's also frustrated because Technical Board policy states he should be able to fix this himself, but he isn't allowed to due to technical issues that no one has resolved.
[20:58] <arraybolt3> Similar to if a MOTU was unable to upload to Universe for reasons.
[20:59] <seb128> come on
[20:59] <arraybolt3> anyways, tsimonq2 did you take a look at what exactly was wrong and make a fix yet?
[20:59] <seb128> that's a store assertion problem
[20:59] <seb128> as a coredev you wouldn't be able to fix launchpad infra problem eithers
[20:59] <seb128> so nothing specific to TB or snaps
[21:00]  * arraybolt3 has never done Snap packaging and is mostly involved from a "avoid conflict" standpoint, I haven't looked into the exact issue or steps to fix it
[21:01] <tsimonq2> Just because it's a development release doesn't mean things *should* break without notice. It happens, sure, we're not in Feature Freeze yet, but disrupting other people's workflows and ability to get work done, then claiming the ping *itself* is non-constructive, is in and of itself non-constructive, IMO.
[21:01] <seb128> the tone isn't constructive, I'm not going to help because you are shooting and warning that you will use CAPITAL LETTERS
[21:01] <tsimonq2> arraybolt3: My snap knowledge is about half a decade outdated, but I see Lucy has some ideas on Matrix. I would bother if I actually thought it would be meaningful.
[21:01] <tsimonq2> seb128: Then don't help, you're not obligated to.
[21:02] <seb128> the issue is a side effect of https://forum.snapcraft.io/t/update-to-the-system-files-interface-used-by-thunderbird going live and them not updating the assertion in a way that keep compatibility for the old interface as they did in https://forum.snapcraft.io/t/update-to-the-system-files-interfaces-used-by-firefox (despite me pointing out that they should)
[21:04] <arraybolt3> seb128: I mean even syslog uses capital letters when something is attention-worthy. If he was doing things like "I CAN'T BELIEVE THIS STEAMING PILE OF AAAAA BROKE SOMEONE FIX IT Y'ALL ARE EVIL" then I'd be like "whoa, dude, calm down" :P I really don't think the "*LOUD*" was for anything more than Just making the message easily visible in the log, it wasn't part of the actual message.
[21:04] <tsimonq2> ^^^
[21:04] <arraybolt3> and he did add "semi" in front to clarify that it wasn't world-ending, it was just severe.
=== liushuyu1 is now known as liushuyu
[21:13] <seb128> arraybolt3, tsimonq2, it's not only the tone, it's also the ranting against snaps
[21:13] <seb128> that's not constructive
[21:13] <arraybolt3> I don't see any ranting against Snaps.
[21:14] <seb128> you can consider that an infra issue, yes you are a coredev and should be able to fix any package, but we also hit sometime launchpad infra issues
[21:14] <arraybolt3> There's a minor amount of ranting against a process surrounding upload rights with Snaps.
[21:14] <arraybolt3> But not anything about Snaps themselves.
[21:14] <seb128> and as a coredev you are not able to fix launchpad
[21:14] <arraybolt3> agreed. If it turns out this is an infra issue then this isn't the problem that tsimonq2 thought it was.
[21:14] <seb128> but nobody complains that it's outrageous as a coredev we don't have access to fix launchpad
[21:15] <arraybolt3> He originally thought it was the package itself that was problematic and needed fixed, but didn't have the needed upload rights to fix it.
[21:15] <seb128> it's a wrong assertion, perhaps closer from a component mismatch, still you would need an archive admin
[21:15] <seb128> right, which was my point
[21:15] <seb128> rather than complaining ask first
[21:16] <arraybolt3> It sounds like though he was right that Kubuntu has no access to fix it?
[21:16] <arraybolt3> And the complaining is a side point. Is there anyone here who hasn't complained as a side point because something ended up going severely wrong? I know I did some of that when the LXQt stack got sync'd from Debian some time back, no one thought I was being unconstructive.
[21:18] <arraybolt3> I'm just very surprised that a high-priority message with a minor "this is really crummy" secondary point that wasn't part of the main message is being greeted by "I don't like your tone, so I won't help". There's nothing hostile or harmful in tsimonq2's message unless I'm as dense as a brick.
[21:18] <seb128> well take that as a piece of feedback if you want or dismiss it if you prefer
[21:19] <arraybolt3> It doesn't seem considerate or collaborative, is all I'm saying.
[21:19] <arraybolt3> anyways, this is probably drowning the real problem at this point. To whomever does want to help and has the ability to (ubuntu-archive I believe), if someone could fix whatever's wrong with the Thunderbird snap that has Kubuntu unable to build, that would be much appreciated.
[21:19] <seb128> I would have been more receptive to 'could someone please help and look at that problem we have'
[21:21] <seb128> anyway, I pinged the store team about the issue now
[21:21] <arraybolt3> thanks
[21:22] <seb128> if I understand it correctly there is several way to fix it, one is for them to fix the assertion to be compatible with the old/new definition
[21:22] <seb128> another one is for me to merge the corresponding code change to stable and kick a new snap build (which will take a couple of hours)
[21:23] <seb128> another one would be to use the snap from the beta channel, but that's a newer version and will create incompatible profile if users want to go back to stable, so I don't like that option
[21:24] <arraybolt3> with my Kubuntu dev hat on, I'll send virtual coffee your way if you do want to help :) I have no idea how Snap works so I don't know if the first or second option is better but the second one sounds better to my untrained ear.
[21:26] <Eickmeyer> FWIW, Ubuntu Studio (seeds thunderbird) built just fine most recently. Likely a transient error.
[21:26] <Eickmeyer> Rebuilding Kubuntu should do the trick.
[21:26] <arraybolt3> based on seb128's analysis of the issue I don't *think* it's going to be transient. I would expect the successful build of Studio to be transient, but meh, could be wrong
[21:27] <arraybolt3> I'd kick off a Lubuntu rebuild to test but I'm about 60% sure we don't see Thunderbir
[21:27] <seb128> I don't think there is anything transient there, it's probably just that store assertion change went live
[21:27] <arraybolt3> well, I'm 100% sure we don't see Thunderbir since Thunderbir doesn't exist to be seen. I'm also 60% sure we don't seed Thunderbird.
[21:28]  * arraybolt3 attempts to warm up fingers so I stop missing letters
[21:28] <seb128> I've pushed https://github.com/ubuntu/thunderbird/commit/2cec280c now to stable which I think will fix it and triggered a new build
[21:28] -ubottu:#ubuntu-release- Commit 2cec280 in ubuntu/thunderbird "Bug 1908870 - Allow reading from /etc/thunderbird"
[21:28]  * arraybolt3 sends virtual coffee towards seb128
[21:28] <arraybolt3> thank you!
[21:28] <seb128> np!
[21:29] <seb128> it will take around 2 hours for it to build but maybe the store people will reply before...
[21:29] <arraybolt3> I think we'll survive two hours :)
[21:31] <jbicha> tsimonq2: new Qt doesn't conflict with new GNOME nor the other way around 🙂
[21:53] <RikMills> seb128: will that fix kubuntu noble daily as well? faled with the same error
[21:55] <RikMills> and thanks. catching up with scrollback....
[22:05] <Eickmeyer> RikMills: Try a rebuild. Seems the issue was fixed between the last build and now. Ubuntu Studio had no errors at 1900 UTC, also seeding Thunderbird.
[22:05] <Eickmeyer> (had failed 24 hours prior with same error)
=== john-cabaj1 is now known as john-cabaj
[23:33] -queuebot:#ubuntu-release- New binary: libpqxx [arm64] (plucky-proposed/universe) [7.10.0-2] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: libpqxx [armhf] (plucky-proposed/universe) [7.10.0-2] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: postgresql-common [amd64] (plucky-proposed/main) [269] (i386-whitelist, ubuntu-server)
[23:38] -queuebot:#ubuntu-release- New binary: python-crypt-r [armhf] (plucky-proposed/none) [3.13.1-1] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: python-crypt-r [arm64] (plucky-proposed/none) [3.13.1-1] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: rust-inlinable-string [armhf] (plucky-proposed/none) [0.1.15-1] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: rust-inlinable-string [arm64] (plucky-proposed/none) [0.1.15-1] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: rust-msvc-demangler [armhf] (plucky-proposed/none) [0.10.1-1] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: rust-msvc-demangler [arm64] (plucky-proposed/none) [0.10.1-1] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: rust-pdb2 [armhf] (plucky-proposed/none) [0.9.1-1] (no packageset)
[23:41] -queuebot:#ubuntu-release- New binary: rust-cacache [arm64] (plucky-proposed/none) [13.0.0-1] (no packageset)
[23:41] -queuebot:#ubuntu-release- New binary: rust-cacache [armhf] (plucky-proposed/none) [13.0.0-1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: rust-pdb2 [arm64] (plucky-proposed/none) [0.9.1-1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: rust-proc-macro2-diagnostics [armhf] (plucky-proposed/none) [0.10.1-1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: rust-proc-macro2-diagnostics [arm64] (plucky-proposed/none) [0.10.1-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: rust-soft-assert [arm64] (plucky-proposed/none) [0.1.1-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: rust-tz-rs [arm64] (plucky-proposed/none) [0.6.14-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: rust-soft-assert [armhf] (plucky-proposed/none) [0.1.1-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: rust-tz-rs [armhf] (plucky-proposed/none) [0.6.14-1] (no packageset)
[23:44] -queuebot:#ubuntu-release- New binary: rust-symsrv [armhf] (plucky-proposed/none) [0.5.3-1] (no packageset)
[23:45] -queuebot:#ubuntu-release- New binary: rust-symsrv [arm64] (plucky-proposed/none) [0.5.3-1] (no packageset)
[23:51] -queuebot:#ubuntu-release- New binary: libpqxx [amd64] (plucky-proposed/universe) [7.10.0-2] (no packageset)
[23:52] -queuebot:#ubuntu-release- New binary: python-crypt-r [amd64] (plucky-proposed/none) [3.13.1-1] (no packageset)
[23:53] -queuebot:#ubuntu-release- New binary: rust-inlinable-string [amd64] (plucky-proposed/none) [0.1.15-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: rust-cacache [amd64] (plucky-proposed/none) [13.0.0-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: rust-pdb2 [amd64] (plucky-proposed/none) [0.9.1-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: rust-msvc-demangler [amd64] (plucky-proposed/none) [0.10.1-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: rust-tz-rs [amd64] (plucky-proposed/none) [0.6.14-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: rust-proc-macro2-diagnostics [amd64] (plucky-proposed/none) [0.10.1-1] (no packageset)
[23:55] -queuebot:#ubuntu-release- New binary: rust-soft-assert [amd64] (plucky-proposed/none) [0.1.1-1] (no packageset)
[23:57] -queuebot:#ubuntu-release- New binary: rust-symsrv [amd64] (plucky-proposed/none) [0.5.3-1] (no packageset)