From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] Drop qemumipsel-buster
Date: Tue, 23 Apr 2024 08:44:56 +0300 [thread overview]
Message-ID: <d9c61748d5ca0dcb31357c092339df999c32b7fe.camel@ilbers.de> (raw)
In-Reply-To: <20240423054134.19100-1-ubely@ilbers.de>
On Tue, 2024-04-23 at 08:41 +0300, Uladzimir Bely wrote:
> Debian dropped support of mipsel (and some other architectures)
...for Buster. Will fix the message on merge (or v2 if needed)
> since 2024-04-13.
>
> Last snapshot including mipsel:
> snapshot.debian.org/archive/debian/20240413T144939Z/dists/buster/main
>
> First snapshot not including it:
> snapshot.debian.org/archive/debian/20240413T211957Z/dists/buster/main
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> kas/machine/Kconfig | 2 +-
> testsuite/citest.py | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/kas/machine/Kconfig b/kas/machine/Kconfig
> index 9ab21d69..86039f1b 100644
> --- a/kas/machine/Kconfig
> +++ b/kas/machine/Kconfig
> @@ -68,7 +68,7 @@ config MACHINE_QEMU_I386
>
> config MACHINE_QEMU_MIPSEL
> bool "qemumipsel"
> - depends on DEBIAN_BUSTER || DEBIAN_BULLSEYE ||
> DEBIAN_BOOKWORM
> + depends on DEBIAN_BULLSEYE || DEBIAN_BOOKWORM
>
> config MACHINE_QEMU_RISCV64
> bool "qemuriscv64"
> diff --git a/testsuite/citest.py b/testsuite/citest.py
> index b1c0b760..42d44f6a 100755
> --- a/testsuite/citest.py
> +++ b/testsuite/citest.py
> @@ -187,7 +187,6 @@ class NoCrossTest(CIBaseTest):
> 'mc:qemui386-bullseye:isar-image-base',
> 'mc:qemuamd64-buster:isar-image-ci',
> 'mc:qemuamd64-bullseye:isar-initramfs',
> - 'mc:qemumipsel-buster:isar-image-base',
> 'mc:qemumipsel-bullseye:isar-image-base',
> 'mc:imx6-sabrelite-bullseye:isar-image-base',
> 'mc:phyboard-mira-bullseye:isar-image-base',
> --
> 2.43.2
>
prev parent reply other threads:[~2024-04-23 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 5:41 Uladzimir Bely
2024-04-23 5:44 ` Uladzimir Bely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9c61748d5ca0dcb31357c092339df999c32b7fe.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox