Am 26.08.26 um 21:34 schrieb Santiago Vila:
If you cannot reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible.Moreover, it also fails here after I triggered a rebuild: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/network-manager.html 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?
OpenPGP_signature.asc
Description: OpenPGP digital signature
