By default, packagegroup-core-nfs do not depend on a certain architecture, there will be qa warning while multilib enabled. $ bitbake packagegroup-core-nfs $ bitbake lib32-packagegroup-core-nfs ... WARNING: The recipe lib32-packagegroup-core-nfs is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /buildarea1/build/10271641-bbw_sstate_cache_LX23/combo4-qemux86-64-standard-glibc-std/bitbake_build/tmp/deploy/rpm/all/packagegroup-core-nfs-server-1.0-r2.0.all.rpm Matched in manifest-allarch-packagegroup-core-nfs.deploy-rpm Please verify which package should provide the above files. ... set PACKAGE_ARCH with MACHINE_ARCH fixed this issue.
There are two 'packagegroup-core-nfs-server-1.0-r2.0.all.rpm' in tmp/deploy/rpm/all. One is made by 'bitbake packagegroup-core-nfs ', and the other is made by 'bitbake lib32-packagegroup-core-nfs '. The last one overrode the previous.
There isn't such an issue in 1.9 any more, I guess that this is because we have changed the ARCH settings location of package group.