Xen 4.9 doesn't build on buster and won't be fixed for that.
Xen 4.10's "-prev" migration tests also fail for the same reason.
There is a (smallish) risk that Debian will break stretch before Xen
4.10 goes completely out of support from the Xen Project. If that
happens we could revert this - but then the 4.10 -prev jobs will stop
building.
Xen 4.9 is nearly out of security support, so for the 4.9 tests this
is a no-brainer.
I have checked the runvar diff. The results are to change
all_host_di_version [*]
all_host_suite
all_hostflags
debian_suite
debianhvm_suite
host_hostflags
in many jobs in
qemu-upstream-4.9-testing
qemu-upstream-4.10-testing
xen-4.9-testing
xen-4.10-testing
[*] this is not visible in standalone-generate-dump-flight-runvars
because it always just uses `current'.
This command produces no output:
diff -ub a <(perl -pe 's/stretch/buster/g' c)
(where `a' is before and `c' is after.)
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
xen-4.1-testing) defsuite="wheezy"; defguestsuite="wheezy";;
xen-4.2-testing) defsuite="wheezy"; defguestsuite="wheezy";;
xen-4.3-testing) defsuite="wheezy"; defguestsuite="wheezy";;
+ xen-4.9-testing) defsuite="stretch"; defguestsuite="stretch";;
+ xen-4.10-testing) defsuite="stretch"; defguestsuite="stretch";;
*)
defsuite=`getconfig DebianSuite`
defguestsuite=`getconfig GuestDebianSuite`