Hi All,
In this case, 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 triggered the QA check.
By default, packagegroup inherit allarch, which means the PACKAGE_ARCH
is "all".
Is it proper that 'all' packages are not supposed to be expanded into the
multilib versions?
There are some other packagegroup recipes have the similar issue.
//Hongxu
On 11/14/2013 05:02 PM, Hongxu Jia wrote:
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:
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.
[YOCTO #5532]
Signed-off-by: Hongxu Jia <[email protected]>
---
meta/recipes-core/packagegroups/packagegroup-core-nfs.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/packagegroups/packagegroup-core-nfs.bb
b/meta/recipes-core/packagegroups/packagegroup-core-nfs.bb
index 531eceb..b57ef63 100644
--- a/meta/recipes-core/packagegroups/packagegroup-core-nfs.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-core-nfs.bb
@@ -7,6 +7,7 @@ LICENSE = "MIT"
PR = "r2"
inherit packagegroup
+PACKAGE_ARCH = "${MACHINE_ARCH}"
PACKAGES = "${PN}-server"
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
