Hi,
* Michael Biebl <[email protected]> [260826 23:31]:
Am 26.08.26 um 21:34 schrieb Santiago Vila:
Whatever is the reason for the failure, it apparently started to
happen somewhere between 2026-08-04 and 2026-08-21 according to my
build history:
Status: successful network-manager_1.58.0-2_amd64-20260729T213058.984Z
Status: successful network-manager_1.58.0-2_amd64-20260804T135514.761Z
Status: failed network-manager_1.58.0-2_amd64-20260821T223539.163Z
Status: failed network-manager_1.58.0-2_amd64-20260822T100432.126Z
Status: failed network-manager_1.58.0-2_amd64-20260823T072345.958Z
Status: failed network-manager_1.58.0-2_amd64-20260823T075901.111Z
Status: failed network-manager_1.58.0-2_amd64-20260826T043132.628Z
Status: failed network-manager_1.58.0-2_amd64-20260826T044547.710Z
Status: failed network-manager_1.58.0-2_amd64-20260826T164703.396Z
Status: failed network-manager_1.58.0-2_amd64-20260826T164801.667Z
Status: failed network-manager_1.58.0-2_amd64-20260826T165148.755Z
Status: failed network-manager_1.58.0-2_amd64-20260826T165326.489Z
Maybe a failure introduced by glib2.0 then.
https://tracker.debian.org/pkg/glib2.0
Can you reproduce the failure with glib2.0 from forky?
I can repro the build failure in unstable, and that building in
forky works. Obviously there are more differences than just forky,
but at least that's a start...
Best,
Chris
