On 8/23/17 1:12 AM, Stefano Pagnottelli wrote: > Hi to all, > > I'm trying to build this layer: > (https://github.com/bachp/meta-homeassistant) using the yocto pyro on a > raspberry pi 3 target and the opkg package system. > > Inside the recipe > (https://github.com/bachp/meta-homeassistant/blob/master/recipes-homeassistant/homeassistant/python3-homeassistant_0.51.2.bb) > there are some RDEPENDS with strict equal > dependencies (ex:python3-aiohttp (= 2.2.5)). > > We I build the image with the opgk package system the system fail in the > do_rootfs task because is not finding the package python3-aiohttp = > 2.2.5.. If I understood correctly this happens because the build system > si appending the recipe revision (PR variable) at end of package name > and the results is python3-aiohttp_2.2.5-r0 and not > python3-aiohttp_2.2.5 as opkg is expecting.
I dont think r0 is in play here. You can test it by changing dependency check to look for (= for 2.2.5-r0), I think it should still fail. > > As workaround I changed all strict = with a >= and the build complete > without errors. this is ok as long as the package can work with newer versions of this package. I am not sure if thats the case, you might have to check with authors intent for using = instead of >= > > My question is: It's possible to instruct the build system to ignore > the recipe revision when it match the version of the package? Or in > alternative it's possible to automatically detect the recipe revision of > the package? > > Thanks in advance > Stefano > … > -- > > There are 10 types of people in this world, those who understand binary > and those who dont > > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto