Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
	Armin Kuster <akuster808@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] [openembedded-core] 21/35: ptest: Add RDEPENDS frpm PN-ptest to PN package
Date: Sun, 9 Jun 2019 09:56:00 +0200	[thread overview]
Message-ID: <20190609075600.GA1487@jama> (raw)
In-Reply-To: <20190607125811.05DDB235A87@git.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 2508 bytes --]

On Fri, Jun 07, 2019 at 12:58:30PM +0000, git@git.openembedded.org wrote:
> This is an automated email from the git hooks/post-receive script.
> 
> rpurdie pushed a commit to branch warrior
> in repository openembedded-core.
> 
> commit 1ad805984c8c9c9a505b6b0e8ad870b8233b13b2
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> AuthorDate: Tue May 14 12:22:14 2019 +0100
> 
>     ptest: Add RDEPENDS frpm PN-ptest to PN package

Hi,

this in warrior is causing following do_rootfs error:

nothing provides dbus-test needed by dbus-test-ptest-1.12.12-r0

in images with dbus-test and ptest enabled.

you need to backport:
commit db4ef506b6b86e62a5ee1cbea8f12f97615dd0b8
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Tue May 14 17:28:08 2019 +0100

    dbus-test: Improve ptest dependencies dependencies

as well, to resolve this (will send it in separate e-mail).

>     
>     Many different ptests are breaking as they assume that ${PN}-ptest
>     depends on ${PN}. It doesn't currently but should. If we fix this, many
>     different ptests start passing when they previously failed.
>     
>     It does depend on fixing an issue in the dbus-test recipe which is done
>     in the preceeding patch (mentioned in case this gets backported).
>     
>     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>     Signed-off-by: Armin Kuster <akuster808@gmail.com>
> ---
>  meta/classes/ptest.bbclass | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/ptest.bbclass b/meta/classes/ptest.bbclass
> index 936bf82..fa4c36e 100644
> --- a/meta/classes/ptest.bbclass
> +++ b/meta/classes/ptest.bbclass
> @@ -13,6 +13,7 @@ PTEST_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 'ptest', '1', '0', d)}"
>  PTEST_ENABLED_class-native = ""
>  PTEST_ENABLED_class-nativesdk = ""
>  PTEST_ENABLED_class-cross-canadian = ""
> +RDEPENDS_${PN}-ptest += "${PN}"
>  RDEPENDS_${PN}-ptest_class-native = ""
>  RDEPENDS_${PN}-ptest_class-nativesdk = ""
>  RRECOMMENDS_${PN}-ptest += "ptest-runner"
> 
> -- 
> To stop receiving notification emails like this one, please contact
> the administrator of this repository.
> -- 
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

           reply	other threads:[~2019-06-09  7:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190607125811.05DDB235A87@git.openembedded.org>]

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=20190609075600.GA1487@jama \
    --to=martin.jansa@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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