From: Dario Faggioli <dfaggioli@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: [PATCH 1/3] automation: update openSUSE Tumbleweed building dependencies
Date: Thu, 30 Apr 2020 20:27:28 +0200 [thread overview]
Message-ID: <158827124854.19371.13461510910212179854.stgit@Palanthas> (raw)
In-Reply-To: <158827088416.19371.17008531228521109457.stgit@Palanthas>
We need python3 (and the respective -devel package), these days.
Signed-off-by: Dario Faggioli <dfaggioli@suse.com>
---
Cc: Doug Goldstein <cardoe@cardoe.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
---
This patch was submitted already, but not as part of this series.
Anyway, changes from v1:
* add python3 instead of replacing python2 with it.
---
I think the tumbleweed image in our registry needs to be updated.
---
.../build/suse/opensuse-tumbleweed.dockerfile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/automation/build/suse/opensuse-tumbleweed.dockerfile b/automation/build/suse/opensuse-tumbleweed.dockerfile
index 2676a87c85..084cce0921 100644
--- a/automation/build/suse/opensuse-tumbleweed.dockerfile
+++ b/automation/build/suse/opensuse-tumbleweed.dockerfile
@@ -56,6 +56,8 @@ RUN zypper install -y --no-recommends \
pkg-config \
python \
python-devel \
+ python3 \
+ python3-devel \
systemd-devel \
tar \
transfig \
next prev parent reply other threads:[~2020-04-30 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 18:27 [PATCH 0/3] Automation: improve openSUSE containers + podman Dario Faggioli
2020-04-30 18:27 ` Dario Faggioli [this message]
2020-04-30 18:27 ` [PATCH 2/3] automation: openSUSE distro names helpers for containerize Dario Faggioli
2020-04-30 18:27 ` [PATCH 3/3] automation: implement (rootless) podman support in containerize Dario Faggioli
2020-05-21 7:43 ` [PATCH 0/3] Automation: improve openSUSE containers + podman Dario Faggioli
2020-05-29 10:20 ` Dario Faggioli
2020-06-02 9:07 ` Wei Liu
2020-06-02 9:23 ` Paul Durrant
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=158827124854.19371.13461510910212179854.stgit@Palanthas \
--to=dfaggioli@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=xen-devel@lists.xenproject.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).