[OE-core] [PATCH] python3-markupsafe: upgrade 2.0.1 -> 2.1.0

[wangmy]

Changelog:
==
Drop support for Python 3.6. :pr:'262'
Remove soft_unicode, which was previously deprecated. Use soft_str instead. 
:pr:'261'
Raise error on missing single placeholder during string interpolation. 
:issue:'225'
Disable speedups module for GraalPython. :issue:'277'

Signed-off-by: Wang Mingyu 
---
 ...{python3-markupsafe_2.0.1.bb => python3-markupsafe_2.1.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-markupsafe_2.0.1.bb => 
python3-markupsafe_2.1.0.bb} (87%)

diff --git a/meta/recipes-devtools/python/python3-markupsafe_2.0.1.bb 
b/meta/recipes-devtools/python/python3-markupsafe_2.1.0.bb
similarity index 87%
rename from meta/recipes-devtools/python/python3-markupsafe_2.0.1.bb
rename to meta/recipes-devtools/python/python3-markupsafe_2.1.0.bb
index 857472cc7b..953ea01cfe 100644
--- a/meta/recipes-devtools/python/python3-markupsafe_2.0.1.bb
+++ b/meta/recipes-devtools/python/python3-markupsafe_2.1.0.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://github.com/mitsuhiko/markupsafe;
 LICENSE = "BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=ffeffa59c90c9c4a033c7574f8f3fb75"
 
-SRC_URI[sha256sum] = 
"594c67807fb16238b30c44bdf74f36c02cdf22d1c8cda91ef8a0ed8dabf5620a"
+SRC_URI[sha256sum] = 
"80beaf63ddfbc64a0452b841d8036ca0611e049650e20afcb882f5d3c266d65f"
 
 PYPI_PACKAGE = "MarkupSafe"
 inherit pypi setuptools3
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162245): 
https://lists.openembedded.org/g/openembedded-core/message/162245
Mute This Topic: https://lists.openembedded.org/mt/89336496/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] python3-hypothesis: upgrade 6.36.2 -> 6.37.2

[wangmy]

This patch fixes a bug in stateful testing, where returning a single value
wrapped in :func:'~hypothesis.stateful.multiple' would be printed such that
the assigned variable was a tuple rather than the single element

Signed-off-by: Wang Mingyu 
---
 ...ython3-hypothesis_6.36.2.bb => python3-hypothesis_6.37.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-hypothesis_6.36.2.bb => 
python3-hypothesis_6.37.2.bb} (91%)

diff --git a/meta/recipes-devtools/python/python3-hypothesis_6.36.2.bb 
b/meta/recipes-devtools/python/python3-hypothesis_6.37.2.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-hypothesis_6.36.2.bb
rename to meta/recipes-devtools/python/python3-hypothesis_6.37.2.bb
index 8642fb55b9..4deed1e56f 100644
--- a/meta/recipes-devtools/python/python3-hypothesis_6.36.2.bb
+++ b/meta/recipes-devtools/python/python3-hypothesis_6.37.2.bb
@@ -13,7 +13,7 @@ SRC_URI += " \
 file://test_rle.py \
 "
 
-SRC_URI[sha256sum] = 
"7202ea05759f591adf6c1887edbd4d53c049821284f630c5ec8ec3f3f57fd46b"
+SRC_URI[sha256sum] = 
"79321035b9174ffa506d724ca5e8af375d7bf532c80e4f602bd433792c527e6c"
 
 RDEPENDS:${PN} += " \
 python3-attrs \
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162243): 
https://lists.openembedded.org/g/openembedded-core/message/162243
Mute This Topic: https://lists.openembedded.org/mt/89336494/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] python3-git: upgrade 3.1.26 -> 3.1.27

[wangmy]

Changelog:
=
-Reduced startup time due to optimized imports.
-Fix a vulenerability that could cause great slowdowns when encountering long
 remote path names when pulling/fetching.

Signed-off-by: Wang Mingyu 
---
 .../python/{python3-git_3.1.26.bb => python3-git_3.1.27.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-git_3.1.26.bb => 
python3-git_3.1.27.bb} (92%)

diff --git a/meta/recipes-devtools/python/python3-git_3.1.26.bb 
b/meta/recipes-devtools/python/python3-git_3.1.27.bb
similarity index 92%
rename from meta/recipes-devtools/python/python3-git_3.1.26.bb
rename to meta/recipes-devtools/python/python3-git_3.1.27.bb
index b6171a0e4d..a09726d54a 100644
--- a/meta/recipes-devtools/python/python3-git_3.1.26.bb
+++ b/meta/recipes-devtools/python/python3-git_3.1.27.bb
@@ -12,7 +12,7 @@ PYPI_PACKAGE = "GitPython"
 
 inherit pypi setuptools3
 
-SRC_URI[sha256sum] = 
"fc8868f63a2e6d268fb25f481995ba185a85a66fcad126f039323ff6635669ee"
+SRC_URI[sha256sum] = 
"1c885ce809e8ba2d88a29befeb385fcea06338d3640712b59ca623c220bb5704"
 
 DEPENDS += " ${PYTHON_PN}-gitdb"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162244): 
https://lists.openembedded.org/g/openembedded-core/message/162244
Mute This Topic: https://lists.openembedded.org/mt/89336495/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [dunfell][PATCH] puzzles: Upstream changed to main branch for development

[Kartikey Rameshbhai Parmar]

From: Kartikey Rameshbhai Parmar 

Signed-off-by: Kartikey Rameshbhai Parmar 
---
 meta/recipes-sato/puzzles/puzzles_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-sato/puzzles/puzzles_git.bb 
b/meta/recipes-sato/puzzles/puzzles_git.bb
index 2edc9ada2e..3ee441998d 100644
--- a/meta/recipes-sato/puzzles/puzzles_git.bb
+++ b/meta/recipes-sato/puzzles/puzzles_git.bb
@@ -9,7 +9,7 @@ DEPENDS = "libxt"
 # The libxt requires x11 in DISTRO_FEATURES
 REQUIRED_DISTRO_FEATURES = "x11"
 
-SRC_URI = "git://git.tartarus.org/simon/puzzles.git;branch=master \
+SRC_URI = "git://git.tartarus.org/simon/puzzles.git;branch=main \
file://fix-compiling-failure-with-option-g-O.patch \
file://0001-palisade-Fix-warnings-with-clang-on-arm.patch \

file://0001-Use-Wno-error-format-overflow-if-the-compiler-suppor.patch \
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162242): 
https://lists.openembedded.org/g/openembedded-core/message/162242
Mute This Topic: https://lists.openembedded.org/mt/89335889/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH][dunfell] ruby: 2.7.4 -> 2.7.5

[Lee Chee Yang]

From: Chee Yang Lee 

This release includes security fixes.
CVE-2021-41817: Regular Expression Denial of Service Vulnerability of Date 
Parsing Methods
CVE-2021-41816: Buffer Overrun in CGI.escape_html
CVE-2021-41819: Cookie Prefix Spoofing in CGI::Cookie.parse

Signed-off-by: Chee Yang Lee 
---
 meta/recipes-devtools/ruby/{ruby_2.7.4.bb => ruby_2.7.5.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/ruby/{ruby_2.7.4.bb => ruby_2.7.5.bb} (95%)

diff --git a/meta/recipes-devtools/ruby/ruby_2.7.4.bb 
b/meta/recipes-devtools/ruby/ruby_2.7.5.bb
similarity index 95%
rename from meta/recipes-devtools/ruby/ruby_2.7.4.bb
rename to meta/recipes-devtools/ruby/ruby_2.7.5.bb
index dafa7d2f6b..44a2527ee7 100644
--- a/meta/recipes-devtools/ruby/ruby_2.7.4.bb
+++ b/meta/recipes-devtools/ruby/ruby_2.7.5.bb
@@ -9,8 +9,8 @@ SRC_URI += " \

file://0001-template-Makefile.in-do-not-write-host-cross-cc-item.patch \
"
 
-SRC_URI[md5sum] = "823cd21d93c69e4168b03dd127369343"
-SRC_URI[sha256sum] = 
"3043099089608859fc8cce7f9fdccaa1f53a462457e3838ec3b25a7d609fbc5b"
+SRC_URI[md5sum] = "ede247b56fb862f1f67f9471189b04d4"
+SRC_URI[sha256sum] = 
"2755b900a21235b443bb16dadd9032f784d4a88f143d852bc5d154f22b8781f1"
 
 PACKAGECONFIG ??= ""
 PACKAGECONFIG += "${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)}"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162241): 
https://lists.openembedded.org/g/openembedded-core/message/162241
Mute This Topic: https://lists.openembedded.org/mt/89335854/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [hardknott][PATCH] expat: fix CVE-2022-23990

[kai]

From: Kai Kang 

CVE: CVE-2022-23990

Based on Steve Sakoman's patch for branch dunfell, fix CVE-2022-23990
for expat in branch hardknott.

And correct indent as well.

Signed-off-by: Kai Kang 
---
 .../expat/expat/CVE-2022-23990.patch  | 49 +++
 meta/recipes-core/expat/expat_2.2.10.bb   |  7 +--
 2 files changed, 53 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-core/expat/expat/CVE-2022-23990.patch

diff --git a/meta/recipes-core/expat/expat/CVE-2022-23990.patch 
b/meta/recipes-core/expat/expat/CVE-2022-23990.patch
new file mode 100644
index 00..c599517b3e
--- /dev/null
+++ b/meta/recipes-core/expat/expat/CVE-2022-23990.patch
@@ -0,0 +1,49 @@
+From ede41d1e186ed2aba88a06e84cac839b770af3a1 Mon Sep 17 00:00:00 2001
+From: Sebastian Pipping 
+Date: Wed, 26 Jan 2022 02:36:43 +0100
+Subject: [PATCH] lib: Prevent integer overflow in doProlog (CVE-2022-23990)
+
+The change from "int nameLen" to "size_t nameLen"
+addresses the overflow on "nameLen++" in code
+"for (; name[nameLen++];)" right above the second
+change in the patch.
+
+Upstream-Status: Backport:
+https://github.com/libexpat/libexpat/pull/551/commits/ede41d1e186ed2aba88a06e84cac839b770af3a1
+
+CVE: CVE-2022-23990
+
+Signed-off-by: Steve Sakoman 
+
+---
+ lib/xmlparse.c | 10 --
+ 1 file changed, 8 insertions(+), 2 deletions(-)
+
+diff --git a/lib/xmlparse.c b/expat/lib/xmlparse.c
+index 5ce31402..d1d17005 100644
+--- a/lib/xmlparse.c
 b/lib/xmlparse.c
+@@ -5372,7 +5372,7 @@ doProlog(XML_Parser parser, const ENCODING *enc, const 
char *s, const char *end,
+   if (dtd->in_eldecl) {
+ ELEMENT_TYPE *el;
+ const XML_Char *name;
+-int nameLen;
++size_t nameLen;
+ const char *nxt
+ = (quant == XML_CQUANT_NONE ? next : next - enc->minBytesPerChar);
+ int myindex = nextScaffoldPart(parser);
+@@ -5388,7 +5388,13 @@ doProlog(XML_Parser parser, const ENCODING *enc, const 
char *s, const char *end,
+ nameLen = 0;
+ for (; name[nameLen++];)
+   ;
+-dtd->contentStringLen += nameLen;
++
++/* Detect and prevent integer overflow */
++if (nameLen > UINT_MAX - dtd->contentStringLen) {
++  return XML_ERROR_NO_MEMORY;
++}
++
++dtd->contentStringLen += (unsigned)nameLen;
+ if (parser->m_elementDeclHandler)
+   handleDefault = XML_FALSE;
+   }
diff --git a/meta/recipes-core/expat/expat_2.2.10.bb 
b/meta/recipes-core/expat/expat_2.2.10.bb
index 074441dc2a..a851e54b2a 100644
--- a/meta/recipes-core/expat/expat_2.2.10.bb
+++ b/meta/recipes-core/expat/expat_2.2.10.bb
@@ -10,13 +10,14 @@ VERSION_TAG = "${@d.getVar('PV').replace('.', '_')}"
 
 SRC_URI = 
"https://github.com/libexpat/libexpat/releases/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2
  \
file://libtool-tag.patch \
-  file://run-ptest \
-  file://0001-Add-output-of-tests-result.patch \
+   file://run-ptest \
+   file://0001-Add-output-of-tests-result.patch \
file://CVE-2022-22822-27.patch \
file://CVE-2021-45960.patch \
file://CVE-2021-46143.patch \
file://CVE-2022-23852.patch \
- "
+   file://CVE-2022-23990.patch \
+   "
 
 UPSTREAM_CHECK_URI = "https://github.com/libexpat/libexpat/releases/;
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162240): 
https://lists.openembedded.org/g/openembedded-core/message/162240
Mute This Topic: https://lists.openembedded.org/mt/89333888/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 3/3] systemd: Minimize udev package size if DISTRO_FEATURES contains systemd

[Yu, Mingli]

On 2/22/22 9:26 PM, Stefan Herbrechtsmeier wrote:

[Please note: This e-mail is from an EXTERNAL e-mail address]

Hi,

Am 22.02.2022 um 10:20 schrieb Yu, Mingli:

Hi,

On 2/2/22 3:35 PM, Stefan Herbrechtsmeier wrote:

[Please note: This e-mail is from an EXTERNAL e-mail address]

From: Stefan Herbrechtsmeier 

Link udev shared with systemd helper to minimize the udev package size
if DISTRO_FEATURES contains systemd.

It is only usefull to link udev static with systemd helper if udev
should be installed without systemd.

Signed-off-by: Stefan Herbrechtsmeier


---

(no changes since v1)

  meta/recipes-core/systemd/systemd_249.7.bb | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/systemd/systemd_249.7.bb
b/meta/recipes-core/systemd/systemd_249.7.bb
index 739f3aae86..431781e6c7 100644
--- a/meta/recipes-core/systemd/systemd_249.7.bb
+++ b/meta/recipes-core/systemd/systemd_249.7.bb
@@ -66,6 +66,7 @@ PACKAGECONFIG ??= " \
  ${@bb.utils.filter('DISTRO_FEATURES', 'acl audit efi ldconfig
pam selinux smack usrmerge polkit seccomp', d)} \
  ${@bb.utils.contains('DISTRO_FEATURES', 'wifi', 'rfkill', '', 
d)} \

  ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'xkbcommon', '',
d)} \
+    ${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'link-udev-shared', '', d)} \


