From: Clayton Casciato <majortomtosourcecontrol@gmail.com>
To: openembedded-core@lists.openembedded.org, zboszor@gmail.com
Subject: [PATCH] rpm-sequoia-crypto-policy: add nativesdk to BBCLASSEXTEND
Date: Sun, 28 Sep 2025 14:32:19 -0600 [thread overview]
Message-ID: <a5b379d1-88b8-499c-bfe6-d741e508ca84@gmail.com> (raw)
Prerequisite for nativesdk-rpm.
Would be required by nativesdk-rpm-sequoia
ERROR: Nothing RPROVIDES 'nativesdk-rpm-sequoia-crypto-policy'
(but virtual:nativesdk:
[...]/meta/recipes-devtools/rpm-sequoia/rpm-sequoia_1.9.0.bb
RDEPENDS on or otherwise requires it)
Reproduce:
1. Add "sequoia" to rpm's default PACKAGECONFIG [1]
2. Add "nativesdk" to rpm-sequoia's BBCLASSEXTEND
3. Configure local.conf [2]
4. Attempt to build "core-image-minimal"
[1] This is seen when directly modifying the weak default.
This does not occur with "PACKAGECONFIG:append:pn-rpm".
[2]
INHERIT += "sign_rpm"
RPM_GPG_NAME = "[...]"
RPM_GPG_PASSPHRASE = "[...]"
GPG_PATH = "[...]"
Signed-off-by: Clayton Casciato <majortomtosourcecontrol@gmail.com>
---
.../rpm-sequoia/rpm-sequoia-crypto-policy_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy_git.bb b/meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy_git.bb
index 19b86ae391..c602bb4b5a 100644
--- a/meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy_git.bb
+++ b/meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy_git.bb
@@ -34,4 +34,4 @@ do_install () {
FILES:${PN} = "${datadir}/crypto-policies/back-ends/*"
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
next reply other threads:[~2025-09-28 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 20:32 Clayton Casciato [this message]
2025-09-29 9:40 ` [OE-core] [PATCH] rpm-sequoia-crypto-policy: add nativesdk to BBCLASSEXTEND Alexander Kanavin
2025-09-29 13:47 ` Clayton Casciato
2025-09-29 14:47 ` Alexander Kanavin
2025-09-29 15:40 ` Clayton Casciato
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=a5b379d1-88b8-499c-bfe6-d741e508ca84@gmail.com \
--to=majortomtosourcecontrol@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=zboszor@gmail.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.