[oe] [Angstrom-devel] Avahi recipe

[pHilipp Zabel]

Hi,

replacing openembedded-users with openembedded-devel
(http://lists.linuxtogo.org/pipermail/openembedded-users/2009-March/000978.html).

On Wed, Mar 11, 2009 at 5:27 AM, Ben Gamari <bgamari at gmail.com> wrote:
> On 03/10/2009 02:21 PM, Stanislav Brabec wrote:
>>
>> I guess I got the problem:
>>
>> Version 0.6.24 is already decently split and you can install
>> avahi-autoipd without triggering additional dependencies. This is not
>> valid for version 0.6.21 triggered in your build.
>>
>> I guess that it's caused by
>> distro/include/preferred-om-2008-versions.inc.
>>
>> Remove three avahi related lines from it and try again.
>>
>
> Nope, no dice. In fact, things are getting even stranger:
>
>> DEBUG: providers for avahi-daemon are: ['avahi-python', 'avahi']
>> DEBUG: update_data()
>> DEBUG: update_data()
>> NOTE: checking PREFERRED_PROVIDER_avahi-python
>> NOTE: checking PREFERRED_PROVIDER_avahi-python-0.6.21
>> NOTE: checking PREFERRED_PROVIDER_avahi-python-0.6.21-r8
>> NOTE: checking PREFERRED_PROVIDER_avahi
>> NOTE: checking PREFERRED_PROVIDER_avahi
>> NOTE: selecting avahi to satisfy runtime avahi-daemon due to
>> PREFERRED_PROVIDER_avahi = avahi
>> DEBUG: sorted providers for avahi-daemon are:
>> ['/mnt/oe/oe/openembedded/packages/avahi/avahi_0.6.24.bb',
>> '/mnt/oe/oe/openembedded/packages/avahi/avahi-python_0.6.21.bb']
>> DEBUG: adding '/mnt/oe/oe/openembedded/packages/avahi/avahi_0.6.24.bb' to
>> satisfy runtime 'avahi-daemon'
>
>> ...
>>
>> DEBUG: adding
>> '/mnt/oe/oe/openembedded/packages/avahi/avahi-python_0.6.21.bb' to satisfy
>> runtime 'avahi-daemon'
>
>> ...
>>
>> DEBUG: providers for avahi-autoipd are: ['avahi-python', 'avahi']
>> DEBUG: update_data()
>> DEBUG: update_data()
>> NOTE: checking PREFERRED_PROVIDER_avahi-python
>> NOTE: checking PREFERRED_PROVIDER_avahi-python-0.6.21
>> NOTE: checking PREFERRED_PROVIDER_avahi-python-0.6.21-r8
>> NOTE: checking PREFERRED_PROVIDER_avahi
>> NOTE: checking PREFERRED_PROVIDER_avahi
>> NOTE: selecting avahi to satisfy runtime avahi-autoipd due to
>> PREFERRED_PROVIDER_avahi = avahi
>> DEBUG: sorted providers for avahi-autoipd are:
>> ['/mnt/oe/oe/openembedded/packages/avahi/avahi_0.6.24.bb',
>> '/mnt/oe/oe/openembedded/packages/avahi/avahi-python_0.6.21.bb']
>> DEBUG: adding '/mnt/oe/oe/openembedded/packages/avahi/avahi_0.6.24.bb' to
>> satisfy runtime 'avahi-autoipd'
>> DEBUG: adding
>> '/mnt/oe/oe/openembedded/packages/avahi/avahi-python_0.6.21.bb' to satisfy
>> runtime 'avahi-autoipd'
>
> It's apparently still trying to install 0.6.21 for some reason, but this
> time in addition to 0.6.24. Odd. Any ideas?

Those messages do not mean that the recipes will be actually built. If
I'm not mistaken, bitbake is just considering alternatives here.
Especially this ...

>> NOTE: selecting avahi to satisfy runtime avahi-autoipd due to
>> PREFERRED_PROVIDER_avahi = avahi

... part sounds like it's going to do the right thing.

I have the same messages in my -DD log. When I call "DISTRO=angstrom
bitbake task-base" on a clean tmp, it just builds avahi (0.6.24), not
avahi-python (0.6.21) or any of its additional dependencies.

regards
Philipp