After this change, the iso image failed to boot with below error:
Cannot find rootfs.img file in /run/media/*, dropping to a shell

And more detailed about the error as the attached.

Steps to reproduce:
1, update conf/local.conf to use systemd as the default init manager
DISTRO_FEATURES:append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
KERNEL_FEATURES:append = " cfg/systemd.scc"

You have to set the INIT_MANAGER variable instead or set the
VIRTUAL-RUNTIME_dev_manager variable to systemd.


2, bitbake core-image-minimal

3, runqemu qemux86-64  core-image-minimal  iso


A revert of the commit solve your problem?


Yes, the issue is gone after revert the commit.

Thanks,



Regards
   Stefan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162239): 
https://lists.openembedded.org/g/openembedded-core/message/162239
Mute This Topic: https://lists.openembedded.org/mt/88853822/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Richard Purdie]

On Wed, 2022-02-23 at 10:57 +1030, Andrew Jeffery wrote:
> 
> On Wed, 23 Feb 2022, at 10:33, Richard Purdie wrote:
> > On Wed, 2022-02-23 at 10:19 +1030, Andrew Jeffery wrote:
> > > 
> > > On Tue, 22 Feb 2022, at 22:58, Richard Purdie wrote:
> > > > On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
> > > > > I have to note that YP does not support ppc systems as build hosts;
> > > > > can this be kept in a bbappend?
> > > > 
> > > > It isn't official but there are obviously people using it. I think we 
> > > > should try
> > > > and do something in core but there is a question of how we maintain 
> > > > this given
> > > > our infrastructure/tests don't cover it :(
> > > 
> > > That's fair. Is it acceptable that it's tested by proxy in OpenBMC if 
> > > we can't work out anything else for YP CI? I don't expect anyone 
> > > maintaining the rust support to test ppc64le explicitly if they don't 
> > > have access. I'd be happy if the ppc64le checksums were just updated 
> > > along with the rest whenever the snapshots are bumped.
> > 
> > The challenge is we have no tooling or support for "bumping" those values. 
> 
> Yeah, that's familiar, when I sent the initial patch fixing the URLs I 
> hacked some stuff to force the BUILD_ARCH value to ppc64le on my x86-64 
> laptop. That's not a scalable approach.

Funnily enough, tweaking BUILD_ARCH was something I was wondering about in some
of our automated tests since that might reduce the changes of some things
breaking.

> Not having the tooling seems reasonable, as having it does kinda 
> suggest you'll try to maintain things you can't test. Even though I'm 
> trying to argue for that, again, it's not scalable and I understand the 
> push-back :)

That is the big worry as we can't really test it.

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162238): 
https://lists.openembedded.org/g/openembedded-core/message/162238
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 1/8] rust: Migrate arch_to_rust_target_arch() to rust-common class

[Andrew Jeffery]

On Tue, 22 Feb 2022, at 20:35, Richard Purdie wrote:
> On Tue, 2022-02-22 at 14:22 +1030, Andrew Jeffery wrote:
>> This will allow us to use it elsewhere for architecture name
>> translation. This move is motivated by powerpc64le support.
>> 
>> Signed-off-by: Andrew Jeffery 
>> ---
>>  meta/classes/rust-common.bbclass   | 16 
>>  meta/recipes-devtools/rust/rust-common.inc | 16 
>>  2 files changed, 16 insertions(+), 16 deletions(-)
>> 
>> diff --git a/meta/classes/rust-common.bbclass 
>> b/meta/classes/rust-common.bbclass
>> index 98d65970e8c0..2f2a31867ad0 100644
>> --- a/meta/classes/rust-common.bbclass
>> +++ b/meta/classes/rust-common.bbclass
>> @@ -1,5 +1,21 @@
>>  inherit python3native
>>  
>> +# Convert a normal arch (HOST_ARCH, TARGET_ARCH, BUILD_ARCH, etc) to 
>> something
>> +# rust's internals won't choke on.
>> +def arch_to_rust_target_arch(arch):
>> +if arch == "i586" or arch == "i686":
>> +return "x86"
>> +elif arch == "mipsel":
>> +return "mips"
>> +elif arch == "mip64sel":
>> +return "mips64"
>> +elif arch == "armv7":
>> +return "arm"
>> +elif arch == "powerpc64le":
>> +return "powerpc64"
>> +else:
>> +return arch
>> +
>>  # Common variables used by all Rust builds
>>  export rustlibdir = "${libdir}/rust"
>>  FILES:${PN} += "${rustlibdir}/*.so"
>
>
> If we're moving this, it may be a good candidate to move to a new
> meta/lib/oe/rust.py python function library for rust. I appreciate that is
> slightly move involved and will likely need the imports in base.bbclass to be
> tweaked but is probably the better long term fix.

I'll take a look.

Andrew

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162237): 
https://lists.openembedded.org/g/openembedded-core/message/162237
Mute This Topic: https://lists.openembedded.org/mt/89310355/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 6/8] rust: Mitigate duplicate sections on matching architectures

[Andrew Jeffery]

On Tue, 22 Feb 2022, at 20:27, Alexander Kanavin wrote:
> This needs a better explanation. 

Ack.

>What is the problem and how is it being fixed?

The immediate error was the build bailed out complaining of duplicate 
sections in the config. Possibly this is an indication of a broken build 
configuration rather than the code needing fixes, but this is how I 
made the problem go away. As mentioned I kind of just slashed my way 
though everything. It deserves some closer analysis like you stated 
above.

Let me take some time to get a better grip on what's happening here.

Andrew

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162236): 
https://lists.openembedded.org/g/openembedded-core/message/162236
Mute This Topic: https://lists.openembedded.org/mt/89310362/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Andrew Jeffery]

On Wed, 23 Feb 2022, at 10:33, Richard Purdie wrote:
> On Wed, 2022-02-23 at 10:19 +1030, Andrew Jeffery wrote:
>> 
>> On Tue, 22 Feb 2022, at 22:58, Richard Purdie wrote:
>> > On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
>> > > I have to note that YP does not support ppc systems as build hosts;
>> > > can this be kept in a bbappend?
>> > 
>> > It isn't official but there are obviously people using it. I think we 
>> > should try
>> > and do something in core but there is a question of how we maintain this 
>> > given
>> > our infrastructure/tests don't cover it :(
>> 
>> That's fair. Is it acceptable that it's tested by proxy in OpenBMC if 
>> we can't work out anything else for YP CI? I don't expect anyone 
>> maintaining the rust support to test ppc64le explicitly if they don't 
>> have access. I'd be happy if the ppc64le checksums were just updated 
>> along with the rest whenever the snapshots are bumped.
>
> The challenge is we have no tooling or support for "bumping" those values. 

Yeah, that's familiar, when I sent the initial patch fixing the URLs I 
hacked some stuff to force the BUILD_ARCH value to ppc64le on my x86-64 
laptop. That's not a scalable approach.

Not having the tooling seems reasonable, as having it does kinda 
suggest you'll try to maintain things you can't test. Even though I'm 
trying to argue for that, again, it's not scalable and I understand the 
push-back :)

> We
> spot issues with the other two build architectures since the autobuilder tests
> them.
>
> There are probably some tricks we could play to handle this. The challenge is
> then that someone needs to take the time to write something to handle this and
> communicate it to the maintainers so they know to use it. We're struggling to 
> do
> all the things like this we'd like to and that leads back to Alex's concern.

I understand.

I have pointed Alex at some resources to access ppc64le systems:

https://lore.kernel.org/openembedded-core/ee6810ac-3c22-45b0-ac49-e35b38e0f...@www.fastmail.com/

But if that's too much fuss then we can maintain the checksums in a 
bbappend in OpenBMC like has been suggested.

Andrew

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162235): 
https://lists.openembedded.org/g/openembedded-core/message/162235
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Andrew Jeffery]

On Wed, 23 Feb 2022, at 00:53, Alexander Kanavin wrote:
> On Tue, 22 Feb 2022 at 13:28, Richard Purdie
>  wrote:
>>
>> On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
>> > I have to note that YP does not support ppc systems as build hosts;
>> > can this be kept in a bbappend?
>>
>> It isn't official but there are obviously people using it. I think we should 
>> try
>> and do something in core but there is a question of how we maintain this 
>> given
>> our infrastructure/tests don't cover it :(
>
> Worse yet, there is no way to test this locally either.  If the ppc64
> binary tarball checksums are added to the core rust recipe, presumably
> I'd be expected to update them together with x86 and arm64 binary
> checksums on version updates, but I'd have to do this completely
> blindly with no testing of any kind :( That's why I am asking to keep
> them in an external bbappend.
>
> Andrew, how hard is it to obtain a shell on ppc64 machines nowadays?

(I work for IBM Power Systems)

IBM have partnered with Oregon State University to provide access to 
ppc64le machines:

* https://osuosl.org/services/powerdev/
* https://power-developer.mybluemix.net/#hardware

You can request access to the OSU setup:

* For a shell: https://osuosl.org/services/powerdev/request_hosting/
* For CI: https://osuosl.org/services/powerdev/request_powerci/

So there are some forms. I'm not sure where the bar sits for you with 
respect to how hard it is to go this route, but feel free to reply to 
me privately or via andre...@au1.ibm.com if you have further questions 
about setting something up on the OSU OSL infrastructure.

Andrew

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162234): 
https://lists.openembedded.org/g/openembedded-core/message/162234
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Richard Purdie]

On Wed, 2022-02-23 at 10:19 +1030, Andrew Jeffery wrote:
> 
> On Tue, 22 Feb 2022, at 22:58, Richard Purdie wrote:
> > On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
> > > I have to note that YP does not support ppc systems as build hosts;
> > > can this be kept in a bbappend?
> > 
> > It isn't official but there are obviously people using it. I think we 
> > should try
> > and do something in core but there is a question of how we maintain this 
> > given
> > our infrastructure/tests don't cover it :(
> 
> That's fair. Is it acceptable that it's tested by proxy in OpenBMC if 
> we can't work out anything else for YP CI? I don't expect anyone 
> maintaining the rust support to test ppc64le explicitly if they don't 
> have access. I'd be happy if the ppc64le checksums were just updated 
> along with the rest whenever the snapshots are bumped.

The challenge is we have no tooling or support for "bumping" those values. We
spot issues with the other two build architectures since the autobuilder tests
them.

There are probably some tricks we could play to handle this. The challenge is
then that someone needs to take the time to write something to handle this and
communicate it to the maintainers so they know to use it. We're struggling to do
all the things like this we'd like to and that leads back to Alex's concern.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162233): 
https://lists.openembedded.org/g/openembedded-core/message/162233
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Andrew Jeffery]

On Tue, 22 Feb 2022, at 22:58, Richard Purdie wrote:
> On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
>> I have to note that YP does not support ppc systems as build hosts;
>> can this be kept in a bbappend?
>
> It isn't official but there are obviously people using it. I think we should 
> try
> and do something in core but there is a question of how we maintain this given
> our infrastructure/tests don't cover it :(

That's fair. Is it acceptable that it's tested by proxy in OpenBMC if 
we can't work out anything else for YP CI? I don't expect anyone 
maintaining the rust support to test ppc64le explicitly if they don't 
have access. I'd be happy if the ppc64le checksums were just updated 
along with the rest whenever the snapshots are bumped.

Andrew

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162232): 
https://lists.openembedded.org/g/openembedded-core/message/162232
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] sudo: add /etc/sudoers to sudo-lib conffiles

[Alex Stewart]

When OE-core commit 788c95c3bb8ede0d3d6a8f125743ac47c0b3f00e created the
`sudo-lib` subpackage, /etc/sudoers was moved from `sudo` to `sudo-lib`.
The commit didn't update the `CONFFILES:${PN}` assignment in sudo.inc,
however. So the `sudo` base package continued to advertise conffile
ownership of /etc/sudoers, though it did not contain it.

Move the CONFFILES assignment to the sudo.bb file, since it is
packaging-related. Change the package owner to the `sudo-lib`
subpackage, since it is the rightful file-owner.

Signed-off-by: Alex Stewart 
---
 meta/recipes-extended/sudo/sudo.inc  | 2 --
 meta/recipes-extended/sudo/sudo_1.9.9.bb | 2 ++
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/sudo/sudo.inc 
b/meta/recipes-extended/sudo/sudo.inc
index 
05d030c2e9f176d63f3f5c5d44321db9729b7983..8947c46129f53e819f62ca6a27fba238babce88f
 100644
--- a/meta/recipes-extended/sudo/sudo.inc
+++ b/meta/recipes-extended/sudo/sudo.inc
@@ -24,8 +24,6 @@ PACKAGECONFIG ??= ""
 PACKAGECONFIG[zlib] = "--enable-zlib,--disable-zlib,zlib"
 PACKAGECONFIG[pam-wheel] = ",,,pam-plugin-wheel"
 
-CONFFILES:${PN} = "${sysconfdir}/sudoers"
-
 EXTRA_OECONF = "--with-editor=${base_bindir}/vi --with-env-editor"
 
 EXTRA_OECONF:append:libc-musl = " --disable-hardening "
diff --git a/meta/recipes-extended/sudo/sudo_1.9.9.bb 
b/meta/recipes-extended/sudo/sudo_1.9.9.bb
index 
f1c0339bb3be7fd48798ceb65a0dbcb0f2da63ea..d7d71bb3643ed94f5e4a5d2a2d9f4d2ff68a8f70
 100644
--- a/meta/recipes-extended/sudo/sudo_1.9.9.bb
+++ b/meta/recipes-extended/sudo/sudo_1.9.9.bb
@@ -48,6 +48,8 @@ do_install:append () {
 FILES:${PN}-dev += "${libdir}/${BPN}/lib*${SOLIBSDEV} ${libdir}/${BPN}/*.la \
 ${libdir}/lib*${SOLIBSDEV} ${libdir}/*.la"
 
+CONFFILES:${PN}-lib = "${sysconfdir}/sudoers"
+
 SUDO_PACKAGES = "${PN}-sudo\
  ${PN}-lib"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162231): 
https://lists.openembedded.org/g/openembedded-core/message/162231
Mute This Topic: https://lists.openembedded.org/mt/89330256/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Andrew Jeffery]

On Wed, 23 Feb 2022, at 05:04, Khem Raj wrote:
> On Tue, Feb 22, 2022 at 6:24 AM Alexander Kanavin
>  wrote:
>>
>> On Tue, 22 Feb 2022 at 13:28, Richard Purdie
>>  wrote:
>> >
>> > On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
>> > > I have to note that YP does not support ppc systems as build hosts;
>> > > can this be kept in a bbappend?
>> >
>> > It isn't official but there are obviously people using it. I think we 
>> > should try
>> > and do something in core but there is a question of how we maintain this 
>> > given
>> > our infrastructure/tests don't cover it :(
>>
>> Worse yet, there is no way to test this locally either.  If the ppc64
>> binary tarball checksums are added to the core rust recipe, presumably
>> I'd be expected to update them together with x86 and arm64 binary
>> checksums on version updates, but I'd have to do this completely
>> blindly with no testing of any kind :(
>
> as long as it does not impede main testing I would think thats ok and
> we can expect the OE community
> members like Andrew to test this and report issues or better fix them

Well, hopefully I've shown I'm at least willing to try fix things :D

And yeah, my preference would be that the ppc64le checksums are just 
bumped along with the rest, but without any explicit testing beyond 
that. I understand that I'm not the maintainer here so will go along 
with whatever approach is chosen, but keeping them here feels like 
we're at least solving the problem in a consistent spot.

As mentioned in the cover letter we found this issue via the ppc64le CI 
machines used in OpenBMC. OpenBMC tries to integrate upstream YP 
changes every fortnight or so. That's obviously not as ideal as ppc64le 
resources dedicated to YP, but I think this provides enough feedback 
that things won't completely rot.

If a bump does cause issues I'll try to resolve them as soon as possible.

Andrew

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162230): 
https://lists.openembedded.org/g/openembedded-core/message/162230
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 32/32] python3-nose: drop recipe

[Tim Orling]

On Tue, Feb 22, 2022 at 2:24 PM Khem Raj  wrote:

> there are packages in meta-python which still need it
>
>   meta-networking/recipes-connectivity/netplan/netplan_0.103.bb:
> RDEPENDS:${PN}
> = "python3 python3-core python3-pyyaml python3-netifaces python3-nos
> e python3-coverage python3-pycodestyle python3-pyflakes
> util-linux-libuuid libnetplan"
>   meta-python/recipes-devtools/python/python3-anyjson_0.3.3.bb:
> ${PYTHON_PN}-nose \
>   meta-python/recipes-devtools/python/python3-blinker_1.4.bb:
> ${PYTHON_PN}-nose \
>   meta-python/recipes-devtools/python/python3-oauthlib_3.2.0.bb:
> PACKAGECONFIG[test]
> = ",,,${PYTHON_PN}-blinker ${PYTHON_PN}-cryptography ${PYTHON_P
> N}-nose ${PYTHON_PN}-pyjwt"
>
> I wonder if these recipes can either be also removed or made free of
> nose module.
>
>
I am thinking the same thing. While we could probably run 2to3 on the nose
plugins
that are the legacy python2 code, I would rather do the right thing.

In some cases, pytest can be a drop in replacement for nosetests, but not
always.

If anyone has any other ideas, please chime in. I am all ears.

On Mon, Feb 21, 2022 at 1:25 PM Tim Orling  wrote:
> >
> > The code has not been touched since 2016 and numerous files still have
> > Python2 syntax code in them. This causes do_compile errors when
> > packaging a wheel (PEP-517 packaging).
> >
> > Nothing in oe-core depends on python3-nose.
> >
> > [YOCTO #14638]
> >
> > Signed-off-by: Tim Orling 
> > ---
> >  meta/conf/distro/include/maintainers.inc   |  1 -
> >  meta/recipes-devtools/python/python-nose.inc   | 18 --
> >  .../python/python3-nose_1.3.7.bb   |  2 --
> >  3 files changed, 21 deletions(-)
> >  delete mode 100644 meta/recipes-devtools/python/python-nose.inc
> >  delete mode 100644 meta/recipes-devtools/python/python3-nose_1.3.7.bb
> >
> > diff --git a/meta/conf/distro/include/maintainers.inc
> b/meta/conf/distro/include/maintainers.inc
> > index 7a65612b7c6..333685cd8b8 100644
> > --- a/meta/conf/distro/include/maintainers.inc
> > +++ b/meta/conf/distro/include/maintainers.inc
> > @@ -616,7 +616,6 @@ RECIPE_MAINTAINER:pn-python3-mako = "Oleksandr
> Kravchuk  >  RECIPE_MAINTAINER:pn-python3-markdown = "Alexander Kanavin <
> alex.kana...@gmail.com>"
> >  RECIPE_MAINTAINER:pn-python3-markupsafe = "Richard Purdie <
> richard.pur...@linuxfoundation.org>"
> >  RECIPE_MAINTAINER:pn-python3-more-itertools = "Tim Orling <
> tim.orl...@konsulko.com>"
> > -RECIPE_MAINTAINER:pn-python3-nose = "Oleksandr Kravchuk <
> open.sou...@oleksandr-kravchuk.com>"
> >  RECIPE_MAINTAINER:pn-python3-numpy = "Oleksandr Kravchuk <
> open.sou...@oleksandr-kravchuk.com>"
> >  RECIPE_MAINTAINER:pn-python3-packaging = "Tim Orling <
> tim.orl...@konsulko.com>"
> >  RECIPE_MAINTAINER:pn-python3-pathlib2 = "Tim Orling <
> tim.orl...@konsulko.com>"
> > diff --git a/meta/recipes-devtools/python/python-nose.inc
> b/meta/recipes-devtools/python/python-nose.inc
> > deleted file mode 100644
> > index 08c380d637c..000
> > --- a/meta/recipes-devtools/python/python-nose.inc
> > +++ /dev/null
> > @@ -1,18 +0,0 @@
> > -SUMMARY = "Extends Python unittest to make testing easier"
> > -HOMEPAGE = "http://readthedocs.org/docs/nose/;
> > -DESCRIPTION = "nose extends the test loading and running features of
> unittest, \
> > -making it easier to write, find and run tests."
> > -SECTION = "devel/python"
> > -LICENSE = "LGPL-2.1-only"
> > -LIC_FILES_CHKSUM =
> "file://lgpl.txt;md5=a6f89e2100d9b6cdffcea4f398e37343"
> > -
> > -SRC_URI[md5sum] = "4d3ad0ff07b61373d2cefc89c5d0b20b"
> > -SRC_URI[sha256sum] =
> "f1bffef9cbc82628f6e7d7b40d7e255aefaa1adb6a1b1d26c69a8b79e6208a98"
> > -
> > -inherit pypi
> > -
> > -RDEPENDS:${PN} = "\
> > -  ${PYTHON_PN}-unittest \
> > -  "
> > -
> > -BBCLASSEXTEND = "native nativesdk"
> > diff --git a/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> > deleted file mode 100644
> > index 13dbf96179a..000
> > --- a/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> > +++ /dev/null
> > @@ -1,2 +0,0 @@
> > -inherit setuptools3
> > -require python-nose.inc
> > --
> > 2.30.2
> >
> >
> > 
> >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162229): 
https://lists.openembedded.org/g/openembedded-core/message/162229
Mute This Topic: https://lists.openembedded.org/mt/89304054/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 32/32] python3-nose: drop recipe

[Khem Raj]

there are packages in meta-python which still need it

  meta-networking/recipes-connectivity/netplan/netplan_0.103.bb:RDEPENDS:${PN}
= "python3 python3-core python3-pyyaml python3-netifaces python3-nos
e python3-coverage python3-pycodestyle python3-pyflakes
util-linux-libuuid libnetplan"
  meta-python/recipes-devtools/python/python3-anyjson_0.3.3.bb:
${PYTHON_PN}-nose \
  meta-python/recipes-devtools/python/python3-blinker_1.4.bb:
${PYTHON_PN}-nose \
  
meta-python/recipes-devtools/python/python3-oauthlib_3.2.0.bb:PACKAGECONFIG[test]
= ",,,${PYTHON_PN}-blinker ${PYTHON_PN}-cryptography ${PYTHON_P
N}-nose ${PYTHON_PN}-pyjwt"

I wonder if these recipes can either be also removed or made free of
nose module.

On Mon, Feb 21, 2022 at 1:25 PM Tim Orling  wrote:
>
> The code has not been touched since 2016 and numerous files still have
> Python2 syntax code in them. This causes do_compile errors when
> packaging a wheel (PEP-517 packaging).
>
> Nothing in oe-core depends on python3-nose.
>
> [YOCTO #14638]
>
> Signed-off-by: Tim Orling 
> ---
>  meta/conf/distro/include/maintainers.inc   |  1 -
>  meta/recipes-devtools/python/python-nose.inc   | 18 --
>  .../python/python3-nose_1.3.7.bb   |  2 --
>  3 files changed, 21 deletions(-)
>  delete mode 100644 meta/recipes-devtools/python/python-nose.inc
>  delete mode 100644 meta/recipes-devtools/python/python3-nose_1.3.7.bb
>
> diff --git a/meta/conf/distro/include/maintainers.inc 
> b/meta/conf/distro/include/maintainers.inc
> index 7a65612b7c6..333685cd8b8 100644
> --- a/meta/conf/distro/include/maintainers.inc
> +++ b/meta/conf/distro/include/maintainers.inc
> @@ -616,7 +616,6 @@ RECIPE_MAINTAINER:pn-python3-mako = "Oleksandr Kravchuk 
>   RECIPE_MAINTAINER:pn-python3-markdown = "Alexander Kanavin 
> "
>  RECIPE_MAINTAINER:pn-python3-markupsafe = "Richard Purdie 
> "
>  RECIPE_MAINTAINER:pn-python3-more-itertools = "Tim Orling 
> "
> -RECIPE_MAINTAINER:pn-python3-nose = "Oleksandr Kravchuk 
> "
>  RECIPE_MAINTAINER:pn-python3-numpy = "Oleksandr Kravchuk 
> "
>  RECIPE_MAINTAINER:pn-python3-packaging = "Tim Orling 
> "
>  RECIPE_MAINTAINER:pn-python3-pathlib2 = "Tim Orling 
> "
> diff --git a/meta/recipes-devtools/python/python-nose.inc 
> b/meta/recipes-devtools/python/python-nose.inc
> deleted file mode 100644
> index 08c380d637c..000
> --- a/meta/recipes-devtools/python/python-nose.inc
> +++ /dev/null
> @@ -1,18 +0,0 @@
> -SUMMARY = "Extends Python unittest to make testing easier"
> -HOMEPAGE = "http://readthedocs.org/docs/nose/;
> -DESCRIPTION = "nose extends the test loading and running features of 
> unittest, \
> -making it easier to write, find and run tests."
> -SECTION = "devel/python"
> -LICENSE = "LGPL-2.1-only"
> -LIC_FILES_CHKSUM = "file://lgpl.txt;md5=a6f89e2100d9b6cdffcea4f398e37343"
> -
> -SRC_URI[md5sum] = "4d3ad0ff07b61373d2cefc89c5d0b20b"
> -SRC_URI[sha256sum] = 
> "f1bffef9cbc82628f6e7d7b40d7e255aefaa1adb6a1b1d26c69a8b79e6208a98"
> -
> -inherit pypi
> -
> -RDEPENDS:${PN} = "\
> -  ${PYTHON_PN}-unittest \
> -  "
> -
> -BBCLASSEXTEND = "native nativesdk"
> diff --git a/meta/recipes-devtools/python/python3-nose_1.3.7.bb 
> b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> deleted file mode 100644
> index 13dbf96179a..000
> --- a/meta/recipes-devtools/python/python3-nose_1.3.7.bb
> +++ /dev/null
> @@ -1,2 +0,0 @@
> -inherit setuptools3
> -require python-nose.inc
> --
> 2.30.2
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162228): 
https://lists.openembedded.org/g/openembedded-core/message/162228
Mute This Topic: https://lists.openembedded.org/mt/89304054/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH][RFC] cve-check: use local copy instead of global db

[Ralph Siemsen]

On Tue, Feb 22, 2022 at 07:46:59PM +0100, Konrad Weihmann wrote:

instead of using a global DB (default in DL_DIR) copy an existing
DB file into WORKDIR and use it from there.
This should avoid running into the reported "database is readonly" error
while at the same time there's no need to arbritrarily limit the
cve_check task to just one run at a time


I tested this on dunfell branch (the patch needed some minor context 
tweaks in order to apply). The slowdown I observed during do_cve_check 
seems to be gone, and the actual CVE report remains unchanged.


Will keep testing it some more, but for now, it seems an improvement.

Tested-by: Ralph Siemsen 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162227): 
https://lists.openembedded.org/g/openembedded-core/message/162227
Mute This Topic: https://lists.openembedded.org/mt/89323890/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] package: rename LICENSE_EXCLUSION

[Saul Wold]

By renaming LICENSE_EXCLUSION to _exclude_incompatible, it makes it
clear that this is an internal variable.

Signed-off-by: Saul Wold 
---
 meta/classes/base.bbclass| 2 +-
 meta/classes/package.bbclass | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 227f1f5a756..d0e669db00d 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -623,7 +623,7 @@ python () {
 if unskipped_pkgs:
 for pkg in skipped_pkgs:
 bb.debug(1, "Skipping the package %s at do_rootfs 
because of incompatible license(s): %s" % (pkg, ' '.join(skipped_pkgs[pkg])))
-d.setVar('LICENSE_EXCLUSION-' + pkg, ' 
'.join(skipped_pkgs[pkg]))
+d.setVar('_exclude_incompatible-' + pkg, ' 
'.join(skipped_pkgs[pkg]))
 for pkg in unskipped_pkgs:
 bb.debug(1, "Including the package %s" % pkg)
 else:
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index f4a661ba25a..f8222581502 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1468,10 +1468,10 @@ python populate_packages () {
 os.umask(oldumask)
 os.chdir(workdir)
 
-# Handle LICENSE_EXCLUSION
+# Handle excluding packages with incompatible licenses
 package_list = []
 for pkg in packages:
-licenses = d.getVar('LICENSE_EXCLUSION-' + pkg)
+licenses = d.getVar('_exclude_incompatible-' + pkg)
 if licenses:
 msg = "Excluding %s from packaging as it has incompatible 
license(s): %s" % (pkg, licenses)
 oe.qa.handle_error("incompatible-license", msg, d)
@@ -2353,7 +2353,7 @@ def gen_packagevar(d, pkgvars="PACKAGEVARS"):
 
 # Ensure that changes to INCOMPATIBLE_LICENSE re-run do_package for
 # affected recipes.
-ret.append('LICENSE_EXCLUSION-%s' % p)
+ret.append('_exclude_incompatible-%s' % p)
 return " ".join(ret)
 
 PACKAGE_PREPROCESS_FUNCS ?= ""
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162226): 
https://lists.openembedded.org/g/openembedded-core/message/162226
Mute This Topic: https://lists.openembedded.org/mt/89324810/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Tim Orling]

On Tue, Feb 22, 2022 at 11:18 AM Khem Raj  wrote:

> On Tue, Feb 22, 2022 at 10:40 AM Tim Orling  wrote:
> >
> >
> >
> > On Tue, Feb 22, 2022 at 10:24 AM Khem Raj  wrote:
> >>
> >> On Tue, Feb 22, 2022 at 10:21 AM Tim Orling  wrote:
> >> >
> >> >
> >> >
> >> > On Tue, Feb 22, 2022 at 9:22 AM Khem Raj  wrote:
> >> >>
> >> >> this is going into dep loops Try
> >> >>
> >> >> bitbake python3-wheel-native
> >> >
> >> >
> >> > It shouldn’t
> >> >
> https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/python/python3-wheel_0.37.1.bb?h=timo/bootstrap-wheels
> >> >
> >>
> >> I have been trying whats on master-next
> >>
> >
> > I can't reproduce. Can you point me at an error log please?
> > It might have something to do with sstate cache, but that's just a hunch.
> >
>
> This is because python3-wheel was moved to core and modified but not
> deleted from meta-python at same time. I have sent a patch for that
>
> Already sent one:
https://patchwork.yoctoproject.org/project/oe/patch/20220222184920.2310391-1-tim.orl...@konsulko.com/


> >>
> >> > DEPENDS:remove:class-native = "python3-pip-native"
> >> >
> >> > do_install:class-native () {
> >> > # We need to bootstrap python3-wheel-native
> >> > install -d ${D}${PYTHON_SITEPACKAGES_DIR}
> >> > PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
> >> > unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
> >> > bbfatal_log "Failed to install"
> >> > }
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Mon, Feb 21, 2022 at 1:23 PM Tim Orling 
> wrote:
> >> >> >
> >> >> > Upstream Python is moving to pyproject.toml rather than setup.py
> and
> >> >> > wheels rather than eggs. The main place this is documented is in
> >> >> > PEP-517[1]. Installing packages with setup.py install is
> deprecated.
> >> >> >
> >> >> > We have a choice with the 'kirkstone' LTS release of introducing
> this
> >> >> > series (and fixing any fall out during the stabilization period) or
> >> >> > living with deprecated Python packaging for the duration of the
> LTS (at
> >> >> > a minimum 2 years). This seems to be a compelling enough reason to
> bring
> >> >> > in this series, even if it results in a slight slip of the 'feature
> >> >> > freeze', which is officially tomorrow, Monday 21 Feb, 2022.
> >> >> >
> >> >> > This series bootstraps python3-setuptools-native,
> >> >> > python3-flit-core-native, python3-wheel-native and
> python3-pip-native,
> >> >> > simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This
> allows all
> >> >> > other recipes to be installed with pip, as intended by upstream.
> >> >> >
> >> >> > Three new classes are introduced:
> >> >> > (1) flit_core which builds PEP-517 compliant packages which use
> >> >> > flit_core.buildapi as their build-backend.
> >> >> > (2) setuptools_build_meta which builds PEP-517 compliant packages
> which use
> >> >> > setuptools_build_meta  as their build-backend.
> >> >> > (3) pip_install_wheel, which simply installs wheels built by other
> >> >> > classes.
> >> >> >
> >> >> > The original setuptools3.bbclass do_compile is modified to
> >> >> > 'setup.py bdist_wheel' (from python3-wheel-native) rather than the
> deprecated
> >> >> > 'setup.py build' mechanism.
> >> >> >
> >> >> > The original setuptools3.bbclass do_install is modified to
> >> >> > use the pip_install_wheel.bbclass to install wheels with pip
> rather than
> >> >> > the deprecated 'setup.py install' mechanism.
> >> >> >
> >> >> > For pip install, we disable dependency checking (--no-deps)
> because it
> >> >> > proves to be brittle in our environment without providing full
> wheel
> >> >> > cache that seems like overhead that we do not need. We also disable
> >> >> > fetching wheels from pypi (--no-index). This is no different than
> our
> >> >> > normal workflow of requiring dependencies to be defined in a
> recipe.
> >> >> >
> >> >> > Missing from this series is documentation of the new features,
> classes
> >> >> > and variables (this will be done under separate cover).
> >> >> >
> >> >> > Also desired and previously discussed in YP meetings is a helper
> >> >> > function to warn that a recipe which currently inherits setuptools3
> >> >> > but has a pyproject.toml and defines a build-system.build-backend
> should
> >> >> > instead use of the new PEP-517 classes. This function is still in
> progress.
> >> >> >
> >> >> > During testing, recipes which use python3-setuptools-scm are
> failing to
> >> >> > determine the version of the python package, For several recipes,
> the fix
> >> >> > was to use pyproject.toml and PEP-517 build backends. To be sure,
> other recipes
> >> >> > are still going to fail for the short term, until the root cause
> can be
> >> >> > determined. This was not seen again in v2 builds.
> >> >> >
> >> >> > Another PEP-517 build-backend, poetry.core.masonry.api has been
> >> >> > identified in recipes in meta-python, but not in oe-core. The
> >> >> > python3-poetry-core recipe is WIP, but brings in a 

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Khem Raj]

On Tue, Feb 22, 2022 at 10:40 AM Tim Orling  wrote:
>
>
>
> On Tue, Feb 22, 2022 at 10:24 AM Khem Raj  wrote:
>>
>> On Tue, Feb 22, 2022 at 10:21 AM Tim Orling  wrote:
>> >
>> >
>> >
>> > On Tue, Feb 22, 2022 at 9:22 AM Khem Raj  wrote:
>> >>
>> >> this is going into dep loops Try
>> >>
>> >> bitbake python3-wheel-native
>> >
>> >
>> > It shouldn’t
>> > https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/python/python3-wheel_0.37.1.bb?h=timo/bootstrap-wheels
>> >
>>
>> I have been trying whats on master-next
>>
>
> I can't reproduce. Can you point me at an error log please?
> It might have something to do with sstate cache, but that's just a hunch.
>

This is because python3-wheel was moved to core and modified but not
deleted from meta-python at same time. I have sent a patch for that

>>
>> > DEPENDS:remove:class-native = "python3-pip-native"
>> >
>> > do_install:class-native () {
>> > # We need to bootstrap python3-wheel-native
>> > install -d ${D}${PYTHON_SITEPACKAGES_DIR}
>> > PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
>> > unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
>> > bbfatal_log "Failed to install"
>> > }
>> >>
>> >>
>> >>
>> >>
>> >> On Mon, Feb 21, 2022 at 1:23 PM Tim Orling  wrote:
>> >> >
>> >> > Upstream Python is moving to pyproject.toml rather than setup.py and
>> >> > wheels rather than eggs. The main place this is documented is in
>> >> > PEP-517[1]. Installing packages with setup.py install is deprecated.
>> >> >
>> >> > We have a choice with the 'kirkstone' LTS release of introducing this
>> >> > series (and fixing any fall out during the stabilization period) or
>> >> > living with deprecated Python packaging for the duration of the LTS (at
>> >> > a minimum 2 years). This seems to be a compelling enough reason to bring
>> >> > in this series, even if it results in a slight slip of the 'feature
>> >> > freeze', which is officially tomorrow, Monday 21 Feb, 2022.
>> >> >
>> >> > This series bootstraps python3-setuptools-native,
>> >> > python3-flit-core-native, python3-wheel-native and python3-pip-native,
>> >> > simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows all
>> >> > other recipes to be installed with pip, as intended by upstream.
>> >> >
>> >> > Three new classes are introduced:
>> >> > (1) flit_core which builds PEP-517 compliant packages which use
>> >> > flit_core.buildapi as their build-backend.
>> >> > (2) setuptools_build_meta which builds PEP-517 compliant packages which 
>> >> > use
>> >> > setuptools_build_meta  as their build-backend.
>> >> > (3) pip_install_wheel, which simply installs wheels built by other
>> >> > classes.
>> >> >
>> >> > The original setuptools3.bbclass do_compile is modified to
>> >> > 'setup.py bdist_wheel' (from python3-wheel-native) rather than the 
>> >> > deprecated
>> >> > 'setup.py build' mechanism.
>> >> >
>> >> > The original setuptools3.bbclass do_install is modified to
>> >> > use the pip_install_wheel.bbclass to install wheels with pip rather than
>> >> > the deprecated 'setup.py install' mechanism.
>> >> >
>> >> > For pip install, we disable dependency checking (--no-deps) because it
>> >> > proves to be brittle in our environment without providing full wheel
>> >> > cache that seems like overhead that we do not need. We also disable
>> >> > fetching wheels from pypi (--no-index). This is no different than our
>> >> > normal workflow of requiring dependencies to be defined in a recipe.
>> >> >
>> >> > Missing from this series is documentation of the new features, classes
>> >> > and variables (this will be done under separate cover).
>> >> >
>> >> > Also desired and previously discussed in YP meetings is a helper
>> >> > function to warn that a recipe which currently inherits setuptools3
>> >> > but has a pyproject.toml and defines a build-system.build-backend should
>> >> > instead use of the new PEP-517 classes. This function is still in 
>> >> > progress.
>> >> >
>> >> > During testing, recipes which use python3-setuptools-scm are failing to
>> >> > determine the version of the python package, For several recipes, the 
>> >> > fix
>> >> > was to use pyproject.toml and PEP-517 build backends. To be sure, other 
>> >> > recipes
>> >> > are still going to fail for the short term, until the root cause can be
>> >> > determined. This was not seen again in v2 builds.
>> >> >
>> >> > Another PEP-517 build-backend, poetry.core.masonry.api has been
>> >> > identified in recipes in meta-python, but not in oe-core. The
>> >> > python3-poetry-core recipe is WIP, but brings in a number of
>> >> > dependencies that are perhaps not worth it to bring into oe-core at this
>> >> > time. Rather we can support these recipes in meta-python?
>> >> >
>> >> > Fixes in v2 include passing --root=${D} to pip install (rather than 
>> >> > --target)
>> >> > and also passing --prefix so that scripts are (usually) installed in 
>> >> > the proper
>> >> > location. pip 

[OE-core] [PATCH v3 32/32] python3-nose: drop recipe

[Tim Orling]

The code has not been touched since 2016 and numerous files still have
Python2 syntax code in them. This causes do_compile errors when
packaging a wheel (PEP-517 packaging).

Nothing in oe-core depends on python3-nose.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/conf/distro/include/maintainers.inc   |  1 -
 meta/recipes-devtools/python/python-nose.inc   | 18 --
 .../python/python3-nose_1.3.7.bb   |  2 --
 3 files changed, 21 deletions(-)
 delete mode 100644 meta/recipes-devtools/python/python-nose.inc
 delete mode 100644 meta/recipes-devtools/python/python3-nose_1.3.7.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index 7a65612b7c6..333685cd8b8 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -616,7 +616,6 @@ RECIPE_MAINTAINER:pn-python3-mako = "Oleksandr Kravchuk 
http://readthedocs.org/docs/nose/;
-DESCRIPTION = "nose extends the test loading and running features of unittest, 
\
-making it easier to write, find and run tests."
-SECTION = "devel/python"
-LICENSE = "LGPL-2.1-only"
-LIC_FILES_CHKSUM = "file://lgpl.txt;md5=a6f89e2100d9b6cdffcea4f398e37343"
-
-SRC_URI[md5sum] = "4d3ad0ff07b61373d2cefc89c5d0b20b"
-SRC_URI[sha256sum] = 
"f1bffef9cbc82628f6e7d7b40d7e255aefaa1adb6a1b1d26c69a8b79e6208a98"
-
-inherit pypi
-
-RDEPENDS:${PN} = "\
-  ${PYTHON_PN}-unittest \
-  "
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/python/python3-nose_1.3.7.bb 
b/meta/recipes-devtools/python/python3-nose_1.3.7.bb
deleted file mode 100644
index 13dbf96179a..000
--- a/meta/recipes-devtools/python/python3-nose_1.3.7.bb
+++ /dev/null
@@ -1,2 +0,0 @@
-inherit setuptools3
-require python-nose.inc
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162223): 
https://lists.openembedded.org/g/openembedded-core/message/162223
Mute This Topic: https://lists.openembedded.org/mt/89324686/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 31/32] python3-packaging: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-packaging_21.3.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-packaging_21.3.bb 
b/meta/recipes-devtools/python/python3-packaging_21.3.bb
index 446edf04e1c..c7d0cb7ef78 100644
--- a/meta/recipes-devtools/python/python3-packaging_21.3.bb
+++ b/meta/recipes-devtools/python/python3-packaging_21.3.bb
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=faadaedca9251a90b205c9167578ce91"
 
 SRC_URI[sha256sum] = 
"dd47c42927d89ab911e606518907cc2d3a1f38bbd026385970643f9c5b8ecfeb"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 BBCLASSEXTEND = "native nativesdk"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16): 
https://lists.openembedded.org/g/openembedded-core/message/16
Mute This Topic: https://lists.openembedded.org/mt/89324685/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 29/32] python3-dbusmock: set PIP_INSTALL_PACKAGE

[Tim Orling]

The name of the wheel as built by bdist_wheel is "python_dbusmock", set
PIP_INSTALL_PACKAGE appropriately.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb 
b/meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb
index 8d97f0d360e..3a9cdda5f62 100644
--- a/meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb
+++ b/meta/recipes-devtools/python/python3-dbusmock_0.25.0.bb
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=e6a600fd5e1d9cbde2d983680233ad02"
 SRC_URI[sha256sum] = 
"6f4ce7650ecbb022684dc158df720e199635f3a3df75f7020f4fe8f6ff0394db"
 
 PYPI_PACKAGE = "python-dbusmock"
+PIP_INSTALL_PACKAGE = "python_dbusmock"
 
 inherit pypi setuptools3
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162220): 
https://lists.openembedded.org/g/openembedded-core/message/162220
Mute This Topic: https://lists.openembedded.org/mt/89324681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 30/32] python3-mako: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-mako_1.1.6.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-mako_1.1.6.bb 
b/meta/recipes-devtools/python/python3-mako_1.1.6.bb
index ec8c9cc12a8..23e13cff948 100644
--- a/meta/recipes-devtools/python/python3-mako_1.1.6.bb
+++ b/meta/recipes-devtools/python/python3-mako_1.1.6.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=943eb67718222db21d44a4ef1836675f"
 
 PYPI_PACKAGE = "Mako"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 SRC_URI[sha256sum] = 
"4e9e345a41924a954251b95b4b28e14a301145b544901332e658907a7464b6b2"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162221): 
https://lists.openembedded.org/g/openembedded-core/message/162221
Mute This Topic: https://lists.openembedded.org/mt/89324682/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 28/32] numpy: set PIP_INSTALL_PACKAGE

[Tim Orling]

The recipe does not inherit pypi so we need to manually set
PIP_INSTALL_PACKAGE appropriately.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-numpy_1.22.2.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/python/python3-numpy_1.22.2.bb 
b/meta/recipes-devtools/python/python3-numpy_1.22.2.bb
index 52fbca94e2c..d2b2f3e38d5 100644
--- a/meta/recipes-devtools/python/python3-numpy_1.22.2.bb
+++ b/meta/recipes-devtools/python/python3-numpy_1.22.2.bb
@@ -20,6 +20,7 @@ UPSTREAM_CHECK_REGEX = "(?P\d+(\.\d+)+)\.tar"
 DEPENDS += "python3-cython-native"
 
 inherit ptest setuptools3
+PIP_INSTALL_PACKAGE = "numpy"
 
 S = "${WORKDIR}/numpy-${PV}"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162219): 
https://lists.openembedded.org/g/openembedded-core/message/162219
Mute This Topic: https://lists.openembedded.org/mt/89324679/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 27/32] gi-docgen: set PIP_INSTALL_PACKAGE

[Tim Orling]

The name of the wheel as built by bdist_wheel is "gi_docgen", set
PIP_INSTALL_PACKAGE appropriately.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-gnome/gi-docgen/gi-docgen_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb 
b/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
index 6a7124c3fea..67617fca393 100644
--- a/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
+++ b/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
@@ -16,6 +16,7 @@ SRCREV = "37b04455ff58cb2ec3f58917d0737c435344f2fb"
 S = "${WORKDIR}/git"
 
 inherit setuptools3
+PIP_INSTALL_PACKAGE = "gi_docgen"
 
 RDEPENDS:${PN} += "python3-asyncio python3-core python3-jinja2 python3-json 
python3-markdown python3-markupsafe python3-pygments python3-toml 
python3-typogrify python3-xml"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162218): 
https://lists.openembedded.org/g/openembedded-core/message/162218
Mute This Topic: https://lists.openembedded.org/mt/89324678/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 26/32] asciidoc: set PIP_INSTALL_PACKAGE

[Tim Orling]

This recipe does not inherit pypi and therefor we need to manually set
PIP_INSTALL_PACKAGE to reflect the wheel built by bdist_wheel.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-extended/asciidoc/asciidoc_10.1.1.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-extended/asciidoc/asciidoc_10.1.1.bb 
b/meta/recipes-extended/asciidoc/asciidoc_10.1.1.bb
index 8de827f09e8..60640d7a0f8 100644
--- a/meta/recipes-extended/asciidoc/asciidoc_10.1.1.bb
+++ b/meta/recipes-extended/asciidoc/asciidoc_10.1.1.bb
@@ -20,6 +20,7 @@ S = "${WORKDIR}/git"
 export SGML_CATALOG_FILES="file://${STAGING_ETCDIR_NATIVE}/xml/catalog"
 
 inherit setuptools3
+PIP_INSTALL_PACKAGE = "asciidoc"
 CLEANBROKEN = "1"
 
 BBCLASSEXTEND = "native nativesdk"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162217): 
https://lists.openembedded.org/g/openembedded-core/message/162217
Mute This Topic: https://lists.openembedded.org/mt/89324677/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 25/32] bmap-tools: set PIP_INSTALL_PACKAGE, BASEVER

[Tim Orling]

Change filename to _git.bb and use BASEVER to set PV.

The wheel built by bdist_wheel is named "bmap_tool-*.whl" set the
PIP_INSTALL_PACKAGE name accordingly.

Use BASEVER to set PYPA_WHEEL to match the version in the wheel produced
by bdist_wheel.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 .../bmap-tools/{bmap-tools_3.6.bb => bmap-tools_git.bb} | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)
 rename meta/recipes-support/bmap-tools/{bmap-tools_3.6.bb => 
bmap-tools_git.bb} (86%)

diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.6.bb 
b/meta/recipes-support/bmap-tools/bmap-tools_git.bb
similarity index 86%
rename from meta/recipes-support/bmap-tools/bmap-tools_3.6.bb
rename to meta/recipes-support/bmap-tools/bmap-tools_git.bb
index 1e87d45c90d..e3315321ed1 100644
--- a/meta/recipes-support/bmap-tools/bmap-tools_3.6.bb
+++ b/meta/recipes-support/bmap-tools/bmap-tools_git.bb
@@ -13,7 +13,8 @@ SRC_URI = 
"git://github.com/intel/${BPN};branch=master;protocol=https"
 
 SRCREV = "c0673962a8ec1624b5189dc1d24f33fe4f06785a"
 S = "${WORKDIR}/git"
-PV .= "+git${SRCPV}"
+BASEVER = "3.6"
+PV = "${BASEVER}+git${SRCPV}"
 
 UPSTREAM_CHECK_GITTAGREGEX = "v(?P\d+(\.\d+)+)"
 
@@ -23,4 +24,7 @@ RDEPENDS:${PN} = "python3-core python3-compression 
python3-mmap python3-setuptoo
 inherit python3native
 inherit setuptools3
 
+PIP_INSTALL_PACKAGE = "bmap_tools"
+PYPA_WHEEL = "${PIP_INSTALL_DIST_PATH}/${PIP_INSTALL_PACKAGE}-${BASEVER}-*.whl"
+
 BBCLASSEXTEND = "native nativesdk"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162216): 
https://lists.openembedded.org/g/openembedded-core/message/162216
Mute This Topic: https://lists.openembedded.org/mt/89324676/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 24/32] python3-magic: set PIP_INSTALL_PACKAGE

[Tim Orling]

The wheel built by bdist_wheel has the name "python_magic-*.whl" so set
PIP_INSTALL_PACKAGE accordingly.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-magic_0.4.25.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/python/python3-magic_0.4.25.bb 
b/meta/recipes-devtools/python/python3-magic_0.4.25.bb
index efc8b6daaaf..bd46b294ae9 100644
--- a/meta/recipes-devtools/python/python3-magic_0.4.25.bb
+++ b/meta/recipes-devtools/python/python3-magic_0.4.25.bb
@@ -8,6 +8,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=61495c152d794e6be5799a9edca149e3"
 
 PYPI_PACKAGE = "python-magic"
+PIP_INSTALL_PACKAGE = "python_magic"
 
 inherit pypi setuptools3
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162215): 
https://lists.openembedded.org/g/openembedded-core/message/162215
Mute This Topic: https://lists.openembedded.org/mt/89324675/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 23/32] python3-subunit: merge inc; set PIP_INSTALL_PACKAGE

[Tim Orling]

We have not supported python2 for some time now, so there is no reason
to maintain a separate python-subunit.inc file.

The wheel built by bdist_wheel is named 'python_subunit-*.whl', so set
PIP_INSALL_PACKAGE appropriately.

Add patch to use vendored _distutils from setuptools.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 .../python/python-subunit.inc | 14 --
 ...001-setup.py-use-vendored-_distutils.patch | 27 +++
 .../python/python3-strict-rfc3339_0.7.bb  |  4 ++-
 .../python/python3-subunit_1.4.0.bb   | 17 ++--
 4 files changed, 45 insertions(+), 17 deletions(-)
 delete mode 100644 meta/recipes-devtools/python/python-subunit.inc
 create mode 100644 
meta/recipes-devtools/python/python3-strict-rfc3339/0001-setup.py-use-vendored-_distutils.patch

diff --git a/meta/recipes-devtools/python/python-subunit.inc 
b/meta/recipes-devtools/python/python-subunit.inc
deleted file mode 100644
index a2f9c5c3ffe..000
--- a/meta/recipes-devtools/python/python-subunit.inc
+++ /dev/null
@@ -1,14 +0,0 @@
-SUMMARY = "Python implementation of subunit test streaming protocol"
-HOMEPAGE = "https://pypi.org/project/python-subunit/;
-SECTION = "devel/python"
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = 
"file://README.rst;beginline=1;endline=20;md5=909c08e291647fd985fbe5d9836d51b6"
-
-PYPI_PACKAGE = "python-subunit"
-
-SRC_URI[md5sum] = "30f1ab20651d94442dd9a7f8c9e8d633"
-SRC_URI[sha256sum] = 
"042039928120fbf392e8c983d60f3d8ae1b88f90a9f8fd7188ddd9c26cad1e48"
-
-inherit pypi
-
-BBCLASSEXTEND = "nativesdk"
diff --git 
a/meta/recipes-devtools/python/python3-strict-rfc3339/0001-setup.py-use-vendored-_distutils.patch
 
b/meta/recipes-devtools/python/python3-strict-rfc3339/0001-setup.py-use-vendored-_distutils.patch
new file mode 100644
index 000..ba1c3d33637
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3-strict-rfc3339/0001-setup.py-use-vendored-_distutils.patch
@@ -0,0 +1,27 @@
+From 857719e82daea0d85b734cac34cf569050724068 Mon Sep 17 00:00:00 2001
+From: Tim Orling 
+Date: Sun, 20 Feb 2022 20:26:51 -0800
+Subject: [PATCH] setup.py: use vendored _distutils
+
+Deprecation warning of distutils is interferring with bdist_wheel build.
+
+For now, use the vendored setuptools._distutils.core.
+
+Upstream-Status: Pending [upstream appears unmaintained]
+
+Signed-off-by: Tim Orling 
+---
+ setup.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index 1bf87cf..a49fb8e 100644
+--- a/setup.py
 b/setup.py
+@@ -1,5 +1,5 @@
+ import os.path
+-from distutils.core import setup
++from setuptools._distutils.core import setup
+ 
+ readme_file = os.path.join(os.path.dirname(__file__), 'README.md')
+ readme = open(readme_file).read()
diff --git a/meta/recipes-devtools/python/python3-strict-rfc3339_0.7.bb 
b/meta/recipes-devtools/python/python3-strict-rfc3339_0.7.bb
index b8e929ef886..b592cb95d4a 100644
--- a/meta/recipes-devtools/python/python3-strict-rfc3339_0.7.bb
+++ b/meta/recipes-devtools/python/python3-strict-rfc3339_0.7.bb
@@ -3,9 +3,11 @@ HOMEPAGE = "https://pypi.org/project/strict-rfc3339/;
 LICENSE = "GPL-3.0-only"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=8f0e2cd40e05189ec81232da84bd6e1a"
 
-SRC_URI[md5sum] = "4d9b635b4df885bc37bc1189d66c9abc"
+SRC_URI += "file://0001-setup.py-use-vendored-_distutils.patch"
 SRC_URI[sha256sum] = 
"5cad17bedfc3af57b399db0fed32771f18fc54bbd917e85546088607ac5e1277"
 
 inherit pypi setuptools3
 
+PIP_INSTALL_PACKAGE = "strict_rfc3339"
+
 BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/python/python3-subunit_1.4.0.bb 
b/meta/recipes-devtools/python/python3-subunit_1.4.0.bb
index a06ded868f5..bc49a2b69ed 100644
--- a/meta/recipes-devtools/python/python3-subunit_1.4.0.bb
+++ b/meta/recipes-devtools/python/python3-subunit_1.4.0.bb
@@ -1,4 +1,17 @@
-inherit setuptools3
-require python-subunit.inc
+SUMMARY = "Python implementation of subunit test streaming protocol"
+HOMEPAGE = "https://pypi.org/project/python-subunit/;
+SECTION = "devel/python"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = 
"file://README.rst;beginline=1;endline=20;md5=909c08e291647fd985fbe5d9836d51b6"
+
+PYPI_PACKAGE = "python-subunit"
+
+SRC_URI[sha256sum] = 
"042039928120fbf392e8c983d60f3d8ae1b88f90a9f8fd7188ddd9c26cad1e48"
+
+inherit pypi setuptools3
+
+PIP_INSTALL_PACKAGE = "python_subunit"
 
 RDEPENDS:${PN} = " python3-testtools"
+
+BBCLASSEXTEND = "nativesdk"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162214): 
https://lists.openembedded.org/g/openembedded-core/message/162214
Mute This Topic: https://lists.openembedded.org/mt/89324674/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 22/32] python3-scons: merge -native recipe

[Tim Orling]

The native recipe simply calls create_wrapper to add a host script. Do
this via do_install:append:class-native()

The scons*.1 man pages are being installed in ${prefix}, move them to
${mandir} (previously installed in ${datadir}).

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 .../python/python3-scons-native_4.3.0.bb|  7 ---
 meta/recipes-devtools/python/python3-scons_4.3.0.bb | 13 -
 2 files changed, 12 insertions(+), 8 deletions(-)
 delete mode 100644 meta/recipes-devtools/python/python3-scons-native_4.3.0.bb

diff --git a/meta/recipes-devtools/python/python3-scons-native_4.3.0.bb 
b/meta/recipes-devtools/python/python3-scons-native_4.3.0.bb
deleted file mode 100644
index 73076b87320..000
--- a/meta/recipes-devtools/python/python3-scons-native_4.3.0.bb
+++ /dev/null
@@ -1,7 +0,0 @@
-require python3-scons_${PV}.bb
-inherit native python3native
-DEPENDS = "python3-native python3-setuptools-native"
-
-do_install:append() {
-create_wrapper ${D}${bindir}/scons 
SCONS_LIB_DIR='${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}' 
PYTHONNOUSERSITE='1'
-}
diff --git a/meta/recipes-devtools/python/python3-scons_4.3.0.bb 
b/meta/recipes-devtools/python/python3-scons_4.3.0.bb
index bff2fdae92d..cfb075f65f3 100644
--- a/meta/recipes-devtools/python/python3-scons_4.3.0.bb
+++ b/meta/recipes-devtools/python/python3-scons_4.3.0.bb
@@ -8,6 +8,7 @@ SRC_URI += " file://0001-Fix-man-page-installation.patch"
 SRC_URI[sha256sum] = 
"d47081587e3675cc168f1f54f0d74a69b328a2fc90ec4feb85f728677419b879"
 
 PYPI_PACKAGE = "SCons"
+PIP_INSTALL_DIST_PATH = "${B}/build/dist"
 
 inherit pypi setuptools3
 
@@ -24,4 +25,14 @@ RDEPENDS:${PN}:class-target = "\
   python3-pprint \
   "
 
-FILES:${PN}-doc += "${datadir}/scons*.1"
+do_install:append() {
+install -d ${D}${mandir}/man1
+mv ${D}${prefix}/scons*.1 ${D}${mandir}/man1/
+}
+FILES:${PN}-doc += "${mandir}/man1/scons*.1"
+
+do_install:append:class-native() {
+create_wrapper ${D}${bindir}/scons 
SCONS_LIB_DIR='${STAGING_DIR_HOST}/${PYTHON_SITEPACKAGES_DIR}' 
PYTHONNOUSERSITE='1'
+}
+
+BBCLASSEXTEND = "native"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162213): 
https://lists.openembedded.org/g/openembedded-core/message/162213
Mute This Topic: https://lists.openembedded.org/mt/89324673/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 21/32] python3-smartypants: patch hash bang to python3

[Tim Orling]

Change hash bang in smartypants and smartypants.py to be /usr/bin/env
python3

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 .../0001-Change-hash-bang-to-python3.patch| 47 +++
 .../python/python3-smartypants_2.0.0.bb   |  1 +
 2 files changed, 48 insertions(+)
 create mode 100644 
meta/recipes-devtools/python/python3-smartypants/0001-Change-hash-bang-to-python3.patch

diff --git 
a/meta/recipes-devtools/python/python3-smartypants/0001-Change-hash-bang-to-python3.patch
 
b/meta/recipes-devtools/python/python3-smartypants/0001-Change-hash-bang-to-python3.patch
new file mode 100644
index 000..aab16eaab41
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3-smartypants/0001-Change-hash-bang-to-python3.patch
@@ -0,0 +1,47 @@
+From e299bcb05405ff49450307bf3002c1fac14a866c Mon Sep 17 00:00:00 2001
+From: Tim Orling 
+Date: Sun, 20 Feb 2022 18:55:50 -0800
+Subject: [PATCH] Change hash bang to python3
+
+In setup.py, smartypants and smartypants.py set hash bang to python3.
+
+Upstream-Status: Inappropriate [oe-core specific]
+
+Signed-off-by: Tim Orling 
+
+---
+ setup.py   | 2 +-
+ smartypants| 2 +-
+ smartypants.py | 2 +-
+ 3 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index ff1ea76..96a8b73 100755
+--- a/setup.py
 b/setup.py
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # Copyright (C) 2013, 2014 by Yu-Jie Lin
+ # For detail license information, See COPYING
+ 
+diff --git a/smartypants b/smartypants
+index 189adf5..0cca568 100755
+--- a/smartypants
 b/smartypants
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # Copyright (c) 2013, 2014 Yu-Jie Lin
+ # Licensed under the BSD License, for detailed license information, see 
COPYING
+ 
+diff --git a/smartypants.py b/smartypants.py
+index a70575b..e53bd87 100755
+--- a/smartypants.py
 b/smartypants.py
+@@ -1,4 +1,4 @@
+-#!/usr/bin/python
++#!/usr/bin/env python3
+ # -*- coding: utf-8 -*-
+ # Copyright (c) 2013, 2014, 2016 Yu-Jie Lin
+ # Copyright (c) 2004, 2005, 2007, 2013 Chad Miller
diff --git a/meta/recipes-devtools/python/python3-smartypants_2.0.0.bb 
b/meta/recipes-devtools/python/python3-smartypants_2.0.0.bb
index ba3408247b7..05c94c390ff 100644
--- a/meta/recipes-devtools/python/python3-smartypants_2.0.0.bb
+++ b/meta/recipes-devtools/python/python3-smartypants_2.0.0.bb
@@ -6,6 +6,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=977036977591ac666c728921ecc54c4f"
 inherit pypi setuptools3
 
 PYPI_PACKAGE = "smartypants"
+SRC_URI += "file://0001-Change-hash-bang-to-python3.patch"
 SRC_URI[sha256sum] = 
"7812353a32022699a1aa8cd5626e01c94a946dcaeedaee2d0b382bae4c4cbf36"
 
 BBCLASSEXTEND = "native"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162212): 
https://lists.openembedded.org/g/openembedded-core/message/162212
Mute This Topic: https://lists.openembedded.org/mt/89324671/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 20/32] python3-libarchive-d: set PIP_INSTALL_PACKAGE

[Tim Orling]

Set PIP_INSTALL_PACKAGE to libarchive_c to match the name of the wheel
built by bdist_wheel.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-libarchive-c_4.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/python/python3-libarchive-c_4.0.bb 
b/meta/recipes-devtools/python/python3-libarchive-c_4.0.bb
index 3c6bc1e1cab..99837848a67 100644
--- a/meta/recipes-devtools/python/python3-libarchive-c_4.0.bb
+++ b/meta/recipes-devtools/python/python3-libarchive-c_4.0.bb
@@ -9,6 +9,8 @@ PYPI_PACKAGE = "libarchive-c"
 
 inherit pypi setuptools3
 
+PIP_INSTALL_PACKAGE = "libarchive_c"
+
 SRC_URI[sha256sum] = 
"a5b41ade94ba58b198d778e68000f6b7de41da768de7140c984f71d7fa8416e5"
 
 RDEPENDS:${PN} += "\
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162211): 
https://lists.openembedded.org/g/openembedded-core/message/162211
Mute This Topic: https://lists.openembedded.org/mt/89324670/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 19/32] meson: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares setuptools.build_meta
to be backend for PEP-517 packaging.

Set PIP_INSTALL_PACKAGE as this recipe does not inherit pypi and
therefor no PYPI_PACKAGE is defined

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/meson/meson_0.61.2.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/meson/meson_0.61.2.bb 
b/meta/recipes-devtools/meson/meson_0.61.2.bb
index 45938af6ffe..a51db1e3d44 100644
--- a/meta/recipes-devtools/meson/meson_0.61.2.bb
+++ b/meta/recipes-devtools/meson/meson_0.61.2.bb
@@ -21,7 +21,9 @@ SRC_URI[sha256sum] = 
"0233a7f8d959079318f6052b0939c27f68a5de86ba601f25c9ee6869fb
 UPSTREAM_CHECK_URI = "https://github.com/mesonbuild/meson/releases;
 UPSTREAM_CHECK_REGEX = "meson-(?P\d+(\.\d+)+)\.tar"
 
-inherit setuptools3
+inherit setuptools_build_meta
+
+PIP_INSTALL_PACKAGE = "meson"
 
 RDEPENDS:${PN} = "ninja python3-modules python3-pkg-resources"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162210): 
https://lists.openembedded.org/g/openembedded-core/message/162210
Mute This Topic: https://lists.openembedded.org/mt/89324669/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 17/32] setuptools3.bbclass: refactor for wheels

[Tim Orling]

Depend on python3-wheel-native so that we can build with 'setup.py
bdist_wheel'.

Use pip_install_wheel class to install the built wheels with pip, as
intended by upstream Python.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/classes/setuptools3.bbclass | 20 
 1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/meta/classes/setuptools3.bbclass b/meta/classes/setuptools3.bbclass
index fd8499d26c7..12561340b07 100644
--- a/meta/classes/setuptools3.bbclass
+++ b/meta/classes/setuptools3.bbclass
@@ -1,6 +1,7 @@
-inherit setuptools3-base
+inherit setuptools3-base pip_install_wheel
 
-B = "${WORKDIR}/build"
+# bdist_wheel builds in ./dist
+#B = "${WORKDIR}/build"
 
 SETUPTOOLS_BUILD_ARGS ?= ""
 SETUPTOOLS_INSTALL_ARGS ?= "--root=${D} \
@@ -23,20 +24,15 @@ setuptools3_do_compile() {
 STAGING_INCDIR=${STAGING_INCDIR} \
 STAGING_LIBDIR=${STAGING_LIBDIR} \
 ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py \
-build --build-base=${B} ${SETUPTOOLS_BUILD_ARGS} || \
-bbfatal_log "'${PYTHON_PN} setup.py build ${SETUPTOOLS_BUILD_ARGS}' 
execution failed."
+bdist_wheel ${SETUPTOOLS_BUILD_ARGS} || \
+bbfatal_log "'${PYTHON_PN} setup.py bdist_wheel 
${SETUPTOOLS_BUILD_ARGS}' execution failed."
 }
 setuptools3_do_compile[vardepsexclude] = "MACHINE"
 
 setuptools3_do_install() {
 cd ${SETUPTOOLS_SETUP_PATH}
-install -d ${D}${PYTHON_SITEPACKAGES_DIR}
-STAGING_INCDIR=${STAGING_INCDIR} \
-STAGING_LIBDIR=${STAGING_LIBDIR} \
-PYTHONPATH=${D}${PYTHON_SITEPACKAGES_DIR} \
-${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py \
-build --build-base=${B} install --skip-build 
${SETUPTOOLS_INSTALL_ARGS} || \
-bbfatal_log "'${PYTHON_PN} setup.py install 
${SETUPTOOLS_INSTALL_ARGS}' execution failed."
+
+pip_install_wheel_do_install
 
 # support filenames with *spaces*
 find ${D} -name "*.py" -exec grep -q ${D} {} \; \
@@ -64,5 +60,5 @@ setuptools3_do_install[vardepsexclude] = "MACHINE"
 EXPORT_FUNCTIONS do_configure do_compile do_install
 
 export LDSHARED="${CCLD} -shared"
-DEPENDS += "python3-setuptools-native"
+DEPENDS += "python3-setuptools-native python3-wheel-native"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162208): 
https://lists.openembedded.org/g/openembedded-core/message/162208
Mute This Topic: https://lists.openembedded.org/mt/89324667/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 18/32] python3-more-itertools: set PIP_INSTALL_PACKAGE

[Tim Orling]

Define PIP_INSTALL_PACKAGE as more_itertools to match the name of the
wheel.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-more-itertools_8.12.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/python/python3-more-itertools_8.12.0.bb 
b/meta/recipes-devtools/python/python3-more-itertools_8.12.0.bb
index c1e34b205da..5788af3f71e 100644
--- a/meta/recipes-devtools/python/python3-more-itertools_8.12.0.bb
+++ b/meta/recipes-devtools/python/python3-more-itertools_8.12.0.bb
@@ -7,6 +7,8 @@ SRC_URI[sha256sum] = 
"7dc6ad46f05f545f900dd59e8dfb4e84a4827b97b3cfecb175ea0c7d24
 
 inherit pypi setuptools3 ptest
 
+PIP_INSTALL_PACKAGE = "more_itertools"
+
 SRC_URI += " \
file://run-ptest \
 "
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162209): 
https://lists.openembedded.org/g/openembedded-core/message/162209
Mute This Topic: https://lists.openembedded.org/mt/89324668/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 16/32] python3-setuptools: inherit setuptools_base_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

We need to bootstrap python3-setuptools-native, simply installing by
unzipping the built wheel. This avoids a dependency loop.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 .../python/python3-setuptools_59.5.0.bb   | 19 ++-
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-devtools/python/python3-setuptools_59.5.0.bb 
b/meta/recipes-devtools/python/python3-setuptools_59.5.0.bb
index 33ca928c3e5..2155101d305 100644
--- a/meta/recipes-devtools/python/python3-setuptools_59.5.0.bb
+++ b/meta/recipes-devtools/python/python3-setuptools_59.5.0.bb
@@ -4,7 +4,7 @@ SECTION = "devel/python"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://LICENSE;beginline=1;endline=19;md5=7a7126e068206290f3fe9f8d6c713ea6"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 SRC_URI:append:class-native = " 
file://0001-conditionally-do-not-fetch-code-by-easy_install.patch"
 
@@ -17,6 +17,19 @@ SRC_URI[sha256sum] = 
"d144f85102f999444d06f9c0e8c737fd0194f10f2f7e5fdb77573f6e2f
 
 DEPENDS += "${PYTHON_PN}"
 
+# Avoid dependency loop; we bootstrap -native
+DEPENDS:remove:class-native = "python3-pip-native python3-setuptools-native"
+DEPENDS:append:class-native = " unzip-native"
+
+PYPA_WHEEL ?= "${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
+
+do_install:class-native() {
+# Bootstrap to prevent dependency loop in python3-pip-native
+install -d ${D}${PYTHON_SITEPACKAGES_DIR}
+unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
+bbfatal_log "Failed to unzip wheel: ${PYPA_WHEEL}. Check the logs."
+}
+
 RDEPENDS:${PN} = "\
 ${PYTHON_PN}-2to3 \
 ${PYTHON_PN}-compile \
@@ -38,10 +51,6 @@ RDEPENDS:${PN} = "\
 ${PYTHON_PN}-xml \
 "
 
-do_install:prepend() {
-install -d ${D}${PYTHON_SITEPACKAGES_DIR}
-}
-
 BBCLASSEXTEND = "native nativesdk"
 
 # The pkg-resources module can be used by itself, without the package 
downloader
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162207): 
https://lists.openembedded.org/g/openembedded-core/message/162207
Mute This Topic: https://lists.openembedded.org/mt/89324666/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 15/32] python3-pluggy: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which while it does not declare the
setuptools.build_meta backend is compatible with it.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-pluggy_1.0.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-pluggy_1.0.0.bb 
b/meta/recipes-devtools/python/python3-pluggy_1.0.0.bb
index 14a7ccb0b0d..73bbcb02697 100644
--- a/meta/recipes-devtools/python/python3-pluggy_1.0.0.bb
+++ b/meta/recipes-devtools/python/python3-pluggy_1.0.0.bb
@@ -10,7 +10,7 @@ RDEPENDS:${PN} += "${PYTHON_PN}-importlib-metadata \
${PYTHON_PN}-more-itertools \
 "
 
-inherit pypi ptest setuptools3
+inherit pypi ptest setuptools_build_meta
 
 SRC_URI += " \
file://run-ptest \
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162206): 
https://lists.openembedded.org/g/openembedded-core/message/162206
Mute This Topic: https://lists.openembedded.org/mt/89324665/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 14/32] python3-py: inherit setuptools_build_meta

[Tim Orling]

Upstreama provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-py_1.11.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-py_1.11.0.bb 
b/meta/recipes-devtools/python/python3-py_1.11.0.bb
index f8be3935e5e..02027248f46 100644
--- a/meta/recipes-devtools/python/python3-py_1.11.0.bb
+++ b/meta/recipes-devtools/python/python3-py_1.11.0.bb
@@ -7,7 +7,7 @@ SRC_URI[sha256sum] = 
"51c75c4126074b472f746a24399ad32f6053d1b34b68d2fa41e558e6f4
 
 DEPENDS += "${PYTHON_PN}-setuptools-scm-native"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 BBCLASSEXTEND = "native nativesdk"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162205): 
https://lists.openembedded.org/g/openembedded-core/message/162205
Mute This Topic: https://lists.openembedded.org/mt/89324663/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 13/32] python3-iniconfig: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which decalres the
setuptools.build_meta backend for PEP-517 packaging.

DEPENDS on python3-setuptools-scm-native (as declared in the
pyproject.toml build-system.requires).

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-iniconfig_1.1.1.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-iniconfig_1.1.1.bb 
b/meta/recipes-devtools/python/python3-iniconfig_1.1.1.bb
index 6b3359712f5..5338980e699 100644
--- a/meta/recipes-devtools/python/python3-iniconfig_1.1.1.bb
+++ b/meta/recipes-devtools/python/python3-iniconfig_1.1.1.bb
@@ -7,4 +7,6 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=a6bb0320b04a0a503f12f69fea479de9"
 SRC_URI[md5sum] = "0b7f3be87481211c183eae095bcea6f1"
 SRC_URI[sha256sum] = 
"bc3af051d7d14b2ee5ef9969666def0cd1a000e121eaea580d4a313df4b37f32"
 
-inherit pypi setuptools3
+DEPENDS += "python3-setuptools-scm-native"
+
+inherit pypi setuptools_build_meta
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162204): 
https://lists.openembedded.org/g/openembedded-core/message/162204
Mute This Topic: https://lists.openembedded.org/mt/89324661/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 12/32] python3-zipp: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-zipp_3.7.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-zipp_3.7.0.bb 
b/meta/recipes-devtools/python/python3-zipp_3.7.0.bb
index 9ce987c8702..d0f936faf7c 100644
--- a/meta/recipes-devtools/python/python3-zipp_3.7.0.bb
+++ b/meta/recipes-devtools/python/python3-zipp_3.7.0.bb
@@ -7,7 +7,7 @@ SRC_URI[sha256sum] = 
"9f50f446828eb9d45b267433fd3e9da8d801f614129124863f9c51ebce
 
 DEPENDS += "${PYTHON_PN}-setuptools-scm-native"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 DEPENDS += "${PYTHON_PN}-toml-native"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162203): 
https://lists.openembedded.org/g/openembedded-core/message/162203
Mute This Topic: https://lists.openembedded.org/mt/89324660/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 11/32] python3-setuptools-scm: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-setuptools-scm_6.4.2.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-setuptools-scm_6.4.2.bb 
b/meta/recipes-devtools/python/python3-setuptools-scm_6.4.2.bb
index 10dad5a37be..182ccecbbfc 100644
--- a/meta/recipes-devtools/python/python3-setuptools-scm_6.4.2.bb
+++ b/meta/recipes-devtools/python/python3-setuptools-scm_6.4.2.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = 
"file://PKG-INFO;beginline=8;endline=8;md5=8227180126797a0148
 SRC_URI[sha256sum] = 
"6833ac65c6ed9711a4d5d2266f8024cfa07c533a0e55f4c12f6eff280a5a9e30"
 
 PYPI_PACKAGE = "setuptools_scm"
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 UPSTREAM_CHECK_REGEX = "setuptools_scm-(?P.*)\.tar"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162202): 
https://lists.openembedded.org/g/openembedded-core/message/162202
Mute This Topic: https://lists.openembedded.org/mt/89324659/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 10/32] python3-pytest: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-pytest_7.0.1.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/python/python3-pytest_7.0.1.bb 
b/meta/recipes-devtools/python/python3-pytest_7.0.1.bb
index 25014064890..ea6ba80300a 100644
--- a/meta/recipes-devtools/python/python3-pytest_7.0.1.bb
+++ b/meta/recipes-devtools/python/python3-pytest_7.0.1.bb
@@ -7,9 +7,9 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=bd27e41b6550fe0fc45356d1d81ee37c"
 
 SRC_URI[sha256sum] = 
"e30905a0c131d3d94b89624a1cc5afec3e0ba2fbdb151867d8e0ebd49850f171"
 
-DEPENDS = "python3-setuptools-scm-native"
+DEPENDS += "python3-setuptools-scm-native"
 
-inherit update-alternatives pypi setuptools3
+inherit update-alternatives pypi setuptools_build_meta
 
 RDEPENDS:${PN}:class-target += " \
 ${PYTHON_PN}-atomicwrites \
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162201): 
https://lists.openembedded.org/g/openembedded-core/message/162201
Mute This Topic: https://lists.openembedded.org/mt/89324657/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 08/32] python3-attrs: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-attrs_21.4.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-attrs_21.4.0.bb 
b/meta/recipes-devtools/python/python3-attrs_21.4.0.bb
index d1dde29d376..20e4541f81c 100644
--- a/meta/recipes-devtools/python/python3-attrs_21.4.0.bb
+++ b/meta/recipes-devtools/python/python3-attrs_21.4.0.bb
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=d4ab25949a73fe7d4fdee93bcbdbf8ff"
 
 SRC_URI[sha256sum] = 
"626ba8234211db98e869df76230a137c4c40a12d72445c45d5f5b716f076e2fd"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 RDEPENDS:${PN}:class-target += " \
 ${PYTHON_PN}-crypt \
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162199): 
https://lists.openembedded.org/g/openembedded-core/message/162199
Mute This Topic: https://lists.openembedded.org/mt/89324655/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 09/32] python3-git: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares the
setuptools.build_meta backend for PEP-517 packaging.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/recipes-devtools/python/python3-git_3.1.26.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-git_3.1.26.bb 
b/meta/recipes-devtools/python/python3-git_3.1.26.bb
index b6171a0e4d1..8f4b13cc15d 100644
--- a/meta/recipes-devtools/python/python3-git_3.1.26.bb
+++ b/meta/recipes-devtools/python/python3-git_3.1.26.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=8b8d26c37c1d5a04f9b0186edbebc183"
 
 PYPI_PACKAGE = "GitPython"
 
-inherit pypi setuptools3
+inherit pypi setuptools_build_meta
 
 SRC_URI[sha256sum] = 
"fc8868f63a2e6d268fb25f481995ba185a85a66fcad126f039323ff6635669ee"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162200): 
https://lists.openembedded.org/g/openembedded-core/message/162200
Mute This Topic: https://lists.openembedded.org/mt/89324656/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 07/32] python3-pip: inherit setuptools_build_meta

[Tim Orling]

Upstream provides a pyproject.toml which declares setuptools.build_meta
as the backend for PEP-517 packaging.

We bootstrap the -native installation by simply unzipping the wheel to
PYTHON_SITEPACKAGES_DIR, so that all other recipes can use pip to
install wheels (as intended by upstream).

Check for presence of ${D}${bindir}/pip and remove if found (this was
originally to make sure Python2 pip was the default).

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 .../python/python3-pip_22.0.3.bb  | 19 +--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/python/python3-pip_22.0.3.bb 
b/meta/recipes-devtools/python/python3-pip_22.0.3.bb
index 889a6bf8adc..c4671f50175 100644
--- a/meta/recipes-devtools/python/python3-pip_22.0.3.bb
+++ b/meta/recipes-devtools/python/python3-pip_22.0.3.bb
@@ -4,17 +4,32 @@ SECTION = "devel/python"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=63ec52baf95163b597008bb46db68030"
 
+inherit pypi setuptools_build_meta
+
 DEPENDS += "python3 python3-setuptools-native"
 
-inherit pypi setuptools3
+# To avoid a dependency loop; we bootstrap -native
+DEPENDS:remove:class-native = "python3-pip-native"
+DEPENDS:append:class-native = " unzip-native"
 
 SRC_URI += "file://0001-change-shebang-to-python3.patch"
 
 SRC_URI[sha256sum] = 
"f29d589df8c8ab99c060e68ad294c4a9ed896624f6368c5349d70aa581b333d0"
 
+PYPA_WHEEL ?= "${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
+
+do_install:class-native() {
+# Bootstrap to prevent dependency loop in python3-pip-native
+install -d ${D}${PYTHON_SITEPACKAGES_DIR}
+unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
+bbfatal_log "Failed to unzip wheel: ${PYPA_WHEEL}. Check the logs."
+}
+
 do_install:append() {
 # Install as pip3 and leave pip2 as default
-rm ${D}/${bindir}/pip
+if [ -e ${D}/${bindir}/pip ]; then
+rm ${D}/${bindir}/pip
+fi
 }
 
 RDEPENDS:${PN} = "\
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162198): 
https://lists.openembedded.org/g/openembedded-core/message/162198
Mute This Topic: https://lists.openembedded.org/mt/89324653/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 06/32] setuptools_build_meta.bbclass: add helper class

[Tim Orling]

This class uses the PEP 517 compliant setuptools.buil_meta to build
wheels.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/classes/setuptools_build_meta.bbclass | 18 ++
 1 file changed, 18 insertions(+)
 create mode 100644 meta/classes/setuptools_build_meta.bbclass

diff --git a/meta/classes/setuptools_build_meta.bbclass 
b/meta/classes/setuptools_build_meta.bbclass
new file mode 100644
index 000..b1441e65dd5
--- /dev/null
+++ b/meta/classes/setuptools_build_meta.bbclass
@@ -0,0 +1,18 @@
+inherit pip_install_wheel setuptools3-base
+
+DEPENDS += "python3 python3-setuptools-native python3-wheel-native"
+
+setuptools_build_meta_do_configure () {
+mkdir -p ${S}/dist
+cat > ${S}/build-it.py << EOF
+from setuptools import build_meta
+wheel = build_meta.build_wheel('./dist')
+print(wheel)
+EOF
+}
+
+setuptools_build_meta_do_compile () {
+nativepython3 ${S}/build-it.py
+}
+
+EXPORT_FUNCTIONS do_configure do_compile
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162197): 
https://lists.openembedded.org/g/openembedded-core/message/162197
Mute This Topic: https://lists.openembedded.org/mt/89324652/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 05/32] pip_install_wheel.bbclass: add helper class

[Tim Orling]

Provide a helper class to use pip to install wheels built by either
bdist_wheel or a PEP-517 backend.

Set pip install arguments via PIP_INSTALL_ARGS, which can be overriden
by recipes.

Pass --root and --prefix to ensure that pip installs things into the
proper place in sysroot.

By passing --no-deps and --no-index we avoid finicky dependency
checking (pip expects wheels in its cache) and avoid trying to fetch
wheels from pypi.org. This is basically the same behavior we have now,
the dependencies should be declared in the recipe.

Also pass --force-reinstall to make sure built wheels are always installed
so that FILES gets properly populated.

Pass --no-cache to avoid a (harmless) warning about the pip cache in
$HOME be avoiding use of cache. We do not likely want wheels cached
anyway,

pip install changes the python interpreter in scripts installed in
${bindir}, e.g. to #!/usr/bin/nativepython3, correct the behavior after
install to #!/usr/bin/env python3.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/classes/pip_install_wheel.bbclass | 39 ++
 1 file changed, 39 insertions(+)
 create mode 100644 meta/classes/pip_install_wheel.bbclass

diff --git a/meta/classes/pip_install_wheel.bbclass 
b/meta/classes/pip_install_wheel.bbclass
new file mode 100644
index 000..70f47d6f79c
--- /dev/null
+++ b/meta/classes/pip_install_wheel.bbclass
@@ -0,0 +1,39 @@
+DEPENDS:append = " python3-pip-native"
+
+PIP_INSTALL_PACKAGE ?= "${PYPI_PACKAGE}"
+PIP_INSTALL_DIST_PATH ?= "${B}/dist"
+PYPA_WHEEL ??= "${PIP_INSTALL_DIST_PATH}/${PIP_INSTALL_PACKAGE}-${PV}-*.whl"
+
+PIP_INSTALL_ARGS ?= "\
+- \
+--force-reinstall \
+--no-cache \
+--no-deps \
+--no-index \
+--root=${D} \
+--prefix=${prefix} \
+"
+
+pip_install_wheel_do_install:prepend () {
+install -d ${D}${PYTHON_SITEPACKAGES_DIR}
+}
+
+export PYPA_WHEEL
+
+PIP_INSTALL_PYTHON = "python3"
+PIP_INSTALL_PYTHON:class-native = "nativepython3"
+
+pip_install_wheel_do_install () {
+nativepython3 -m pip install ${PIP_INSTALL_ARGS} ${PYPA_WHEEL} ||
+bbfatal_log "Failed to pip install wheel. Check the logs."
+
+for i in ${D}${bindir}/* ${D}${sbindir}/*; do
+if [ -f "$i" ]; then
+sed -i -e "1s,#!.*nativepython3,#!${USRBINPATH}/env 
${PIP_INSTALL_PYTHON}," $i
+sed -i -e "s:${PYTHON}:${USRBINPATH}/env\ ${PIP_INSTALL_PYTHON}:g" 
$i
+sed -i -e "s:${STAGING_BINDIR_NATIVE}:${bindir}:g" $i
+fi
+done
+}
+
+EXPORT_FUNCTIONS do_install
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162196): 
https://lists.openembedded.org/g/openembedded-core/message/162196
Mute This Topic: https://lists.openembedded.org/mt/89324650/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 04/32] python3-wheel: inherit flit_core

[Tim Orling]

Backport pyproject.toml from flit-backend branch.
Inherit flit_core class to build
Inherit pip_install_wheel to install wheels for target

We need to bootstrap python3-wheel-native in order to have bdist_wheel
available to python3-setuptools-native and the refactored
setuptools3.bbclass. Simply unzip the wheel into
PYTHON_SITEPACKAGES_DIR for class-native.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 ...roject.toml-from-flit-backend-branch.patch | 100 ++
 .../python/python3-wheel_0.37.1.bb|  16 ++-
 2 files changed, 114 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-devtools/python/python3-wheel/0001-Backport-pyproject.toml-from-flit-backend-branch.patch

diff --git 
a/meta/recipes-devtools/python/python3-wheel/0001-Backport-pyproject.toml-from-flit-backend-branch.patch
 
b/meta/recipes-devtools/python/python3-wheel/0001-Backport-pyproject.toml-from-flit-backend-branch.patch
new file mode 100644
index 000..023de0e6a88
--- /dev/null
+++ 
b/meta/recipes-devtools/python/python3-wheel/0001-Backport-pyproject.toml-from-flit-backend-branch.patch
@@ -0,0 +1,100 @@
+From f00dd220346773bc088d403847ee7f06f2b4c30a Mon Sep 17 00:00:00 2001
+From: Tim Orling 
+Date: Fri, 18 Feb 2022 11:09:16 -0800
+Subject: [PATCH] Backport pyproject.toml from flit-backend branch
+
+This allows us to bootstrap wheels and PEP-517 packaging.
+
+Upstream-Status: Backport from flit-backend branch
+https://raw.githubusercontent.com/pypa/wheel/4f6ba78fede38a8d9e35a14e38377a121033afb3/pyproject.toml
+
+Signed-off-by: Tim Orling 
+---
+ pyproject.toml | 78 ++
+ 1 file changed, 78 insertions(+)
+ create mode 100644 pyproject.toml
+
+diff --git a/pyproject.toml b/pyproject.toml
+new file mode 100644
+index 000..749b8de
+--- /dev/null
 b/pyproject.toml
+@@ -0,0 +1,78 @@
++[build-system]
++requires = ["flit_core >=3.2,<4"]
++build-backend = "flit_core.buildapi"
++
++[project]
++name = "wheel"
++description = "A built-package format for Python"
++readme = "README.rst"
++classifiers = [
++"Development Status :: 5 - Production/Stable",
++"Intended Audience :: Developers",
++"Topic :: System :: Archiving :: Packaging",
++"License :: OSI Approved :: MIT License",
++"Programming Language :: Python",
++"Programming Language :: Python :: 3 :: Only",
++"Programming Language :: Python :: 3.7",
++"Programming Language :: Python :: 3.8",
++"Programming Language :: Python :: 3.9",
++"Programming Language :: Python :: 3.10"
++]
++authors = [{name = "Daniel Holth", email = "dho...@fastmail.fm"}]
++maintainers = [{name = "Alex Grönholm", email = "alex.gronh...@nextday.fi"}]
++keywords = ["wheel", "packaging"]
++license = {file = "LICENSE.txt"}
++requires-python = ">=3.7"
++dependencies = [
++"setuptools >= 45.2.0"
++]
++dynamic = ["version"]
++
++[project.urls]
++Documentation = "https://wheel.readthedocs.io/;
++Changelog = "https://wheel.readthedocs.io/en/stable/news.html;
++"Issue Tracker" = "https://github.com/pypa/wheel/issues;
++
++[project.scripts]
++wheel = "wheel.cli:main"
++
++[project.entry-points."distutils.commands"]
++bdist_wheel = "wheel.bdist_wheel:bdist_wheel"
++
++[project.optional-dependencies]
++test = [
++"pytest >= 3.0.0"
++]
++
++[tool.flit.sdist]
++exclude = [
++".cirrus.yml",
++".github/*",
++".gitignore",
++".pre-commit-config.yaml",
++".readthedocs.yml"
++]
++
++[tool.black]
++target-version = ['py37']
++extend-exclude = '''
++^/src/wheel/vendored/
++'''
++
++[tool.isort]
++src_paths = ["src"]
++profile = "black"
++skip_gitignore = true
++
++[tool.flake8]
++max-line-length = 88
++
++[tool.pytest.ini_options]
++testpaths = "tests"
++
++[tool.coverage.run]
++source = ["wheel"]
++omit = ["*/vendored/*"]
++
++[tool.coverage.report]
++show_missing = true
diff --git a/meta/recipes-devtools/python/python3-wheel_0.37.1.bb 
b/meta/recipes-devtools/python/python3-wheel_0.37.1.bb
index 6c7a31db9e7..c7354c9d982 100644
--- a/meta/recipes-devtools/python/python3-wheel_0.37.1.bb
+++ b/meta/recipes-devtools/python/python3-wheel_0.37.1.bb
@@ -6,7 +6,19 @@ LIC_FILES_CHKSUM = 
"file://PKG-INFO;beginline=10;endline=10;md5=8227180126797a01
 
 SRC_URI[sha256sum] = 
"e9a504e793efbca1b8e0e9cb979a249cf4a0a7b5b8c9e8b65a5e39d49529c1c4"
 
-inherit pypi setuptools3
+inherit flit_core pypi setuptools3-base
 
-BBCLASSEXTEND = "native"
+SRC_URI += " 
file://0001-Backport-pyproject.toml-from-flit-backend-branch.patch"
+
+DEPENDS:remove:class-native = "python3-pip-native"
+
+do_install:class-native () {
+# We need to bootstrap python3-wheel-native
+install -d ${D}${PYTHON_SITEPACKAGES_DIR}
+PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
+unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
+bbfatal_log "Failed to install"
+}
+
+BBCLASSEXTEND = "native nativesdk"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply 

[OE-core] [PATCH v3 03/32] flit_core.bbclass: add helper for newer python packaging

[Tim Orling]

Some python packages now use pyproject.toml and declare
flit_core.buildapi as the build engine

Use pip_install_wheel class to install.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/classes/flit_core.bbclass | 16 
 1 file changed, 16 insertions(+)
 create mode 100644 meta/classes/flit_core.bbclass

diff --git a/meta/classes/flit_core.bbclass b/meta/classes/flit_core.bbclass
new file mode 100644
index 000..0f2eec85d0b
--- /dev/null
+++ b/meta/classes/flit_core.bbclass
@@ -0,0 +1,16 @@
+inherit pip_install_wheel python3native python3-dir
+
+DEPENDS += "python3 python3-flit-core-native python3-pip-native"
+
+do_configure () {
+mkdir -p ${S}/dist
+cat > ${S}/build-it.py << EOF
+from flit_core import buildapi
+buildapi.build_wheel('./dist')
+EOF
+}
+
+do_compile () {
+${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} ${S}/build-it.py
+}
+
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162194): 
https://lists.openembedded.org/g/openembedded-core/message/162194
Mute This Topic: https://lists.openembedded.org/mt/89324646/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 02/32] python3-flit-core: add recipe for 3.6.0

[Tim Orling]

This is the core of one of the "new build system" tools--hosted
officially as part of the pypa (Python Packaging Authority)
repositories--it is an increasingly common build tool (e.g.
typing_extensions and tomli) as declared in pyproject.toml for
said packages.

This package provides a very simple bootstrapping method that builds
the source tarball (build_sdist) and a wheel (build_wheel).

Bootstrap -native by simply unzipping the wheel to
PYTHON_SITEPACKAGES_DIR.

Use pip to install the wheel for class-target.

Wheels are the official vehicle for delivering Python packages now.
Eggs (egg-info) are deprecated and will increasingly go away.

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/conf/distro/include/maintainers.inc  |  1 +
 .../python/python3-flit-core_3.6.0.bb | 41 +++
 2 files changed, 42 insertions(+)
 create mode 100644 meta/recipes-devtools/python/python3-flit-core_3.6.0.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index 72cd0125814..7a65612b7c6 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -599,6 +599,7 @@ RECIPE_MAINTAINER:pn-python3-pycryptodome = "Joshua Watt 
"
 RECIPE_MAINTAINER:pn-python3-pycryptodomex = "Joshua Watt 
"
 RECIPE_MAINTAINER:pn-python3-pyrsistent = "Bruce Ashfield 
"
 RECIPE_MAINTAINER:pn-python3-extras = "Oleksandr Kravchuk 
"
+RECIPE_MAINTAINER:pn-python3-flit-core = "Tim Orling "
 RECIPE_MAINTAINER:pn-python3-git = "Oleksandr Kravchuk 
"
 RECIPE_MAINTAINER:pn-python3-gitdb = "Oleksandr Kravchuk 
"
 RECIPE_MAINTAINER:pn-python3-hypothesis = "Tim Orling 
"
diff --git a/meta/recipes-devtools/python/python3-flit-core_3.6.0.bb 
b/meta/recipes-devtools/python/python3-flit-core_3.6.0.bb
new file mode 100644
index 000..d0b88c3fa50
--- /dev/null
+++ b/meta/recipes-devtools/python/python3-flit-core_3.6.0.bb
@@ -0,0 +1,41 @@
+LICENSE = "BSD-3-Clause"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=41eb78fa8a872983a882c694a8305f08"
+
+SRC_URI[sha256sum] = 
"b1464e006df4df4c8eeb37671c0e0ce66e1d04e4a36d91b702f180a25fde3c11"
+
+inherit python3native python3-dir pypi setuptools3-base
+
+DEPENDS:append:class-target = " python3-pip-native"
+DEPENDS:append:class-native = " unzip-native"
+
+# We need the full flit tarball
+PYPI_PACKAGE = "flit"
+
+do_compile () {
+nativepython3 flit_core/build_dists.py
+}
+
+do_install () {
+install -d ${D}${PYTHON_SITEPACKAGES_DIR}
+PYTHONPATH=${D}${PYTHON_SITEPACKAGES_DIR} \
+nativepython3 -m pip install - --no-deps --no-index --target 
${D}${PYTHON_SITEPACKAGES_DIR} ./flit_core/dist/flit_core-${PV}-py3-none-any.whl
+}
+
+do_install:class-native () {
+install -d ${D}${PYTHON_SITEPACKAGES_DIR}
+unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} 
./flit_core/dist/flit_core-${PV}-py3-none-any.whl
+}
+
+FILES:${PN} += "\
+${PYTHON_SITEPACKAGES_DIR}/flit_core/* \
+${PYTHON_SITEPACKAGES_DIR}/flit_core-${PV}.dist-info/* \
+"
+
+PACKAGES =+ "${PN}-tests"
+
+FILES:${PN}-tests += "\
+${PYTHON_SITEPACKAGES_DIR}/flit_core/tests/* \
+"
+
+BBCLASSEXTEND = "native nativesdk"
+
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162193): 
https://lists.openembedded.org/g/openembedded-core/message/162193
Mute This Topic: https://lists.openembedded.org/mt/89324644/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 01/32] python3-wheel: move 0.37.1 from meta-python

[Tim Orling]

This is one of the "new build tools" which are part of pypa (Python
Packaging Authority) toolchain.

Wheels are the official delivery mechanism for Python packages, replacing
the now deprecated Eggs (egg-info).

[YOCTO #14638]

Signed-off-by: Tim Orling 
---
 meta/conf/distro/include/maintainers.inc |  1 +
 meta/recipes-devtools/python/python3-wheel_0.37.1.bb | 12 
 2 files changed, 13 insertions(+)
 create mode 100644 meta/recipes-devtools/python/python3-wheel_0.37.1.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index 740e5fe55c4..72cd0125814 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -651,6 +651,7 @@ RECIPE_MAINTAINER:pn-python3-typogrify = "Alexander Kanavin 
https://github.com/pypa/wheel;
+SECTION = "devel/python"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://PKG-INFO;beginline=10;endline=10;md5=8227180126797a0148f94f483f3e1489"
+
+SRC_URI[sha256sum] = 
"e9a504e793efbca1b8e0e9cb979a249cf4a0a7b5b8c9e8b65a5e39d49529c1c4"
+
+inherit pypi setuptools3
+
+BBCLASSEXTEND = "native"
+
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162192): 
https://lists.openembedded.org/g/openembedded-core/message/162192
Mute This Topic: https://lists.openembedded.org/mt/89324643/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v3 00/32] Python PEP-517: build wheels and install with pip

[Tim Orling]

Upstream Python is moving to pyproject.toml rather than setup.py and
wheels rather than eggs. The main place this is documented is in
PEP-517[1]. Installing packages with setup.py install is deprecated.

We have a choice with the 'kirkstone' LTS release of introducing this
series (and fixing any fall out during the stabilization period) or
living with deprecated Python packaging for the duration of the LTS (at
a minimum 2 years). This seems to be a compelling enough reason to bring
in this series, even if it results in a slight slip of the 'feature
freeze', which is officially tomorrow, Monday 21 Feb, 2022.

This series bootstraps python3-setuptools-native,
python3-flit-core-native, python3-wheel-native and python3-pip-native,
simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows all
other recipes to be installed with pip, as intended by upstream.

Three new classes are introduced:
(1) flit_core which builds PEP-517 compliant packages which use
flit_core.buildapi as their build-backend.
(2) setuptools_build_meta which builds PEP-517 compliant packages which use
setuptools_build_meta  as their build-backend.
(3) pip_install_wheel, which simply installs wheels built by other
classes.

The original setuptools3.bbclass do_compile is modified to
'setup.py bdist_wheel' (from python3-wheel-native) rather than the deprecated
'setup.py build' mechanism. 

The original setuptools3.bbclass do_install is modified to
use the pip_install_wheel.bbclass to install wheels with pip rather than
the deprecated 'setup.py install' mechanism. 

For pip install, we disable dependency checking (--no-deps) because it
proves to be brittle in our environment without providing full wheel
cache that seems like overhead that we do not need. We also disable
fetching wheels from pypi (--no-index). This is no different than our
normal workflow of requiring dependencies to be defined in a recipe.

Missing from this series is documentation of the new features, classes
and variables (this will be done under separate cover).

Also desired and previously discussed in YP meetings is a helper
function to warn that a recipe which currently inherits setuptools3
but has a pyproject.toml and defines a build-system.build-backend should
instead use of the new PEP-517 classes. This function is still in progress.

During testing, recipes which use python3-setuptools-scm are failing to
determine the version of the python package, For several recipes, the fix
was to use pyproject.toml and PEP-517 build backends. To be sure, other recipes
are still going to fail for the short term, until the root cause can be
determined. This was not seen again in v2 builds.

Another PEP-517 build-backend, poetry.core.masonry.api has been
identified in recipes in meta-python, but not in oe-core. The
python3-poetry-core recipe is WIP, but brings in a number of
dependencies that are perhaps not worth it to bring into oe-core at this
time. Rather we can support these recipes in meta-python?

Fixes in v2 include passing --root=${D} to pip install (rather than --target)
and also passing --prefix so that scripts are (usually) installed in the proper
location. pip install also 'helpfully' overwrites python3 intepreter with 
nativepython3
in #!, so add a fix to return the values to what is actually correct (similar 
to what is
done in setuptools3.bbclass). Also several recipes still needed 
PIP_INSTALL_PACKAGE defined.

Fixes in v3 include:
* passing --force-reinstall to pip install to ensure FILES can be
  populated.
*  passing --no-cache to pip install to avoid a (harmless) warning about
  $HOME
* Fix check for ${D}${bindir}/pip in python3-pip-native (-e vs -f)
* Properly note that python3-wheel recipe is 0.37.1 not 0.37.0

[YOCTO #14638]

[1] https://www.python.org/dev/peps/pep-0517/

The following changes since commit 41ae26ecab731f2fb6593df143476c94183be209:

  releases: update to include 3.4.2 (2022-02-21 16:46:22 +)

are available in the Git repository at:

  git://git.yoctoproject.org/git/poky-contrib timo/bootstrap-wheels
  
http://git.yoctoproject.org/cgit.cgi/git/poky-contrib/log/?h=timo/bootstrap-wheels

Tim Orling (32):
  python3-wheel: move 0.37.1 from meta-python
  python3-flit-core: add recipe for 3.6.0
  flit_core.bbclass: add helper for newer python packaging
  python3-wheel: inherit flit_core
  pip_install_wheel.bbclass: add helper class
  setuptools_build_meta.bbclass: add helper class
  python3-pip: inherit setuptools_build_meta
  python3-attrs: inherit setuptools_build_meta
  python3-git: inherit setuptools_build_meta
  python3-pytest: inherit setuptools_build_meta
  python3-setuptools-scm: inherit setuptools_build_meta
  python3-zipp: inherit setuptools_build_meta
  python3-iniconfig: inherit setuptools_build_meta
  python3-py: inherit setuptools_build_meta
  python3-pluggy: inherit setuptools_build_meta
  python3-setuptools: inherit setuptools_base_meta
  setuptools3.bbclass: refactor for wheels
  python3-more-itertools: set 

[OE-core] [PATCH][RFC] cve-check: use local copy instead of global db

[Konrad Weihmann]

instead of using a global DB (default in DL_DIR) copy an existing
DB file into WORKDIR and use it from there.
This should avoid running into the reported "database is readonly" error
while at the same time there's no need to arbritrarily limit the
cve_check task to just one run at a time

Signed-off-by: Konrad Weihmann 
---
This patch should be tested by users that run cve-check on a regular
on hosts with as much as possible cores, before merging.
In local testing I haven't found any issues on a world build,
but as mentioned in the previous patch the issue is kind of hard to
reproduce.
So this patch aims at lifting the arbitrary task lock, while preventing
access by more than one thread/process at a time by sqlite.
Feedback through heavy local testing is very much appreciated

 meta/classes/cve-check.bbclass | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 21d3da7974..e4389b7001 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -28,6 +28,7 @@ CVE_VERSION ??= "${PV}"
 CVE_CHECK_DB_DIR ?= "${DL_DIR}/CVE_CHECK"
 CVE_CHECK_DB_FILE ?= "${CVE_CHECK_DB_DIR}/nvdcve_1.1.db"
 CVE_CHECK_DB_FILE_LOCK ?= "${CVE_CHECK_DB_FILE}.lock"
+CVE_CHECK_DB_FILE_LOCAL = 
"${WORKDIR}/${@os.path.basename(d.getVar('CVE_CHECK_DB_FILE'))}"
 
 CVE_CHECK_LOG ?= "${T}/cve.log"
 CVE_CHECK_TMP_FILE ?= "${TMPDIR}/cve_check"
@@ -94,9 +95,11 @@ python do_cve_check () {
 """
 Check recipe for patched and unpatched CVEs
 """
+import bb.utils
 from oe.cve_check import get_patched_cves
 
 if os.path.exists(d.getVar("CVE_CHECK_DB_FILE")):
+bb.utils.copyfile(d.getVar("CVE_CHECK_DB_FILE"), 
d.getVar("CVE_CHECK_DB_FILE_LOCAL"))
 try:
 patched_cves = get_patched_cves(d)
 except FileNotFoundError:
@@ -111,7 +114,6 @@ python do_cve_check () {
 }
 
 addtask cve_check before do_build after do_fetch
-do_cve_check[lockfiles] += "${CVE_CHECK_DB_FILE_LOCK}"
 do_cve_check[depends] = "cve-update-db-native:do_fetch"
 do_cve_check[nostamp] = "1"
 
@@ -185,7 +187,7 @@ def check_cves(d, patched_cves):
 cve_whitelist = d.getVar("CVE_CHECK_WHITELIST").split()
 
 import sqlite3
-db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
+db_file = d.expand("file:${CVE_CHECK_DB_FILE_LOCAL}?mode=ro")
 conn = sqlite3.connect(db_file, uri=True)
 
 # For each of the known product names (e.g. curl has CPEs using curl and 
libcurl)...
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162190): 
https://lists.openembedded.org/g/openembedded-core/message/162190
Mute This Topic: https://lists.openembedded.org/mt/89323890/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Tim Orling]

On Tue, Feb 22, 2022 at 10:39 AM Tim Orling  wrote:

>
>
> On Tue, Feb 22, 2022 at 10:24 AM Khem Raj  wrote:
>
>> On Tue, Feb 22, 2022 at 10:21 AM Tim Orling  wrote:
>> >
>> >
>> >
>> > On Tue, Feb 22, 2022 at 9:22 AM Khem Raj  wrote:
>> >>
>> >> this is going into dep loops Try
>> >>
>> >> bitbake python3-wheel-native
>> >
>> >
>> > It shouldn’t
>> >
>> https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/python/python3-wheel_0.37.1.bb?h=timo/bootstrap-wheels
>> >
>>
>> I have been trying whats on master-next
>>
>>
> I can't reproduce. Can you point me at an error log please?
> It might have something to do with sstate cache, but that's just a hunch.
>
>
Ah. I bet you have meta-python in the bblayers and therefore python3-wheel
recipe from meta-python is winning.


> > DEPENDS:remove:class-native = "python3-pip-native"
>> >
>> > do_install:class-native () {
>> > # We need to bootstrap python3-wheel-native
>> > install -d ${D}${PYTHON_SITEPACKAGES_DIR}
>> > PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
>> > unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
>> > bbfatal_log "Failed to install"
>> > }
>> >>
>> >>
>> >>
>> >>
>> >> On Mon, Feb 21, 2022 at 1:23 PM Tim Orling  wrote:
>> >> >
>> >> > Upstream Python is moving to pyproject.toml rather than setup.py and
>> >> > wheels rather than eggs. The main place this is documented is in
>> >> > PEP-517[1]. Installing packages with setup.py install is deprecated.
>> >> >
>> >> > We have a choice with the 'kirkstone' LTS release of introducing this
>> >> > series (and fixing any fall out during the stabilization period) or
>> >> > living with deprecated Python packaging for the duration of the LTS
>> (at
>> >> > a minimum 2 years). This seems to be a compelling enough reason to
>> bring
>> >> > in this series, even if it results in a slight slip of the 'feature
>> >> > freeze', which is officially tomorrow, Monday 21 Feb, 2022.
>> >> >
>> >> > This series bootstraps python3-setuptools-native,
>> >> > python3-flit-core-native, python3-wheel-native and
>> python3-pip-native,
>> >> > simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows
>> all
>> >> > other recipes to be installed with pip, as intended by upstream.
>> >> >
>> >> > Three new classes are introduced:
>> >> > (1) flit_core which builds PEP-517 compliant packages which use
>> >> > flit_core.buildapi as their build-backend.
>> >> > (2) setuptools_build_meta which builds PEP-517 compliant packages
>> which use
>> >> > setuptools_build_meta  as their build-backend.
>> >> > (3) pip_install_wheel, which simply installs wheels built by other
>> >> > classes.
>> >> >
>> >> > The original setuptools3.bbclass do_compile is modified to
>> >> > 'setup.py bdist_wheel' (from python3-wheel-native) rather than the
>> deprecated
>> >> > 'setup.py build' mechanism.
>> >> >
>> >> > The original setuptools3.bbclass do_install is modified to
>> >> > use the pip_install_wheel.bbclass to install wheels with pip rather
>> than
>> >> > the deprecated 'setup.py install' mechanism.
>> >> >
>> >> > For pip install, we disable dependency checking (--no-deps) because
>> it
>> >> > proves to be brittle in our environment without providing full wheel
>> >> > cache that seems like overhead that we do not need. We also disable
>> >> > fetching wheels from pypi (--no-index). This is no different than our
>> >> > normal workflow of requiring dependencies to be defined in a recipe.
>> >> >
>> >> > Missing from this series is documentation of the new features,
>> classes
>> >> > and variables (this will be done under separate cover).
>> >> >
>> >> > Also desired and previously discussed in YP meetings is a helper
>> >> > function to warn that a recipe which currently inherits setuptools3
>> >> > but has a pyproject.toml and defines a build-system.build-backend
>> should
>> >> > instead use of the new PEP-517 classes. This function is still in
>> progress.
>> >> >
>> >> > During testing, recipes which use python3-setuptools-scm are failing
>> to
>> >> > determine the version of the python package, For several recipes,
>> the fix
>> >> > was to use pyproject.toml and PEP-517 build backends. To be sure,
>> other recipes
>> >> > are still going to fail for the short term, until the root cause can
>> be
>> >> > determined. This was not seen again in v2 builds.
>> >> >
>> >> > Another PEP-517 build-backend, poetry.core.masonry.api has been
>> >> > identified in recipes in meta-python, but not in oe-core. The
>> >> > python3-poetry-core recipe is WIP, but brings in a number of
>> >> > dependencies that are perhaps not worth it to bring into oe-core at
>> this
>> >> > time. Rather we can support these recipes in meta-python?
>> >> >
>> >> > Fixes in v2 include passing --root=${D} to pip install (rather than
>> --target)
>> >> > and also passing --prefix so that scripts are (usually) installed in
>> the proper
>> >> > location. pip install also 'helpfully' overwrites 

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Tim Orling]

On Tue, Feb 22, 2022 at 10:24 AM Khem Raj  wrote:

> On Tue, Feb 22, 2022 at 10:21 AM Tim Orling  wrote:
> >
> >
> >
> > On Tue, Feb 22, 2022 at 9:22 AM Khem Raj  wrote:
> >>
> >> this is going into dep loops Try
> >>
> >> bitbake python3-wheel-native
> >
> >
> > It shouldn’t
> >
> https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/python/python3-wheel_0.37.1.bb?h=timo/bootstrap-wheels
> >
>
> I have been trying whats on master-next
>
>
I can't reproduce. Can you point me at an error log please?
It might have something to do with sstate cache, but that's just a hunch.


> > DEPENDS:remove:class-native = "python3-pip-native"
> >
> > do_install:class-native () {
> > # We need to bootstrap python3-wheel-native
> > install -d ${D}${PYTHON_SITEPACKAGES_DIR}
> > PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
> > unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
> > bbfatal_log "Failed to install"
> > }
> >>
> >>
> >>
> >>
> >> On Mon, Feb 21, 2022 at 1:23 PM Tim Orling  wrote:
> >> >
> >> > Upstream Python is moving to pyproject.toml rather than setup.py and
> >> > wheels rather than eggs. The main place this is documented is in
> >> > PEP-517[1]. Installing packages with setup.py install is deprecated.
> >> >
> >> > We have a choice with the 'kirkstone' LTS release of introducing this
> >> > series (and fixing any fall out during the stabilization period) or
> >> > living with deprecated Python packaging for the duration of the LTS
> (at
> >> > a minimum 2 years). This seems to be a compelling enough reason to
> bring
> >> > in this series, even if it results in a slight slip of the 'feature
> >> > freeze', which is officially tomorrow, Monday 21 Feb, 2022.
> >> >
> >> > This series bootstraps python3-setuptools-native,
> >> > python3-flit-core-native, python3-wheel-native and python3-pip-native,
> >> > simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows
> all
> >> > other recipes to be installed with pip, as intended by upstream.
> >> >
> >> > Three new classes are introduced:
> >> > (1) flit_core which builds PEP-517 compliant packages which use
> >> > flit_core.buildapi as their build-backend.
> >> > (2) setuptools_build_meta which builds PEP-517 compliant packages
> which use
> >> > setuptools_build_meta  as their build-backend.
> >> > (3) pip_install_wheel, which simply installs wheels built by other
> >> > classes.
> >> >
> >> > The original setuptools3.bbclass do_compile is modified to
> >> > 'setup.py bdist_wheel' (from python3-wheel-native) rather than the
> deprecated
> >> > 'setup.py build' mechanism.
> >> >
> >> > The original setuptools3.bbclass do_install is modified to
> >> > use the pip_install_wheel.bbclass to install wheels with pip rather
> than
> >> > the deprecated 'setup.py install' mechanism.
> >> >
> >> > For pip install, we disable dependency checking (--no-deps) because it
> >> > proves to be brittle in our environment without providing full wheel
> >> > cache that seems like overhead that we do not need. We also disable
> >> > fetching wheels from pypi (--no-index). This is no different than our
> >> > normal workflow of requiring dependencies to be defined in a recipe.
> >> >
> >> > Missing from this series is documentation of the new features, classes
> >> > and variables (this will be done under separate cover).
> >> >
> >> > Also desired and previously discussed in YP meetings is a helper
> >> > function to warn that a recipe which currently inherits setuptools3
> >> > but has a pyproject.toml and defines a build-system.build-backend
> should
> >> > instead use of the new PEP-517 classes. This function is still in
> progress.
> >> >
> >> > During testing, recipes which use python3-setuptools-scm are failing
> to
> >> > determine the version of the python package, For several recipes, the
> fix
> >> > was to use pyproject.toml and PEP-517 build backends. To be sure,
> other recipes
> >> > are still going to fail for the short term, until the root cause can
> be
> >> > determined. This was not seen again in v2 builds.
> >> >
> >> > Another PEP-517 build-backend, poetry.core.masonry.api has been
> >> > identified in recipes in meta-python, but not in oe-core. The
> >> > python3-poetry-core recipe is WIP, but brings in a number of
> >> > dependencies that are perhaps not worth it to bring into oe-core at
> this
> >> > time. Rather we can support these recipes in meta-python?
> >> >
> >> > Fixes in v2 include passing --root=${D} to pip install (rather than
> --target)
> >> > and also passing --prefix so that scripts are (usually) installed in
> the proper
> >> > location. pip install also 'helpfully' overwrites python3 intepreter
> with nativepython3
> >> > in #!, so add a fix to return the values to what is actually correct
> (similar to what is
> >> > done in setuptools3.bbclass). Also several recipes still needed
> PIP_INSTALL_PACKAGE defined.
> >> >
> >> > Also added self as maintainer of new recipes.

Re: [OE-core] [RFC PATCH 7/8] rust: Add snapshot checksums for powerpc64le

[Khem Raj]

On Tue, Feb 22, 2022 at 6:24 AM Alexander Kanavin
 wrote:
>
> On Tue, 22 Feb 2022 at 13:28, Richard Purdie
>  wrote:
> >
> > On Tue, 2022-02-22 at 10:59 +0100, Alexander Kanavin wrote:
> > > I have to note that YP does not support ppc systems as build hosts;
> > > can this be kept in a bbappend?
> >
> > It isn't official but there are obviously people using it. I think we 
> > should try
> > and do something in core but there is a question of how we maintain this 
> > given
> > our infrastructure/tests don't cover it :(
>
> Worse yet, there is no way to test this locally either.  If the ppc64
> binary tarball checksums are added to the core rust recipe, presumably
> I'd be expected to update them together with x86 and arm64 binary
> checksums on version updates, but I'd have to do this completely
> blindly with no testing of any kind :(

as long as it does not impede main testing I would think thats ok and
we can expect the OE community
members like Andrew to test this and report issues or better fix them

That's why I am asking to keep
> them in an external bbappend.
>
> Andrew, how hard is it to obtain a shell on ppc64 machines nowadays?
> Is it something specific to your employer?
>
> Alex
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162187): 
https://lists.openembedded.org/g/openembedded-core/message/162187
Mute This Topic: https://lists.openembedded.org/mt/89310363/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Khem Raj]

On Tue, Feb 22, 2022 at 10:21 AM Tim Orling  wrote:
>
>
>
> On Tue, Feb 22, 2022 at 9:22 AM Khem Raj  wrote:
>>
>> this is going into dep loops Try
>>
>> bitbake python3-wheel-native
>
>
> It shouldn’t
> https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/python/python3-wheel_0.37.1.bb?h=timo/bootstrap-wheels
>

I have been trying whats on master-next

> DEPENDS:remove:class-native = "python3-pip-native"
>
> do_install:class-native () {
> # We need to bootstrap python3-wheel-native
> install -d ${D}${PYTHON_SITEPACKAGES_DIR}
> PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
> unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
> bbfatal_log "Failed to install"
> }
>>
>>
>>
>>
>> On Mon, Feb 21, 2022 at 1:23 PM Tim Orling  wrote:
>> >
>> > Upstream Python is moving to pyproject.toml rather than setup.py and
>> > wheels rather than eggs. The main place this is documented is in
>> > PEP-517[1]. Installing packages with setup.py install is deprecated.
>> >
>> > We have a choice with the 'kirkstone' LTS release of introducing this
>> > series (and fixing any fall out during the stabilization period) or
>> > living with deprecated Python packaging for the duration of the LTS (at
>> > a minimum 2 years). This seems to be a compelling enough reason to bring
>> > in this series, even if it results in a slight slip of the 'feature
>> > freeze', which is officially tomorrow, Monday 21 Feb, 2022.
>> >
>> > This series bootstraps python3-setuptools-native,
>> > python3-flit-core-native, python3-wheel-native and python3-pip-native,
>> > simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows all
>> > other recipes to be installed with pip, as intended by upstream.
>> >
>> > Three new classes are introduced:
>> > (1) flit_core which builds PEP-517 compliant packages which use
>> > flit_core.buildapi as their build-backend.
>> > (2) setuptools_build_meta which builds PEP-517 compliant packages which use
>> > setuptools_build_meta  as their build-backend.
>> > (3) pip_install_wheel, which simply installs wheels built by other
>> > classes.
>> >
>> > The original setuptools3.bbclass do_compile is modified to
>> > 'setup.py bdist_wheel' (from python3-wheel-native) rather than the 
>> > deprecated
>> > 'setup.py build' mechanism.
>> >
>> > The original setuptools3.bbclass do_install is modified to
>> > use the pip_install_wheel.bbclass to install wheels with pip rather than
>> > the deprecated 'setup.py install' mechanism.
>> >
>> > For pip install, we disable dependency checking (--no-deps) because it
>> > proves to be brittle in our environment without providing full wheel
>> > cache that seems like overhead that we do not need. We also disable
>> > fetching wheels from pypi (--no-index). This is no different than our
>> > normal workflow of requiring dependencies to be defined in a recipe.
>> >
>> > Missing from this series is documentation of the new features, classes
>> > and variables (this will be done under separate cover).
>> >
>> > Also desired and previously discussed in YP meetings is a helper
>> > function to warn that a recipe which currently inherits setuptools3
>> > but has a pyproject.toml and defines a build-system.build-backend should
>> > instead use of the new PEP-517 classes. This function is still in progress.
>> >
>> > During testing, recipes which use python3-setuptools-scm are failing to
>> > determine the version of the python package, For several recipes, the fix
>> > was to use pyproject.toml and PEP-517 build backends. To be sure, other 
>> > recipes
>> > are still going to fail for the short term, until the root cause can be
>> > determined. This was not seen again in v2 builds.
>> >
>> > Another PEP-517 build-backend, poetry.core.masonry.api has been
>> > identified in recipes in meta-python, but not in oe-core. The
>> > python3-poetry-core recipe is WIP, but brings in a number of
>> > dependencies that are perhaps not worth it to bring into oe-core at this
>> > time. Rather we can support these recipes in meta-python?
>> >
>> > Fixes in v2 include passing --root=${D} to pip install (rather than 
>> > --target)
>> > and also passing --prefix so that scripts are (usually) installed in the 
>> > proper
>> > location. pip install also 'helpfully' overwrites python3 intepreter with 
>> > nativepython3
>> > in #!, so add a fix to return the values to what is actually correct 
>> > (similar to what is
>> > done in setuptools3.bbclass). Also several recipes still needed 
>> > PIP_INSTALL_PACKAGE defined.
>> >
>> > Also added self as maintainer of new recipes.
>> >
>> > [YOCTO #14638]
>> >
>> > [1] https://www.python.org/dev/peps/pep-0517/
>> >
>> > The following changes since commit 
>> > 41ae26ecab731f2fb6593df143476c94183be209:
>> >
>> >   releases: update to include 3.4.2 (2022-02-21 16:46:22 +)
>> >
>> > are available in the Git repository at:
>> >
>> >   git://git.yoctoproject.org/git/poky-contrib timo/bootstrap-wheels

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Tim Orling]

On Tue, Feb 22, 2022 at 9:22 AM Khem Raj  wrote:

> this is going into dep loops Try
>
> bitbake python3-wheel-native


It shouldn’t
https://git.yoctoproject.org/poky-contrib/tree/meta/recipes-devtools/python/python3-wheel_0.37.1.bb?h=timo/bootstrap-wheels

DEPENDS:remove:class-native = "python3-pip-native"
do_install:class-native () {
# We need to bootstrap python3-wheel-native
install -d ${D}${PYTHON_SITEPACKAGES_DIR}
PYPA_WHEEL="${B}/dist/${PYPI_PACKAGE}-${PV}-*.whl"
unzip -d ${D}${PYTHON_SITEPACKAGES_DIR} ${PYPA_WHEEL} || \
bbfatal_log "Failed to install"}


>
>
> On Mon, Feb 21, 2022 at 1:23 PM Tim Orling  wrote:
> >
> > Upstream Python is moving to pyproject.toml rather than setup.py and
> > wheels rather than eggs. The main place this is documented is in
> > PEP-517[1]. Installing packages with setup.py install is deprecated.
> >
> > We have a choice with the 'kirkstone' LTS release of introducing this
> > series (and fixing any fall out during the stabilization period) or
> > living with deprecated Python packaging for the duration of the LTS (at
> > a minimum 2 years). This seems to be a compelling enough reason to bring
> > in this series, even if it results in a slight slip of the 'feature
> > freeze', which is officially tomorrow, Monday 21 Feb, 2022.
> >
> > This series bootstraps python3-setuptools-native,
> > python3-flit-core-native, python3-wheel-native and python3-pip-native,
> > simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows all
> > other recipes to be installed with pip, as intended by upstream.
> >
> > Three new classes are introduced:
> > (1) flit_core which builds PEP-517 compliant packages which use
> > flit_core.buildapi as their build-backend.
> > (2) setuptools_build_meta which builds PEP-517 compliant packages which
> use
> > setuptools_build_meta  as their build-backend.
> > (3) pip_install_wheel, which simply installs wheels built by other
> > classes.
> >
> > The original setuptools3.bbclass do_compile is modified to
> > 'setup.py bdist_wheel' (from python3-wheel-native) rather than the
> deprecated
> > 'setup.py build' mechanism.
> >
> > The original setuptools3.bbclass do_install is modified to
> > use the pip_install_wheel.bbclass to install wheels with pip rather than
> > the deprecated 'setup.py install' mechanism.
> >
> > For pip install, we disable dependency checking (--no-deps) because it
> > proves to be brittle in our environment without providing full wheel
> > cache that seems like overhead that we do not need. We also disable
> > fetching wheels from pypi (--no-index). This is no different than our
> > normal workflow of requiring dependencies to be defined in a recipe.
> >
> > Missing from this series is documentation of the new features, classes
> > and variables (this will be done under separate cover).
> >
> > Also desired and previously discussed in YP meetings is a helper
> > function to warn that a recipe which currently inherits setuptools3
> > but has a pyproject.toml and defines a build-system.build-backend should
> > instead use of the new PEP-517 classes. This function is still in
> progress.
> >
> > During testing, recipes which use python3-setuptools-scm are failing to
> > determine the version of the python package, For several recipes, the fix
> > was to use pyproject.toml and PEP-517 build backends. To be sure, other
> recipes
> > are still going to fail for the short term, until the root cause can be
> > determined. This was not seen again in v2 builds.
> >
> > Another PEP-517 build-backend, poetry.core.masonry.api has been
> > identified in recipes in meta-python, but not in oe-core. The
> > python3-poetry-core recipe is WIP, but brings in a number of
> > dependencies that are perhaps not worth it to bring into oe-core at this
> > time. Rather we can support these recipes in meta-python?
> >
> > Fixes in v2 include passing --root=${D} to pip install (rather than
> --target)
> > and also passing --prefix so that scripts are (usually) installed in the
> proper
> > location. pip install also 'helpfully' overwrites python3 intepreter
> with nativepython3
> > in #!, so add a fix to return the values to what is actually correct
> (similar to what is
> > done in setuptools3.bbclass). Also several recipes still needed
> PIP_INSTALL_PACKAGE defined.
> >
> > Also added self as maintainer of new recipes.
> >
> > [YOCTO #14638]
> >
> > [1] https://www.python.org/dev/peps/pep-0517/
> >
> > The following changes since commit
> 41ae26ecab731f2fb6593df143476c94183be209:
> >
> >   releases: update to include 3.4.2 (2022-02-21 16:46:22 +)
> >
> > are available in the Git repository at:
> >
> >   git://git.yoctoproject.org/git/poky-contrib timo/bootstrap-wheels
> >
> http://git.yoctoproject.org/cgit.cgi/git/poky-contrib/log/?h=timo/bootstrap-wheels
> >
> > Tim Orling (32):
> >   python3-wheel: move 0.37.0 from meta-python
> >   python3-flit-core: add recipe for 3.6.0
> >   flit_core.bbclass: add helper 

Re: [OE-core] [PATCH v3] patch.py: Prevent git repo reinitialization

[Christian Eggers]

On Monday, 21 February 2022, 20:17:29 CET, Pavel Zhukov wrote:
> There were few bugs in the _isInitialized() function which might trigger
> git repo to be reinitialized and patches failing to apply.
> 
> Signed-off-by: Pavel Zhukov 
> ---
>  .../recipes-test/gitrepotest/gitrepotest.bb   | 16 
>  .../gitrepotest/0001-testpatch.patch  |  9 +
>  meta/lib/oe/patch.py  | 11 ---
>  meta/lib/oeqa/selftest/cases/bbtests.py   | 19 +--
>  4 files changed, 50 insertions(+), 5 deletions(-)
>  create mode 100644 meta-selftest/recipes-test/gitrepotest/gitrepotest.bb
>  create mode 100644 
> meta-selftest/recipes-test/gitrepotest/gitrepotest/0001-testpatch.patch
> 
> diff --git a/meta-selftest/recipes-test/gitrepotest/gitrepotest.bb 
> b/meta-selftest/recipes-test/gitrepotest/gitrepotest.bb
> new file mode 100644
> index 00..f1b6c55833
> --- /dev/null
> +++ b/meta-selftest/recipes-test/gitrepotest/gitrepotest.bb
> @@ -0,0 +1,16 @@
> +SUMMARY = "Test recipe for git repo initialization"
> +HOMEPAGE = "https://git.yoctoproject.org/git/matchbox-panel-2;
> +LICENSE = "GPL-2.0-or-later"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
> +
> +INHIBIT_DEFAULT_DEPS = "1"
> +
> +PATCHTOOL="git"
> +
> +SRC_URI = 
> "git://git.yoctoproject.org/git/matchbox-panel-2;branch=master;protocol=https 
> \
> +   file://0001-testpatch.patch \
> +  "
> +
> +SRCREV = "f82ca3f42510fb3ef10f598b393eb373a2c34ca7"
> +
> +S = "${WORKDIR}/git"
> diff --git 
> a/meta-selftest/recipes-test/gitrepotest/gitrepotest/0001-testpatch.patch 
> b/meta-selftest/recipes-test/gitrepotest/gitrepotest/0001-testpatch.patch
> new file mode 100644
> index 00..bccda17ee9
> --- /dev/null
> +++ b/meta-selftest/recipes-test/gitrepotest/gitrepotest/0001-testpatch.patch
> @@ -0,0 +1,9 @@
> +diff --git a/Makefile.am b/Makefile.am
> +index 432a9b4..bbf7c74 100644
> +--- a/Makefile.am
>  b/Makefile.am
> +@@ -1,3 +1,4 @@
> ++## This is useless comment to test if patch works
> + ACLOCAL_AMFLAGS = -I m4
> + 
> + SUBDIRS = matchbox-panel applets data po
> diff --git a/meta/lib/oe/patch.py b/meta/lib/oe/patch.py
> index 950fe723dc..9034fcae03 100644
> --- a/meta/lib/oe/patch.py
> +++ b/meta/lib/oe/patch.py
> @@ -304,14 +304,19 @@ class GitApplyTree(PatchTree):
>  
>  def _isInitialized(self):
>  cmd = "git rev-parse --show-toplevel"
> -(status, output) = subprocess.getstatusoutput(cmd.split())
> +try:
> +output = runcmd(cmd.split(), self.dir).strip()
> +except CmdError as err:
> +## runcmd returned non-zero which most likely means 128
> +## Not a git directory
> +return False
>  ## Make sure repo is in builddir to not break top-level git repos
> -return status == 0 and os.path.samedir(output, self.dir)
> +return os.path.samefile(output, self.dir)

output = 
/home/eggers/<...>/build/devel-kirkstone/tmp/work-shared/orbiter/kernel-source
self.dir = 
/home/eggers/<...>/build/devel-kirkstone/tmp/work/orbiter-poky-linux-musleabi/linux-stable-rt/5.10.100-rt62-orbiter+gitAUTOINC+ca44e6dff2-r0/git
os.path.samefile(output, self.dir) = 1

Looks fine now. The build on the affected CI machine is also fixed.

>  
>  def _initRepo(self):
>  runcmd("git init".split(), self.dir)
>  runcmd("git add .".split(), self.dir)
> -runcmd("git commit -a --allow-empty -m Patching_started".split(), 
> self.dir)
> +runcmd("git commit -a --allow-empty -m 
> bitbake_patching_started".split(), self.dir)
>  
>  @staticmethod
>  def extractPatchHeader(patchfile):
> diff --git a/meta/lib/oeqa/selftest/cases/bbtests.py 
> b/meta/lib/oeqa/selftest/cases/bbtests.py
> index ce72c4bcc6..35ad9f3cd6 100644
> --- a/meta/lib/oeqa/selftest/cases/bbtests.py
> +++ b/meta/lib/oeqa/selftest/cases/bbtests.py
> @@ -307,11 +307,26 @@ INHERIT:remove = \"report-error\"
>  src = get_bb_var("SRC_URI",test_recipe)
>  gitscm = re.search("git://", src)
>  self.assertFalse(gitscm, "test_git_patchtool pre-condition failed: 
> {} test recipe contains git repo!".format(test_recipe))
> -result = bitbake('man-db -c patch', ignore_status=False)
> +result = bitbake('{} -c patch'.format(test_recipe), 
> ignore_status=False)
>  fatal = re.search("fatal: not a git repository (or any of the parent 
> directories)", result.output)
>  self.assertFalse(fatal, "Failed to patch using PATCHTOOL=\"git\"")
>  self.delete_recipeinc(test_recipe)
> -bitbake('-cclean man-db')
> +bitbake('-cclean {}'.format(test_recipe))
> +
> +def test_git_patchtool2(self):
> +""" Test if PATCHTOOL=git works with git repo and doesn't 
> reinitialize it
> +"""
> +test_recipe = "gitrepotest"
> +src = get_bb_var("SRC_URI",test_recipe)
> +gitscm = re.search("git://", 

Re: [OE-core] [PATCH][RFC] cve-check: add lockfile to task

[Konrad Weihmann]

On 22.02.22 18:50, Ross Burton wrote:

On Tue, 22 Feb 2022 at 17:01, Konrad Weihmann  wrote:

This is somehow expected from my side tbh - as the lock file disables
any kind of parallelism - so just one instance of cve-check-task can run
at a time.
One thing that came to my mind is to move the created CVE_CHECK-sqlite
db into the recipe-sysroot before running the task (currently it resides
in DL_DIR), so each task would run on its own copy of the db - that
would avoid having multiple access call to the same file while enabling
us to remove the arbitrary task lock.


Hang on - surely the cve_check tasks are read-only, so why do we need
to lock the database?

Ross


TBH I don't know - I (and Ralph confirmed that) see occasionally this 
error from the original patch.
As I mentioned I lack the experience with sqlite to get to the bottom of 
it - all I can say is that since the task lock had been merged I'm error 
free in all the pipelines I monitor

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162183): 
https://lists.openembedded.org/g/openembedded-core/message/162183
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH][RFC] cve-check: add lockfile to task

[Ross Burton]

On Tue, 22 Feb 2022 at 17:01, Konrad Weihmann  wrote:
> This is somehow expected from my side tbh - as the lock file disables
> any kind of parallelism - so just one instance of cve-check-task can run
> at a time.
> One thing that came to my mind is to move the created CVE_CHECK-sqlite
> db into the recipe-sysroot before running the task (currently it resides
> in DL_DIR), so each task would run on its own copy of the db - that
> would avoid having multiple access call to the same file while enabling
> us to remove the arbitrary task lock.

Hang on - surely the cve_check tasks are read-only, so why do we need
to lock the database?

Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162182): 
https://lists.openembedded.org/g/openembedded-core/message/162182
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH][RFC] cve-check: add lockfile to task

[Ralph Siemsen]

On Tue, Feb 22, 2022 at 06:01:00PM +0100, Konrad Weihmann wrote:


This is somehow expected from my side tbh - as the lock file disables 
any kind of parallelism - so just one instance of cve-check-task can 
run at a time.


That likely explains why the loadavg is only around 1 during cve-check.

One thing that came to my mind is to move the created CVE_CHECK-sqlite 
db into the recipe-sysroot before running the task (currently it 
resides in DL_DIR), so each task would run on its own copy of the db - 
that would avoid having multiple access call to the same file while 
enabling us to remove the arbitrary task lock.


I actually do something like this manually - in local.conf for each of 
my builds, I set CVE_CHECK_DB_DIR to a unique subdirectory within 
$DL_DIR. And I still see the occasional build failure due to "database 
in use".


Ralph


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162181): 
https://lists.openembedded.org/g/openembedded-core/message/162181
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 00/32] Python PEP-517: build wheels and install with pip

[Khem Raj]

this is going into dep loops Try

bitbake python3-wheel-native


On Mon, Feb 21, 2022 at 1:23 PM Tim Orling  wrote:
>
> Upstream Python is moving to pyproject.toml rather than setup.py and
> wheels rather than eggs. The main place this is documented is in
> PEP-517[1]. Installing packages with setup.py install is deprecated.
>
> We have a choice with the 'kirkstone' LTS release of introducing this
> series (and fixing any fall out during the stabilization period) or
> living with deprecated Python packaging for the duration of the LTS (at
> a minimum 2 years). This seems to be a compelling enough reason to bring
> in this series, even if it results in a slight slip of the 'feature
> freeze', which is officially tomorrow, Monday 21 Feb, 2022.
>
> This series bootstraps python3-setuptools-native,
> python3-flit-core-native, python3-wheel-native and python3-pip-native,
> simply unzipping the wheel into PYTHON_SITEPACKAGES_DIR. This allows all
> other recipes to be installed with pip, as intended by upstream.
>
> Three new classes are introduced:
> (1) flit_core which builds PEP-517 compliant packages which use
> flit_core.buildapi as their build-backend.
> (2) setuptools_build_meta which builds PEP-517 compliant packages which use
> setuptools_build_meta  as their build-backend.
> (3) pip_install_wheel, which simply installs wheels built by other
> classes.
>
> The original setuptools3.bbclass do_compile is modified to
> 'setup.py bdist_wheel' (from python3-wheel-native) rather than the deprecated
> 'setup.py build' mechanism.
>
> The original setuptools3.bbclass do_install is modified to
> use the pip_install_wheel.bbclass to install wheels with pip rather than
> the deprecated 'setup.py install' mechanism.
>
> For pip install, we disable dependency checking (--no-deps) because it
> proves to be brittle in our environment without providing full wheel
> cache that seems like overhead that we do not need. We also disable
> fetching wheels from pypi (--no-index). This is no different than our
> normal workflow of requiring dependencies to be defined in a recipe.
>
> Missing from this series is documentation of the new features, classes
> and variables (this will be done under separate cover).
>
> Also desired and previously discussed in YP meetings is a helper
> function to warn that a recipe which currently inherits setuptools3
> but has a pyproject.toml and defines a build-system.build-backend should
> instead use of the new PEP-517 classes. This function is still in progress.
>
> During testing, recipes which use python3-setuptools-scm are failing to
> determine the version of the python package, For several recipes, the fix
> was to use pyproject.toml and PEP-517 build backends. To be sure, other 
> recipes
> are still going to fail for the short term, until the root cause can be
> determined. This was not seen again in v2 builds.
>
> Another PEP-517 build-backend, poetry.core.masonry.api has been
> identified in recipes in meta-python, but not in oe-core. The
> python3-poetry-core recipe is WIP, but brings in a number of
> dependencies that are perhaps not worth it to bring into oe-core at this
> time. Rather we can support these recipes in meta-python?
>
> Fixes in v2 include passing --root=${D} to pip install (rather than --target)
> and also passing --prefix so that scripts are (usually) installed in the 
> proper
> location. pip install also 'helpfully' overwrites python3 intepreter with 
> nativepython3
> in #!, so add a fix to return the values to what is actually correct (similar 
> to what is
> done in setuptools3.bbclass). Also several recipes still needed 
> PIP_INSTALL_PACKAGE defined.
>
> Also added self as maintainer of new recipes.
>
> [YOCTO #14638]
>
> [1] https://www.python.org/dev/peps/pep-0517/
>
> The following changes since commit 41ae26ecab731f2fb6593df143476c94183be209:
>
>   releases: update to include 3.4.2 (2022-02-21 16:46:22 +)
>
> are available in the Git repository at:
>
>   git://git.yoctoproject.org/git/poky-contrib timo/bootstrap-wheels
>   
> http://git.yoctoproject.org/cgit.cgi/git/poky-contrib/log/?h=timo/bootstrap-wheels
>
> Tim Orling (32):
>   python3-wheel: move 0.37.0 from meta-python
>   python3-flit-core: add recipe for 3.6.0
>   flit_core.bbclass: add helper for newer python packaging
>   python3-wheel: inherit flit_core
>   pip_install_wheel.bbclass: add helper class
>   setuptools_build_meta.bbclass: add helper class
>   python3-pip: inherit setuptools_build_meta
>   python3-attrs: inherit setuptools_build_meta
>   python3-git: inherit setuptools_build_meta
>   python3-pytest: inherit setuptools_build_meta
>   python3-setuptools-scm: inherit setuptools_build_meta
>   python3-zipp: inherit setuptools_build_meta
>   python3-iniconfig: inherit setuptools_build_meta
>   python3-py: inherit setuptools_build_meta
>   python3-pluggy: inherit setuptools_build_meta
>   python3-setuptools: inherit setuptools_base_meta
>   setuptools3.bbclass: refactor 

Re: [OE-core] [PATCH][RFC] cve-check: add lockfile to task

[Konrad Weihmann]

On 22.02.22 16:50, Ralph Siemsen wrote:

Hi Konrad,

On Fri, Jan 7, 2022 at 4:59 AM Konrad Weihmann > wrote:


On 07.01.22 10:48, Konrad Weihmann wrote:
 > this should prevent running into the very rare error
 > sqlite3.OperationalError: attempt to write a readonly database

It's also possible that check_same_thread (that defaults to True ) in
the sqlite3.connect causes this (see
https://docs.python.org/3/library/sqlite3.html#sqlite3.connect
) -
I have
too little experience with sqlite to provide any further input.

I'd be happy to get some feedback from users that do have that
experience with sqlite in a highly multithreaded/multiprocess
environment. Or by people that use cvecheck class in larger setups than
just core.


Afraid I am not well versed in the internals of sqlite, so I cannot 
comment on that part.


However, I do run cve-check on a larger setup than core, and after this 
commit recently landed in dunfell branch, I noticed that do_cve_check 
step is taking considerably longer than it used to. I have not 
benchmarked it carefully, but visually from watching the console during 
the build, it seems to be somewhere from 2 to 5 times slower. This is 
running a native build on an ext4 filesystem (not using containers etc).


This is somehow expected from my side tbh - as the lock file disables 
any kind of parallelism - so just one instance of cve-check-task can run 
at a time.
One thing that came to my mind is to move the created CVE_CHECK-sqlite 
db into the recipe-sysroot before running the task (currently it resides 
in DL_DIR), so each task would run on its own copy of the db - that 
would avoid having multiple access call to the same file while enabling 
us to remove the arbitrary task lock.




Are others seeing similar behaviour?

While I am writing, I should also mention that the CVE JSON feeds are 
apparently going to be changing (again).
https://www.cve.org/Media/News/item/news/2022/01/11/Changes-Coming-to-CVE-Record 


I wonder if we should perhaps move instead to using the git repo:
https://github.com/CVEProject/cvelist 
  (existing v4 format)
https://github.com/CVEProject/cvelistV5 
 (preview of upcoming v5 format)
This would not solve the sqlite locking issue, though perhaps we could 
sidestep it and just search the json directly?

I guess I should really start a separate thread about this ;-)

Regards,
Ralph

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162179): 
https://lists.openembedded.org/g/openembedded-core/message/162179
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH][RFC] cve-check: add lockfile to task

[Ross Burton]

On Tue, 22 Feb 2022 at 15:50, Ralph Siemsen  wrote:
> While I am writing, I should also mention that the CVE JSON feeds are 
> apparently going to be changing (again).
> https://www.cve.org/Media/News/item/news/2022/01/11/Changes-Coming-to-CVE-Record
> I wonder if we should perhaps move instead to using the git repo:
> https://github.com/CVEProject/cvelist  (existing v4 format)
> https://github.com/CVEProject/cvelistV5 (preview of upcoming v5 format)
> This would not solve the sqlite locking issue, though perhaps we could 
> sidestep it and just search the json directly?
> I guess I should really start a separate thread about this ;-)

Urgh. Thanks for bringing this to our attention.

Can you file a bug?

Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162178): 
https://lists.openembedded.org/g/openembedded-core/message/162178
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Yocto Project Status WW08`22

[Stephen Jolley]

Current Dev Position: YP 3.5 M4

Next Deadline: 4th April. 2022 YP 3.5 M4 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Feb. 24th 7:30 am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Mar. 1st at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Feb. 22nd at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   We are now at feature freeze for 3.5, our next LTS release
*   YP 3.1.14 and YP 3.2.4 were released
*   YP 3.3.5 is in QA
*   After a last minute push, the base set of inclusive language changes
have merged. There is a conversion script which can be run to convert
layers. Not all changes needed have been written yet but enough are present
to allow the conversion process to start.
*   There were also changes to convert LICENSE fields to use SPDX
identifiers and there is a second conversion script for this that can be
used.
*   We have updated the core layer series name to kirkstone and other
layers will now need to update to confirm compatibility with kirkstone.
*   There is a patchset to update python's build processes to use the
upstream preferred wheel approach which would aid support of python over the
next few years. It is late in the cycle for this kind of change but we will
give this series a few days of testing to make a decision and welcome user
feedback either way on these changes.
*   As such, the M3 release build will likely not happen until early
next week.
*   The autobuilder infrastructure is planned to be offline 26-28th
February for a data center move. Public services like the website, wiki and
git servers will remain live but the git backend (push.yoctoproject.org)
will be offline, as will the downloads and sstate services and the
autobuilder/NAS.
*   Capacity has been improved on the sstate server which was causing
intermittent timeout issues for downloads.
*   Intermittent issues continue to be at record high levels and help is
very much welcome in trying to resolve them. You can see the list of
failures we're continuing to see by searching for the "AB-INT" tag in
bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

In particular, we're struggling to understand the intermittent network issue
with external hosts we're seeing very occasionally.

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.5. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.
*   Help us resolve CVE issues:
 CVE metrics 

 

YP 3.5 Milestone Dates:

*   YP 3.5 M3 build date 2022/02/21
*   YP 3.5 M3 Release date 2022/03/04
*   YP 3.5 M4 build date 2022/04/04
*   YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

*   YP 3.1.14  is released
*   YP 3.4.2 is released
*   YP 3.3.5  is in QA
*   YP 3.3.5 Release date 2022/02/25
*   YP 3.1.15 build date 2022/03/14
*   YP 3.1.15 Release date 2022/03/25
*   YP 3.4.3 build date 2022/03/21
*   YP 3.4.3 Release date 2022/04/01
*   YP 3.3.6 build date 2022/03/28
*   YP 3.3.6 Release date 2022/04/08
*   YP 3.1.16 build date 2022/04/25
*   YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

*   WDD 2652 (last week 2662) (

https://wiki.yoctoproject.org/charts/combo.html)
*   OE-Core/Poky Patch Metrics

*   Total patches found: 1202 (last week 1208)
*   Patches in the Pending State: 334 (28%) [last week 334 (28%)]

 

The Yocto Project's technical governance is 

Re: [OE-core] [PATCH][RFC] cve-check: add lockfile to task

[Ralph Siemsen]

Hi Konrad,

On Fri, Jan 7, 2022 at 4:59 AM Konrad Weihmann 
wrote:

> On 07.01.22 10:48, Konrad Weihmann wrote:
> > this should prevent running into the very rare error
> > sqlite3.OperationalError: attempt to write a readonly database
>
> It's also possible that check_same_thread (that defaults to True ) in
> the sqlite3.connect causes this (see
> https://docs.python.org/3/library/sqlite3.html#sqlite3.connect) - I have
> too little experience with sqlite to provide any further input.
>
> I'd be happy to get some feedback from users that do have that
> experience with sqlite in a highly multithreaded/multiprocess
> environment. Or by people that use cvecheck class in larger setups than
> just core.
>

Afraid I am not well versed in the internals of sqlite, so I cannot comment
on that part.

However, I do run cve-check on a larger setup than core, and after this
commit recently landed in dunfell branch, I noticed that do_cve_check step
is taking considerably longer than it used to. I have not benchmarked it
carefully, but visually from watching the console during the build, it
seems to be somewhere from 2 to 5 times slower. This is running a native
build on an ext4 filesystem (not using containers etc).

Are others seeing similar behaviour?

While I am writing, I should also mention that the CVE JSON feeds are
apparently going to be changing (again).
https://www.cve.org/Media/News/item/news/2022/01/11/Changes-Coming-to-CVE-Record
I wonder if we should perhaps move instead to using the git repo:
https://github.com/CVEProject/cvelist  (existing v4 format)
https://github.com/CVEProject/cvelistV5 (preview of upcoming v5 format)
This would not solve the sqlite locking issue, though perhaps we could
sidestep it and just search the json directly?
I guess I should really start a separate thread about this ;-)

Regards,
Ralph

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162176): 
https://lists.openembedded.org/g/openembedded-core/message/162176
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Yocto Project Status WW08`22

[Stephen Jolley]

Current Dev Position: YP 3.5 M4

Next Deadline: 4th April. 2022 YP 3.5 M4 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Feb. 25th 7:30 am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Mar. 1st at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Feb. 23rd at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   We are now at feature freeze for 3.5, our next LTS release
*   YP 3.1.14 and YP 3.2.4 were released
*   YP 3.3.5 is in QA
*   After a last minute push, the base set of inclusive language changes
have merged. There is a conversion script which can be run to convert
layers. Not all changes needed have been written yet but enough are present
to allow the conversion process to start.
*   There were also changes to convert LICENSE fields to use SPDX
identifiers and there is a second conversion script for this that can be
used.
*   We have updated the core layer series name to kirkstone and other
layers will now need to update to confirm compatibility with kirkstone.
*   There is a patchset to update python's build processes to use the
upstream preferred wheel approach which would aid support of python over the
next few years. It is late in the cycle for this kind of change but we will
give this series a few days of testing to make a decision and welcome user
feedback either way on these changes.
*   As such, the M3 release build will likely not happen until early
next week.
*   The autobuilder infrastructure is planned to be offline 26-28th
February for a data center move. Public services like the website, wiki and
git servers will remain live but the git backend (push.yoctoproject.org)
will be offline, as will the downloads and sstate services and the
autobuilder/NAS.
*   Capacity has been improved on the sstate server which was causing
intermittent timeout issues for downloads.
*   Intermittent issues continue to be at record high levels and help is
very much welcome in trying to resolve them. You can see the list of
failures we're continuing to see by searching for the "AB-INT" tag in
bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

In particular, we're struggling to understand the intermittent network issue
with external hosts we're seeing very occasionally.

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.5. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.
*   Help us resolve CVE issues:
 CVE metrics 

 

YP 3.5 Milestone Dates:

*   YP 3.5 M3 build date 2022/02/21
*   YP 3.5 M3 Release date 2022/03/04
*   YP 3.5 M4 build date 2022/04/04
*   YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

*   YP 3.1.14  is released
*   YP 3.4.2 is released
*   YP 3.3.5  is in QA
*   YP 3.3.5 Release date 2022/02/25
*   YP 3.1.15 build date 2022/03/14
*   YP 3.1.15 Release date 2022/03/25
*   YP 3.4.3 build date 2022/03/21
*   YP 3.4.3 Release date 2022/04/01
*   YP 3.3.6 build date 2022/03/28
*   YP 3.3.6 Release date 2022/04/08
*   YP 3.1.16 build date 2022/04/25
*   YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

*   WDD 2652 (last week 2662) (

https://wiki.yoctoproject.org/charts/combo.html)
*   OE-Core/Poky Patch Metrics

*   Total patches found: 1202 (last week 1208)
*   Patches in the Pending State: 334 (28%) [last week 334 (28%)]

 

The Yocto Project's technical governance is 

[OE-core] [honister][PATCH 38/38] uninative: Upgrade to 3.5

[Anuj Mittal]

From: Michael Halstead 

Add support for glibc 2.35.

Signed-off-by: Michael Halstead 
Signed-off-by: Richard Purdie 
(cherry picked from commit 347b8c87fb4e2c398644f900728cf6e22ba4516d)
Signed-off-by: Anuj Mittal 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 6833072cd3..bfe05ce1eb 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.34"
-UNINATIVE_VERSION = "3.4"
+UNINATIVE_MAXGLIBCVERSION = "2.35"
+UNINATIVE_VERSION = "3.5"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"3013cdda8f0dc6639ce1c80f33eabce66f06b890bd5b58739a6d7a92a0bb7100"
-UNINATIVE_CHECKSUM[i686] ?= 
"abed500de584aad63ec237546db20cdd0c69d8870a6f8e94ac31721ace64b376"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"126f4f7f6f21084ee140dac3eb4c536b963837826b7c38599db0b512c3377ba2"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"6de0771bd21e0fcb5e80388e5b561a8023b24083bcbf46e056a089982aff75d7"
+UNINATIVE_CHECKSUM[i686] ?= 
"8c8745becbfa1c341bae839c7eab56ddf17ce36c303bcd73d3b2f2f788b631c2"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"e8047a5748e6f266165da141eb6d08b23674f30e477b0e5505b6403d50fbc4b2"
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162174): 
https://lists.openembedded.org/g/openembedded-core/message/162174
Mute This Topic: https://lists.openembedded.org/mt/89318335/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 36/38] tiff: Add backports for two CVEs from upstream

[Anuj Mittal]

From: Richard Purdie 

Signed-off-by: Richard Purdie 
(cherry picked from commit 6ae14b4ff7a655b48c6d99ac565d12bf8825414f)
Signed-off-by: Anuj Mittal 
---
 ...al-buffer-overflow-for-ASCII-tags-wh.patch |  0
 ...99c99f987dc32ae110370cfdd7df7975586b.patch | 30 +
 ...0712f4c3a5b449f70c57988260a667ddbdef.patch | 32 +++
 meta/recipes-multimedia/libtiff/tiff_4.3.0.bb |  4 ++-
 4 files changed, 65 insertions(+), 1 deletion(-)
 rename meta/recipes-multimedia/libtiff/{files => 
tiff}/0001-tiffset-fix-global-buffer-overflow-for-ASCII-tags-wh.patch (100%)
 create mode 100644 
meta/recipes-multimedia/libtiff/tiff/561599c99f987dc32ae110370cfdd7df7975586b.patch
 create mode 100644 
meta/recipes-multimedia/libtiff/tiff/eecb0712f4c3a5b449f70c57988260a667ddbdef.patch

diff --git 
a/meta/recipes-multimedia/libtiff/files/0001-tiffset-fix-global-buffer-overflow-for-ASCII-tags-wh.patch
 
b/meta/recipes-multimedia/libtiff/tiff/0001-tiffset-fix-global-buffer-overflow-for-ASCII-tags-wh.patch
similarity index 100%
rename from 
meta/recipes-multimedia/libtiff/files/0001-tiffset-fix-global-buffer-overflow-for-ASCII-tags-wh.patch
rename to 
meta/recipes-multimedia/libtiff/tiff/0001-tiffset-fix-global-buffer-overflow-for-ASCII-tags-wh.patch
diff --git 
a/meta/recipes-multimedia/libtiff/tiff/561599c99f987dc32ae110370cfdd7df7975586b.patch
 
b/meta/recipes-multimedia/libtiff/tiff/561599c99f987dc32ae110370cfdd7df7975586b.patch
new file mode 100644
index 00..0b41dde606
--- /dev/null
+++ 
b/meta/recipes-multimedia/libtiff/tiff/561599c99f987dc32ae110370cfdd7df7975586b.patch
@@ -0,0 +1,30 @@
+From 561599c99f987dc32ae110370cfdd7df7975586b Mon Sep 17 00:00:00 2001
+From: Even Rouault 
+Date: Sat, 5 Feb 2022 20:36:41 +0100
+Subject: [PATCH] TIFFReadDirectory(): avoid calling memcpy() with a null
+ source pointer and size of zero (fixes #362)
+
+Upstream-Status: Backport
+CVE: CVE-2022-0562
+
+---
+ libtiff/tif_dirread.c | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/libtiff/tif_dirread.c b/libtiff/tif_dirread.c
+index 2bbc4585..23194ced 100644
+--- a/libtiff/tif_dirread.c
 b/libtiff/tif_dirread.c
+@@ -4177,7 +4177,8 @@ TIFFReadDirectory(TIFF* tif)
+ goto bad;
+ }
+ 
+-memcpy(new_sampleinfo, tif->tif_dir.td_sampleinfo, 
old_extrasamples * sizeof(uint16_t));
++if (old_extrasamples > 0)
++memcpy(new_sampleinfo, tif->tif_dir.td_sampleinfo, 
old_extrasamples * sizeof(uint16_t));
+ _TIFFsetShortArray(>tif_dir.td_sampleinfo, 
new_sampleinfo, tif->tif_dir.td_extrasamples);
+ _TIFFfree(new_sampleinfo);
+ }
+-- 
+GitLab
+
diff --git 
a/meta/recipes-multimedia/libtiff/tiff/eecb0712f4c3a5b449f70c57988260a667ddbdef.patch
 
b/meta/recipes-multimedia/libtiff/tiff/eecb0712f4c3a5b449f70c57988260a667ddbdef.patch
new file mode 100644
index 00..74f9649fdf
--- /dev/null
+++ 
b/meta/recipes-multimedia/libtiff/tiff/eecb0712f4c3a5b449f70c57988260a667ddbdef.patch
@@ -0,0 +1,32 @@
+From eecb0712f4c3a5b449f70c57988260a667ddbdef Mon Sep 17 00:00:00 2001
+From: Even Rouault 
+Date: Sun, 6 Feb 2022 13:08:38 +0100
+Subject: [PATCH] TIFFFetchStripThing(): avoid calling memcpy() with a null
+ source pointer and size of zero (fixes #362)
+
+Upstream-Status: Backport
+CVE: CVE-2022-0561
+
+---
+ libtiff/tif_dirread.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/libtiff/tif_dirread.c b/libtiff/tif_dirread.c
+index 23194ced..50ebf8ac 100644
+--- a/libtiff/tif_dirread.c
 b/libtiff/tif_dirread.c
+@@ -5777,8 +5777,9 @@ TIFFFetchStripThing(TIFF* tif, TIFFDirEntry* dir, 
uint32_t nstrips, uint64_t** l
+   _TIFFfree(data);
+   return(0);
+   }
+-_TIFFmemcpy(resizeddata,data, (uint32_t)dir->tdir_count * 
sizeof(uint64_t));
+-_TIFFmemset(resizeddata+(uint32_t)dir->tdir_count, 0, 
(nstrips - (uint32_t)dir->tdir_count) * sizeof(uint64_t));
++  if( dir->tdir_count )
++  _TIFFmemcpy(resizeddata,data, (uint32_t)dir->tdir_count 
* sizeof(uint64_t));
++  _TIFFmemset(resizeddata+(uint32_t)dir->tdir_count, 0, (nstrips 
- (uint32_t)dir->tdir_count) * sizeof(uint64_t));
+   _TIFFfree(data);
+   data=resizeddata;
+   }
+-- 
+GitLab
+
diff --git a/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb 
b/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb
index ef8e8460fb..86b55ad284 100644
--- a/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb
+++ b/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb
@@ -9,7 +9,9 @@ LIC_FILES_CHKSUM = 
"file://COPYRIGHT;md5=34da3db46fab7501992f9615d7e158cf"
 CVE_PRODUCT = "libtiff"
 
 SRC_URI = "http://download.osgeo.org/libtiff/tiff-${PV}.tar.gz \
-   
file://0001-tiffset-fix-global-buffer-overflow-for-ASCII-tags-wh.patch"
+   

[OE-core] [honister][PATCH 37/38] expat: Upgrade 2.4.5 -> 2.4.6

[Anuj Mittal]

From: Richard Purdie 

Signed-off-by: Richard Purdie 
(cherry picked from commit 91aa5e3f94a7f82be7949ecfde2764d51384ad42)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-core/expat/{expat_2.4.5.bb => expat_2.4.6.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/expat/{expat_2.4.5.bb => expat_2.4.6.bb} (91%)

diff --git a/meta/recipes-core/expat/expat_2.4.5.bb 
b/meta/recipes-core/expat/expat_2.4.6.bb
similarity index 91%
rename from meta/recipes-core/expat/expat_2.4.5.bb
rename to meta/recipes-core/expat/expat_2.4.6.bb
index 2d9894a057..3e779c3dea 100644
--- a/meta/recipes-core/expat/expat_2.4.5.bb
+++ b/meta/recipes-core/expat/expat_2.4.6.bb
@@ -15,7 +15,7 @@ SRC_URI = 
"https://github.com/libexpat/libexpat/releases/download/R_${VERSION_TA
 
 UPSTREAM_CHECK_URI = "https://github.com/libexpat/libexpat/releases/;
 
-SRC_URI[sha256sum] = 
"fbb430f964c7a2db2626452b6769e6a8d5d23593a453ccbc21701b74deabedff"
+SRC_URI[sha256sum] = 
"ce317706b07cae150f90cddd4253f5b4fba929607488af5ac47bf2bc08e31f09"
 
 EXTRA_OECMAKE:class-native += "-DEXPAT_BUILD_DOCS=OFF"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162173): 
https://lists.openembedded.org/g/openembedded-core/message/162173
Mute This Topic: https://lists.openembedded.org/mt/89318333/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 35/38] vim: Upgrade 8.2.4314 -> 8.2.4424

[Anuj Mittal]

From: Richard Purdie 

License file had some grammar fixes.

Includes CVE-2022-0554.

Signed-off-by: Richard Purdie 
(cherry picked from commit a8d0a4026359c2c8a445dba9456f8a05470293c1)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-support/vim/vim.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 8044500d6b..59e0b4ed7a 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -11,7 +11,7 @@ RSUGGESTS:${PN} = "diffutils"
 
 LICENSE = "vim"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=6b30ea4fa660c483b619924bc709ef99 \
-
file://runtime/doc/uganda.txt;md5=600a38dc53e8931fdfb1238276ee09b0"
+
file://runtime/doc/uganda.txt;md5=a3f193c20c6faff93c69185d5d070535"
 
 SRC_URI = "git://github.com/vim/vim.git;branch=master;protocol=https \
file://disable_acl_header_check.patch \
@@ -21,8 +21,8 @@ SRC_URI = 
"git://github.com/vim/vim.git;branch=master;protocol=https \
file://racefix.patch \
"
 
-PV .= ".4314"
-SRCREV = "8cbf2499179db39a46e700ab04d0b36e22bcc1bb"
+PV .= ".4424"
+SRCREV = "cdf717283ca70b18f20b8a2cefe7957083280c6f"
 
 # Do not consider .z in x.y.z, as that is updated with every commit
 UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+\.\d+)\.0"
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162171): 
https://lists.openembedded.org/g/openembedded-core/message/162171
Mute This Topic: https://lists.openembedded.org/mt/89318329/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 34/38] expat: Upgrade 2.4.4 -> 2.4.5

[Anuj Mittal]

From: Richard Purdie 

This is a security fix release containing fixes for CVE-2022-25235, 
CVE-2022-25236,
CVE-2022-25313, CVE-2022-25314 and CVE-2022-25315.

Signed-off-by: Richard Purdie 
(cherry picked from commit b71344dacb71cfc452b335a6f2fb9cb74e2e1ff8)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-core/expat/{expat_2.4.4.bb => expat_2.4.5.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/expat/{expat_2.4.4.bb => expat_2.4.5.bb} (91%)

diff --git a/meta/recipes-core/expat/expat_2.4.4.bb 
b/meta/recipes-core/expat/expat_2.4.5.bb
similarity index 91%
rename from meta/recipes-core/expat/expat_2.4.4.bb
rename to meta/recipes-core/expat/expat_2.4.5.bb
index 63d291ed40..2d9894a057 100644
--- a/meta/recipes-core/expat/expat_2.4.4.bb
+++ b/meta/recipes-core/expat/expat_2.4.5.bb
@@ -15,7 +15,7 @@ SRC_URI = 
"https://github.com/libexpat/libexpat/releases/download/R_${VERSION_TA
 
 UPSTREAM_CHECK_URI = "https://github.com/libexpat/libexpat/releases/;
 
-SRC_URI[sha256sum] = 
"14c58c2a0b5b8b31836514dfab41bd191836db7aa7b84ae5c47bc0327a20d64a"
+SRC_URI[sha256sum] = 
"fbb430f964c7a2db2626452b6769e6a8d5d23593a453ccbc21701b74deabedff"
 
 EXTRA_OECMAKE:class-native += "-DEXPAT_BUILD_DOCS=OFF"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162170): 
https://lists.openembedded.org/g/openembedded-core/message/162170
Mute This Topic: https://lists.openembedded.org/mt/89318328/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 33/38] linux-firmware: upgrade 20211216 -> 20220209

[Anuj Mittal]

From: wangmy 

License-Update:
Version of some driver files updated
Added files for some drivers

Signed-off-by: Wang Mingyu 
Signed-off-by: Richard Purdie 
(cherry picked from commit 1a2a64082d2a4845bebe802afed2a65dac994043)
Signed-off-by: Anuj Mittal 
---
 ...{linux-firmware_20211216.bb => linux-firmware_20220209.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-kernel/linux-firmware/{linux-firmware_20211216.bb => 
linux-firmware_20220209.bb} (99%)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20211216.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_20220209.bb
similarity index 99%
rename from meta/recipes-kernel/linux-firmware/linux-firmware_20211216.bb
rename to meta/recipes-kernel/linux-firmware/linux-firmware_20220209.bb
index 5f1b696092..fe51892eb4 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20211216.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20220209.bb
@@ -132,7 +132,7 @@ LIC_FILES_CHKSUM = 
"file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc \
 file://LICENCE.xc4000;md5=0ff51d2dc49fce04814c9155081092f0 
\
 file://LICENCE.xc5000;md5=1e170c13175323c32c7f4d0998d53f66 
\
 
file://LICENCE.xc5000c;md5=12b02efa3049db65d524aeb418dd87ca \
-file://WHENCE;md5=79f477f9d53eedee5a65b45193785963 \
+file://WHENCE;md5=ed3d7426e4df06fbadcca24ebf00cc5f \
 "
 
 # These are not common licenses, set NO_GENERIC_LICENSE for them
@@ -205,7 +205,7 @@ PE = "1"
 
 SRC_URI = "${KERNELORG_MIRROR}/linux/kernel/firmware/${BPN}-${PV}.tar.xz"
 
-SRC_URI[sha256sum] = 
"eeddb4e6bef31fd1a3757f12ccc324929bbad97855c0b9ec5ed780f74de1837d"
+SRC_URI[sha256sum] = 
"e2e46fa618414952bbf2f6920cd3abcddbef45bfb7d1352994b4bfc35394d177"
 
 inherit allarch
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162169): 
https://lists.openembedded.org/g/openembedded-core/message/162169
Mute This Topic: https://lists.openembedded.org/mt/89318327/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 31/38] linux-yocto/5.10: ppc/riscv: fix build with binutils 2.3.8

[Anuj Mittal]

From: Bruce Ashfield 

Integrating the following commit(s) to linux-yocto/5.10:

1bd813fe8d0e riscv: fix build with binutils 2.38
835a2d1b24c6 powerpc/lib/sstep: fix 'ptesync' build error

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie 
(cherry picked from commit 8279495332f560902a9c264939da50b8302828b6)
Signed-off-by: Anuj Mittal 
---
 .../linux/linux-yocto-rt_5.10.bb  |  2 +-
 .../linux/linux-yocto-tiny_5.10.bb|  4 ++--
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 20 +--
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
index f353a0610c..4315ef6fa3 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
@@ -11,7 +11,7 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "53a27dc510c8d9152ffa4d2d95b888db7d3d97b6"
+SRCREV_machine ?= "c8061a9f265a0d314e5b780a651662f462e4b287"
 SRCREV_meta ?= "a58f4e7cca3973e04d3f9a40356ef9c2c0bb10a5"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb
index e9c20c6c79..c968d404d0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb
@@ -15,8 +15,8 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine:qemuarm ?= "b7823b6ac25671f8dc5ee2c4cf74af3be88207cf"
-SRCREV_machine ?= "7558a33fc5b60d4327b683c3376c5352cba11ed1"
+SRCREV_machine:qemuarm ?= "5e7b4957ac1a94fdaaa719f6b62b80856e8a55e6"
+SRCREV_machine ?= "24a50caea8c65c2af4987c60067dc55ef737ebca"
 SRCREV_meta ?= "a58f4e7cca3973e04d3f9a40356ef9c2c0bb10a5"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.10.bb
index a7b3d08d9e..ae607d721b 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb
@@ -13,16 +13,16 @@ KBRANCH:qemux86  ?= "v5.10/standard/base"
 KBRANCH:qemux86-64 ?= "v5.10/standard/base"
 KBRANCH:qemumips64 ?= "v5.10/standard/mti-malta64"
 
-SRCREV_machine:qemuarm ?= "c3a59bad41cefbe15d6bcde0ec2fe5c7ea28ba2b"
-SRCREV_machine:qemuarm64 ?= "07ca3e3c85445f2c31bd081b27741c9680536168"
-SRCREV_machine:qemumips ?= "10ae40d47f14b3c05dd6506c70576383c5474670"
-SRCREV_machine:qemuppc ?= "bc2a7c884103143e0a4360518247fe01bf2c13d3"
-SRCREV_machine:qemuriscv64 ?= "84f6a75f64961e59d61bf3d70ab17e8bb430386b"
-SRCREV_machine:qemuriscv32 ?= "84f6a75f64961e59d61bf3d70ab17e8bb430386b"
-SRCREV_machine:qemux86 ?= "84f6a75f64961e59d61bf3d70ab17e8bb430386b"
-SRCREV_machine:qemux86-64 ?= "84f6a75f64961e59d61bf3d70ab17e8bb430386b"
-SRCREV_machine:qemumips64 ?= "13998bd0244737548a21a17d1969ca65af0712b1"
-SRCREV_machine ?= "84f6a75f64961e59d61bf3d70ab17e8bb430386b"
+SRCREV_machine:qemuarm ?= "7f5de9bc153963749c9a566828b59d4e63796432"
+SRCREV_machine:qemuarm64 ?= "c5bed4d604e64e8ce795a28576e341a2e790b4de"
+SRCREV_machine:qemumips ?= "0361229f491eec312e503cf7e58931571e53503f"
+SRCREV_machine:qemuppc ?= "2d7e10b0e0bab9b364e7612caf81b318f1d28b27"
+SRCREV_machine:qemuriscv64 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
+SRCREV_machine:qemuriscv32 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
+SRCREV_machine:qemux86 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
+SRCREV_machine:qemux86-64 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
+SRCREV_machine:qemumips64 ?= "931424f9c84cc440e8f154465062e71e2bdc2f03"
+SRCREV_machine ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
 SRCREV_meta ?= "a58f4e7cca3973e04d3f9a40356ef9c2c0bb10a5"
 
 # remap qemuarm to qemuarma15 for the 5.8 kernel
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162167): 
https://lists.openembedded.org/g/openembedded-core/message/162167
Mute This Topic: https://lists.openembedded.org/mt/89318325/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 32/38] linux-yocto/5.10: fix dssall build error with binutils 2.3.8

[Anuj Mittal]

From: Bruce Ashfield 

Integrating the following commit(s) to linux-yocto/5.10:

c0b313d988a1 powerpc/mm: Switch obsolete dssall to .long

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie 
(cherry picked from commit b063ee0529c02f8b31a1034289ea1a202e496d0b)
Signed-off-by: Anuj Mittal 
---
 .../linux/linux-yocto-rt_5.10.bb  |  4 ++--
 .../linux/linux-yocto-tiny_5.10.bb|  6 ++---
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 22 +--
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
index 4315ef6fa3..8a8a7eabe9 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
@@ -11,8 +11,8 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "c8061a9f265a0d314e5b780a651662f462e4b287"
-SRCREV_meta ?= "a58f4e7cca3973e04d3f9a40356ef9c2c0bb10a5"
+SRCREV_machine ?= "e5b266bc6b15dc8852649b7d2a31395195dc7b3a"
+SRCREV_meta ?= "b53e11ea46f4e78ff4cb48532a11e1dbad7939b1"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.10;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb
index c968d404d0..bf7662eed3 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.10.bb
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine:qemuarm ?= "5e7b4957ac1a94fdaaa719f6b62b80856e8a55e6"
-SRCREV_machine ?= "24a50caea8c65c2af4987c60067dc55ef737ebca"
-SRCREV_meta ?= "a58f4e7cca3973e04d3f9a40356ef9c2c0bb10a5"
+SRCREV_machine:qemuarm ?= "9a8497a8761a22b3086cab63d18698024a69a410"
+SRCREV_machine ?= "317635e1feaecfd8aa29bc94d8d03ba873190414"
+SRCREV_meta ?= "b53e11ea46f4e78ff4cb48532a11e1dbad7939b1"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.10.bb
index ae607d721b..ecb2d03949 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb
@@ -13,17 +13,17 @@ KBRANCH:qemux86  ?= "v5.10/standard/base"
 KBRANCH:qemux86-64 ?= "v5.10/standard/base"
 KBRANCH:qemumips64 ?= "v5.10/standard/mti-malta64"
 
-SRCREV_machine:qemuarm ?= "7f5de9bc153963749c9a566828b59d4e63796432"
-SRCREV_machine:qemuarm64 ?= "c5bed4d604e64e8ce795a28576e341a2e790b4de"
-SRCREV_machine:qemumips ?= "0361229f491eec312e503cf7e58931571e53503f"
-SRCREV_machine:qemuppc ?= "2d7e10b0e0bab9b364e7612caf81b318f1d28b27"
-SRCREV_machine:qemuriscv64 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
-SRCREV_machine:qemuriscv32 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
-SRCREV_machine:qemux86 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
-SRCREV_machine:qemux86-64 ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
-SRCREV_machine:qemumips64 ?= "931424f9c84cc440e8f154465062e71e2bdc2f03"
-SRCREV_machine ?= "1bd813fe8d0e8e2bc4b05fdf61fb77d68ee416c5"
-SRCREV_meta ?= "a58f4e7cca3973e04d3f9a40356ef9c2c0bb10a5"
+SRCREV_machine:qemuarm ?= "5c9de82973348b40bfdcecc0623f488d9443038e"
+SRCREV_machine:qemuarm64 ?= "8c841836837414c6d07fa08ef8482162760fc27a"
+SRCREV_machine:qemumips ?= "d8287fdfbe460acdd62cf57e351411c992101514"
+SRCREV_machine:qemuppc ?= "f436ec6dd3942a87331abf39805e791460e499ef"
+SRCREV_machine:qemuriscv64 ?= "c0b313d988a16b25c1ee730bfe7393c462ee8a5c"
+SRCREV_machine:qemuriscv32 ?= "c0b313d988a16b25c1ee730bfe7393c462ee8a5c"
+SRCREV_machine:qemux86 ?= "c0b313d988a16b25c1ee730bfe7393c462ee8a5c"
+SRCREV_machine:qemux86-64 ?= "c0b313d988a16b25c1ee730bfe7393c462ee8a5c"
+SRCREV_machine:qemumips64 ?= "ae7887fe8d4da06d2d0d0a5071d09155899de26c"
+SRCREV_machine ?= "c0b313d988a16b25c1ee730bfe7393c462ee8a5c"
+SRCREV_meta ?= "b53e11ea46f4e78ff4cb48532a11e1dbad7939b1"
 
 # remap qemuarm to qemuarma15 for the 5.8 kernel
 # KMACHINE:qemuarm ?= "qemuarma15"
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162168): 
https://lists.openembedded.org/g/openembedded-core/message/162168
Mute This Topic: https://lists.openembedded.org/mt/89318326/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 29/38] oeqa/buildtools: Switch to our webserver instead of example.com

[Anuj Mittal]

From: Richard Purdie 

Similarly to the sanity connectivity check, switch away from example.com
for the buildtools tests.

Signed-off-by: Richard Purdie 
(cherry picked from commit ed10f3c2b4c678069fe1cee73f79f6e388ce)
Signed-off-by: Anuj Mittal 
---
 meta/lib/oeqa/sdk/buildtools-cases/https.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/sdk/buildtools-cases/https.py 
b/meta/lib/oeqa/sdk/buildtools-cases/https.py
index 134879aab3..35e549eb40 100644
--- a/meta/lib/oeqa/sdk/buildtools-cases/https.py
+++ b/meta/lib/oeqa/sdk/buildtools-cases/https.py
@@ -13,8 +13,8 @@ class HTTPTests(OESDKTestCase):
 """
 
 def test_wget(self):
-self._run('env -i wget --debug --output-document /dev/null 
https://www.example.com')
+self._run('env -i wget --debug --output-document /dev/null 
https://yoctoproject.org/connectivity.html')
 
 def test_python(self):
 # urlopen() returns a file-like object on success and throws an 
exception otherwise
-self._run('python3 -c \'import urllib.request; 
urllib.request.urlopen("https://www.example.com/;)\'')
+self._run('python3 -c \'import urllib.request; 
urllib.request.urlopen("https://yoctoproject.org/connectivity.html;)\'')
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162164): 
https://lists.openembedded.org/g/openembedded-core/message/162164
Mute This Topic: https://lists.openembedded.org/mt/89318321/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 28/38] default-distrovars.inc: Switch connectivity check to a yoctoproject.org page

[Anuj Mittal]

From: Richard Purdie 

example.com is proving unreliable at present so switch to our own connectivity
page instead. That page is very simple avoiding app overhead on our web server
which was an original reason for switching to example.com.

Signed-off-by: Richard Purdie 
(cherry picked from commit dc6b043cb75c5751b5a98afd2201aa31f9b4b9f6)
Signed-off-by: Anuj Mittal 
---
 meta/classes/sanity.bbclass | 2 +-
 meta/conf/distro/include/default-distrovars.inc | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index ddba1e6e1e..49eef2f418 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -395,7 +395,7 @@ def check_connectivity(d):
 msg += "Please ensure your host's network is configured 
correctly.\n"
 msg += "If your ISP or network is blocking the above 
URL,\n"
 msg += "try with another domain name, for example by 
setting:\n"
-msg += "CONNECTIVITY_CHECK_URIS = 
\"https://www.yoctoproject.org/\";
+msg += "CONNECTIVITY_CHECK_URIS = 
\"https://www.example.com/\";
 msg += "You could also set BB_NO_NETWORK = \"1\" to 
disable network\n"
 msg += "access if all required sources are on local 
disk.\n"
 retval = msg
diff --git a/meta/conf/distro/include/default-distrovars.inc 
b/meta/conf/distro/include/default-distrovars.inc
index fb0f1097da..3bba651a77 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -54,4 +54,4 @@ KERNEL_IMAGETYPES ??= "${KERNEL_IMAGETYPE}"
 # fetch from the network (and warn you if not). To disable the test set
 # the variable to be empty.
 # Git example url: 
git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=master;branch=master
-CONNECTIVITY_CHECK_URIS ?= "https://www.example.com/;
+CONNECTIVITY_CHECK_URIS ?= "https://yoctoproject.org/connectivity.html;
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162165): 
https://lists.openembedded.org/g/openembedded-core/message/162165
Mute This Topic: https://lists.openembedded.org/mt/89318323/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 30/38] linux-yocto/5.10: update to v5.10.99

[Anuj Mittal]

From: Bruce Ashfield 

Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:

fb063a6465f9 Linux 5.10.99
4889d6ee9e48 selftests: nft_concat_range: add test for reload with no 
element add/del
557727313534 cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning
f1f7d1a22fd7 net: dsa: mt7530: make NET_DSA_MT7530 select MEDIATEK_GE_PHY
84b76a509cc3 ext4: fix incorrect type issue during replay_del_range
62e46e0ffc02 ext4: fix error handling in ext4_fc_record_modified_inode()
764793b4a5d0 ext4: fix error handling in ext4_restore_inline_data()
6c5bd55e36d3 ext4: modify the logic of ext4_mb_new_blocks_simple
8d71fc23fcb8 ext4: prevent used blocks from being allocated during fast 
commit replay
ef2053afd71e EDAC/xgene: Fix deferred probing
2a12faf55bae EDAC/altera: Fix deferred probing
dd274cf85269 x86/perf: Default set FREEZE_ON_SMI for all
456f041e0359 perf/x86/intel/pt: Fix crash with stop filters in single-range 
mode
8c0e6a8a630e perf stat: Fix display of grouped aliased events
57e8859acc60 fbcon: Add option to enable legacy hardware acceleration
460f6b1a238d Revert "fbcon: Disable accelerated scrolling"
460aa9d87340 rtc: cmos: Evaluate century appropriate
2324f5fcdf9d tools/resolve_btfids: Do not print any commands when building 
silently
1536fafa23ac selftests: futex: Use variable MAKE instead of make
8f0fff8b5968 selftests/exec: Remove pipe from TEST_GEN_FILES
6304a613a97d bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
f744a064041c gve: fix the wrong AdminQ buffer queue index check
51e88e892273 nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed 
client.
ec4334152dae scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
fd482f2d63db pinctrl: bcm2835: Fix a few error paths
752d9eafc64e pinctrl: intel: fix unexpected interrupt
14bc9978b486 pinctrl: intel: Fix a glitch when updating IRQ flags on a 
preconfigured line
5a45448ac95b ASoC: max9759: fix underflow in speaker_gain_control_put()
02f459719832 ASoC: cpcap: Check for NULL pointer after calling 
of_get_child_by_name
cb5f1fbd1f22 ASoC: xilinx: xlnx_formatter_pcm: Make buffer bytes multiple 
of period bytes
56e0747d59ac ASoC: fsl: Add missing error handling in pcm030_fabric_probe
3e698375517d drm/i915/overlay: Prevent divide by zero bugs in scaling
9ea018536111 net: stmmac: ensure PTP time register reads are consistent
41df2da2c1f3 net: stmmac: dump gmac4 DMA registers correctly
114bf9350413 net: macsec: Verify that send_sci is on when setting Tx sci 
explicitly
2e7f5b6ee1a7 net: macsec: Fix offload support for NETDEV_UNREGISTER event
87b1c9fab6fe net: ieee802154: Return meaningful error codes from the 
netlink helpers
78b3f20c17cb net: ieee802154: ca8210: Stop leaking skb's
0bfe50dc5d91 net: ieee802154: mcr20a: Fix lifs/sifs periods
75bbda318987 net: ieee802154: hwsim: Ensure proper channel selection at 
probe time
e895e067d73e spi: uniphier: fix reference count leak in uniphier_spi_probe()
ec942d08e070 spi: meson-spicc: add IRQ check in meson_spicc_probe
c2cf65e1008b spi: mediatek: Avoid NULL pointer crash in interrupt
30e05c98b99d spi: bcm-qspi: check for valid cs before applying chip select
6d226e8afe88 iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
9d9995b0371e iommu/vt-d: Fix potential memory leak in 
intel_setup_irq_remapping()
b3958d315163 RDMA/mlx4: Don't continue event handler after memory 
allocation failure
d3f8b927df2f RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
c7db20f5be73 IB/rdmavt: Validate remote_addr during loopback atomic tests
75c610212b9f RDMA/ucma: Protect mc during concurrent multicast leaves
371979069a57 RDMA/cma: Use correct address when leaving multicast group
aa4ecd995f59 memcg: charge fs_context and legacy_fs_context
080f371d984e Revert "ASoC: mediatek: Check for error clk pointer"
4a9bd1e6780f IB/hfi1: Fix AIP early init panic
5d40f1bdad3d dma-buf: heaps: Fix potential spectre v1 gadget
30de3bc09978 block: bio-integrity: Advance seed correctly for larger 
interval sizes
352715593e81 mm/kmemleak: avoid scanning potential huge holes
7053188ddba3 mm/pgtable: define pte_index so that preprocessor could 
recognize it
bce7f5d74d74 mm/debug_vm_pgtable: remove pte entry from the page table
2d83a7463d75 nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
a0c73dbdd197 drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 
15" Apple Retina panels
f071d9fa8575 drm/nouveau: fix off by one in BIOS boundary checking
32747e01436a btrfs: fix deadlock between quota disable and qgroup rescan 
worker
aa5d406153c5 ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus 
Xtreme after reboot from Windows
d4aa3a98596f ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus 
Master (newer chipset)

[OE-core] [honister][PATCH 27/38] libpcap: Disable DPDK explicitly

[Anuj Mittal]

From: Sean Anderson 

libpcap looks for DPDK in the same way it looks for DAG. This can poison
the build even if it doesn't find anything. Explicitly disable dpdk.

Signed-off-by: Sean Anderson 
Signed-off-by: Richard Purdie 
(cherry picked from commit be5442f065da40b41d3cd60793341e22654f2681)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-connectivity/libpcap/libpcap_1.10.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/libpcap/libpcap_1.10.1.bb 
b/meta/recipes-connectivity/libpcap/libpcap_1.10.1.bb
index 9a8c46e0ef..dbe2fd8157 100644
--- a/meta/recipes-connectivity/libpcap/libpcap_1.10.1.bb
+++ b/meta/recipes-connectivity/libpcap/libpcap_1.10.1.bb
@@ -19,10 +19,11 @@ BINCONFIG = "${bindir}/pcap-config"
 
 # Explicitly disable dag support. We don't have recipe for it and if enabled 
here,
 # configure script poisons the include dirs with /usr/local/include even when 
the
-# support hasn't been detected.
+# support hasn't been detected. Do the same thing for DPDK.
 EXTRA_OECONF = " \
  --with-pcap=linux \
  --without-dag \
+ --without-dpdk \
  "
 EXTRA_AUTORECONF += "--exclude=aclocal"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162163): 
https://lists.openembedded.org/g/openembedded-core/message/162163
Mute This Topic: https://lists.openembedded.org/mt/89318319/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 26/38] gcc-target: fix glob to remove gcc- binary

[Anuj Mittal]

From: Stefan Herbrechtsmeier 

The glob to remove the gcc- binary expects a single-digit major
version which is no longer true.

Signed-off-by: Stefan Herbrechtsmeier 
Signed-off-by: Richard Purdie 
(cherry picked from commit 30de10cf939cf65c0cab6730a3575bced5c7533a)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-devtools/gcc/gcc-target.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-target.inc 
b/meta/recipes-devtools/gcc/gcc-target.inc
index bf55e692e6..bcea75b2fa 100644
--- a/meta/recipes-devtools/gcc/gcc-target.inc
+++ b/meta/recipes-devtools/gcc/gcc-target.inc
@@ -193,7 +193,7 @@ do_install () {
rm -f *c++*
 
# We don't care about the gcc- ones for this
-   rm -f *gcc-?.?*
+   rm -f *gcc-?*.?*
 
# Not sure why we end up with these but we don't want them...
rm -f ${TARGET_PREFIX}${TARGET_PREFIX}*
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162162): 
https://lists.openembedded.org/g/openembedded-core/message/162162
Mute This Topic: https://lists.openembedded.org/mt/89318318/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 24/38] gcc : Fix CVE-2021-46195

[Anuj Mittal]

From: pgowda 

Upstream-Status: Backport 
[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f10bec5ffa487ad3033ed5f38cfd0fc7d696deab]

Signed-off-by: pgowda 
Signed-off-by: Richard Purdie 
(cherry picked from commit 81e9f8aedab70dfb0a016601150623ef9a7c1596)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-devtools/gcc/gcc-11.2.inc|   1 +
 .../gcc/gcc/0001-CVE-2021-46195.patch | 128 ++
 2 files changed, 129 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch

diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
b/meta/recipes-devtools/gcc/gcc-11.2.inc
index 886ef3c35b..40d2b59354 100644
--- a/meta/recipes-devtools/gcc/gcc-11.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
@@ -76,6 +76,7 @@ SRC_URI = "\
file://0002-CVE-2021-42574.patch \
file://0003-CVE-2021-42574.patch \
file://0004-CVE-2021-42574.patch \
+   file://0001-CVE-2021-46195.patch \
 "
 SRC_URI[sha256sum] = 
"d08edc536b54c372a1010ff6619dd274c0f1603aa49212ba20f7aa2cda36fa8b"
 
diff --git a/meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch 
b/meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch
new file mode 100644
index 00..7b3651c73e
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch
@@ -0,0 +1,128 @@
+From f10bec5ffa487ad3033ed5f38cfd0fc7d696deab Mon Sep 17 00:00:00 2001
+From: Nick Clifton 
+Date: Mon, 31 Jan 2022 14:28:42 +
+Subject: [PATCH] libiberty: Fix infinite recursion in rust demangler.
+
+libiberty/
+   PR demangler/98886
+   PR demangler/99935
+   * rust-demangle.c (struct rust_demangler): Add a recursion
+   counter.
+   (demangle_path): Increment/decrement the recursion counter upon
+   entry and exit.  Fail if the counter exceeds a fixed limit.
+   (demangle_type): Likewise.
+   (rust_demangle_callback): Initialise the recursion counter,
+   disabling if requested by the option flags.
+
+CVE: CVE-2021-46195
+Upstream-Status: Backport
+[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f10bec5ffa487ad3033ed5f38cfd0fc7d696deab]
+Signed-off-by: Pgowda 
+---
+ libiberty/rust-demangle.c | 47 ++-
+ 1 file changed, 41 insertions(+), 6 deletions(-)
+
+diff --git a/libiberty/rust-demangle.c b/libiberty/rust-demangle.c
+index 18c760491bd..3b24d63892a 100644
+--- a/libiberty/rust-demangle.c
 b/libiberty/rust-demangle.c
+@@ -74,6 +74,12 @@ struct rust_demangler
+   /* Rust mangling version, with legacy mangling being -1. */
+   int version;
+ 
++  /* Recursion depth.  */
++  unsigned int recursion;
++  /* Maximum number of times demangle_path may be called recursively.  */
++#define RUST_MAX_RECURSION_COUNT  1024
++#define RUST_NO_RECURSION_LIMIT   ((unsigned int) -1)
++
+   uint64_t bound_lifetime_depth;
+ };
+ 
+@@ -671,6 +677,15 @@ demangle_path (struct rust_demangler *rdm, int in_value)
+   if (rdm->errored)
+ return;
+ 
++  if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++{
++  ++ rdm->recursion;
++  if (rdm->recursion > RUST_MAX_RECURSION_COUNT)
++  /* FIXME: There ought to be a way to report
++ that the recursion limit has been reached.  */
++  goto fail_return;
++}
++
+   switch (tag = next (rdm))
+ {
+ case 'C':
+@@ -688,10 +703,7 @@ demangle_path (struct rust_demangler *rdm, int in_value)
+ case 'N':
+   ns = next (rdm);
+   if (!ISLOWER (ns) && !ISUPPER (ns))
+-{
+-  rdm->errored = 1;
+-  return;
+-}
++  goto fail_return;
+ 
+   demangle_path (rdm, in_value);
+ 
+@@ -776,9 +788,15 @@ demangle_path (struct rust_demangler *rdm, int in_value)
+ }
+   break;
+ default:
+-  rdm->errored = 1;
+-  return;
++  goto fail_return;
+ }
++  goto pass_return;
++
++ fail_return:
++  rdm->errored = 1;
++ pass_return:
++  if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++-- rdm->recursion;
+ }
+ 
+ static void
+@@ -870,6 +888,19 @@ demangle_type (struct rust_demangler *rdm)
+   return;
+ }
+ 
++   if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++{
++  ++ rdm->recursion;
++  if (rdm->recursion > RUST_MAX_RECURSION_COUNT)
++  /* FIXME: There ought to be a way to report
++ that the recursion limit has been reached.  */
++  {
++rdm->errored = 1;
++-- rdm->recursion;
++return;
++  }
++}
++
+   switch (tag)
+ {
+ case 'R':
+@@ -1030,6 +1061,9 @@ demangle_type (struct rust_demangler *rdm)
+   rdm->next--;
+   demangle_path (rdm, 0);
+ }
++
++  if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++-- rdm->recursion;
+ }
+ 
+ /* A trait in a trait object may have some "existential projections"
+@@ -1320,6 +1354,7 @@ rust_demangle_callback (const char *mangled, int options,
+   rdm.skipping_printing = 0;
+   rdm.verbose = (options & DMGL_VERBOSE) != 0;
+   rdm.version = 0;
++  rdm.recursion = (options & 

[OE-core] [honister][PATCH 25/38] initramfs-framework: unmount automounts before switch_root

[Anuj Mittal]

From: Justin Bronder 

If mounts are left lingering, then after we switch_root, attempts to
modify the block devices will result in an EBUSY with no way to unmount
them.  As we're about to switch_root anyways, there isn't much use to
keep anything mounted unless it has the new rootfs.

Signed-off-by: Justin Bronder 
Signed-off-by: Richard Purdie 
(cherry picked from commit 4dc7af6d25597ea10ea43e76c7c3d7251462c0e5)
Signed-off-by: Anuj Mittal 
---
 .../initrdscripts/initramfs-framework/finish | 12 
 1 file changed, 12 insertions(+)

diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/finish 
b/meta/recipes-core/initrdscripts/initramfs-framework/finish
index 717383ebac..f08a920867 100755
--- a/meta/recipes-core/initrdscripts/initramfs-framework/finish
+++ b/meta/recipes-core/initrdscripts/initramfs-framework/finish
@@ -12,6 +12,18 @@ finish_run() {
fatal "ERROR: There's no '/dev' on rootfs."
fi
 
+   # Unmount anything that was automounted by busybox via 
mdev-mount.sh.
+   # We're about to switch_root, and leaving anything mounted will 
prevent
+   # the next rootfs from modifying the block device.  Ignore 
ROOT_DISK,
+   # if it was set by setup-live, because it'll be mounted over 
loopback
+   # to ROOTFS_DIR.
+   local dev
+   for dev in /run/media/*; do
+   if mountpoint -q "${dev}" && [ "${dev##*/}" != 
"${ROOT_DISK}" ]; then
+   umount -f "${dev}" || debug "Failed to unmount 
${dev}"
+   fi
+   done
+
info "Switching root to '$ROOTFS_DIR'..."
 
