Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Ross Burton" <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org, nd@arm.com
Subject: Re: [OE-core] [PATCH 1/3] Add python3-hatchling (from meta-oe)
Date: Mon, 20 Jun 2022 14:53:20 +0200	[thread overview]
Message-ID: <20220620145320.4ce9ae2a@booty> (raw)
In-Reply-To: <20220620144832.0c93a7b8@booty>

Hi,

On Mon, 20 Jun 2022 14:48:32 +0200
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:

> Hi Ross,
> 
> On Sun, 19 Jun 2022 22:25:18 +0100
> "Ross Burton" <ross.burton@arm.com> wrote:
> 
> > Recipes in core are now needing to use the Hatch build system, so
> > move the hatchling recipe and class from meta-oe to oe-core.
> > 
> > Signed-off-by: Ross Burton <ross.burton@arm.com>  
> 
> This patch is causing failures on the autobuilders:
> 
> ERROR: Nothing PROVIDES 'python3-pathspec-native' (but .../python3-hatchling_1.3.0.bb DEPENDS on or otherwise requires it). Close matches:

References:
https://autobuilder.yoctoproject.org/typhoon/#/builders/39/builds/5402/steps/18/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/39/builds/5402/steps/16/logs/stdio


-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2022-06-20 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 21:25 [PATCH 1/3] Add python3-hatchling (from meta-oe) Ross Burton
2022-06-19 21:25 ` [PATCH 2/3] python3-hatch-vcs: add new recipe Ross Burton
2022-06-19 21:25 ` [PATCH 3/3] python3-jsonschema: upgrade 4.5.1 -> 4.6.0 Ross Burton
2022-06-20 11:13 ` [OE-core] [PATCH 1/3] Add python3-hatchling (from meta-oe) Ross Burton
2022-06-20 12:48 ` Luca Ceresoli
2022-06-20 12:53   ` Luca Ceresoli [this message]
2022-06-20 13:12     ` Ross Burton

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=20220620145320.4ce9ae2a@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=nd@arm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    /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