Since we are using all proposed for ruby I don't need to explicitly select
vargant.
Also the recent rebuild made the old trigger target unavailable.
https://autopkgtest.ubuntu.com/request.cgi?release=bionic=amd64=vagrant-mutate=qemu%2F1%3A2.11%2Bdfsg-1ubuntu4=1
Due to ruby transition we need all proposed to get ruby in all of its variety
for 2.5.
Hopefully the rest in proposed is not having issues, utherwise this will become
a very long list of triggers.
Again ...
https://autopkgtest.ubuntu.com/request.cgi?release=bionic=amd64=vagrant-mutate=qemu%2F1%3A2.11%2Bdfsg-1ubuntu4=vagrant%2F2.0.2%2Bdfsg-2
https://autopkgtest.ubuntu.com/request.cgi?release=bionic=arm64=vagrant-mutate=qemu%2F1%3A2.11%2Bdfsg-1ubuntu4=vagrant%2F2.0.2%2Bdfsg-2
Vagrant 2 still did not migrate.
So it blocks qemu again - new links to trigger the test of vagrant-mutate (done
for qemu) against the new working vagrant version.
I discussed with Pitti, via adding the extra trigger of vagrant this will work.
So we will retry the tests originally triggered by distro-info and qemu but
with =vagrant%2F2.0.2%2Bdfsg-2 appended.
That would force it to pin the tested + vagrant from proposed and that should
work.
Full list of