debug "Moving /dev, /proc and /sys onto rootfs..."
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162161): 
https://lists.openembedded.org/g/openembedded-core/message/162161
Mute This Topic: https://lists.openembedded.org/mt/89318317/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 23/38] qemuboot: Fix build error if UNINATIVE_LOADER is unset

[Anuj Mittal]

From: Zoltán Böszörményi 

I got this error on current master:

File: 'exec_func_python() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_write_qemuboot_conf(d)
 0003:
File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 
141, function: do_write_qemuboot_conf
 0137:else:
 0138:val = d.getVar(k)
 0139:# we only want to write out relative paths so that we can 
relocate images
 0140:# and still run them
 *** 0141:if val.startswith(topdir):
 0142:val = os.path.relpath(val, finalpath)
 0143:cf.set('config_bsp', k, '%s' % val)
 0144:
 0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of a 
symlink
Exception: AttributeError: 'NoneType' object has no attribute 'startswith'

Do nothing if "val" is None, which may happen for k = "UNINATIVE_LOADER".

Signed-off-by: Zoltán Böszörményi 
Signed-off-by: Richard Purdie 
(cherry picked from commit 020043c16ce25238313cbf0d10e40e9f6551bf14)
Signed-off-by: Anuj Mittal 
---
 meta/classes/qemuboot.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index bf529e9aa4..5e7e7c0659 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -131,6 +131,8 @@ python do_write_qemuboot_conf() {

'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
 else:
 val = d.getVar(k)
+if val is None:
+continue
 # we only want to write out relative paths so that we can relocate 
images
 # and still run them
 if val.startswith(topdir):
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162159): 
https://lists.openembedded.org/g/openembedded-core/message/162159
Mute This Topic: https://lists.openembedded.org/mt/89318314/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 21/38] linux-yocto/5.10: update to v5.10.96

