From: akuster808 <akuster808@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: [meta-selinux][PATCH] policycoreutils: remove oe_filter_out
Date: Sat, 21 Apr 2018 08:14:46 -0700 [thread overview]
Message-ID: <b3d86d0d-8b83-9a7d-034c-3e3b48040fe6@gmail.com> (raw)
In-Reply-To: <1523745199-16128-1-git-send-email-akuster@mvista.com>
On 04/14/2018 03:33 PM, Armin Kuster wrote:
> bb.data_smart.ExpansionError: Failure expanding variable WARN_QA[:=], expression was ${@oe_filter_out('unsafe-references-in-scripts', 'ldflags useless-rpaths rpaths staticdev libdir xorg-driver-abi textrel already-stripped incompatible-license files-invalid installed-vs-shipped compile-host-path install-host-path pn-overrides infodir build-deps unknown-configure-option symlink-to-sysroot multilib invalid-packageconfig host-user-contaminated uppercase-pn ', d)} which triggered exception NameError: name 'oe_filter_out' is not defined
>
> Signed-off-by: Armin Kuster <akuster@mvista.com>
> ---
> recipes-security/selinux/policycoreutils.inc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-security/selinux/policycoreutils.inc b/recipes-security/selinux/policycoreutils.inc
> index 442b086..1842fd8 100644
> --- a/recipes-security/selinux/policycoreutils.inc
> +++ b/recipes-security/selinux/policycoreutils.inc
> @@ -64,8 +64,8 @@ RDEPENDS_${BPN}-setsebool += "\
> "
> RDEPENDS_${BPN} += "selinux-python"
>
> -WARN_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${WARN_QA}', d)}"
> -ERROR_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${ERROR_QA}', d)}"
> +WARN_QA_remove = " unsafe-references-in-scripts"
> +ERROR_QA_remove = " unsafe-references-in-scripts"
>
Ping
>
> PACKAGES =+ "\
next prev parent reply other threads:[~2018-04-21 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 22:33 [meta-selinux][PATCH] policycoreutils: remove oe_filter_out Armin Kuster
2018-04-21 15:14 ` akuster808 [this message]
2018-04-23 8:55 ` wenzong fan
2018-05-07 17:20 ` akuster
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=b3d86d0d-8b83-9a7d-034c-3e3b48040fe6@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@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 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.