[OE-core] [PATCH 1/2] bluez5: upgrade to 5.37

[Maxin B. John]

Hi Martin,

On Tue, Jan 05, 2016 at 04:01:24PM +0100, Martin Jansa wrote:
> On Tue, Jan 05, 2016 at 04:08:13PM +0200, Maxin B. John wrote:
> > 5.36 -> 5.37
> > 
> > Remove the backported patch:
> > core-profile-Fix-possible-crash-when-registering-pro.patch
> Don't you need to remove
> file://core-profile-Fix-possible-crash-when-registering-pro.patch
> from SRC_URI when you're removing the file?

Yes, that change is present in the patch (based on "ross/mut" branch)

> Can you please add PNBLACKLIST which will blacklist bluez5 when bluez4
> is in DISTRO_FEATURES?

Sure, will do that.

> Like I did for bluez4 in:
> http://git.openembedded.org/meta-openembedded/commit/?id=73ba7cd70f75a898bf4c3f8ae38c9904fc3e4724
> 
> Making bluez4 and bluez5 really mutually exclusive would help with
> issues like this one:
> http://lists.openembedded.org/pipermail/openembedded-devel/2016-January/105341.html

Thank you very much for the comments. Will include these changes in v2.

> > Signed-off-by: Maxin B. John <maxin.john at intel.com>
> > ---
> >  ...e-Fix-possible-crash-when-registering-pro.patch | 54 ----------------------
> >  .../bluez5/{bluez5_5.36.bb => bluez5_5.37.bb}      |  5 +-
> >  2 files changed, 2 insertions(+), 57 deletions(-)
> >  delete mode 100644 meta/recipes-connectivity/bluez5/bluez5/core-profile-Fix-possible-crash-when-registering-pro.patch
> >  rename meta/recipes-connectivity/bluez5/{bluez5_5.36.bb => bluez5_5.37.bb} (83%)

<snip>

> > -SRC_URI += "file://core-profile-Fix-possible-crash-when-registering-pro.patch"
> > -SRC_URI[md5sum] = "9a0ee479cacc44fac68f6a65b1cd3eba"
> > -SRC_URI[sha256sum] = "a343ea1aeb53d3bd139087f3b1c1e1fb70db452d9762cc7a3d23e75962e578f2"
> > +SRC_URI[md5sum] = "33177e5743e24b2b3738f72be64e3ffb"
> > +SRC_URI[sha256sum] = "c14ba9ddcb0055522073477b8fd8bf1ddf5d219e75fdfd4699b7e0ce5350d6b0"

Best Regards,
Maxin