[Anuj Mittal]

From: Bruce Ashfield 

Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:

f255ac9e8776 Linux 5.10.96
b43e9d2f6fc7 mtd: rawnand: mpc5121: Remove unused variable in 
ads5121_select_chip()
b63e120189fd block: Fix wrong offset in bio_truncate()
0b4e82403c84 fsnotify: invalidate dcache before IN_DELETE event
8bae6db29c7f usr/include/Makefile: add linux/nfc.h to the compile-test 
coverage
f36554de7897 dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config
446ff1fc37c7 net: bridge: vlan: fix memory leak in __allowed_ingress
bc58a5bb9e6c ipv4: remove sparse error in ip_neigh_gw4()
ebc5b8e471e5 ipv4: tcp: send zero IPID in SYNACK messages
58f72918f942 ipv4: raw: lock the socket in raw_bind()
9ffc94a81b0f net: bridge: vlan: fix single net device option dumping
869f1704f1c2 Revert "ipv6: Honor all IPv6 PIO Valid Lifetime values"
699eef4ed910 net: hns3: handle empty unknown interrupt for VF
c9c81b393c74 net: cpsw: Properly initialise struct page_pool_params
729e54636b3e yam: fix a memory leak in yam_siocdevprivate()
93a6e920d8cc drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
0b7d8db87d0b drm/msm/hdmi: Fix missing put_device() call in msm_hdmi_get_phy
d1d4616d3e75 video: hyperv_fb: Fix validation of screen resolution
0a60d04abc62 ibmvnic: don't spin in tasklet
55258b505996 ibmvnic: init ->running_cap_crqs early
b469cf91fb63 ipv4: fix ip option filtering for locally generated fragments
9b197252 net: ipv4: Fix the warning for dereference
2f56c4845df9 net: ipv4: Move ip_options_fragment() out of loop
55402a461872 powerpc/perf: Fix power_pmu_disable to call 
clear_pmi_irq_pending only if PMI is pending
0bdbf93ee253 hwmon: (lm90) Mark alert as broken for MAX6654
c534287a57dc efi/libstub: arm64: Fix image check alignment at entry
3572205b194c rxrpc: Adjust retransmission backoff
5067f5699de7 octeontx2-pf: Forward error codes to VF
bd024e36f681 phylib: fix potential use-after-free
a839a79f4d6b net: phy: broadcom: hook up soft_reset for BCM54616S
57b2f3632b2f sched/pelt: Relax the sync of util_sum with util_avg
91b04e83c710 perf: Fix perf_event_read_local() time
cffed7e631b5 kernel: delete repeated words in comments
1af995c98b81 netfilter: conntrack: don't increment invalid counter on 
NF_REPEAT
129c71829d7f powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA 
v2.06
7a32824f7a9c NFS: Ensure the server has an up to date ctime before renaming
666f6ab882ea NFS: Ensure the server has an up to date ctime before 
hardlinking
4cd0ef621509 ipv6: annotate accesses to fn->fn_sernum
79c0b5287ded drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable
3ab44a408bba drm/msm/dsi: Fix missing put_device() call in dsi_get_phy
82c310d04b0f drm/msm: Fix wrong size calculation
f57a99c9a55c net-procfs: show net devices bound packet types
87880e3803ce NFSv4: nfs_atomic_open() can race when looking up a 
non-regular file
ce8c552b88ca NFSv4: Handle case where the lookup of a directory fails
b48a05cee2c0 hwmon: (lm90) Reduce maximum conversion rate for G781
b26fed25e67b ipv4: avoid using shared IP generator for connected sockets
283aa5a5afbc ping: fix the sk_bound_dev_if match in ping_lookup
7bcb0c19abf4 hwmon: (lm90) Mark alert as broken for MAX6680
925cbd596aa2 hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649
db044d97460e net: fix information leakage in /proc/net/ptype
feb770cc00a8 ipv6_tunnel: Rate limit warning messages
00849de10f79 scsi: bnx2fc: Flush destroy_work queue before calling 
bnx2fc_interface_put()
fcaf94c49a84 rpmsg: char: Fix race between the release of rpmsg_eptdev and 
cdev
1dbb206730f3 rpmsg: char: Fix race between the release of rpmsg_ctrldev and 
cdev
20f667582189 usb: roles: fix include/linux/usb/role.h compile issue
6aeff8a7c742 i40e: fix unsigned stat widths
d2ed5997a94b i40e: Fix for failed to init adminq while VF reset
768eb705e638 i40e: Fix queues reservation for XDP
39896710f732 i40e: Fix issue when maximum queues is exceeded
9068bcb2195b i40e: Increase delay to 1 s after global EMP reset
b4c9b6afa3a7 powerpc/32: Fix boot failure with GCC latent entropy plugin
50f5d0a8bd0e powerpc/32s: Fix kasan_init_region() for KASAN
5d3af1dfdf0f powerpc/32s: Allocate one 256k IBAT instead of two 
consecutives 128k IBATs
08f090bb9b69 x86/MCE/AMD: Allow thresholding interface updates after init
791e5d5daa2c sched/membarrier: Fix membarrier-rseq fence command missing 
from query bitmask
afbde455ebf4 ocfs2: fix a deadlock when commit trans
97f75e7d4c30 jbd2: export jbd2_journal_[grab|put]_journal_head
3921d081c9c3 ucsi_ccg: Check DEV_INT bit only when starting CCG4
598a884c772c usb: typec: tcpm: Do not disconnect while receiving VBUS off
e3b131e30e61 USB: core: Fix hang in 

