qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QEMU's Haiku CI image


From: Thomas Huth
Subject: Re: QEMU's Haiku CI image
Date: Wed, 16 Feb 2022 18:39:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0

On 16/02/2022 18.16, Philippe Mathieu-Daudé wrote:
On 16/2/22 17:32, Thomas Huth wrote:
On 16/02/2022 16.52, Alexander von Gluck IV wrote:
February 16, 2022 6:31 AM, "Thomas Huth" <thuth@redhat.com> wrote:

while researching the different "sed" options on our supported build platform today, I started "make vm-build-haiku.x86_64" in my QEMU build directory for the first time since many months again. And I had to discover that this is completely out of date. The image does not contain any version of Python 3 yet which we require for compilation since more than a year now already, and the Haiku version in there seems to be too old to do a "pkgman install -y python3" ... so this has been completely been bitrotting since more than a year now. Is anybody still interested in keeping the Haiku support in QEMU? If so, please help to get the VM image updated. Thanks!

I submitted
20220216154208.2985103-1-kallisti5@unixzen.com/">https://patchwork.kernel.org/project/qemu-devel/patch/20220216154208.2985103-1-kallisti5@unixzen.com/
to fix this issue.  The build runs as expected after that patchset.

Likely cause is us no longer packing a "python" binary, deferring to "python2" vs "python3"

I'm still the most likely maintainer.  Are there still plans to automate the tests for Haiku to
prevent this from happening again in the future?

AFAIK we still don't have a machine where we could properly run VM-based tests in the CI, do we? Peter? Cleber?

We still have unused fosshost.org resources. What we don't have is a
sysadmin willing to install the VM and maintain it over time.

I thought that one does not have KVM enabled?

 Thomas





reply via email to

[Prev in Thread] Current Thread [Next in Thread]