Bug#977961: gtk+3.0: FTBFS if imagemagick display(1) is installed

[Simon McVittie]

Control: retitle -1 gtk+3.0: FTBFS if imagemagick display(1) is installed
Control: reassign -1 libglib2.0-dev-bin 2.66.3-2
Control: affects -1 + gtk+3.0
Control: tags -1 + confirmed patch upstream
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1902

On Wed, 23 Dec 2020 at 13:00:07 +0100, Pablo Barciela wrote:
> TEST: cairo... (pid=2808385)
>   /drawing/set-source-big-pixbuf:                                      OK
> PASS: cairo
> TEST: display... (pid=2808418)
> display-im6.q16: unable to open image `--quiet': No such file or directory @ error/blob.c/OpenBlob/2924.
> display-im6.q16: no decode delegate for this image format `' @ error/constitute.c/ReadImage/566.
> display-im6.q16: unable to open image `--keep-going': No such file or directory @ error/blob.c/OpenBlob/2924.
> display-im6.q16: no decode delegate for this image format `' @ error/constitute.c/ReadImage/566.
> display-im6.q16: unrecognized option `-m=quick' @ error/display.c/DisplayImageCommand/1391.
> FAIL: display

This appears to be a bug in GLib, which affects the deprecated gtester(1)
tool that GTK 3 uses to run its build-time tests. gtester intends to run
the 'display' executable in the current working directory testsuite/gdk/,
but as a result of the GLib bug, it actually runs /usr/bin/display instead.

Workaround: Build GTK in a chroot or container that does not have
/usr/bin/display installed, or with DEB_BUILD_OPTIONS=nocheck.

    smcv