Bug#1111373: glib2.0: autopkgtest regression on i386 since 2.84.4-1: statically linked program segfaults

[Simon McVittie]

Control: severity -1 important
Control: tags -1 + unreproducible

On Sun, 17 Aug 2025 at 14:12:52 +0100, Simon McVittie wrote:
>In glib2.0 since 2.84.4-1, the autopkgtest test-cases "libglib2.0-dev"
>and "build-static" are failing on i386 only

I could not immediately reproduce this in a sid podman container:

$ podman run --arch i386 --rm -it docker.io/i386/debian:sid-slim
# apt update
# apt upgrade
# apt install build-essential gdb gir1.2-glib-2.0-dev libglib2.0-dev pkgconf vim
# sed -i -e 's/^Types: deb$/& deb-src/g' /etc/apt/sources.list.d/debian.sources
# apt update
# apt source glib2.0
# cd glib2.0-*
# export AUTOPKGTEST_TMP=$(mktemp -d)
# debian/tests/build-static
# debian/tests/libglib2.0-dev

I also could not reproduce this in a forky podman container, using 
similar steps but with all binary packages from src:glib2.0 (and no 
other binary packages) upgraded to their sid versions.

And the statically-linked qemu-sparc from the qemu-user package does not 
segfault on startup (I only tried with --help).

It is also not reproducible on ci.debian.net when retried today, so, 
*shrug* maybe we will never know what happened.

     smcv