openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][mickledore 10/13] populate_sdk_base.bbclass: respect MLPREFIX for ptest-pkgs's ptest-runner
Date: Thu,  1 Jun 2023 16:22:09 -1000	[thread overview]
Message-ID: <3cdfdeb8f18dd467e2c5c6e9d6e3739aaf5c0c3d.1685672395.git.steve@sakoman.com> (raw)
In-Reply-To: <cover.1685672395.git.steve@sakoman.com>

From: Martin Jansa <Martin.Jansa@gmail.com>

* since "populate_sdk_base: ensure ptest-pkgs pulls in ptest-runner" change:
  https://git.openembedded.org/openembedded-core/commit/?id=ecff0642be5781f7f6cca617158b04ac9a0e85f0
  in multilib build when building lib32-foo-image it can pick wrong
  ptest-runner package if it was built in the same TMPDIR before the
  image, do_rootfs then fails to find it, if the package manager config
  doesn't have 64-bit feed enabled:

  opkg_prepare_url_for_install: Couldn't find anything to satisfy 'ptest-runner'

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
(cherry picked from commit 4d24749e7e94881bb952f5c927f0012eb70d4390)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
---
 meta/classes-recipe/populate_sdk_base.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/populate_sdk_base.bbclass b/meta/classes-recipe/populate_sdk_base.bbclass
index 1c619ef3cf..b23ea26d40 100644
--- a/meta/classes-recipe/populate_sdk_base.bbclass
+++ b/meta/classes-recipe/populate_sdk_base.bbclass
@@ -15,7 +15,7 @@ COMPLEMENTARY_GLOB[staticdev-pkgs] = '*-staticdev'
 COMPLEMENTARY_GLOB[doc-pkgs] = '*-doc'
 COMPLEMENTARY_GLOB[dbg-pkgs] = '*-dbg'
 COMPLEMENTARY_GLOB[src-pkgs] = '*-src'
-COMPLEMENTARY_GLOB[ptest-pkgs] = '*-ptest ptest-runner'
+COMPLEMENTARY_GLOB[ptest-pkgs] = '*-ptest ${MLPREFIX}ptest-runner'
 COMPLEMENTARY_GLOB[bash-completion-pkgs] = '*-bash-completion'
 
 def complementary_globs(featurevar, d):
-- 
2.34.1



  parent reply	other threads:[~2023-06-02  2:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  2:21 [OE-core][mickledore 00/13] Patch review Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 01/13] linux-yocto/5.15: update to v5.15.109 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 02/13] linux-yocto/5.15: update to v5.15.110 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 03/13] linux-yocto/5.15: update to v5.15.111 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 04/13] linux-yocto/5.15: update to v5.15.112 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 05/13] linux-yocto/5.15: update to v5.15.113 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 06/13] git: ignore CVE-2023-25815 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 07/13] libgcrypt: update 1.10.1 -> 1.10.2 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 08/13] e2fsprogs: fix ptest bug for second running Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 09/13] tiff: Remove unused patch from tiff Steve Sakoman
2023-06-02  2:22 ` Steve Sakoman [this message]
2023-06-02  2:22 ` [OE-core][mickledore 11/13] qemurunner: avoid leaking server_socket Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 12/13] uninative: Upgrade to 3.10 to support gcc 13 Steve Sakoman
2023-06-02  2:22 ` [OE-core][mickledore 13/13] uninative: Upgrade to 4.0 to include latest gcc 13.1.1 Steve Sakoman
2023-06-04 17:39   ` Martin Jansa
2023-06-04 19:14     ` Steve Sakoman
2023-06-04 20:34       ` Martin Jansa
2023-06-08 18:50         ` Steve Sakoman
2023-06-08 19:01           ` Martin Jansa
2023-06-15 15:06         ` mkfs.ext4 segfaults with uninative-4.0 Was: " Martin Jansa
     [not found]         ` <1768DD7D92A3BE8A.10197@lists.openembedded.org>
2023-06-15 15:17           ` Martin Jansa

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=3cdfdeb8f18dd467e2c5c6e9d6e3739aaf5c0c3d.1685672395.git.steve@sakoman.com \
    --to=steve@sakoman.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;
as well as URLs for NNTP newsgroup(s).