Simon McVittie

> we should rethink what we do and don't share in each scenario Now done, and the result is that the next "Steam Linux Runtime - sniper" beta is likely...

> As for the libraries you listed none are in use and older glibc executables are supposed to be forwards-compatible afaik, so I think I will get away with it...

> You need the Steam client beta for now (but I think this feature is meant to land in the general-availability branch during the next big update) If I'm reading...

> Is this on Steam Deck or Desktop? I was testing on desktop, without using Flatpak (on the old Debian-based SteamOS 2, as it happens, but that doesn't have its...

Yes, today's soldier and sniper client betas have the change I described in https://github.com/libretro/RetroArch/issues/14266#issuecomment-1204406330. If you would like to be notified when this reaches the default branch, please subscribe to...

Hmm, this makes the tests fail, because some of the tests expect it to be possible to fail to patch a function. Sorry, I'm not sure I understand how those...

The upstream source code release that's used in Debian, which was downloaded from , doesn't include the gtkspell.py module (presumably the upstream developer built their `sdist` tarball without specifically enabling...

The gtkspell module was already described as a "legacy API" in the commit that added it to gtkspellcheck in 2012, so it seems to be going quite far back into...

Or change the spellchecker plugin so that instead of trying to use pygtkspellcheck via gtkspell, it calls into pygtkspellcheck directly? gtkspell is a very thin wrapper around pygtkspellcheck: it doesn't...

LXC probably doesn't leave it with enough privileges to run successfully. In general, "nesting" containers is harder to do successfully or securely than creating a single level of container on...