qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org
Subject: Re: [RFC PATCH 3/4] lcitool: allow overriding package mappings and target facts
Date: Wed, 8 Feb 2023 17:31:01 +0000	[thread overview]
Message-ID: <Y+PcVRXC0acaf8Iz@redhat.com> (raw)
In-Reply-To: <20230117091638.50523-4-pbonzini@redhat.com>

On Tue, Jan 17, 2023 at 10:16:37AM +0100, Paolo Bonzini wrote:
> lcitool has generally catered to the Libvirt's needs in terms of
> package versions, which are pretty conservative. For example, lcitool
> is hardcoding a version of Meson equal to 0.56. QEMU on the other hand
> has different needs since some features were added to Meson for the
> project's benefit in versions as recent as 0.63.
> 
> Until now, QEMU has managed to avoid the problem by shipping its own
> version of Meson. However, the next release of QEMU will face a breaking
> point in that Meson 0.63 does not work with the 3.6 version of Python
> that is provided by CentOS Stream 8 and OpenSUSE LEAP 15.3.
> 
> Implement locally the functionality provided by
> https://gitlab.com/libvirt/libvirt-ci/-/merge_requests/341, so that
> QEMU can override the mappings and target paths that are used for its CI.

I'd like to just push ahead with getting that merged so we
use the lcitool --data-dir arg to do what QEMU needs, and
stay away from the internal python code.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-02-08 17:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  9:16 [RFC PATCH 0/4] Update CentOS and OpenSUSE CI to Python >=3.7 Paolo Bonzini
2023-01-17  9:16 ` [RFC PATCH 1/4] lcitool: update submodule Paolo Bonzini
2023-01-17  9:16 ` [RFC PATCH 2/4] lcitool: use libvirt-ci as library Paolo Bonzini
2023-02-08 17:27   ` Daniel P. Berrangé
2023-01-17  9:16 ` [RFC PATCH 3/4] lcitool: allow overriding package mappings and target facts Paolo Bonzini
2023-02-08 17:31   ` Daniel P. Berrangé [this message]
2023-01-17  9:16 ` [RFC PATCH 4/4] ci, docker: update CentOS and OpenSUSE Python to non-EOL versions Paolo Bonzini
2023-02-08 17:45   ` Daniel P. Berrangé
2023-02-08 17:22 ` [RFC PATCH 0/4] Update CentOS and OpenSUSE CI to Python >=3.7 Paolo Bonzini

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=Y+PcVRXC0acaf8Iz@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).