Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Ernst Sjöstrand" <ernstp@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/6] python3-fixtures: add recipe
Date: Wed, 3 May 2023 14:33:33 +0200	[thread overview]
Message-ID: <202305031233333684da27@mail.local> (raw)
In-Reply-To: <20230502173422.1439794-2-ernstp@gmail.com>

Hello,

without a maintainers entry, this will fail build testing

On 02/05/2023 19:34:18+0200, Ernst Sj�strand wrote:
> Signed-off-by: Ernst Sj�strand <ernstp@gmail.com>
> ---
>  .../python/python3-fixtures_4.0.1.bb          | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
>  create mode 100644 meta/recipes-devtools/python/python3-fixtures_4.0.1.bb
> 
> diff --git a/meta/recipes-devtools/python/python3-fixtures_4.0.1.bb b/meta/recipes-devtools/python/python3-fixtures_4.0.1.bb
> new file mode 100644
> index 00000000000..f71eec6497e
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python3-fixtures_4.0.1.bb
> @@ -0,0 +1,19 @@
> +SUMMARY = "Python fixtures for testing / resource management"
> +HOMEPAGE = "https://github.com/testing-cabal/fixtures"
> +SECTION = "devel/python"
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=239e2f4698b85aad5ed39bae5d2ef226"
> +
> +inherit pypi setuptools3
> +
> +SRC_URI[sha256sum] = "d2758826400d095b79666cf93a32a84f50ff8cd179831927efb48cd1e3ca7466"
> +
> +DEPENDS += " \
> +    ${PYTHON_PN}-pbr-native \
> +    "
> +
> +RDEPENDS:${PN} += "\
> +    ${PYTHON_PN}-pbr \
> +    "
> +
> +BBCLASSEXTEND = "nativesdk"
> -- 
> 2.39.2
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#180757): https://lists.openembedded.org/g/openembedded-core/message/180757
> Mute This Topic: https://lists.openembedded.org/mt/98644245/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-05-03 12:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 17:34 [PATCH 1/6] python3-hatchling: fix rdepends Ernst Sjöstrand
2023-05-02 17:34 ` [PATCH 2/6] python3-fixtures: add recipe Ernst Sjöstrand
2023-05-03 12:33   ` Alexandre Belloni [this message]
2023-05-04  4:47   ` [OE-core] " Tim Orling
2023-05-04  4:47     ` Tim Orling
2023-05-04  7:34       ` Ernst Sjöstrand
2023-05-02 17:34 ` [PATCH 3/6] python3-testtools: add fixtures to rdepends Ernst Sjöstrand
2023-05-02 17:34 ` [PATCH 4/6] python3-charset-normalizer: add recipe Ernst Sjöstrand
2023-05-04  4:53   ` [OE-core] " Tim Orling
2023-05-02 17:34 ` [PATCH 5/6] python3-requests: fix rdepends Ernst Sjöstrand
2023-05-02 17:34 ` [PATCH 6/6] python3-subunit: " Ernst Sjöstrand
     [not found] ` <175B640FA76D30B2.7535@lists.openembedded.org>
2023-05-03  9:22   ` [OE-core] [PATCH 5/6] python3-requests: " Ernst Sjöstrand

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=202305031233333684da27@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=ernstp@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