Bug 5030 - Multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) warning
Summary: Multiple providers are available for runtime libasound-module-bluez (bluez4, ...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: connectivity (show other bugs)
Version: 1.5
Hardware: All Multiple
: Medium normal
Target Milestone: 1.5 M4
Assignee: Cristian Iorga
QA Contact:
URL:
Whiteboard:
: 5029 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-08-20 17:15 UTC by Cristian Iorga
Modified: 2013-08-26 07:31 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cristian Iorga 2013-08-20 17:15:56 UTC 
Have both bluez4 and bluez5 recipes in a world build causes the following WARNING:

NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5)
NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez
Comment 1 Cristian Iorga 2013-08-20 17:17:27 UTC 
A line defining the preferred provide needs to be added in meta/conf/distro/include/default-providers.inc in order to solve this issue.
Comment 2 Cristian Iorga 2013-08-20 17:20:59 UTC 
Issue's log:
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for runtime 
> libasound-module-bluez (bluez4, bluez5)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match 
> libasound-module-bluez
> NOTE: multiple providers are available for runtime 
> lib32-libasound-module-bluez (lib32-bluez5, lib32-bluez4)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match 
> lib32-libasound-module-bluez
> NOTE: Preparing runqueue
Comment 3 Saul Wold 2013-08-20 19:44:48 UTC 
*** Bug 5029 has been marked as a duplicate of this bug. ***
Comment 4 Cristian Iorga 2013-08-21 09:13:55 UTC 
Investigation started.
Comment 5 Cristian Iorga 2013-08-22 07:30:36 UTC 
Fix submitted for review.
Comment 6 Cristian Iorga 2013-08-26 07:31:32 UTC 
Fixed with commit 747f5bee1bc60749c102552a1d7e9e419b62c7b9.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=747f5bee1bc60749c102552a1d7e9e419b62c7b9