From: Paul Barker <paul@pbarker.dev>
To: alex.kanavin@gmail.com, Quan.Sun@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0
Date: Thu, 07 May 2026 16:01:21 +0100 [thread overview]
Message-ID: <46e6de3dea514e2f30dfe806dbddef9f08caa60a.camel@pbarker.dev> (raw)
In-Reply-To: <CANNYZj_++oDps3s2uq51a7j3CQgK1MSuuSgY9Cz0-wFtE2gnSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Thu, 2026-05-07 at 13:23 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> On Wed, 6 May 2026 at 23:49, Quan.Sun via lists.openembedded.org
> <Quan.Sun=windriver.com@lists.openembedded.org> wrote:
> > +SRC_URI += "git://gitlab.com/qemu-project/python-qemu-qmp.git;protocol=https;branch=main;destsuffix=python-qemu-qmp;name=qemu-qmp"
> > +SRCREV_qemu-qmp = "82006cb788d27b090a8b84fc7831feb9c528bcdc"
>
> This component should be provided with a separate recipe.
To explain this a little more:
- python-qemu-qmp has its own version numbers now that it has been
broken out into its own repository. So, it would be much better to
have a proper recipe for this with the correct version number
specified.
- In the README file, under "Who is this library for?" it says: "This
library was split out of the QEMU source tree in order to share a
reference version of a QMP library that was usable both within and
outside of the QEMU source tree." - so, python-qemu-qmp may be used by
other software packages in the future as well as being directly used
by qemu.
- Packaging may be cleaner if this Python library is a separate recipe.
Feel free to ask if you have any questions :)
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-05-07 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 21:48 [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0 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 [this message]
2026-05-07 20:29 ` Quan Sun
2026-05-08 20:08 ` Alexander Kanavin
2026-05-08 21:35 ` Quan Sun
-- strict thread matches above, loose matches on Subject: below --
2026-05-15 15:48 Quan.Sun
2026-05-15 16:24 ` Alexander Kanavin
2026-05-15 19:15 ` Quan Sun
2026-05-05 0:16 Quan.Sun
2026-05-05 7:43 ` Richard Purdie
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=46e6de3dea514e2f30dfe806dbddef9f08caa60a.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=Quan.Sun@windriver.com \
--cc=alex.kanavin@gmail.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.