From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Javier Viguera <javier.viguera@digi.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [backport to Daisy] dbus: fix a hard dependency about dbus-ptest
Date: Tue, 17 Jun 2014 08:52:18 +0100 [thread overview]
Message-ID: <1402991538.562.84.camel@ted> (raw)
In-Reply-To: <CAJTo0LZXUh1giimTFpdQYBpVJ640wCgr6j6vELaa9h3L+_huyw@mail.gmail.com>
On Mon, 2014-06-16 at 17:36 +0100, Burton, Ross wrote:
> On 16 June 2014 16:10, Javier Viguera <javier.viguera@digi.com> wrote:
> > Attached the obvious cherry-pick of the commit from *master* with a basic
> > conflict solved. But I don't think this is acceptable in an already-released
> > stable branch "Daisy" as it involves a recipe rename (dbus-ptest_1.6.18.bb
> > => dbus-test_1.6.18.bb) that probably will break the projects of current
> > users of yocto Daisy.
>
> +PACKAGES += "${@base_contains('DISTRO_FEATURES', 'ptest',
> 'dbus-ptest', '', d)}"
>
> This was changed in master to use PTEST_ENABLED:
>
> PACKAGES += "${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus-ptest', '', d)}"
>
> If you could compare dbus.inc in this patch with master to ensure that
> there's nothing else that should be merged that would be great. Also
> remove the Conflicts line from the message.
For what its worth I've pulled the two patches we need into the daisy
branch for this. I'd appreciate someone confirming it does the right
thing though.
Cheers,
Richard
next prev parent reply other threads:[~2014-06-17 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 3:30 [PATCH V4 0/1] dbus: fix a hard dependency about dbus-ptest Chong Lu
2014-04-08 3:30 ` [PATCH V4 1/1] " Chong Lu
2014-04-14 2:00 ` Chong Lu
2014-06-16 12:04 ` [backport to Daisy] " Javier Viguera
2014-06-16 13:31 ` Burton, Ross
2014-06-16 15:10 ` Javier Viguera
2014-06-16 15:12 ` Burton, Ross
2014-06-16 16:36 ` Burton, Ross
2014-06-17 7:52 ` Richard Purdie [this message]
2014-06-17 9:43 ` Viguera, Javier
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=1402991538.562.84.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=javier.viguera@digi.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.