public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <openembedded-core@lists.openembedded.org>, <nikhil.r@bmwtechworks.in>
Subject: Re: [OE-core][master][PATCH] libseccomp: add diffutils to ptest RDEPENDS
Date: Fri, 27 Feb 2026 00:04:40 +0100	[thread overview]
Message-ID: <DGP9PLZJ9IIH.1AFCGS6H37VUZ@smile.fr> (raw)
In-Reply-To: <20260225094114.44082-1-git-patches@bmwtechworks.in>

On Wed Feb 25, 2026 at 10:41 AM CET, Nikhil R via lists.openembedded.org wrote:
> From: Nikhil R <nikhil.r@bmwtechworks.in>
>
> libseccomp ptest needs diff during test execution,
> add diffutils to the runtime ptest deps.
>
> Signed-off-by: Nikhil R <nikhil.r@bmwtechworks.in>
> ---
>  meta/recipes-support/libseccomp/libseccomp_2.5.5.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/libseccomp/libseccomp_2.5.5.bb b/meta/recipes-support/libseccomp/libseccomp_2.5.5.bb
> index 478e5f4289..dd253a7826 100644
> --- a/meta/recipes-support/libseccomp/libseccomp_2.5.5.bb
> +++ b/meta/recipes-support/libseccomp/libseccomp_2.5.5.bb

Given the recipe version, this patch is targeted at scarthgap and does
not apply on master.

> @@ -59,4 +59,4 @@ FILES:${PN} = "${bindir} ${libdir}/${BPN}.so* ${PYTHON_SITEPACKAGES_DIR}/"
>  FILES:${PN}-dbg += "${libdir}/${PN}/tests/.debug/* ${libdir}/${PN}/tools/.debug"
>  
>  RDEPENDS:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'python', 'python3', '', d)}"
> -RDEPENDS:${PN}-ptest = "coreutils bash"
> +RDEPENDS:${PN}-ptest = "coreutils bash diffutils"

-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-02-26 23:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  9:41 [OE-core][master][PATCH] libseccomp: add diffutils to ptest RDEPENDS Nikhil R
2026-02-26 23:04 ` Yoann Congal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-25  9:16 Nikhil R

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=DGP9PLZJ9IIH.1AFCGS6H37VUZ@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=nikhil.r@bmwtechworks.in \
    --cc=openembedded-core@lists.openembedded.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