[Pkg-utopia-maintainers] Bug#918439: cockpit: FTBFS (failing tests)

[Martin Pitt]

Control: block -1 by bug 918892

Hello Santiago, Andreas,

Andreas Henriksson [2019-01-12 21:41 +0100]:
> > # FAIL:  31
> 
> Lots of failing tests there....

Right, but they have two different root causes. The first is bug 918892, a
recent regression in libssh 0.8.6, which causes all the cockpit-ssh unit tests
to fail, e. g.:

| cockpit-ssh-Message: 07:28:13.450: cockpit-ssh 127.0.0.1:46795: -1 couldn't connect: Public key from server (rsa-sha2-512) doesn't match user preference (ssh-rsa,ssh-dss,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256) '127.0.0.1' '46795'
| **
| ERROR:src/ssh/test-sshbridge.c:515:wait_until_transport_init: assertion failed (problem == expect_problem): ("no-host" == NULL)

Thus blocking this bug bug by that, and I bumped 918892 to RC as well.

> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cockpit.html
> 
> I just looked at the first one and it fails here:
> 
> $ head -n 57 src/common/test-webserver.c  | tail -n 2
>   inet = cockpit_test_find_non_loopback_address ();
>   g_assert (inet != NULL);
> 
> I'm thus going to assume that the build environments that runs into
> these problems uses network namespaces or similar and doesn't expose
> anything but loopback to the build chroot.

Indeed, this points out a broken build environment that doesn't have a loopback
device. But this isn't new, nor happens on the official buildds (nor in local
schroot), and thus isn't an RC bug.

Thanks,

Martin