Daniel P. Berrangé <[email protected]> writes: > On Mon, Sep 22, 2025 at 12:38:09PM +0400, Marc-André Lureau wrote: >> Hi >> >> On Fri, Sep 19, 2025 at 6:21 PM Daniel P. Berrangé <[email protected]> >> wrote: >> >> > On Fri, Sep 19, 2025 at 05:33:08PM +0400, [email protected] >> > wrote: >> > > From: Marc-André Lureau <[email protected]> >> > > >> > > We are updating debian which dropped support for it: >> > > >> > https://www.debian.org/releases/trixie/release-notes/issues.html#mips-architectures-removed >> > >> > If Debian 13 has dropped it, why aren't we just keeping the mips >> > dockerfiles on 12 ? >> > >> > The debian-legacy-test-cross a manually written dockerfile that >> > has almost none of our deps installed, and is still on 11 which >> > is outside our support matrix now. So I don't think we should >> > be expanding use of debian-legacy-test-cross, ideally it would >> > be removed entirely. >> > >> > >> debian-legacy-test-cross is for tests/tcg. Debian 11 supports more >> architecture than 12 or 13.. > > If there are architectures in 11 that can't be tested in 12, > then from QEMU's POV that is now an untestable feature, since > 11 is outside our support target and we don't want to be > holding back our support platforms for this. > >> > > diff --git a/tests/lcitool/refresh b/tests/lcitool/refresh >> > > index 6f98a91277..917ff4abfb 100755 >> > > --- a/tests/lcitool/refresh >> > > +++ b/tests/lcitool/refresh >> > > @@ -215,16 +215,6 @@ try: >> > > "x86_64-linux-user," >> > > >> > "i386-softmmu,i386-linux-user")) >> > > >> > > - generate_dockerfile("debian-mips64el-cross", "debian-12", >> > > - cross="mips64el", >> > > - trailer=cross_build("mips64el-linux-gnuabi64-", >> > > - >> > "mips64el-softmmu,mips64el-linux-user")) >> > > - >> > > - generate_dockerfile("debian-mipsel-cross", "debian-12", >> > > - cross="mipsel", >> > > - trailer=cross_build("mipsel-linux-gnu-", >> > > - >> > "mipsel-softmmu,mipsel-linux-user")) >> > > - >> > >> > I'm not seeing the need to remove these, when they could just >> > stay on -12, when the next commit updates the other arches >> > to -13. >> > >> >> Indeed.. it depends how much we want to keep covering. We already don't >> cover all qemu cross compilations. The question is do we want to keep >> cross-compiling for soon unsupported arches?
Cross compiling QEMU depends on decent multi-arch support and indeed we should deprecate it now so we can drop it when bookworm finally drops out of LTS. debian-legacy-test-cross is the held back version of debian-all-test-cross which is a native build + the cross compilers for check-tcg. >> >> @Bennée, Alex <[email protected]> might know, thanks > > A feature remains fully supported for production use the while time it > is marked as deprecated. Provided one of our current supported platforms > has the ability to test it, there should be no change to our testing > status of deprecated features. Given that -12 is still a supported > platform we should continue to use that, and certainly not replace it > with -11 which is an unsupported platform. > > With regards, > Daniel -- Alex Bennée Virtualisation Tech Lead @ Linaro
