qemu-arm.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, "Gustavo Romero" <gustavo.romero@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"BALATON Zoltan" <balaton@eik.bme.hu>,
	qemu-s390x@nongnu.org, "Liviu Ionescu" <ilg@livius.net>
Subject: Re: [PATCH 0/5] testing/next - arm custom runner tweaks
Date: Tue, 14 Oct 2025 20:19:02 +0200	[thread overview]
Message-ID: <c32612d4-3def-47b3-b32c-fbd1ec527012@redhat.com> (raw)
In-Reply-To: <874is1l7db.fsf@draig.linaro.org>

On 14/10/2025 19.29, Alex Bennée wrote:
> Thomas Huth <thuth@redhat.com> writes:
> 
>> On 14/10/2025 12.43, Alex Bennée wrote:
>>> This isn't quite ready yet as there is an in-flight MR for libvirt-ci
>>> and the final patch has to manually drop a couple of packages which
>>> don't cleanly install. I don't know if we should deal with that
>>> upstream or in the lcitool metadata. For reference the two packages
>>> are:
>>>     libcurl4-gnutls-dev:armhf
>>>     libglusterfs-dev:armhf
>>
>> FYI, glusterfs is deprecated in QEMU since a while:
>>
>>   https://gitlab.com/qemu-project/qemu/-/commit/b873463821343c6f702c4195f2168790b09cf44e
>>
>> ... so you could also add a patch that removes it from QEMU now, I
>> guess.
> 
> I can do that.
> 
> 
> Richard and Phillipe reminded me that we are due to drop 32 bit hosts
> real soon now so maybe I should just remove the runner and the hacks
> needed to get it working?

Let see ... the last time I tried to deprecate 32-bit arm, I've been told 
that the Raspberry Pis still use a 32-bit OS by default:

  https://lore.kernel.org/qemu-devel/F852C238-77B8-4E24-9494-8D060EB78F9F@livius.net/

... and the right time to drop 32-bit arm is when most Pi users install a 
64-bit OS by default:

  https://lore.kernel.org/qemu-devel/379B4C23-61C2-4AA3-A851-EEFC98A9AFF6@livius.net/

So looking at https://www.raspberrypi.com/software/operating-systems/ now, 
it seems like the 64-bit version is the default nowadays (at least it is the 
first option there, and no more recommendation for the 32-bit version), so 
yes, it's likely about time to get rid of the 32-bit arm hosts now!

  Thomas



      reply	other threads:[~2025-10-14 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 10:43 [PATCH 0/5] testing/next - arm custom runner tweaks Alex Bennée
2025-10-14 10:43 ` [PATCH 1/5] tests/lcitool: bump to latest version and regenerate (!wait on upstream) Alex Bennée
2025-10-14 10:43 ` [PATCH 2/5] gitlab: use template for ubuntu-24.04-aarch64 jobs Alex Bennée
2025-10-14 10:43 ` [PATCH 3/5] gitlab: modernise the ubuntu24.04-aarch32 jobs Alex Bennée
2025-10-14 10:43 ` [PATCH 4/5] scripts/setup: update the armhf overlay Alex Bennée
2025-10-14 10:43 ` [PATCH 5/5] scripts/setup: update build-environment to use armhf yaml (!WIP) Alex Bennée
2025-10-14 10:47 ` [PATCH 0/5] testing/next - arm custom runner tweaks Thomas Huth
2025-10-14 17:29   ` Alex Bennée
2025-10-14 18:19     ` Thomas Huth [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=c32612d4-3def-47b3-b32c-fbd1ec527012@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=balaton@eik.bme.hu \
    --cc=gustavo.romero@linaro.org \
    --cc=ilg@livius.net \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).