[OE-core] [honister][PATCH 22/38] virglrenderer: fix CVE-2022-0135 and -0175

[Anuj Mittal]

From: Joe Slater 

CVE-2022-0135 concerns out-of-bounds writes in read_transfer_data().
CVE-2022-0175 concerns using malloc() instead of calloc().

We "cherry-pick" from upstream.  The actual cherry-picks are from
upstream master to branch-0.9.1 and are the patches entered here.

Signed-off-by: Joe Slater 
Signed-off-by: Richard Purdie 
(cherry picked from commit 91f7511df79c5c1f93add9f2827a5a266453614e)
Signed-off-by: Anuj Mittal 
---
 .../virglrenderer/cve-2022-0135.patch | 117 ++
 .../virglrenderer/cve-2022-0175.patch | 107 
 .../virglrenderer/virglrenderer_0.9.1.bb  |   2 +
 3 files changed, 226 insertions(+)
 create mode 100644 
meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch
 create mode 100644 
meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch

diff --git 
a/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch 
b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch
new file mode 100644
index 00..ae42dc8f6c
--- /dev/null
+++ b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch
@@ -0,0 +1,117 @@
+From 63aee871365f9c9e7fa9125672302a0fb250d34d Mon Sep 17 00:00:00 2001
+From: Gert Wollny 
+Date: Tue, 30 Nov 2021 09:16:24 +0100
+Subject: [PATCH 2/2] vrend: propperly check whether the shader image range is
+ correct
+
+Also add a test to check the integer underflow.
+
+Closes: #251
+Signed-off-by: Gert Wollny 
+Reviewed-by: Chia-I Wu 
+
+cherry-pick from anongit.freedesktop.org/virglrenderer
+commit 2aed5d4...
+
+CVE: CVE-2022-0135
+Upstream-Status: Backport
+Signed-off-by: Joe Slater 
+
+---
+ src/vrend_decode.c  |  3 +-
+ tests/test_fuzzer_formats.c | 57 +
+ 2 files changed, 59 insertions(+), 1 deletion(-)
+
+diff --git a/src/vrend_decode.c b/src/vrend_decode.c
+index 91f5f24..6771b10 100644
+--- a/src/vrend_decode.c
 b/src/vrend_decode.c
