Draft: [bookworm] Fix truncation in places sidebar with large text accessibility setting

Closes: #1043261

I considered pulling in the whole of the upstream gnome-44 gtk-4-8 branch, but there are quite a lot of changes, so that seemed too high-risk for a stable update. I'd reconsider that if upstream make a 4.8.4 release with some level of actual QA, but they've said on the upstream issue tracker that there will likely be no new 4.8.x releases after 4.10.0.

Are you saying that you thought about switching Debian 12 to gtk 4.10? I have received multiple requests for that for people wanting bugfixes, or the grid view in the file chooser dialog.

Sorry, no, I've been doing too much GNOME 44 work in parallel and had gnome-44 in my head.

I meant gtk-4-8 (the branch that targets GNOME 43), so switching Debian 12 to 4.8.3-66-g7f9f29b7d1 or wherever the 4.8.x branch is up to by the time it happens - but even that seemed too intrusive.

If you want to try to sell GTK 4.10 to the release team, go for it, but I don't have enough spoons to try to convince them that its diffstat would be acceptable.

What do you think about gtk4 4.10 in Backports? And then I guess libadwaita 1.3 too?

I don't recall us ever putting a GTK in backports, but maybe it wouldn't be too much of a burden for us?

It seems impractical to go any further than 4.10. 4.12 would require a new glib for instance.

Backports policy is that the backport is meant to be from testing and stay up to date, so if we plan to ever have GTK 4.12 in trixie, we would need a plan for having it in bookworm-backports.

People have backported GLib in the past, but if I remember correctly they were not GNOME team members and didn't keep it backports-policy-compliant.

Ok, so that idea is blocked on talking with the Backports team about whether an exception is reasonable to not be perpetually updating GTK4 and a long list of dependencies (also gobject-introspection & wayland-protocols).

And blocked on someone who cares enough to do the work

merged