So since it migrated now a quite normal "sudo sbuild-update -udcar zesty-amd64" gave me: Get:10 http://archive.ubuntu.com/ubuntu zesty/main amd64 libgnutls30 amd64 3.5.6-4ubuntu1 [626 kB]
So I checked if that will "help" to reproduce locally and it does. It seems we were just in the worst spot of the trigger depending on a package that was just in migration. With that properly migrated it now fails in local VM as well as on PPA builds - yeah?! Debian seems to build against that new gnutls version fine. But there are no new patches to the tests upstream that are in Debian but not in the current Ubuntu. Also while there were general changes to tls code in the meantime upstream none seems to affect this - only one build fix but referring to a commit that is not in libvirt 2.1. Depending on how debugging goes we might "just" have to do the libvirt merge now to fix the FTBFS. Since the merge should contain more cleanup I'd like to avoid it for now, but lets see. Debuggable without the libtool wrapper via: gdb -directory ../../../src/test ./.libs/lt-virnettlssessiontest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641615 Title: FTBFS of libvirt 2.1 in zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1641615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
