From: Changqing Li <changqing.li@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [kirkstone][master][PATCH] apt: fix do_package_qa failure
Date: Thu, 28 Jul 2022 11:53:40 +0800 [thread overview]
Message-ID: <1dfde637-8448-920a-91cb-7963cda09297@windriver.com> (raw)
In-Reply-To: <CANNYZj--dxtiE6OvQzmUkpzKD3nQ-Zt1C5kbPLUWaBszfvqFLA@mail.gmail.com>
On 7/27/22 19:51, Alexander Kanavin wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> What is actually being installed in there? Is it really right to remove it?
An empty dir apt is installed under /var/log/. It should be ok to remove
it since apt could create it when it doesn't exist.
We have remove it for target. So I do the same for nativesdk. Another
solution could be INSANE_SKIP the empty-dirs.
How do you think?
Changqing
>
> Alex
>
> On Wed, 27 Jul 2022 at 07:39, Changqing Li <changqing.li@windriver.com> wrote:
>> From: Changqing Li <changqing.li@windriver.com>
>>
>> bitbake nativesdk-apt failed with error:
>> ERROR: nativesdk-apt-2.4.5-r0 do_package_qa: QA Issue: nativesdk-apt installs files in /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/var/volatile, but it is expected to be empty [empty-dirs]
>>
>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
>> ---
>> meta/recipes-devtools/apt/apt_2.4.5.bb | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta/recipes-devtools/apt/apt_2.4.5.bb b/meta/recipes-devtools/apt/apt_2.4.5.bb
>> index 1d94dd118c..d79a33857a 100644
>> --- a/meta/recipes-devtools/apt/apt_2.4.5.bb
>> +++ b/meta/recipes-devtools/apt/apt_2.4.5.bb
>> @@ -123,6 +123,7 @@ do_install:append:class-native() {
>>
>> do_install:append:class-nativesdk() {
>> customize_apt_conf_sample
>> + rm -rf ${D}${localstatedir}/log
>> }
>>
>> do_install:append:class-target() {
>> --
>> 2.25.1
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#168542): https://lists.openembedded.org/g/openembedded-core/message/168542
>> Mute This Topic: https://lists.openembedded.org/mt/92643987/1686489
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
next prev parent reply other threads:[~2022-07-28 3:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 5:39 [kirkstone][master][PATCH] apt: fix do_package_qa failure changqing.li
2022-07-27 11:51 ` [OE-core] " Alexander Kanavin
2022-07-28 3:53 ` Changqing Li [this message]
2022-07-28 7:05 ` Alexander Kanavin
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=1dfde637-8448-920a-91cb-7963cda09297@windriver.com \
--to=changqing.li@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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