[00:12] Eickmeyer: why did you restrict the architecture field when uploading dpf-plugins?+ [00:13] vorlon: Woah, that was a very long time ago, I'd have to go back and check. [00:13] ok, well the package has been stuck in -proposed ever since because it regressed the architecture support [00:15] Oh, nvm, that was a package upgrade. Let me figure out why. [00:20] vorlon: Found the reason, this was sloppy packaging on my part as I didn't take the upstream packaging from Debian as, for some reason, I had it in my head that this was an Ubuntu package. I'll fix this in short order. [00:20] Eickmeyer[m]: cheers === Beret- is now known as Beret [09:06] ubuntu-archive, please drop the apport SRU from the jammy unapproved queue. I want to upload a version that fixes all autopkgtest issues. [09:08] bdrung: done [09:09] tjaalton, thanks. can you also drop the focal SRU? [09:11] bdrung: done that too [09:11] *did [09:13] sil2100: meh, mesa backport jammy->focal would need a newer libva [09:14] this dep bump went below the radar, as sid/jammy already had that [09:22] tjaalton, thanks [09:38] sil2100: and that's not the only one, wayland-protocols would also need to be updated [10:47] tjaalton: hm, so to get the new mesa we'd have to have quite a big stack update? [10:49] sil2100: yeah :/ [10:50] the libva change can be reverted [10:55] tjaalton: so how many package updates are we thinking right now? [10:56] sil2100: llvm-13 (new), libdrm, wayland-protocols [10:56] for mesa, and mesa-amber (new) so that old dri drivers are still available [10:57] mesa-amber, llvm-13 and libdrm are on the queue [10:57] wayland-protocols is kinda a trivial one, since it's just xml files [10:58] it needs 1.24, jammy/kinetic has 1.25-1 [11:00] I think this still feels 'okay', especially if libva can be skipped [11:00] Let me try looking at those in the queue too [11:02] llvm took a few iterations to build, but what has been reverted is to again avoid backporting more [11:02] uh [11:02] wayland-protocols needs newer meson.. [11:08] I'll try to relax it, maybe 0.53.2 has subproject support backported [11:09] All this starts sounding scary. What's your feeling, with all the changes you need to do to relax the dependencies and such, is it still relatively safe to update? [11:10] well, it could be done post .5 [11:11] if at all [11:13] well, wayland-protocols built with 0.53.2 [11:16] "egl/wayland: add initial dma-buf feedback support" would need to be reverted to avoid new wayland-protocols [11:16] should be doable I think [11:23] then again, that might open another can of worms [11:25] sil2100: safest to skip, and if someone later yells loudly, try again with more time? [11:25] post .5 [11:33] pushed a build with the reverts to a ppa to see how it goes [11:44] bah, incomplete backport, build failed [11:45] will need to revisit this later in the evening [16:39] tjaalton: If you've got an extra SRU cycle for a quick ack on quassel? bug 1980687, affects both lubuntu and ubuntu studio. [16:39] Bug 1980687 in quassel (Ubuntu Jammy) "[SRU] Quassel should not have #debian as default channel in Ubuntu" [High, In Progress] https://launchpad.net/bugs/1980687 [17:25] sklearn/metrics/tests/test_dist_metrics.py::test_cdist[X11-X21-metric_param_grid0] Fatal Python error: Bus error [17:25] [17:28] oof [20:23] vorlon: RE: tjaalton 's message above, I've got people willing to test on standby. [20:23] Rather, my message to him.