[08:14] <Saviq> Mornang o/
[09:14] <Saviq> alan_g I've ignored the CVE notices for snaps that include Mir since we're in the middle of a release, so they will get rebuilt / retested anyway.
[09:15] <alan_g[m]> Fair
[09:21] <Saviq> (and I'd have to rebuild without ~rc anyway)
[11:48] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [issue #2792](https://github.com/MirServer/mir/issues/2792): [23.04] swaybg requires a newer version of wl-output than we support... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/b2d9ca1be5ff6b6e104efd29635706f066957c01>)
[12:05] <alan_g[m]> RAOF (he/they) I've done the testing I can for https://github.com/MirServer/mir/pull/2789, but while they should be benign, there are platform changes since 2.10 that ought to be tested with the eglstream platform. Could you?
[12:11] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths requested a review from RAOF for [pull request #2789](https://github.com/MirServer/mir/pull/2789): Release 2.12.0
[12:15] <Saviq> alan_g is `Qt5-bomber-first-try` legit, or a leftover? https://github.com/MirServer/iot-example-graphical-snap/tree/Qt5-bomber-first-try
[12:16] <alan_g[m]> It is a part of the tutorial that demonstrates the type of problem that may be encountered
[12:16] <Saviq> OK, so should be part of https://github.com/MirServer/iot-example-graphical-snap/pull/15
[12:17] <alan_g[m]> Yeah, rebase "first-try" on main, "bomber" on "first-try"
[12:19] <Saviq> How about rebasing both on main? I mean, I can do 👆️, but not sure worth the added complexity?
[12:21] <alan_g[m]> OK, should only make a difference when "first-try" need intervention anyway
[12:31] <Saviq> alan_g for testing if it runs… you're thinking something along the lines of `xvfb-run frame-it iot-example-graphical-snap`?
[12:32] <Saviq> And if it doesn't die within a few seconds, we assume it works?
[13:03] <alan_g[m]> I'm not being prescriptive. My local script just starts it an waits for manual intervention
[13:03] <Saviq> Yeah I'll work something out
[16:35] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq closed [issue #2772](https://github.com/MirServer/mir/issues/2772): wlcs.PrimarySelection tests failing on PowerPC
[16:56] -GitHub[m]:#mir-server- **[MirServer/wlcs]** Saviq opened [issue #262](https://github.com/MirServer/wlcs/issues/262): FTBFS on ppc64el "error: ‘memcpy’ accessing $loads or more bytes…"... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/a49c27e4484606da006655b6b13ff2b6fc423af9>)
[17:16] <alan_g[m]> Am I missing something? That does look like the same confusion around concatinating strings as LP#1983852
[17:16] <Saviq> I don't think you _are_ missing anything, but yeah PCH are the differentiating factor here. The "solution" before was to disable those. But they're not enabled on wlcs…
[17:18] <alan_g[m]> Maybe worth adding to the LP bug? And the wlcs code does look more likely to afford creating a reproducer
[17:19] <Saviq> Yeah will do
[17:52] <Saviq> G'night o/
[17:58] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww assigned wmww to [issue #2792](https://github.com/MirServer/mir/issues/2792): [23.04] swaybg requires a newer version of wl-output than we support