[yocto] Added package to RDEPENDS in packagegroup, image that IMAGE_INSTALLs packagegroup not rebuilt

Vuille, Martin (Martin) vmartin at avaya.com
Tue Nov 4 14:02:16 PST 2014


I reported a similar issue a few days ago, but at the time I did not
know how to collect the relevant information to help diagnose the
issue. Hopefully I did better this time.

I have an image that lists several packagegroups in IMAGE_INSTALL.

I updated one of the packagegroups by adding a new package to
the list of RDEPENDS.

I ran bitbake <image> but do_rootfs was not run for the image. I
had built the package earlier so the only task to do should have been
do_rootfs. (When I saw this problem before and had not pre-built
the package, bitbake did build the package but then did not run the
image do_rootfs task).

In Toaster, looking at the tasks for the packagegroup recipe shows
Prebuilt for do_build and Covered for all others.

If I look at the list of packages for that image, the new package is not listed.

If I look at the list of runtime dependencies for the packagegroup in
the image, the new package is not listed.

bitbake <image> -g -u depexp does not show any dependency on the
new package, in fact it does not list the new package at all.

Neither does bitbake <packagegroup> -g -u depexp

I added a second extra (pre-built) package to the packagegroup and
ran bitbake again (with -DDD). The names of the two newly-added
packages are nowhere to be found in the debug output.

It's as though bitbake is not seeing my changes.

Any suggestions for debugging this further?

MV





More information about the yocto mailing list