All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore A. Roth" <troth@openavr.org>
To: meta-virtualization@lists.yoctoproject.org
Cc: "Theodore A. Roth" <troth@openavr.org>,
	"Theodore A . Roth" <theodore_roth@trimble.com>
Subject: [meta-virtualization][PATCH] podman: Fix QA error for invalid PACKAGECONFIG
Date: Wed,  9 Apr 2025 09:06:20 -0600	[thread overview]
Message-ID: <20250409150620.59558-1-troth@openavr.org> (raw)

The insane.bbclass now flags as errors when PACKAGECONFIG contains a
value that does not have a setting.

For example, setting a value like this:

    PACKAGECONFIG += "foo"

without something like this in the recipe:

    PACKAGECONFIG[foo] = "stuff"

will result in QA errors like the following:

    ERROR: podman-v5.4.1-r0 do_recipe_qa: QA Issue: podman:
           invalid PACKAGECONFIG(s): docker rootless [invalid-packageconfig]
    ERROR: podman-v5.4.1-r0 do_recipe_qa: Fatal QA errors were found, failing task.

Signed-off-by: Theodore A. Roth <troth@openavr.org>
Signed-off-by: Theodore A. Roth <theodore_roth@trimble.com>
---
 recipes-containers/podman/podman_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-containers/podman/podman_git.bb b/recipes-containers/podman/podman_git.bb
index be85e512..9f886ed4 100644
--- a/recipes-containers/podman/podman_git.bb
+++ b/recipes-containers/podman/podman_git.bb
@@ -70,6 +70,9 @@ EXTRA_OEMAKE = " \
 # packageconfig, the podman package will rconfict with docker.
 PACKAGECONFIG ?= "docker"
 
+PACKAGECONFIG[docker] ?= ""
+PACKAGECONFIG[rootless] ?= ""
+
 do_compile() {
 	cd ${S}/src
 	rm -rf .gopath
-- 
2.34.1



             reply	other threads:[~2025-04-09 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 15:06 Theodore A. Roth [this message]
2025-04-09 20:53 ` [meta-virtualization][PATCH] podman: Fix QA error for invalid PACKAGECONFIG Bruce Ashfield
2025-04-09 21:28   ` Theodore A. Roth

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=20250409150620.59558-1-troth@openavr.org \
    --to=troth@openavr.org \
    --cc=meta-virtualization@lists.yoctoproject.org \
    --cc=theodore_roth@trimble.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.