Created attachment 2537 [details] image build info I experiences a problem related to smart package manager that I wanted to discuss with you. I was interested in your feedback, knowledge of this and maybe advices on how should we proceed further. The bug I experienced can be duplicated with the information available in the "patch-info.txt" file attached to this email. I also attached the log of the error for easier read in the "image-build-info.txt" file. After some careful investigation I discovered that the problem is caused by the smart package manager, after the install_complementary function call when it in fact tries to call smart with "install --attempt -y" arguments. It is not able to see the fact that those packages were already installed and tries to do it again. This error behavior might also be related to the problems mentioned here: https://www.mail-archive.com/yocto@yoctoproject.org/msg24279.html and https://bugs.launchpad.net/smart/+bug/1238492 Thanks again for all your help. If any further information would be required I will be more than happy to share it.
Created attachment 2538 [details] patch info
Created attachment 2540 [details] bitbake -e core-image-minimal output
Created attachment 2541 [details] do_rootfs log output
error link: http://pastebin.com/v5aGejyq It is not machine or architecture dependent since it was replicated on both qemuppc and qemux86.
I have now reproduced this with qemuppc. However, in this instance the warnings are not cause for alarm - looking at the log, the rootfs construction code is explicitly asking smart to install the named packages on the command line, and it happens that those packages are already installed - so it's just warning you that it's not going to do anything with those. In case it's not clear, smart gets invoked twice as part of rootfs construction - once to install the main list of packages, and a second time to bring in "complementary" packages e.g. -dev and -dbg packages for every package installed in the first invocation (where available). In this instance some of the -dev/-dbg packages are already in the image after the first invocation because they are dependencies of one of the packages that's going into the image - I believe most of these are coming in through packagegroup-buildessential's dependency on libstdc++-dev (and in turn packagegroup-buildessential is in there because tools-sdk is being added to IMAGE_FEATURES). The other aspect of this is that these warnings almost certainly aren't new - they were exposed in 1.8 when we started checking the do_rootfs log for warnings. I suspect the correct course of action here is to patch smart to make this an informational message rather than a warning, as even when invoking smart manually, asking smart to install a package that's already installed is not really a problem that merits a warning IMO.
I've sent a fix for this (along with a semi-related fix for how the warnings are reported): http://lists.openembedded.org/pipermail/openembedded-core/2015-June/105799.html
Reviewed and tested it. All OK. Bug can be marked as resolved.
Fix was merged to master in: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e5a11759d8d6f15191167ab1f3ffb3db8b6715aa We probably ought to backport this to fido as well.