From: Peter Kjellerstedt <pkj@axis.com>
To: <meta-virtualization@lists.yoctoproject.org>
Subject: [nanbield][PATCH] containerd-opencontainers: Use RDEPENDS:${PN} instead of RDEPENDS:${BPN}
Date: Tue, 30 Jan 2024 22:07:38 +0100 [thread overview]
Message-ID: <20240130210738.3679348-1-pkj@axis.com> (raw)
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
The original purpose of using BPN vs PN in the RDEPENDS was due to
32bit multilib issues. Those problems are no longer present, so we
can adjust this recipe to use the standard PN in rdepends.
This change avoids the following warning:
WARNING: .../containerd-opencontainers_git.bb: Variable key
RDEPENDS:${PN} (...) replaces original key
RDEPENDS:containerd-opencontainers
( ${VIRTUAL-RUNTIME_container_runtime}).
if, e.g., RDEPENDS:${PN}:append = " ..." is used in a bbappend or
bbclass.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
recipes-containers/containerd/containerd-opencontainers_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-containers/containerd/containerd-opencontainers_git.bb b/recipes-containers/containerd/containerd-opencontainers_git.bb
index 78fe694..d365820 100644
--- a/recipes-containers/containerd/containerd-opencontainers_git.bb
+++ b/recipes-containers/containerd/containerd-opencontainers_git.bb
@@ -98,6 +98,6 @@ INSANE_SKIP:${PN} += "ldflags already-stripped"
COMPATIBLE_HOST = "^(?!(qemu)?mips).*"
-RDEPENDS:${BPN} += " ${VIRTUAL-RUNTIME_container_runtime}"
+RDEPENDS:${PN} += " ${VIRTUAL-RUNTIME_container_runtime}"
CVE_PRODUCT = "containerd"
next reply other threads:[~2024-01-30 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 21:07 Peter Kjellerstedt [this message]
2024-02-01 14:17 ` [meta-virtualization] [nanbield][PATCH] containerd-opencontainers: Use RDEPENDS:${PN} instead of RDEPENDS:${BPN} Bruce Ashfield
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=20240130210738.3679348-1-pkj@axis.com \
--to=pkj@axis.com \
--cc=meta-virtualization@lists.yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).