From: "Philippe Mathieu-Daudé via" <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: "Ed Maste" <emaste@freebsd.org>, "Thomas Huth" <thuth@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Li-Wen Hsu" <lwhsu@freebsd.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [PATCH v6 6/7] tests: Manually remove libxml2 on MSYS2 runners
Date: Fri, 21 Jan 2022 16:41:33 +0100 [thread overview]
Message-ID: <20220121154134.315047-7-f4bug@amsat.org> (raw)
In-Reply-To: <20220121154134.315047-1-f4bug@amsat.org>
lcitool doesn't support MSYS2 targets, so manually remove
this now unnecessary library.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
.cirrus.yml | 1 -
.gitlab-ci.d/windows.yml | 2 --
2 files changed, 3 deletions(-)
diff --git a/.cirrus.yml b/.cirrus.yml
index 02c43a074a1..7552d709745 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -32,7 +32,6 @@ windows_msys2_task:
mingw-w64-x86_64-libgcrypt
mingw-w64-x86_64-libpng
mingw-w64-x86_64-libssh
- mingw-w64-x86_64-libxml2
mingw-w64-x86_64-snappy
mingw-w64-x86_64-libusb
mingw-w64-x86_64-usbredir
diff --git a/.gitlab-ci.d/windows.yml b/.gitlab-ci.d/windows.yml
index 62dd9ed8329..1df16303491 100644
--- a/.gitlab-ci.d/windows.yml
+++ b/.gitlab-ci.d/windows.yml
@@ -44,7 +44,6 @@ msys2-64bit:
mingw-w64-x86_64-libssh
mingw-w64-x86_64-libtasn1
mingw-w64-x86_64-libusb
- mingw-w64-x86_64-libxml2
mingw-w64-x86_64-nettle
mingw-w64-x86_64-ninja
mingw-w64-x86_64-pixman
@@ -80,7 +79,6 @@ msys2-32bit:
mingw-w64-i686-libssh
mingw-w64-i686-libtasn1
mingw-w64-i686-libusb
- mingw-w64-i686-libxml2
mingw-w64-i686-lzo2
mingw-w64-i686-ninja
mingw-w64-i686-pixman
--
2.34.1
next prev parent reply other threads:[~2022-01-21 15:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 15:41 [PATCH v6 0/7] tests: Refresh lcitool submodule & remove libxml2 Philippe Mathieu-Daudé via
2022-01-21 15:41 ` [PATCH v6 1/7] MAINTAINERS: Cover lcitool submodule with build test / automation Philippe Mathieu-Daudé via
2022-01-21 15:41 ` [PATCH v6 2/7] gitmodules: Correct libvirt-ci submodule URL Philippe Mathieu-Daudé via
2022-01-21 15:41 ` [PATCH v6 3/7] tests/lcitool: Include local qemu.yml when refreshing cirrus-ci files Philippe Mathieu-Daudé via
2022-01-21 15:41 ` [PATCH v6 4/7] drop libxml2 checks since libxml is not actually used (for parallels) Philippe Mathieu-Daudé via
2022-01-21 15:41 ` [PATCH v6 5/7] tests/lcitool: Refresh submodule and remove libxml2 Philippe Mathieu-Daudé via
2022-01-21 15:41 ` Philippe Mathieu-Daudé via [this message]
2022-01-21 15:41 ` [PATCH v6 7/7] tests/lcitool: Install libibumad to cover RDMA on Debian based distros Philippe Mathieu-Daudé via
2022-01-24 9:16 ` [PATCH v6 0/7] tests: Refresh lcitool submodule & remove libxml2 Alex Bennée
2022-01-24 10:55 ` Alex Bennée
2022-01-24 18:29 ` Philippe Mathieu-Daudé via
2022-01-24 19:16 ` Alex Bennée
2022-01-24 19:33 ` Philippe Mathieu-Daudé via
2022-01-25 10:59 ` Philippe Mathieu-Daudé via
2022-01-31 7:04 ` Alessandro Di Federico via
2022-01-26 7:38 ` Mark Cave-Ayland
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=20220121154134.315047-7-f4bug@amsat.org \
--to=qemu-devel@nongnu.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=emaste@freebsd.org \
--cc=f4bug@amsat.org \
--cc=lwhsu@freebsd.org \
--cc=mjt@tls.msk.ru \
--cc=thuth@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.