From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xenproject.org
Cc: Olaf Hering <olaf@aepfle.de>, Doug Goldstein <cardoe@cardoe.com>
Subject: [PATCH v1] automation: use zypper dup in tumbleweed dockerfile
Date: Thu, 8 Jul 2021 15:57:04 +0200 [thread overview]
Message-ID: <20210708135704.25626-1-olaf@aepfle.de> (raw)
The 'dup' command aligns the installed packages with the packages
found in the enabled repositories, taking the repository priorities
into account. Using this command is generally a safe thing to do.
In the context of Tumbleweed using 'dup' is essential, because package
versions might be downgraded, and package names occasionally change.
Only 'dup' will do the correct thing in such cases.
Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
automation/build/suse/opensuse-tumbleweed.dockerfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/automation/build/suse/opensuse-tumbleweed.dockerfile b/automation/build/suse/opensuse-tumbleweed.dockerfile
index a33ab0d870..3965e7f9cd 100644
--- a/automation/build/suse/opensuse-tumbleweed.dockerfile
+++ b/automation/build/suse/opensuse-tumbleweed.dockerfile
@@ -7,7 +7,7 @@ ENV USER root
RUN mkdir /build
WORKDIR /build
-RUN zypper ref && zypper up -y --no-recommends
+RUN zypper ref && zypper dup -y --no-recommends
RUN zypper install -y --no-recommends \
acpica \
bc \
next reply other threads:[~2021-07-08 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 13:57 Olaf Hering [this message]
2021-07-08 14:30 ` [PATCH v1] automation: use zypper dup in tumbleweed dockerfile Andrew Cooper
2021-07-08 14:33 ` Olaf Hering
2021-07-08 14:44 ` Andrew Cooper
2021-07-08 15:00 ` Olaf Hering
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=20210708135704.25626-1-olaf@aepfle.de \
--to=olaf@aepfle.de \
--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 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.