public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Niko Mauno <realint@runbox.com>
To: openembedded-core@lists.openembedded.org,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH] icu: Fix 'buildpaths' QA error
Date: Sun, 1 Sep 2024 20:24:34 +0300	[thread overview]
Message-ID: <c6ee0d69-bc30-404c-9883-47faab5255f5@runbox.com> (raw)
In-Reply-To: <b7b2d9e74f400fb604c2f5976538b1f788dd50f0.camel@linuxfoundation.org>

On 9/1/24 13:55, Richard Purdie wrote:
> On Sat, 2024-08-31 at 16:01 +0300, Niko Mauno via
> lists.openembedded.org wrote:
>> Add stripping of STAGING_DIR_NATIVE during target/nativesdk specific
>> do_install, which mitigates following BitBake failure:
>>
>>    ERROR: icu-75-1-r0 do_package_qa: QA Issue: File
>> /usr/lib/icu/75.1/pkgdata.inc in package icu-dev contains reference
>> to TMPDIR [buildpaths]
>>    ERROR: icu-75-1-r0 do_package_qa: Fatal QA errors were found,
>> failing task.
>>
>> While doing so, we also drop HOSTTOOLS_DIR stripping, as it's value
>> does not appear in the content of either file that are manipulated
>> here.
>>
>> Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
>> ---
>>   meta/recipes-support/icu/icu_75-1.bb | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Why aren't we seeing this issue in automated test?

I should have known better, in a new workspace I was unable to reproduce 
to issue. Apologies for the noise.
-Niko


      reply	other threads:[~2024-09-01 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 13:01 [PATCH] icu: Fix 'buildpaths' QA error Niko Mauno
2024-09-01 10:55 ` [OE-core] " Richard Purdie
2024-09-01 17:24   ` Niko Mauno [this message]

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=c6ee0d69-bc30-404c-9883-47faab5255f5@runbox.com \
    --to=realint@runbox.com \
    --cc=niko.mauno@iki.fi \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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