From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH-for-5.0 v2 3/4] tests/docker: Use Python3 PyYAML in the Fedora image
Date: Sun, 22 Mar 2020 13:01:03 +0100 [thread overview]
Message-ID: <20200322120104.21267-4-philmd@redhat.com> (raw)
In-Reply-To: <20200322120104.21267-1-philmd@redhat.com>
The Python2 PyYAML is now pointless, switch to the Python3 version.
Fixes: bcbf27947 (docker: move tests from python2 to python3)
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
tests/docker/dockerfiles/fedora.docker | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/docker/dockerfiles/fedora.docker b/tests/docker/dockerfiles/fedora.docker
index 019eb12dcb..174979c7af 100644
--- a/tests/docker/dockerfiles/fedora.docker
+++ b/tests/docker/dockerfiles/fedora.docker
@@ -79,8 +79,8 @@ ENV PACKAGES \
perl-Test-Harness \
pixman-devel \
python3 \
+ python3-PyYAML \
python3-sphinx \
- PyYAML \
rdma-core-devel \
SDL2-devel \
snappy-devel \
--
2.21.1
next prev parent reply other threads:[~2020-03-22 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 12:01 [PATCH-for-5.0 v2 0/4] tests/docker: Fixes for 5.0 Philippe Mathieu-Daudé
2020-03-22 12:01 ` [PATCH-for-5.0 v2 1/4] tests/docker: Keep package list sorted Philippe Mathieu-Daudé
2020-03-22 12:01 ` [PATCH-for-5.0 v2 2/4] tests/docker: Install gcrypt devel package in Debian image Philippe Mathieu-Daudé
2020-03-23 10:08 ` Philippe Mathieu-Daudé
2020-03-22 12:01 ` Philippe Mathieu-Daudé [this message]
2020-03-22 12:01 ` [PATCH-for-5.0 v2 4/4] tests/docker: Add libepoxy and libudev packages to the Fedora image Philippe Mathieu-Daudé
2020-03-23 9:58 ` [PATCH-for-5.0 v2 0/4] tests/docker: Fixes for 5.0 Alex Bennée
2020-03-23 10:06 ` Philippe Mathieu-Daudé
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=20200322120104.21267-4-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--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).