From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 1/1] lib32-packagegroup-core-nfs: fix qa issue - install files into a shared area when those files already exist
Date: Thu, 21 Nov 2013 13:50:07 +0000 [thread overview]
Message-ID: <1385041807.16887.131.camel@ted> (raw)
In-Reply-To: <528E0D2D.4010202@windriver.com>
On Thu, 2013-11-21 at 21:39 +0800, Hongxu Jia wrote:
> 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?
Yes.
> There are some other packagegroup recipes have the similar issue.
It sounds like there is some configuration causing this to get rebuild.
Can you run bitbake-diffsigs on the stamps for the two tasks and see why
its building this twice? It sound only happen once.
Cheers,
Richard
next prev parent reply other threads:[~2013-11-21 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 9:02 [PATCH 0/1]lib32-packagegroup-core-nfs: fix qa issue - install files into a shared area when those files already exist Hongxu Jia
2013-11-14 9:02 ` [PATCH 1/1] lib32-packagegroup-core-nfs: " Hongxu Jia
2013-11-21 13:39 ` [RFC PATCH " Hongxu Jia
2013-11-21 13:50 ` Richard Purdie [this message]
2013-11-22 12:21 ` Hongxu Jia
2013-11-22 12:27 ` Richard Purdie
2013-11-23 1:50 ` Hongxu Jia
2013-11-26 11:42 ` Hongxu Jia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1385041807.16887.131.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox