Bug#1041599: gtk4, glib2.0: might need to migrate together to avoid test failure

[Simon McVittie]

Source: gtk4
Version: 4.8.3+ds-2
Severity: important
Tags: trixie sid
User: debian-ci at lists.debian.org
Usertags: needs-update
Control: close -1 gtk4/4.10.4+ds-2
Control: affects -1 + src:glib2.0 src:libadwaita-1

As a result of upstream tightening up some checks in glib2.0, the
autopkgtest for gtk4/4.8.3+ds-2 regresses after upgrading glib2.0 to
2.76.4-3:

> 286s autopkgtest [04:19:38]: test python3-gi-wayland:  - - - - - - - - - - stderr - - - - - - - - - -
> 286s
> 286s (process:5608): GLib-GObject-CRITICAL **: 04:19:38.033: Attempting to freeze the notification queue for object GtkImage[0x2cb5430]; Property notification does not work during instance finalization.

This is fixed in gtk4/4.10.x by upstream commit
b3b5a506 "Do not change the notification queue inside finalization".

For end-user applications, this would be noisy but non-fatal, so I don't
think it's really bad enough to require Breaks.

These might migrate "naturally" when ready, or we might need to ask the
release team to add some hints when glib2.0 and gtk4 are otherwise ready
to migrate, so that they will either ignore the test regression or migrate
together.

     smcv