+@@ -1249,8 +1249,9 @@ static int vrend_decode_set_shader_images(struct 
vrend_context *ctx, const uint3
+if (num_images < 1) {
+   return 0;
+}
++
+if (start_slot > PIPE_MAX_SHADER_IMAGES ||
+-   start_slot > PIPE_MAX_SHADER_IMAGES - num_images)
++   start_slot + num_images > PIPE_MAX_SHADER_IMAGES)
+   return EINVAL;
+ 
+for (uint32_t i = 0; i < num_images; i++) {
+diff --git a/tests/test_fuzzer_formats.c b/tests/test_fuzzer_formats.c
+index 154a2e5..e32caf0 100644
+--- a/tests/test_fuzzer_formats.c
 b/tests/test_fuzzer_formats.c
+@@ -958,6 +958,61 @@ static void test_vrend_set_signle_abo_heap_overflow() {
+ virgl_renderer_submit_cmd((void *) cmd, ctx_id, 0xde);
+ }
+ 
++static void test_vrend_set_shader_images_overflow()
++{
++uint32_t num_shaders = PIPE_MAX_SHADER_IMAGES + 1;
++uint32_t size = num_shaders * VIRGL_SET_SHADER_IMAGE_ELEMENT_SIZE + 3;
++uint32_t cmd[size];
++int i = 0;
++cmd[i++] = ((size - 1)<< 16) | 0 << 8 | VIRGL_CCMD_SET_SHADER_IMAGES;
++cmd[i++] = PIPE_SHADER_FRAGMENT;
++memset([i], 0, size - i);
++
++virgl_renderer_submit_cmd((void *) cmd, ctx_id, size);
++}
++
++/* Test adapted from yaojun8558...@gmail.com:
++ * https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/250
++*/
++static void test_vrend_3d_resource_overflow() {
++
++struct virgl_renderer_resource_create_args resource;
++resource.handle = 0x4c474572;
++resource.target = PIPE_TEXTURE_2D_ARRAY;
++resource.format = VIRGL_FORMAT_Z24X8_UNORM;
++resource.nr_samples = 2;
++resource.last_level = 0;
++resource.array_size = 3;
++resource.bind = VIRGL_BIND_SAMPLER_VIEW;
++resource.depth = 1;
++resource.width = 8;
++resource.height = 4;
++resource.flags = 0;
++
++virgl_renderer_resource_create(, NULL, 0);
++virgl_renderer_ctx_attach_resource(ctx_id, resource.handle);
++
++uint32_t size = 0x400;
++uint32_t cmd[size];
++int i = 0;
++cmd[i++] = (size - 1) << 16 | 0 << 8 | VIRGL_CCMD_RESOURCE_INLINE_WRITE;
++cmd[i++] = resource.handle;
++cmd[i++] = 0; // level
++cmd[i++] = 0; // usage
++cmd[i++] = 0; // stride
++cmd[i++] = 0; // layer_stride
++cmd[i++] = 0; // x
++cmd[i++] = 0; // y
++cmd[i++] = 0; // z
++cmd[i++] = 8; // w
++cmd[i++] = 4; // h
++cmd[i++] = 3; // d
++memset([i], 0, size - i);
++
++virgl_renderer_submit_cmd((void *) cmd, ctx_id, size);
++}
++
++
+ int main()
+ {
+initialize_environment();
+@@ -980,6 +1035,8 @@ int main()
+test_cs_nullpointer_deference();
+test_vrend_set_signle_abo_heap_overflow();
+ 
++   test_vrend_set_shader_images_overflow();
++   test_vrend_3d_resource_overflow();
+ 
+virgl_renderer_context_destroy(ctx_id);
+virgl_renderer_cleanup();
+-- 
+2.25.1
+
diff --git 
a/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch 
b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch
new file mode 100644
index 

[OE-core] [honister][PATCH 19/38] vim: Upgrade 4269 -> 4134

[Anuj Mittal]

From: Richard Purdie 

License text underwent changes on how to submit Uganda donations, switch from 
http
to https urls and an update date change but the license itself is unchanged.

Also, add an entry for the top level license file. This is also the vim license
so LICENSE is unchanged but we should monitor it too.

Signed-off-by: Richard Purdie 
(cherry picked from commit d195005e415b0b2d7c8b0b65c0aef888d4d6fc8e)
Signed-off-by: Anuj Mittal 
---
 meta/recipes-support/vim/vim.inc | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 6c70bb7529..8044500d6b 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -10,7 +10,8 @@ DEPENDS = "ncurses gettext-native"
 RSUGGESTS:${PN} = "diffutils"
 
 LICENSE = "vim"
-LIC_FILES_CHKSUM = 
"file://runtime/doc/uganda.txt;endline=287;md5=909f1394892b7e0f9c2a95306c0c552b"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=6b30ea4fa660c483b619924bc709ef99 \
+
file://runtime/doc/uganda.txt;md5=600a38dc53e8931fdfb1238276ee09b0"
 
 SRC_URI = "git://github.com/vim/vim.git;branch=master;protocol=https \
file://disable_acl_header_check.patch \
@@ -20,8 +21,8 @@ SRC_URI = 
"git://github.com/vim/vim.git;branch=master;protocol=https \
file://racefix.patch \
"
 
-PV .= ".4269"
-SRCREV = "48a604845e33399893d6bf293e71bcd2a412800d"
+PV .= ".4314"
+SRCREV = "8cbf2499179db39a46e700ab04d0b36e22bcc1bb"
 
 # Do not consider .z in x.y.z, as that is updated with every commit
 UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+\.\d+)\.0"
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162155): 
https://lists.openembedded.org/g/openembedded-core/message/162155
Mute This Topic: https://lists.openembedded.org/mt/89318308/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 20/38] binutils: Add fix for CVE-2021-45078

