From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Trevor Gamblin <tgamblin@baylibre.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Khem Raj <raj.khem@gmail.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>,
openembedded-core@lists.openembedded.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [OE-core][PATCH 06/20] python3-libfdt: new package
Date: Thu, 18 May 2023 17:17:18 +0200 [thread overview]
Message-ID: <20230518151718e4c83ed0@mail.local> (raw)
In-Reply-To: <6c6ca6c1-3052-5a3b-5173-df780d77a64b@baylibre.com>
On 17/05/2023 12:16:21-0400, Trevor Gamblin wrote:
>
> On 2023-05-17 04:06, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> >
> > Add a recipe for python bindings for libfdt (spun out of upstream dtc)
> > fetched from pypi.
> >
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > ---
> > .../python/python3-libfdt_1.7.0.post1.bb | 20 +++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> > create mode 100644 meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb
> >
> > diff --git a/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb b/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb
> > new file mode 100644
> > index 0000000000..1ff3decbb9
> > --- /dev/null
> > +++ b/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb
> > @@ -0,0 +1,20 @@
> > +SUMMARY = "Python bindings for libfdt."
> > +LICENSE = "GPL-2.0-only | BSD-2-Clause"
> > +LIC_FILES_CHKSUM = " \
> > + file://BSD-2-Clause;md5=5d6306d1b08f8df623178dfd81880927 \
> > + file://GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> > +"
> > +
> > +inherit pypi setuptools3
> > +
> > +PYPI_PACKAGE = "pylibfdt"
> > +
> > +SRC_URI[sha256sum] = "2d048f9f8ce9a0527d497f423dea1f1135f9811c05b009cc5d5753771c1f9ba1"
> > +
> > +BBCLASSEXTEND = "native nativesdk"
> > +
> > +DEPENDS += " \
> > + python3-pip-native \
> > + python3-setuptools-scm-native \
> > + swig-native \
> > +"
> Can you also add this recipe to the meta/conf/distro/include/maintainers.inc
> file?
As stated, this fails on the autobuilders:
The following recipes do not have a maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file.
python3-libfdt (/home/pokybuild/yocto-worker/oe-selftest-ubuntu/build/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb)
I also got this:
stdio: WARNING: python3-libfdt-1.7.0.post1-r0 do_fetch: QA Issue: Recipe python3-libfdt in /home/pokybuild/yocto-worker/a-full/build/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb does not contain a HOMEPAGE. Please add an entry. [missing-metadata]
stdio: WARNING: python3-libfdt-1.7.0.post1-r0 do_fetch: QA Issue: Recipe python3-libfdt in /home/pokybuild/yocto-worker/a-full/build/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb does not have an assigned maintainer. Please add an entry into meta/conf/distro/include/maintainers.inc. [missing-metadata]
stdio: WARNING: python3-libfdt-native-1.7.0.post1-r0 do_fetch: QA Issue: Recipe python3-libfdt in /home/pokybuild/yocto-worker/a-full/build/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb does not contain a HOMEPAGE. Please add an entry. [missing-metadata]
stdio: WARNING: nativesdk-python3-libfdt-1.7.0.post1-r0 do_fetch: QA Issue: Recipe python3-libfdt in /home/pokybuild/yocto-worker/a-full/build/meta/recipes-devtools/python/python3-libfdt_1.7.0.post1.bb does not contain a HOMEPAGE. Please add an entry. [missing-metadata]
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-05-18 15:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 8:06 [OE-core][PATCH 00/20] python3: fix run-time dependencies Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 01/20] python3-async: add missing " Bartosz Golaszewski
2023-05-17 16:15 ` Trevor Gamblin
2023-05-17 18:17 ` Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 02/20] python3-attrs: unify RDEPENDS Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 03/20] python3-attrs: don't use PYTHON_PN Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 04/20] python3-attrs: add missing run-time dependencies Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 05/20] python3-certifi: " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 06/20] python3-libfdt: new package Bartosz Golaszewski
2023-05-17 16:16 ` Trevor Gamblin
2023-05-18 15:17 ` Alexandre Belloni [this message]
2023-05-17 16:32 ` Bruce Ashfield
2023-05-18 16:56 ` Ross Burton
2023-05-19 11:37 ` Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 07/20] python3-dtschema: add missing run-time dependencies Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 08/20] python3-hypothesis: fix " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 09/20] python3-tomli: add missing " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 10/20] python3-pathspec: " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 11/20] python3-installer: " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 12/20] python3-sphinx-rtd-theme: " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 13/20] python3-setuptools-rust: fix RDEPENDS and allow target build Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 14/20] python3-pyproject-hooks: add missing run-time dependencies Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 15/20] python3-pycryptodome: don't use PYTHON_PN Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 16/20] python3-pycryptodome: add missing run-time dependencies Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 17/20] python3-pygobject: " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 18/20] python3-manifest: cgitb: new package Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 19/20] python3-manifest: zipapp: " Bartosz Golaszewski
2023-05-17 8:06 ` [OE-core][PATCH 20/20] python3-manifest: turtle: " Bartosz Golaszewski
2023-05-17 8:38 ` [OE-core][PATCH 00/20] python3: fix run-time dependencies Alexander Kanavin
2023-05-19 0:06 ` Tim Orling
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=20230518151718e4c83ed0@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=tgamblin@baylibre.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 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.