Bug 5532 - lib32-packagegroup-core-nfs: qa issue - install files into a shared area when those files already exist
Summary: lib32-packagegroup-core-nfs: qa issue - install files into a shared area when...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.9 M3
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-11-14 08:58 UTC by Hongxu Jia
Modified: 2015-06-30 03:19 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hongxu Jia 2013-11-14 08:58:20 UTC
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.
Comment 1 Hongxu Jia 2013-11-21 02:17:30 UTC
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.
Comment 2 Robert Yang 2015-06-30 03:19:19 UTC
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.