Message ID | 20190501104604.21416-1-ian.jackson@eu.citrix.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [OSSTEST] Drop Xen 4.5 and earlier | expand |
On 5/1/19 11:46 AM, Ian Jackson wrote: > These releases are out of security support. They are known not to > build on Debian stretch, which is what we are using, and we do not > intend to ever update them to fix that. > > Xen 4.6 is also out of security support but we want osstest to be able > to continue to build it so that we can test 4.6->4.7 migration, for > the purposes of testing Xen 4.7, which is still supported right now. > > So we have recently applied some build fixes to the 4.6 tree, and for > now we retain 4.6 in osstest so that build fixes applied to > staging-4.6 can propagate to stable-4.6. FWIW This all seems sensible to me. Thanks for keeping us in the loop. -George
>>> On 01.05.19 at 12:46, <ian.jackson@eu.citrix.com> wrote: > These releases are out of security support. They are known not to > build on Debian stretch, which is what we are using, and we do not > intend to ever update them to fix that. > > Xen 4.6 is also out of security support but we want osstest to be able > to continue to build it so that we can test 4.6->4.7 migration, for > the purposes of testing Xen 4.7, which is still supported right now. > > So we have recently applied some build fixes to the 4.6 tree, and for > now we retain 4.6 in osstest so that build fixes applied to > staging-4.6 can propagate to stable-4.6. > > CC: committers@xenproject.org > Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> In case it matters Acked-by: Jan Beulich <jbeulich@suse.com> However, ... > --- a/cr-for-branches > +++ b/cr-for-branches > @@ -31,7 +31,7 @@ scriptoptions="$1"; shift > LOGFILE=tmp/cr-for-branches.log > export LOGFILE > > -: ${BRANCHES:=osstest xen-4.0-testing xen-4.1-testing xen-4.2-testing > xen-4.3-testing xen-4.4-testing xen-4.5-testing xen-4.6-testing xen-4.7-testing > xen-4.8-testing xen-4.9-testing xen-4.10-testing xen-4.11-testing xen-4.12-testing > xen-unstable qemu-mainline qemu-upstream-unstable qemu-upstream-4.2-testing > qemu-upstream-4.3-testing qemu-upstream-4.4-testing qemu-upstream-4.5-testing > qemu-upstream-4.6-testing qemu-upstream-4.7-testing qemu-upstream-4.8-testing > qemu-upstream-4.9-testing qemu-upstream-4.10-testing qemu-upstream-4.11-testing > qemu-upstream-4.12-testing linux-linus linux-4.19 linux-4.14 linux-4.9 linux-4.4 > linux-4.1 linux-3.18 linux-3.16 linux-3.14 linux-3.10 linux-3.4 linux-arm-xen seabios > ovmf xtf ${EXTRA_BRANCHES}} > +: ${BRANCHES:=osstest xen-4.6-testing xen-4.7-testing xen-4.8-testing > xen-4.9-testing xen-4.10-testing xen-4.11-testing xen-4.12-testing xen-unstable > qemu-mainline qemu-upstream-unstable qemu-upstream-4.6-testing > qemu-upstream-4.7-testing qemu-upstream-4.8-testing qemu-upstream-4.9-testing > qemu-upstream-4.10-testing qemu-upstream-4.11-testing qemu-upstream-4.12-testing > linux-linus linux-4.19 linux-4.14 linux-4.9 linux-4.4 linux-4.1 linux-3.18 > linux-3.16 linux-3.14 linux-3.10 linux-3.4 linux-arm-xen seabios ovmf xtf > ${EXTRA_BRANCHES}} ... aren't the older Linux branches then in similar need of pruning? Seeing that for 32-bit Arm you can't even build mainline Linux with the newer compiler, I doubt at least the pretty old ones here have any chance of building cleanly. Jan
diff --git a/cr-for-branches b/cr-for-branches index 0ac3a97d..bc9ce2d3 100755 --- a/cr-for-branches +++ b/cr-for-branches @@ -31,7 +31,7 @@ scriptoptions="$1"; shift LOGFILE=tmp/cr-for-branches.log export LOGFILE -: ${BRANCHES:=osstest xen-4.0-testing xen-4.1-testing xen-4.2-testing xen-4.3-testing xen-4.4-testing xen-4.5-testing xen-4.6-testing xen-4.7-testing xen-4.8-testing xen-4.9-testing xen-4.10-testing xen-4.11-testing xen-4.12-testing xen-unstable qemu-mainline qemu-upstream-unstable qemu-upstream-4.2-testing qemu-upstream-4.3-testing qemu-upstream-4.4-testing qemu-upstream-4.5-testing qemu-upstream-4.6-testing qemu-upstream-4.7-testing qemu-upstream-4.8-testing qemu-upstream-4.9-testing qemu-upstream-4.10-testing qemu-upstream-4.11-testing qemu-upstream-4.12-testing linux-linus linux-4.19 linux-4.14 linux-4.9 linux-4.4 linux-4.1 linux-3.18 linux-3.16 linux-3.14 linux-3.10 linux-3.4 linux-arm-xen seabios ovmf xtf ${EXTRA_BRANCHES}} +: ${BRANCHES:=osstest xen-4.6-testing xen-4.7-testing xen-4.8-testing xen-4.9-testing xen-4.10-testing xen-4.11-testing xen-4.12-testing xen-unstable qemu-mainline qemu-upstream-unstable qemu-upstream-4.6-testing qemu-upstream-4.7-testing qemu-upstream-4.8-testing qemu-upstream-4.9-testing qemu-upstream-4.10-testing qemu-upstream-4.11-testing qemu-upstream-4.12-testing linux-linus linux-4.19 linux-4.14 linux-4.9 linux-4.4 linux-4.1 linux-3.18 linux-3.16 linux-3.14 linux-3.10 linux-3.4 linux-arm-xen seabios ovmf xtf ${EXTRA_BRANCHES}} export BRANCHES fetchwlem=$wlem
These releases are out of security support. They are known not to build on Debian stretch, which is what we are using, and we do not intend to ever update them to fix that. Xen 4.6 is also out of security support but we want osstest to be able to continue to build it so that we can test 4.6->4.7 migration, for the purposes of testing Xen 4.7, which is still supported right now. So we have recently applied some build fixes to the 4.6 tree, and for now we retain 4.6 in osstest so that build fixes applied to staging-4.6 can propagate to stable-4.6. CC: committers@xenproject.org Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> --- cr-for-branches | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)