All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Quan.Sun@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0
Date: Tue, 05 May 2026 08:43:33 +0100	[thread overview]
Message-ID: <09130fab3a76b8402ad4753bfb1d71fd6775ebd2.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260505001613.1203967-1-Quan.Sun@windriver.com>

On Mon, 2026-05-04 at 17:16 -0700, Quan.Sun via lists.openembedded.org wrote:
> From: Quan Sun <Quan.Sun@windriver.com>
> 
> Signed-off-by: Quan Sun <Quan.Sun@windriver.com>

The changelog should mention any key changes.

> @@ -26,8 +26,6 @@ do_install:append() {
>      rm -rf ${D}${datadir}/icons/
>      rm -rf ${D}${includedir}/qemu-plugin.h
>  
> -    # Install qmp.py to be used with testimage
> -    install -d ${D}${libdir}/qemu-python/qmp/
> -    install -D ${S}/python/qemu/qmp/* ${D}${libdir}/qemu-python/qmp/
> +    # The qemu.qmp library from the main QEMU repository has now been removed.
>  }

This looks like a key change that should be mentioned!

Unfortunately, as the code says, testimage uses qmp. We therefore need
to find a new way to provide qmp for testimage. We can't simply delete
it and the comment you've left isn't useful either.

https://github.com/qemu/qemu/commit/e1e49b35b3c3cf6b7c68b6b1df18a477ac3183e5

mentioned we should be using:

https://gitlab.com/qemu-project/python-qemu-qmp/


> @@ -26,5 +26,5 @@ index 82cace1..83bbda9 100755
>  -fi
>  +meson=`which meson`
>   
> - # Conditionally ensure Sphinx is installed.
> - 
> + # On Haiku, meson might show up in a "non-packaged" subfolder instead, see
> + # https://github.com/haiku/haiku/blob/r1beta5/docs/user/storage/storageintro.dox
> diff --git a/meta/recipes-devtools/qemu/qemu/0010-meson-fix-subproject-include-paths-for-standalone-bu.patch b/meta/recipes-devtools/qemu/qemu/0010-meson-fix-subproject-include-paths-for-standalone-bu.patch
> new file mode 100644
> index 0000000000..b7d31f0ed7
> --- /dev/null
> +++ b/meta/recipes-devtools/qemu/qemu/0010-meson-fix-subproject-include-paths-for-standalone-bu.patch
> @@ -0,0 +1,52 @@
> +From f013e84d382bc1bd7d49206bdf47c689b0c6fbb5 Mon Sep 17 00:00:00 2001
> +From: Quan Sun <Quan.Sun@windriver.com>
> +Date: Fri, 1 May 2026 13:53:24 -0700
> +Subject: [PATCH] meson: fix subproject include paths for standalone builds
> +
> +Upstream-Status: Pending

Why Pending? Do we need to dicuss this issue with upstream?

Cheers,

Richard




  parent reply	other threads:[~2026-05-05  7:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  0:16 [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0 Quan.Sun
2026-05-05  1:00 ` Patchtest results for " patchtest
2026-05-05  7:43 ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-06 21:48 Quan.Sun
2026-05-07 10:34 ` Mathieu Dubois-Briand
2026-05-07 20:49   ` Quan Sun
2026-05-07 11:23 ` Alexander Kanavin
2026-05-07 15:01   ` Paul Barker
2026-05-07 20:29   ` Quan Sun
2026-05-08 20:08     ` Alexander Kanavin
2026-05-08 21:35       ` Quan Sun
2026-05-15 15:48 Quan.Sun
2026-05-15 16:24 ` Alexander Kanavin
2026-05-15 19:15   ` Quan Sun

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=09130fab3a76b8402ad4753bfb1d71fd6775ebd2.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Quan.Sun@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.