Re: [XEN PATCH v2 6/7] automation: Remove testing on Debian Jessie

From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel@lists.xenproject.org
Cc: Doug Goldstein <cardoe@cardoe.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v2 6/7] automation: Remove testing on Debian Jessie
Date: Tue, 21 Feb 2023 17:59:11 +0000	[thread overview]
Message-ID: <04e6ccb1-919f-671e-6d70-15a74e01bbb4@citrix.com> (raw)
In-Reply-To: <20230221165542.7642-7-anthony.perard@citrix.com>

On 21/02/2023 4:55 pm, Anthony PERARD wrote:
> Jessie as rearch EOL in 2020.
>
> Even if we update the containers, we would still not be able to reach
> HTTPS webside with Let's Encrypt certificates and thus would need more
> change to the container.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>

How is this interact with the other patches in the series?

I presume we do want to take patch 4 and rebuild the containers, for the
older branches.  And that's fine.

And IMO we should be dropping jessie testing, so this is almost fine for
staging.

Except, jessie-32 is the only x86-32 build test we've got, so I think we
want to replace it with a newer container before dropping the jessie*.

> ---
> Notes:
>     HTTPS would fail unless we commit "automation: Remove expired root
>     certificates used to be used by let's encrypt", that is. Patch still in
>     the series, and fix Jessie.

If we're dropping the jessie containers, do we really need that change
too?  Because we really shouldn't be playing around with URLs on older
branches.

~Andrew