All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: tprrt <tprrt@tupi.fr>
Subject: Re: [meta-systemd][PATCH] Rename bluez4_4.101.bbappend to bluez5_5.29.bbappend, to fix build issue below: ERROR: No recipes available for: /home/tprrt/dev/oe-build-easy/combination/meta-systemd/oe-core/recipes-connectivity/bluez/bluez4_4.101.bbappend
Date: Tue, 5 May 2015 17:52:57 +0200	[thread overview]
Message-ID: <20150505155257.GD2378@jama> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB2F4BBCDC@irsmsx105.ger.corp.intel.com>

On Tue, May 05, 2015 at 03:13:53PM +0000, Iorga, Cristian wrote:
> Martin, can I help with the aforementioned build failures?

Most of them aren't related to bluez4.

The only exception is this patch:
http://lists.openembedded.org/pipermail/openembedded-devel/2015-May/101302.html
I had to extend it a bit (navit, libsyncml, obexftp depend on
blacklisted components), but you can help by reviewing it (or even
checking if some of these components can actually use bluez5 (and
${BLUEZ}).

Most of issues are caused by thumb, tracked in:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7717

and linux-yocto failing in various places for various MACHINEs.

Regards,

> Also, NACK for the original patch.
> /Cristian
> 
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Martin Jansa
> Sent: Tuesday, May 5, 2015 3:02 PM
> To: openembedded-devel@lists.openembedded.org
> Cc: tprrt
> Subject: Re: [oe] [meta-systemd][PATCH] Rename bluez4_4.101.bbappend to bluez5_5.29.bbappend, to fix build issue below: ERROR: No recipes available for: /home/tprrt/dev/oe-build-easy/combination/meta-systemd/oe-core/recipes-connectivity/bluez/bluez4_4.101.bbappend
> 
> On Tue, May 05, 2015 at 01:18:29PM +0200, Thomas Perrot wrote:
> > From: tprrt <tprrt@tupi.fr>
> 
> NAK, see pending patches for bluez4 (I plan to merge them as soon as builds stop failing completely).
> 
> > Signed-off-by: tprrt <tprrt@tupi.fr>
> > ---
> >  .../bluez/{bluez4_4.101.bbappend => bluez5_5.29.bbappend}              |    0
> >  1 file changed, 0 insertions(+), 0 deletions(-)  rename 
> > meta-systemd/oe-core/recipes-connectivity/bluez/{bluez4_4.101.bbappend 
> > => bluez5_5.29.bbappend} (100%)
> > 
> > diff --git 
> > a/meta-systemd/oe-core/recipes-connectivity/bluez/bluez4_4.101.bbappen
> > d 
> > b/meta-systemd/oe-core/recipes-connectivity/bluez/bluez5_5.29.bbappend
> > similarity index 100%
> > rename from 
> > meta-systemd/oe-core/recipes-connectivity/bluez/bluez4_4.101.bbappend
> > rename to 
> > meta-systemd/oe-core/recipes-connectivity/bluez/bluez5_5.29.bbappend
> > --
> > 1.7.10.4
> > 
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> 
> -- 
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

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


      reply	other threads:[~2015-05-05 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 11:18 [meta-systemd][PATCH] Rename bluez4_4.101.bbappend to bluez5_5.29.bbappend, to fix build issue below: ERROR: No recipes available for: /home/tprrt/dev/oe-build-easy/combination/meta-systemd/oe-core/recipes-connectivity/bluez/bluez4_4.101.bbappend Thomas Perrot
2015-05-05 12:01 ` Martin Jansa
2015-05-05 15:13   ` Iorga, Cristian
2015-05-05 15:52     ` Martin Jansa [this message]

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=20150505155257.GD2378@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=tprrt@tupi.fr \
    /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.