I've found quite a few instances of the 'recipe' field in 'target_package' returning 'null', when there is definitely a recipe generating the package. For example: {\"size\": 0, \"version\": \"\", \"recipe\": null, \"target\": 55, \"name\": \"\\\"busybox-hwclock\\\"\"}}, According to the information collected by build history, the busybox-hwclock package is built by busybox. So the 'recipe' field should not be returning null. When 'recipe' is null, 'version' is empty.
Created attachment 1623 [details] busybox-hwclock has the recipe Hi Belen, I've made some builds, also including busybox-hwclock, but everything seems to be ok. Please see the attachment. I don't know how to reproduce it. Have you seen this recently? If yes, please give some advices how to reproduce it. Thanks,Cristiana
I was able to reproduce in master:d7ccfc7605f1eb61511b1b2b8db4ac689ce6a468 building core-image-minimal with a clean tmp directory. If you visit the target packages page, some of them are missing the recipe (in the attached screenshot missing-recipes-in-target-packages.png we are missing recipes for libz1, libkmod2, libc6, kernel-3.10.17-yocto-standard, kernel-module-uvesafb, libblkid1 and libuuid1.
Created attachment 1629 [details] missing-recipes-in-target-packages.png
The database was changed and the target_package table was removed. I will mark this bug as obsolete.
verified as per above comment.