All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guðni Már Gilbert" <gudnimar@noxmedical.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH] python3-bleak: upgrade 0.21.1 -> 0.22.2
Date: Fri, 28 Jun 2024 10:06:26 -0700	[thread overview]
Message-ID: <19910.1719594386814066905@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1sqpPQAdq7FOratvtZoAGJwL0bo0L=nDHAh4YjSWw6Jg=Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

I will look into this over the weekend (running ptests is a new area for me). I'm curious what images you usually use / recommend?

I've usually just used this one core-image-minimal ( https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-core/images/core-image-minimal.bb ) from openembedded-core and used oe-init-build-env ( https://github.com/openembedded/openembedded-core/blob/master/oe-init-build-env ) for the environment and manually added meta-openembedded/meta-python into bblayers.conf.

I see core-image-ptest ( https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-core/images/core-image-ptest.bb ) exists and looks like a better choice than core-image-minimal ( https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-core/images/core-image-minimal.bb )

Thanks for the feedback by the way, I really appreciate it.

[-- Attachment #2: Type: text/html, Size: 1085 bytes --]

  reply	other threads:[~2024-06-28 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 22:41 [meta-python][PATCH] python3-bleak: upgrade 0.21.1 -> 0.22.2 Guðni Már Gilbert
2024-06-28 13:45 ` [oe] " Tom Geelen
2024-06-28 14:09   ` Tim Orling
2024-06-28 15:47   ` Khem Raj
2024-06-28 17:06     ` Guðni Már Gilbert [this message]
2024-06-28 18:32       ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2024-06-27 22:38 Guðni Már Gilbert

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=19910.1719594386814066905@lists.openembedded.org \
    --to=gudnimar@noxmedical.com \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.