[07:04] <pitti> cpaelzer: hah, thanks for the super-fast response wrt. libvirt-dbus :-) but I think I got this
[07:08] <cpaelzer> you do - as always
[07:09] <cpaelzer> but even if sometimes I can't help I at least want to let you know that you are not alone :-)
[07:09]  * cpaelzer hugs pitti
[07:21]  * pitti hugs cpaelzer back, thanks :)
[07:21] <pitti> cpaelzer: I am currently enabling all our projects for 22.04, working my way upwards from podman/criu/container (done), now machines/libvirt (just started), and finally cockpit itself
[07:21] <pitti> it covers so many APIs, it's a pretty rigorous "server OS" test
[07:22] <pitti> for focal we did that too late, so a lot of regressions surfaced after release only
[07:22] <pitti> this time I hope to squash a few bugs before release 😀
[07:26] <cpaelzer> thank you for that!
[07:49] <pitti> cpaelzer: at least after that unkillable libvirt-dbus permission zombie bug, the rest of the libvirt stack looks 👍 https://logs.cockpit-project.org/logs/pull-638-20220325-073412-51a515d9-ubuntu-2204/log.html
[08:43] <eoli3n> Hi
[08:44] <eoli3n> since few time, my preseed installation installs oem kernel
[08:44] <eoli3n> how to disable it, and run stock kernel ?
[08:44] <eoli3n> s/installation//
[08:46] <eoli3n> https://wiki.ubuntu.com/Kernel/OEMKernel
[08:46] <eoli3n> i want to automatically install stock kernel and not that one, which break my os on specific hardware
=== mirespace_ is now known as mirespace
[09:52] <eoli3n> https://x0.at/CiKE.txt
[09:52] <eoli3n> ubuntu-drivers --no-oem is broken
[09:59] <eoli3n> that story is funny
[09:59] <eoli3n> Canonical provides a oem kernel to "improve" hardware support.
[10:00] <eoli3n> installing this breaks my OS, which can't start lightdm
[10:00] <eoli3n> removing oem driver fix the issue
[10:00] <eoli3n> i noticed that what installed oem things is my "ubuntu-drivers install" task
[10:01] <eoli3n> then i try "ubuntu-drivers --no-oem install" which breaks
[10:01] <eoli3n> good job, really, it amaze me how deep you work to break things
[11:02] <seb128> ginggs, hey, how often is the ftbfs report refreshed? daily?
[11:03] <ginggs> seb128: daily, but manually. I'm actually just about to upload a fresh report.
[11:04] <seb128> ginggs, great, thanks!
[11:08] <ginggs> seb128: .
[11:08] <seb128> ginggs, 👍
[11:09] <seb128> ginggs, it doesn't take account updates which are in proposed right?
[11:11] <ginggs> seb128: correct, those would be on http://qa.ubuntuwire.com/ftbfs/
[11:13] <seb128> ginggs, ack, it was rather the other way around, it would be nice if entries that have an update which built in proposed and didn't migrate yet cleared off from the list because technically the build failure is resolved
[11:16] <ginggs> seb128: except those updates might never migrate
[11:31] <juliank> heh nothing migrates right now anyway, the queues are full and capped at 40-50% capacity
[11:43] <seb128> ginggs, right
[11:43] <seb128> ginggs, what's the process to ask for a retry for https://launchpad.net/ubuntu/+archive/test-rebuild-20220317-jammy/+build/23329873 ?
[11:46] <ginggs> seb128: pinging me with the link in irc :) retried
[11:46] <seb128> ginggs, thanks!
[12:17] <pitti> cpaelzer: FTR, I have cockpit covered as well; I found/reported a PAM regression, the others we found were already known/reported elsewhere; so, mostly 👍 😀
[12:32] <ahasenack> pitti: is that cockpit running on ubuntu, managing ubuntu systems?
[12:33] <pitti> ahasenack: both (although for most detected regressions, the latter is the important part)
[12:33] <ahasenack> interesting
[12:33] <ahasenack> pitti: is that cockpit the ubuntu package from the ubuntu archive, or a separate build you have?
[12:33]  * ahasenack double checks it is in the ubuntu archive
[12:34] <ahasenack> yeah, 264-1, from debian
[12:34] <pitti> ahasenack: not sure what "that" is -- my linked log from earlier was upstream main
[12:34] <ahasenack> I meant the deb
[12:34] <ahasenack> but upstream main, ok
[12:34] <pitti> but in the course of the regular upstream release → debian upload → ubuntu sync it'll also get there
[12:35] <pitti> (however, I didn't sync the latest upstream release because feature freeze)
=== sem2peie- is now known as sem2peie