From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, manos.pitsidianakis@linaro.org,
"Ed Maste" <emaste@freebsd.org>, "Li-Wen Hsu" <lwhsu@freebsd.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [RFC PATCH] build deps: update lcitool to include rust bits
Date: Fri, 12 Jul 2024 11:12:06 +0100 [thread overview]
Message-ID: <ZpEBds6AUnPsVCY4@redhat.com> (raw)
In-Reply-To: <20240710154335.2510260-1-alex.bennee@linaro.org>
On Wed, Jul 10, 2024 at 04:43:35PM +0100, Alex Bennée wrote:
> For rust development we need cargo, rustc and bindgen in our various
> development environments. Update the libvirt-ci project to (!495) and
> regenerate the containers and other dependency lists.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> ---
> NB:
> - this is currently waiting on the upstream MR, but if you manually
> add the remote
> https://gitlab.com/stsquad/libvirt-ci/-/tree/more-rust-mappings the
> submodule update will work.
> ---
> .gitlab-ci.d/cirrus/freebsd-13.vars | 2 +-
> .gitlab-ci.d/cirrus/macos-13.vars | 2 +-
> .gitlab-ci.d/cirrus/macos-14.vars | 2 +-
> scripts/ci/setup/ubuntu/ubuntu-2204-aarch64.yaml | 3 +++
> scripts/ci/setup/ubuntu/ubuntu-2204-s390x.yaml | 3 +++
> tests/docker/dockerfiles/alpine.docker | 3 +++
> tests/docker/dockerfiles/centos9.docker | 3 +++
> tests/docker/dockerfiles/debian-amd64-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-arm64-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-armel-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-armhf-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-i686-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-mips64el-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-mipsel-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-ppc64el-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian-s390x-cross.docker | 4 ++++
> tests/docker/dockerfiles/debian.docker | 3 +++
> tests/docker/dockerfiles/fedora-win64-cross.docker | 3 +++
> tests/docker/dockerfiles/fedora.docker | 3 +++
> tests/docker/dockerfiles/opensuse-leap.docker | 2 ++
> tests/docker/dockerfiles/ubuntu2204.docker | 3 +++
> tests/lcitool/libvirt-ci | 2 +-
> tests/lcitool/projects/qemu.yml | 3 +++
> tests/vm/generated/freebsd.json | 2 ++
> 24 files changed, 71 insertions(+), 4 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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 :|
next prev parent reply other threads:[~2024-07-12 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 15:43 [RFC PATCH] build deps: update lcitool to include rust bits Alex Bennée
2024-07-12 9:09 ` Philippe Mathieu-Daudé
2024-07-12 10:12 ` Daniel P. Berrangé [this message]
2024-07-12 13:21 ` Manos Pitsidianakis
2024-07-12 14:24 ` Alex Bennée
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=ZpEBds6AUnPsVCY4@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=emaste@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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.