Source: libsoup3 Version: 3.2.2-1 Severity: normal libsoup3 (and libsoup2.4 as well) are having autopkgtests failures on armhf after updating samba:
https://tracker.debian.org/pkg/samba https://ci.debian.net/data/autopkgtest/testing/armhf/libs/libsoup3/30761624/log.gz https://ci.debian.net/data/autopkgtest/testing/armhf/libs/libsoup3/30761624/log.gz There are a few tests failing in there: malloc(): unsorted double linked list corrupted FAIL: libsoup-3.0/multithread-test.test (Child process killed by signal 6) Running test: libsoup-3.0/session-test.test LCE2X1/httpd.pid' '-k' 'start' (98)Address already in use: AH00072: make_sock: could not bind to address 127.0.0.1:47524 no listening sockets available, shutting down AH00015: Unable to open logs Could not start apache # -> failed FAIL: libsoup-3.0/proxy-test.test (Child process exited with code 1) WA7GY1/httpd.pid' '-k' 'start' (98)Address already in use: AH00072: make_sock: could not bind to address 127.0.0.1:47524 no listening sockets available, shutting down AH00015: Unable to open logs Could not start apache # -> failed FAIL: libsoup-3.0/auth-test.test (Child process exited with code 1) None of these seems to be related in any way to samba (triggered by winbind in tests/control). These failures are holding python3-defaults transition now. Can you please take a look? /mjt