[Anuj Mittal]

From: Richard Purdie 

Backport a fix for CVE-2021-45078.

Signed-off-by: Richard Purdie 
(cherry picked from commit f3128fd1b2e5cbf3683dc69eabc56fbc0bd0e7d5)
Signed-off-by: Anuj Mittal 
---
 .../binutils/binutils-2.37.inc|   1 +
 ...87d12167b1e36193385485c1f6ce92f74f02.patch | 247 ++
 2 files changed, 248 insertions(+)
 create mode 100644 
meta/recipes-devtools/binutils/binutils/161e87d12167b1e36193385485c1f6ce92f74f02.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.37.inc 
b/meta/recipes-devtools/binutils/binutils-2.37.inc
index be0a0a5539..f4427aef45 100644
--- a/meta/recipes-devtools/binutils/binutils-2.37.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.37.inc
@@ -37,5 +37,6 @@ SRC_URI = "\
  file://0016-Check-for-clang-before-checking-gcc-version.patch \
  file://0017-bfd-Close-the-file-descriptor-if-there-is-no-archive.patch \
  file://0001-CVE-2021-42574.patch \
+ file://161e87d12167b1e36193385485c1f6ce92f74f02.patch \
 "
 S  = "${WORKDIR}/git"
diff --git 
a/meta/recipes-devtools/binutils/binutils/161e87d12167b1e36193385485c1f6ce92f74f02.patch
 
