[oe] OE weekly changelog 2009-07-13 to 2009-07-20 - Bluetooth still not working

[Ulf Samuelsson]

Cliff Brake skrev:
> OE weekly changelog 2009-07-13 to 2009-07-20
>
> Dmitry Eremin-Solenikov (5):
>   bluez4: make bluez4-dev rprovide bluez-libs-dev to fix SDK building
>
> Graeme Gregory (10):
>   Revert "bluez3: blacklist for angstrom, bluez4 should be used instead"
>   angstrom-2008.1.conf : add bluez3 blacklist
>
> Koen Kooi (31):
>   bluez3: blacklist for angstrom, bluez4 should be used instead
>   bluez4: provide bluez-utils-dbus as well
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   
Seems Bluetooth support still is not healthy.
Building Angstrom gpe-image for sam9263:

++++++++++++++++
ulf at grond:~/projects/OE_atmel/build> bitbake gpe-image
/home/ulf/projects/OE_atmel/bitbake/lib/bb/COW.py:29:
DeprecationWarning: the sets module is deprecated
  import types, sets
NOTE: Handling BitBake files: / (4928/6992) [70 %]NOTE: Angstrom DOES
NOT support bluez-utils because bluez3 has been replace by bluez4
NOTE: Angstrom DOES NOT support bluez-utils because bluez3 has been
replace by bluez4
NOTE: Handling BitBake files: \ (4932/6992) [70 %]NOTE: Angstrom DOES
NOT support bluez-libs because bluez3 has been replace by bluez4
NOTE: Handling BitBake files: | (4940/6992) [70 %]NOTE: Angstrom DOES
NOT support bluez-libs because bluez3 has been replace by bluez4
NOTE: Angstrom DOES NOT support bluez-libs because bluez3 has been
replace by bluez4
NOTE: Handling BitBake files: \ (6992/6992) [100 %]
NOTE: Parsing finished. 0 cached, 6699 parsed, 293 skipped, 0 masked.
NOTE: Resolving any missing task queue dependencies
NOTE: Runtime target 'bluez-utils-dbus' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bluez-utils-dbus',
'bluez-libs-3.36']
ERROR: Required build target 'gpe-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['gpe-image',
'task-gpe-base', 'bluez-utils-dbus', 'bluez-libs-3.36']
-----------------------------

Do we want to disable bluetooth in Angstrom,  until this is fixed,
or is it just gpe-image that has a problem with bluetooth?

Seems is it not that simple to disable Bluetooth.
One would think that removing bluetooth from DISTRO_FEATURES
should be enough, but this is not enough.


-- 
Best Regards
Ulf Samuelsson