On Thu, 2024-02-29 at 13:30 +0000, Simon McVittie wrote: > The advice for "end users" would be don't run unstable or > experimental, > and wait for maintainers to fix release-critical bugs like this one > as > they are detected.
Well "end user" is a broad range :-) I guess quite some people do run unstable on their regular systems like I do, which gives them kind of a rolling release, while at the same time being 99,xx% super stable (at least in my experience)... and on the other hand helps Debian at a whole, as much more testing is done. Suggesting such people to use the testing suite is only a partial replacement, as that generally lacks some packages (like firefox). > I'm sorry if this means I am not living up to your > expectations. Uhm? No I'm absolutely fine... an do no in any way think that you (or anyone else) should have "performed any better" - nor would I have any such demands/expectations. :-) > Installing and then reinstalling libglib2.0-0t64 should recreate this > cache, yes. > > If you have multiarch versions of libglib2.0-0t64 installed > (typically libglib2.0-0t64:amd64 and libglib2.0-0t64:i386) then you > will need to reinstall each of them. I see. Well I guess that's then already enough of instructions for any end user (in the sense of "is not a glib expert" user). Thanks, Chris.
