Control: tags -1 + confirmed
On Fri, 25 Sep 2020 at 21:50:53 +0200, Paul Gevers wrote:
> With a recent upload of glib-networking the autopkgtest of libsoup2.4
> fails in testing when that autopkgtest is run with the binary packages
> of glib-networking from unstable. It passes when run with only packages
> from testing.
The build-time tests have the same behaviour, and libsoup 2.72.0-1 from
experimental fails in the same way, so these might be easier steps to
reproduce:
* be on a pure bullseye/testing system
- glib-networking is version 2.64.3-2
* have libsoup2.4_2.70.0-1 source (from testing) or 2.72.0-1
(from experimental)
* build from source
- tests pass
* upgrade glib-networking and dependent packages to 2.66.0
* build from source
- tests fail
I'll try to bisect glib-networking. Bisecting libsoup looks unlikely to
be useful (but the solution might end up being a fix in libsoup and a
versioned Breaks, even if it's a glib-networking change that triggers it).
https://gitlab.gnome.org/GNOME/libsoup/-/issues/193 and
https://gitlab.gnome.org/GNOME/libsoup/-/issues/188 might be related.
In particular, libsoup#188 indicates that ssl-test was not completely
reliable even before upgrading glib-networking, so we might have to mark
it as flaky.
smcv