b/meta/recipes-devtools/binutils/binutils/161e87d12167b1e36193385485c1f6ce92f74f02.patch
new file mode 100644
index 00..8a655af06c
--- /dev/null
+++ 
b/meta/recipes-devtools/binutils/binutils/161e87d12167b1e36193385485c1f6ce92f74f02.patch
@@ -0,0 +1,247 @@
+From: Alan Modra 
+Date: Wed, 15 Dec 2021 01:18:42 + (+1030)
+Subject: PR28694, Out-of-bounds write in stab_xcoff_builtin_type
+CVE: CVE-2021-45078
+
+Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=161e87d12167b1e36193385485c1f6ce92f74f02]
+
+PR28694, Out-of-bounds write in stab_xcoff_builtin_type
+
+   PR 28694
+   * stabs.c (stab_xcoff_builtin_type): Make typenum unsigned.
+   Negate typenum earlier, simplifying bounds checking.  Correct
+   off-by-one indexing.  Adjust switch cases.
+---
+
+diff --git a/binutils/stabs.c b/binutils/stabs.c
+index 274bfb0e7fa..83ee3ea5fa4 100644
+--- a/binutils/stabs.c
 b/binutils/stabs.c
+@@ -202,7 +202,7 @@ static debug_type stab_find_type (void *, struct 
stab_handle *, const int *);
+ static bool stab_record_type
+   (void *, struct stab_handle *, const int *, debug_type);
+ static debug_type stab_xcoff_builtin_type
+-  (void *, struct stab_handle *, int);
++  (void *, struct stab_handle *, unsigned int);
+ static debug_type stab_find_tagged_type
+   (void *, struct stab_handle *, const char *, int, enum debug_type_kind);
+ static debug_type *stab_demangle_argtypes
+@@ -3496,166 +3496,167 @@ stab_record_type (void *dhandle ATTRIBUTE_UNUSED, 
struct stab_handle *info,
+ 
+ static debug_type
+ stab_xcoff_builtin_type (void *dhandle, struct stab_handle *info,
+-   int typenum)
++   unsigned int typenum)
+ {
+   debug_type rettype;
+   const char *name;
+ 
+-  if (typenum >= 0 || typenum < -XCOFF_TYPE_COUNT)
++  typenum = -typenum - 1;
++  if (typenum >= XCOFF_TYPE_COUNT)
+ {
+-  fprintf (stderr, _("Unrecognized XCOFF type %d\n"), typenum);
++  fprintf (stderr, _("Unrecognized XCOFF type %d\n"), -typenum - 1);
+   return DEBUG_TYPE_NULL;
+ }
+-  if (info->xcoff_types[-typenum] != NULL)
+-return info->xcoff_types[-typenum];
++  if (info->xcoff_types[typenum] != NULL)
++return info->xcoff_types[typenum];
+ 
+-  switch (-typenum)
++  switch (typenum)
+ {
+-case 1:
++case 0:
+   /* The size of this and all the other types are fixed, defined
+by the debugging format.  */
+   name = "int";
+   rettype = debug_make_int_type (dhandle, 4, false);
+   break;
+-case 2:
++case 1:
+   name = "char";
+   rettype = debug_make_int_type (dhandle, 1, false);
+   break;
+-case 3:
++case 2:
+   name = "short";
+   rettype = debug_make_int_type (dhandle, 2, false);
+   break;
+-case 4:
++case 3:
+   name = "long";
+   rettype = debug_make_int_type (dhandle, 4, false);
+   break;
+-case 5:
++case 4:
+   name = "unsigned char";
+   rettype = debug_make_int_type (dhandle, 1, true);
+   break;
+-case 6:
++case 5:
+   name = "signed char";
+   rettype = debug_make_int_type (dhandle, 1, false);
+   break;
+-case 7:
++case 6:
+   name = "unsigned short";
+   rettype = debug_make_int_type (dhandle, 2, true);
+   break;
+-case 8:
++case 7:
+   name = "unsigned int";
+   rettype = debug_make_int_type (dhandle, 4, true);
+   break;
+-case 9:
++case 8:
+   name = "unsigned";
+   rettype = debug_make_int_type (dhandle, 4, true);
+   break;
+-case 10:
++case 9:
+   name = "unsigned long";
+   rettype = debug_make_int_type (dhandle, 4, true);
+   break;
+-case 11:
++case 10:
+   name = "void";
+   rettype = debug_make_void_type (dhandle);
+   break;
+-case 

[OE-core] [honister][PATCH 18/38] devtool: deploy-target: Remove stripped binaries in pseudo context

[Anuj Mittal]

From: Florian Amstutz 

deploy-target may fail the second time with "pseudo abort" because
devtool-deploy-target-stripped is deleted outside of pseudo's fakeroot
context.

Signed-off-by: Florian Amstutz 
Signed-off-by: Richard Purdie 
(cherry picked from commit 2338a33b690b0bbe279cde3f73764911b239cb50)
Signed-off-by: Anuj Mittal 
---
 scripts/lib/devtool/deploy.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/devtool/deploy.py b/scripts/lib/devtool/deploy.py
index 833322571f..e14a587417 100644
--- a/scripts/lib/devtool/deploy.py
+++ b/scripts/lib/devtool/deploy.py
@@ -170,7 +170,7 @@ def deploy(args, config, basepath, workspace):
 srcdir = recipe_outdir
 recipe_outdir = os.path.join(rd.getVar('WORKDIR'), 
'devtool-deploy-target-stripped')
 if os.path.isdir(recipe_outdir):
-bb.utils.remove(recipe_outdir, True)
+exec_fakeroot(rd, "rm -rf %s" % recipe_outdir, shell=True)
 exec_fakeroot(rd, "cp -af %s %s" % (os.path.join(srcdir, '.'), 
recipe_outdir), shell=True)
 os.environ['PATH'] = ':'.join([os.environ['PATH'], 
rd.getVar('PATH') or ''])
 oe.package.strip_execs(args.recipename, recipe_outdir, 
rd.getVar('STRIP'), rd.getVar('libdir'),
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162154): 
https://lists.openembedded.org/g/openembedded-core/message/162154
Mute This Topic: https://lists.openembedded.org/mt/89318306/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 17/38] scripts/runqemu-ifdown: Don't treat the last iptables command as special

[Anuj Mittal]

From: Daniel Müller 

The runqemu-ifup script performs a bunch of setup steps that
runqemu-ifdown attempts to undo later on. While a bunch of said setup
operations are considered fatal should they fail, the iptables based NAT
setup notably is not.
The tear down procedure in runqemu-ifdown, however, has the iptables
based tear down as the last operation, with the status of it determining
the overall status of the script. Hence, if this step fails, the script
is considered a failure overall. That is arguably inconsistent: If the
NAT setup did not succeed, the tear down cannot succeed either.
To ensure similarity of the two paths, let's not treat the last iptables
tear down operation any special and allow it to fail the runqemu-ifdown
script, but just ignore failures.

Background: we have seen a NAT related setup problem on the ifup path
(which didn't cause script failure), but then saw an issue bubbled up
when this operation was meant to be undone on the ifdown path.

Signed-off-by: Daniel Müller 
Signed-off-by: Richard Purdie 
(cherry picked from commit 0ebcfb034bcad81efef5f746f0aa0b69772901a0)
Signed-off-by: Anuj Mittal 
---
 scripts/runqemu-ifdown | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/runqemu-ifdown b/scripts/runqemu-ifdown
index a104c37bf8..e0eb5344c6 100755
--- a/scripts/runqemu-ifdown
+++ b/scripts/runqemu-ifdown
@@ -64,3 +64,4 @@ n=$[ (`echo $TAP | sed 's/tap//'` * 2) + 1 ]
 dest=$[ (`echo $TAP | sed 's/tap//'` * 2) + 2 ]
 $IPTABLES -D POSTROUTING -t nat -j MASQUERADE -s 192.168.7.$n/32
 $IPTABLES -D POSTROUTING -t nat -j MASQUERADE -s 192.168.7.$dest/32
+true
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162152): 
https://lists.openembedded.org/g/openembedded-core/message/162152
Mute This Topic: https://lists.openembedded.org/mt/89318304/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 08/38] gstreamer1.0-omx: 1.18.5 -> 1.18.6

[Anuj Mittal]

From: Jose Quaresma 

Signed-off-by: Jose Quaresma 
Signed-off-by: Anuj Mittal 
---
 .../{gstreamer1.0-omx_1.18.5.bb => gstreamer1.0-omx_1.18.6.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-omx_1.18.5.bb => 
gstreamer1.0-omx_1.18.6.bb} (95%)

diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.18.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.18.6.bb
similarity index 95%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.18.5.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.18.6.bb
index b2c1eb3ea0..a220d677aa 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.18.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.18.6.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=4fbd65380cdd255951079008b364516c \
 
 SRC_URI = "https://gstreamer.freedesktop.org/src/gst-omx/gst-omx-${PV}.tar.xz;
 
-SRC_URI[sha256sum] = 
"2cd457c1e8deb1a9b39608048fb36a44f6c9a864a6b6115b1453a32e7be93b42"
+SRC_URI[sha256sum] = 
"b5281c938e959fd2418e989cfb6065fdd9fe5f6f87ee86236c9427166e708163"
 
 S = "${WORKDIR}/gst-omx-${PV}"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162153): 
https://lists.openembedded.org/g/openembedded-core/message/162153
Mute This Topic: https://lists.openembedded.org/mt/89318305/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 16/38] cve-check: create directory of CVE_CHECK_MANIFEST before copy

[Anuj Mittal]

From: Stefan Herbrechtsmeier 

Create directory of the CVE_CHECK_MANIFEST variable before copy to it,
so that the variable can use an arbitrary directory name.

Signed-off-by: Stefan Herbrechtsmeier 
Signed-off-by: Richard Purdie 
(cherry picked from commit 9829c16301bf2dce39fa046401a984f112fa0322)
Signed-off-by: Anuj Mittal 
---
 meta/classes/cve-check.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 6c04ff9f09..21d3da7974 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -144,6 +144,7 @@ python cve_check_write_rootfs_manifest () {
 manifest_name = d.getVar("CVE_CHECK_MANIFEST")
 cve_tmp_file = d.getVar("CVE_CHECK_TMP_FILE")
 
+bb.utils.mkdirhier(os.path.dirname(manifest_name))
 shutil.copyfile(cve_tmp_file, manifest_name)
 
 if manifest_name and os.path.exists(manifest_name):
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162151): 
https://lists.openembedded.org/g/openembedded-core/message/162151
Mute This Topic: https://lists.openembedded.org/mt/89318303/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 12/38] gst-examples: 1.18.5 -> 1.18.6

[Anuj Mittal]

From: Jose Quaresma 

Signed-off-by: Jose Quaresma 
Signed-off-by: Anuj Mittal 
---
 .../{gst-examples_1.18.5.bb => gst-examples_1.18.6.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-multimedia/gstreamer/{gst-examples_1.18.5.bb => 
gst-examples_1.18.6.bb} (96%)

diff --git a/meta/recipes-multimedia/gstreamer/gst-examples_1.18.5.bb 
b/meta/recipes-multimedia/gstreamer/gst-examples_1.18.6.bb
similarity index 96%
rename from meta/recipes-multimedia/gstreamer/gst-examples_1.18.5.bb
rename to meta/recipes-multimedia/gstreamer/gst-examples_1.18.6.bb
index a720bb73ff..2a7a3c3111 100644
--- a/meta/recipes-multimedia/gstreamer/gst-examples_1.18.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gst-examples_1.18.6.bb
@@ -12,7 +12,7 @@ SRC_URI = 
"git://gitlab.freedesktop.org/gstreamer/gst-examples.git;protocol=http
file://gst-player.desktop \
"
 
-SRCREV = "fe9a365dc0f1ff632abcfe3322ac5527a2cf30a0"
+SRCREV = "70e4fcf4fc8ae19641aa990de5f37d758cdfcea4"
 
 S = "${WORKDIR}/git"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162147): 
https://lists.openembedded.org/g/openembedded-core/message/162147
Mute This Topic: https://lists.openembedded.org/mt/89318299/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 13/38] mc: fix build if ncurses have been configured without wide characters

[Anuj Mittal]

From: Christian Eggers 

Some distros like poky-tiny set ENABLE_WIDEC=false, which disables wide
character support for ncurses. The new patch fixes the build of mc for
this case.

Since 9000f8033662, NCURSES_WIDECHAR is set explicitly to 1 for musl.
This doesn't work for ENABLE_WIDEC==false. In this case,
NCURSES_WIDECHAR must be set explicitly to 0, as curses.h does not
record whether the ncurses library has actually been built with or
without wide characters.

Fixes: 9000f8033662 ("mc: upgrade 4.8.25 -> 4.8.26")
Signed-off-by: Christian Eggers 
Signed-off-by: Richard Purdie 
Signed-off-by: Anuj Mittal 
---
 ...FTBFS-with-ncurses-build-with-disabl.patch | 87 +++
 meta/recipes-extended/mc/mc_4.8.27.bb |  5 +-
 2 files changed, 91 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-extended/mc/files/0001-Ticket-4200-fix-FTBFS-with-ncurses-build-with-disabl.patch

diff --git 
a/meta/recipes-extended/mc/files/0001-Ticket-4200-fix-FTBFS-with-ncurses-build-with-disabl.patch
 
b/meta/recipes-extended/mc/files/0001-Ticket-4200-fix-FTBFS-with-ncurses-build-with-disabl.patch
new file mode 100644
index 00..408473664f
--- /dev/null
+++ 
b/meta/recipes-extended/mc/files/0001-Ticket-4200-fix-FTBFS-with-ncurses-build-with-disabl.patch
@@ -0,0 +1,87 @@
+From e7bbf72544ab62db9c92bfe7bd1155227e78c621 Mon Sep 17 00:00:00 2001
+From: Andrew Borodin 
+Date: Sat, 28 Aug 2021 11:46:53 +0300
+Subject: [PATCH] Ticket #4200: fix FTBFS with ncurses build with
+ --disable-widec.
+
+Upstream-Status: Accepted 
[https://github.com/MidnightCommander/mc/commit/e7bbf72544]
+Signed-off-by: Andrew Borodin 
+---
+ lib/tty/tty-ncurses.c   | 8 
+ lib/tty/tty-ncurses.h   | 5 +
+ lib/tty/tty-slang.h | 2 ++
+ src/filemanager/boxes.c | 2 ++
+ 4 files changed, 17 insertions(+)
+
+diff --git a/lib/tty/tty-ncurses.c b/lib/tty/tty-ncurses.c
+index f619c0a7bf31..13058a624208 100644
+--- a/lib/tty/tty-ncurses.c
 b/lib/tty/tty-ncurses.c
+@@ -560,6 +560,7 @@ tty_fill_region (int y, int x, int rows, int cols, 
unsigned char ch)
+ void
+ tty_colorize_area (int y, int x, int rows, int cols, int color)
+ {
++#ifdef ENABLE_SHADOWS
+ cchar_t *ctext;
+ wchar_t wch[10];/* TODO not sure if the length is correct */
+ attr_t attrs;
+@@ -585,6 +586,13 @@ tty_colorize_area (int y, int x, int rows, int cols, int 
color)
+ }
+ 
+ g_free (ctext);
++#else
++(void) y;
++(void) x;
++(void) rows;
++(void) cols;
++(void) color;
++#endif /* ENABLE_SHADOWS */
+ }
+ 
+ /* 
-
 */
+diff --git a/lib/tty/tty-ncurses.h b/lib/tty/tty-ncurses.h
+index d75df9533ab9..8feb17ccd045 100644
+--- a/lib/tty/tty-ncurses.h
 b/lib/tty/tty-ncurses.h
+@@ -30,6 +30,11 @@
+ #define NCURSES_CONST const
+ #endif
+ 
++/* do not draw shadows if NCurses is built with --disable-widec */
++#if defined(NCURSES_WIDECHAR) && NCURSES_WIDECHAR
++#define ENABLE_SHADOWS 1
++#endif
++
+ /*** typedefs(not structures) and defined constants 
**/
+ 
+ /*** enums 
***/
+diff --git a/lib/tty/tty-slang.h b/lib/tty/tty-slang.h
+index 5b12c6512853..eeaade388af4 100644
+--- a/lib/tty/tty-slang.h
 b/lib/tty/tty-slang.h
+@@ -23,6 +23,8 @@
+ #define COLS  SLtt_Screen_Cols
+ #define LINES SLtt_Screen_Rows
+ 
++#define ENABLE_SHADOWS 1
++
+ /*** enums 
***/
+ 
+ enum
+diff --git a/src/filemanager/boxes.c b/src/filemanager/boxes.c
+index 3eb525be4a9b..98df5ff2ed9a 100644
+--- a/src/filemanager/boxes.c
 b/src/filemanager/boxes.c
+@@ -280,7 +280,9 @@ appearance_box_callback (Widget * w, Widget * sender, 
widget_msg_t msg, int parm
+ switch (msg)
+ {
+ case MSG_INIT:
++#ifdef ENABLE_SHADOWS
+ if (!tty_use_colors ())
++#endif
+ {
+ Widget *shadow;
+ 
+-- 
+2.34.1
+
diff --git a/meta/recipes-extended/mc/mc_4.8.27.bb 
b/meta/recipes-extended/mc/mc_4.8.27.bb
index 546e615d1d..e877780ea0 100644
--- a/meta/recipes-extended/mc/mc_4.8.27.bb
+++ b/meta/recipes-extended/mc/mc_4.8.27.bb
@@ -11,6 +11,7 @@ RRECOMMENDS:${PN} = "ncurses-terminfo"
 SRC_URI = "http://www.midnight-commander.org/downloads/${BPN}-${PV}.tar.bz2 \
file://0001-mc-replace-perl-w-with-use-warnings.patch \
file://nomandate.patch \
+   
file://0001-Ticket-4200-fix-FTBFS-with-ncurses-build-with-disabl.patch \
"
 SRC_URI[sha256sum] = 
"2f52dd9c75c20d8eac7701bd3a8c6c125aaf8cdd9cf12b78ca50a0102b543407"
 
@@ -27,7 +28,9 @@ PACKAGECONFIG ??= ""
 PACKAGECONFIG[smb] = "--enable-vfs-smb,--disable-vfs-smb,samba,"
 PACKAGECONFIG[sftp] = "--enable-vfs-sftp,--disable-vfs-sftp,libssh2,"
 
-CFLAGS:append:libc-musl = ' -DNCURSES_WIDECHAR=1 '
+# enable NCURSES_WIDECHAR=1 only if 

[OE-core] [honister][PATCH 15/38] recipetool: Fix circular reference in SRC_URI

[Anuj Mittal]

From: Saul Wold 

When creating a new recipe.bb file for a binary, don't use BP which
includes the version information, instead use BPN which is just the
name base Package Name.

Since PB is not specified, it takes the default:
PV = "1.0+git${SRCPV}"

But SRCPV is defined in terms of the SRC_URI, which leads to infinite
recursion (traceback below). Here are the pertinent variables which
cause the recursion:

SRC_URI = "git://github.com/lvc/abi-dumper;protocol=https;subdir=${BP}"
BP = "${BPN}-${PV}"
PV = "1.0+git${SRCPV}"
SRCPV = "${@bb.fetch2.get_srcrev(d)}"

def get_srcrev(d, method_name='sortable_revision'):
# ... trimmed
scms = []
fetcher = Fetch(d.getVar('SRC_URI').split(), d)
# ... trimmed

[YOCTO #14040]

Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie 
(cherry picked from commit 3b8d43fc53ee13d39abc3b2a1f706a97fcf752aa)
Signed-off-by: Anuj Mittal 
---
 scripts/lib/recipetool/create.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/recipetool/create.py b/scripts/lib/recipetool/create.py
index 63e7f0658b..b4b1f817f1 100644
--- a/scripts/lib/recipetool/create.py
+++ b/scripts/lib/recipetool/create.py
@@ -435,7 +435,7 @@ def create_recipe(args):
 if args.binary:
 # Assume the archive contains the directory structure verbatim
 # so we need to extract to a subdirectory
-fetchuri += ';subdir=${BP}'
+fetchuri += ';subdir=${BPN}'
 srcuri = fetchuri
 rev_re = re.compile(';rev=([^;]+)')
 res = rev_re.search(srcuri)
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162150): 
https://lists.openembedded.org/g/openembedded-core/message/162150
Mute This Topic: https://lists.openembedded.org/mt/89318302/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 14/38] sdk: fix search for dynamic loader

[Anuj Mittal]

From: Christian Eggers 

if the package "nativesdk-glibc-dbg" is installed as part of the SDK,
the existing search expression finds two files:

$OECORE_NATIVE_SYSROOT/lib/.debug/ld-linux-x86-64.so.2
$OECORE_NATIVE_SYSROOT/lib/ld-linux-x86-64.so.2

The generated relocate_sdk.sh shell script contains then an extra
newline and segfaults during SDK relocation.

Limit the search depth to 1, to avoid finding the file in the .debug
directory.

Signed-off-by: Christian Eggers 
Signed-off-by: Richard Purdie 
Signed-off-by: Anuj Mittal 
---
 meta/files/toolchain-shar-relocate.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/files/toolchain-shar-relocate.sh 
b/meta/files/toolchain-shar-relocate.sh
index 3ece04db0a..cee9adbf39 100644
--- a/meta/files/toolchain-shar-relocate.sh
+++ b/meta/files/toolchain-shar-relocate.sh
@@ -5,7 +5,7 @@ fi
 
 # fix dynamic loader paths in all ELF SDK binaries
 native_sysroot=$($SUDO_EXEC cat $env_setup_script |grep 
'OECORE_NATIVE_SYSROOT='|cut -d'=' -f2|tr -d '"')
-dl_path=$($SUDO_EXEC find $native_sysroot/lib -name "ld-linux*")
+dl_path=$($SUDO_EXEC find $native_sysroot/lib -maxdepth 1 -name "ld-linux*")
 if [ "$dl_path" = "" ] ; then
echo "SDK could not be set up. Relocate script unable to find 
ld-linux.so. Abort!"
exit 1
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162149): 
https://lists.openembedded.org/g/openembedded-core/message/162149
Mute This Topic: https://lists.openembedded.org/mt/89318301/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [honister][PATCH 10/38] gstreamer1.0-python: 1.18.5 -> 1.18.6

[Anuj Mittal]

From: Jose Quaresma 

Signed-off-by: Jose Quaresma 
Signed-off-by: Anuj Mittal 
---
 ...reamer1.0-python_1.18.5.bb => gstreamer1.0-python_1.18.6.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-python_1.18.5.bb => 
gstreamer1.0-python_1.18.6.bb} (91%)

diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.18.5.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.18.6.bb
similarity index 91%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.18.5.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.18.6.bb
index 74dd15b3eb..c80c3928eb 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.18.5.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-python_1.18.6.bb
@@ -8,7 +8,7 @@ LICENSE = "LGPLv2.1"
 LIC_FILES_CHKSUM = "file://COPYING;md5=c34deae4e395ca07e725ab0076a5f740"
 
 SRC_URI = 
"https://gstreamer.freedesktop.org/src/${PNREAL}/${PNREAL}-${PV}.tar.xz;
-SRC_URI[sha256sum] = 
"533685871305959d6db89507f3b3aa6c765c2f2b0dacdc32c5a6543e72e5bc52"
+SRC_URI[sha256sum] = 
"bdc0ea22fbd7335ad9decc151561aacc53c51206a9735b81eac700ce5b0bbd4a"
 
 DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base python3-pygobject"
 RDEPENDS:${PN} += "gstreamer1.0 gstreamer1.0-plugins-base python3-pygobject"
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162145): 
https://lists.openembedded.org/g/openembedded-core/message/162145
Mute This Topic: https://lists.openembedded.org/mt/89318297/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-