Changing a value in a multiconfig does not result in the any new build tasks. Steps to reproduce: 1) clone poky & run 'bitbake core-image-minimal' 2) Create empty multiconfig touch conf/multiconfig/testconfig.conf Add following line to local.conf BBMULTICONFIG = "testconfig" 3) Build with multiconfig 'bitbake multiconfig:testconfig:core-image-minimal' 4) Add following line to testconfig.conf IMAGE_INSTALL_append_pn-core-image-minimal = " screen " 5) Build with multiconfig 'bitbake multiconfig:testconfig:core-image-minimal' Screen package is not built. 6) Move append line from testconfig.conf to local.conf & rebuild. Screen package is built. After step 5, the bitbake environment shows screen in IMAGE_INSTALL, but bitbake-whatchanged shows no changes. 'bitbake multiconfig:testconfig:core-image-minimal -e' <snip> # $IMAGE_INSTALL [6 operations] # _append[pn-core-image-minimal] /projects/upsteam-poky/poky/build/conf/multiconfig/testconfig.conf:2 # " screen " # set /projects/upsteam-poky/poky/meta/conf/documentation.conf:212 # [doc] "Specifies the packages to install into an image. Image recipes set IMAGE_INSTALL to specify the packages to install into an image through image.bbclass." # set /projects/upsteam-poky/poky/meta/recipes-core/images/core-image-minimal.bb:3 # "packagegroup-core-boot ${CORE_IMAGE_EXTRA_INSTALL}" # set? /projects/upsteam-poky/poky/meta/classes/core-image.bbclass:70 # "${CORE_IMAGE_BASE_INSTALL}" # set? /projects/upsteam-poky/poky/meta/classes/image.bbclass:80 # "" # set /projects/upsteam-poky/poky/meta/classes/image.bbclass:81 # [type] "list" # pre-expansion value: # "packagegroup-core-boot ${CORE_IMAGE_EXTRA_INSTALL} screen " IMAGE_INSTALL="packagegroup-core-boot screen " <snip> $ bitbake-whatchanged multiconfig:testconfig:core-image-minimal Figuring out the STAMPS_DIR ... Generating the new stamps ... (need several minutes) === Summary: (0 changed, 0 unchanged) Newly added: 0 PV changed: 0 PR changed: 0 Dependencies changed: 0 Reverting 66fd4c13d97a23338f6cdde6770ffb0e60f0b814 resolves the issue.
Note the reverted change that resolved this is from https://bugzilla.yoctoproject.org/show_bug.cgi?id=13359.
http://lists.openembedded.org/pipermail/bitbake-devel/2019-September/020345.html http://lists.openembedded.org/pipermail/openembedded-core/2019-September/287165.html
I believe its this commit. Bitbake: https://git.openembedded.org/bitbake/commit/?h=1.44&id=c74481aa15226e1bff9d53e4ee4b702ebfa1ad32 Core: https://git.openembedded.org/openembedded-core/commit/meta/lib/oeqa?h=zeus&id=a424ef0a0c49123f4518e8fef993fd10f6fc5f4e
the bitbake changes are already committed to mainline branches.
the selftest part breaks build so not backporting.. The bitbake parts are in.
closing