From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libtelepathy: python-native is used during build
Date: Mon, 07 Jan 2013 13:59:14 +0000 [thread overview]
Message-ID: <1357567154.25855.22.camel@ted> (raw)
In-Reply-To: <1357566682-7595-1-git-send-email-cristian.iorga@intel.com>
On Mon, 2013-01-07 at 15:51 +0200, Cristian Iorga wrote:
> python-native was not used during the build.
> This could lead to problems.
What kind of "problems"? Yes, I could go and look at the bugzilla but
commit messages should be self supporting, at least with a summary.
Cheers,
Richard
> Fixes [YOCTO #3679]
>
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
> meta/recipes-connectivity/telepathy/libtelepathy_0.3.3.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-connectivity/telepathy/libtelepathy_0.3.3.bb b/meta/recipes-connectivity/telepathy/libtelepathy_0.3.3.bb
> index ee131ee..7d0ef79 100644
> --- a/meta/recipes-connectivity/telepathy/libtelepathy_0.3.3.bb
> +++ b/meta/recipes-connectivity/telepathy/libtelepathy_0.3.3.bb
> @@ -17,7 +17,7 @@ SRC_URI = "http://telepathy.freedesktop.org/releases/libtelepathy/libtelepathy-$
> SRC_URI[md5sum] = "490ca1a0c614d4466394b72d43bf7370"
> SRC_URI[sha256sum] = "e0d230be855125163579743418203c6f6be2f10f98c4f065735c1dc9ed115878"
>
> -inherit autotools pkgconfig
> +inherit autotools pkgconfig pythonnative
>
> FILES_${PN} += "${datadir}/telepathy \
> ${datadir}/dbus-1"
next prev parent reply other threads:[~2013-01-07 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 13:51 [PATCH] libtelepathy: python-native is used during build Cristian Iorga
2013-01-07 13:59 ` Richard Purdie [this message]
2013-01-07 14:08 ` Iorga, Cristian
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=1357567154.25855.22.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=cristian.iorga@intel.com \
--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