@ddstreet: systemd/ubunut-image should be flaky - I have restarted them. vagrant-mutate sometimes breaks due to external changes, you might need to look into. For now I have restarted it as well.
Two things are concerning in excuses: qemu (1:2.11+dfsg-1ubuntu7 to 1:2.11+dfsg-1ubuntu7.29) ^^ where is the former .28? qemu-user-static/amd64 has unsatisfiable Built-Using on gcc-8 8.4.0-1ubuntu1~18.04 qemu-user-static/amd64 has unsatisfiable Built-Using on glib2.0 2.56.4-0ubuntu0.18.04.6 qemu-user-static/amd64 has unsatisfiable Built-Using on glibc 2.27-3ubuntu1.2 I don't see anything about that in http://launchpadlibrarian.net/488558105/qemu_1%3A2.11+dfsg-1ubuntu7.28_1%3A2.11+dfsg-1ubuntu7.29.diff.gz Comparing https://launchpadlibrarian.net/486520742/buildlog_ubuntu-bionic-amd64.qemu_1%3A2.11+dfsg-1ubuntu7.28_BUILDING.txt.gz https://launchpadlibrarian.net/488663141/buildlog_ubuntu-bionic-amd64.qemu_1%3A2.11+dfsg-1ubuntu7.29_BUILDING.txt.gz Since it is static it correctly collects the BUilt-using. .28: Built-Using: gcc-8 (= 8.4.0-1ubuntu1~18.04), glib2.0 (= 2.56.4-0ubuntu0.18.04.6), glibc (= 2.27-3ubuntu1), zlib (= 1:1.2.11.dfsg-0ubuntu2) .29 Built-Using: gcc-8 (= 8.4.0-1ubuntu1~18.04), glib2.0 (= 2.56.4-0ubuntu0.18.04.6), glibc (= 2.27-3ubuntu1.2), zlib (= 1:1.2.11.dfsg-0ubuntu2) All that is available in bionic-updates, it almost seems it miscompares to bionic-release instead of bionic-updates. Might there have been any issue in selecting the target pocket? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887525 Title: qemu vhost-user should ignore irrelevant mem regions because it has limit of 8 regions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887525/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
