[OE-core] [poky][dunfell][PATCH 8/8] libcap: Use specific BSD license variant

2022-01-31 Thread Nisha Parrakat 
From: Joshua Watt 

Make the license more accurate by specifying the specific variant of BSD
license instead of the generic one. This helps with SPDX license
attribution as "BSD" is not a valid SPDX license.

(From OE-Core rev: 9e8b2bc55792932e23d3b053b393b7ff88bffd6b)

Signed-off-by: Joshua Watt 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-support/libcap/libcap_2.32.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/libcap/libcap_2.32.bb 
b/meta/recipes-support/libcap/libcap_2.32.bb
index 325fa87a1b..d67babb5e9 100644
--- a/meta/recipes-support/libcap/libcap_2.32.bb
+++ b/meta/recipes-support/libcap/libcap_2.32.bb
@@ -4,7 +4,7 @@ These allow giving various kinds of specific privileges to 
individual \
 users, without giving them full root permissions."
 HOMEPAGE = "http://sites.google.com/site/fullycapable/;
 # no specific GPL version required
-LICENSE = "BSD | GPLv2"
+LICENSE = "BSD-3-Clause | GPLv2"
 LIC_FILES_CHKSUM = "file://License;md5=3f84fd6f29d453a56514cb7e4ead25f1"
 
 DEPENDS = "hostperl-runtime-native gperf-native"
-- 
2.17.1


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

[OE-core] [poky][dunfell][PATCH 6/8] shadow: Use specific BSD license variant

2022-01-31 Thread Nisha Parrakat 
From: Joshua Watt 

Make the license more accurate by specifying the specific variant of BSD
license instead of the generic one. This helps with SPDX license
attribution as "BSD" is not a valid SPDX license.

(From OE-Core rev: 65e3b23e1b266653fd30c90222e953f7e37fba0c)

Signed-off-by: Joshua Watt 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-extended/shadow/shadow.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/shadow/shadow.inc 
b/meta/recipes-extended/shadow/shadow.inc
index 7061dc7505..bfe50c18f6 100644
--- a/meta/recipes-extended/shadow/shadow.inc
+++ b/meta/recipes-extended/shadow/shadow.inc
@@ -3,7 +3,7 @@ HOMEPAGE = "http://github.com/shadow-maint/shadow;
 DESCRIPTION = "${SUMMARY}"
 BUGTRACKER = "http://github.com/shadow-maint/shadow/issues;
 SECTION = "base/utils"
-LICENSE = "BSD | Artistic-1.0"
+LICENSE = "BSD-3-Clause | Artistic-1.0"
 LIC_FILES_CHKSUM = "file://COPYING;md5=ed80ff1c2b40843cf5768e5229cf16e5 \
 
file://src/passwd.c;beginline=2;endline=30;md5=5720ff729a6ff39ecc9f64555d75f4af"
 
-- 
2.17.1


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

[OE-core] [poky][dunfell][PATCH 7/8] shadow-sysroot: sync license with shadow

2022-01-31 Thread Nisha Parrakat 
From: Ross Burton 

This recipe is just a single data file from shadow, but as we can't
easily tell what license that specific file is under just copy the full
license statement.

(From OE-Core rev: f0e2f3b1f855ea6e184bd1d8d796279fedcbfa33)

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-extended/shadow/shadow-sysroot_4.6.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/shadow/shadow-sysroot_4.6.bb 
b/meta/recipes-extended/shadow/shadow-sysroot_4.6.bb
index 5f7ea00bf1..4e68f826c6 100644
--- a/meta/recipes-extended/shadow/shadow-sysroot_4.6.bb
+++ b/meta/recipes-extended/shadow/shadow-sysroot_4.6.bb
@@ -2,7 +2,7 @@ SUMMARY = "Shadow utils requirements for useradd.bbclass"
 HOMEPAGE = "http://github.com/shadow-maint/shadow;
 BUGTRACKER = "http://github.com/shadow-maint/shadow/issues;
 SECTION = "base utils"
-LICENSE = "BSD | Artistic-1.0"
+LICENSE = "BSD-3-Clause | Artistic-1.0"
 LIC_FILES_CHKSUM = 
"file://login.defs_shadow-sysroot;md5=25e2f2de4dfc8f966ac5cdfce45cd7d5"
 
 DEPENDS = "base-passwd"
-- 
2.17.1


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

[OE-core] [poky][dunfell][PATCH 4/8] e2fsprogs: Use specific BSD license variant

2022-01-31 Thread Nisha Parrakat 
From: Joshua Watt 

Make the license more accurate by specifying the specific variant of BSD
license instead of the generic one. This helps with SPDX license
attribution as "BSD" is not a valid SPDX license.

(From OE-Core rev: 966fb77981e4fed0ab7998439940b1e05dd0ee43)

Signed-off-by: Joshua Watt 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-devtools/e2fsprogs/e2fsprogs.inc | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
index 45fb9720ee..08fb30fc71 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
@@ -3,12 +3,12 @@ DESCRIPTION = "The Ext2 Filesystem Utilities (e2fsprogs) 
contain all of the stan
 fixing, configuring , and debugging ext2 filesystems."
 HOMEPAGE = "http://e2fsprogs.sourceforge.net/;
 
-LICENSE = "GPLv2 & LGPLv2 & BSD & MIT"
-LICENSE_e2fsprogs-dumpe2fs = "GPLv2"
-LICENSE_e2fsprogs-e2fsck = "GPLv2"
-LICENSE_e2fsprogs-mke2fs = "GPLv2"
-LICENSE_e2fsprogs-tune2fs = "GPLv2"
-LICENSE_e2fsprogs-badblocks = "GPLv2"
+LICENSE = "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
+LICENSE:e2fsprogs-dumpe2fs = "GPLv2"
+LICENSE:e2fsprogs-e2fsck = "GPLv2"
+LICENSE:e2fsprogs-mke2fs = "GPLv2"
+LICENSE:e2fsprogs-tune2fs = "GPLv2"
+LICENSE:e2fsprogs-badblocks = "GPLv2"
 LIC_FILES_CHKSUM = "file://NOTICE;md5=d50be0580c0b0a7fbc7a4830bbe6c12b \
   
file://lib/ext2fs/ext2fs.h;beginline=1;endline=9;md5=596a8dedcb4e731c6b21c7a46fba6bef
 \
   
file://lib/e2p/e2p.h;beginline=1;endline=7;md5=8a74ade8f9d65095d70ef2d4bf48e36a 
\
-- 
2.17.1


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

[OE-core] [poky][dunfell][PATCH 5/8] glib-2.0: Use specific BSD license variant

2022-01-31 Thread Nisha Parrakat 
From: Joshua Watt 

Make the license more accurate by specifying the specific variant of BSD
license instead of the generic one. This helps with SPDX license
attribution as "BSD" is not a valid SPDX license.

(From OE-Core rev: 91cd1ef01a3f3883c04bac67af2672ec60e20fb8)

Signed-off-by: Joshua Watt 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-core/glib-2.0/glib.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/glib-2.0/glib.inc 
b/meta/recipes-core/glib-2.0/glib.inc
index c3ddf18387..1849a6e05c 100644
--- a/meta/recipes-core/glib-2.0/glib.inc
+++ b/meta/recipes-core/glib-2.0/glib.inc
@@ -4,7 +4,7 @@ HOMEPAGE = "https://developer.gnome.org/glib/;
 
 # pcre is under BSD;
 # docs/reference/COPYING is with a 'public domain'-like license!
-LICENSE = "LGPLv2.1+ & BSD & PD"
+LICENSE = "LGPLv2.1+ & BSD-3-Clause & PD"
 LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c \
 
file://glib/glib.h;beginline=4;endline=17;md5=b88abb7f3ad09607e71cb9d530155906 \
 
file://gmodule/COPYING;md5=4fbd65380cdd255951079008b364516c \
-- 
2.17.1


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

[OE-core] [poky][dunfell][PATCH 3/8] tzdata: Remove BSD License specifier

2022-01-31 Thread Nisha Parrakat 
From: Joshua Watt 

The code in question is licensed under the BSD-3-Clause license, so
including the generic "BSD" license is unnecessary.

(From OE-Core rev: c39fc075ce3fd5b53c2a2fccb43500ee0a12f39d)

Signed-off-by: Joshua Watt 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-extended/timezone/timezone.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/timezone/timezone.inc 
b/meta/recipes-extended/timezone/timezone.inc
index e9eb249afe..43d14d7f12 100644
--- a/meta/recipes-extended/timezone/timezone.inc
+++ b/meta/recipes-extended/timezone/timezone.inc
@@ -3,7 +3,7 @@ DESCRIPTION = "The Time Zone Database contains code and data 
that represent \
 the history of local time for many representative locations around the globe."
 HOMEPAGE = "http://www.iana.org/time-zones;
 SECTION = "base"
-LICENSE = "PD & BSD & BSD-3-Clause"
+LICENSE = "PD & BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
 
 PV = "2021e"
-- 
2.17.1


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

[OE-core] [poky][dunfell][PATCH 2/8] lsof: correct LICENSE

2022-01-31 Thread Nisha Parrakat 
From: Ross Burton 

The lsof LICENSE is superficially BSD-like, but it isn't BSD.  Now that
we have the full SPDX license set in oe-core, use Spencer-94.

(From OE-Core rev: 5c1d61d1d4dfacb643a366285c0392e6a31087ed)

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
Signed-off-by: Nisha Parrakat 
---
 meta/recipes-extended/lsof/lsof_4.91.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/lsof/lsof_4.91.bb 
b/meta/recipes-extended/lsof/lsof_4.91.bb
index b3adfd57af..7c85bf23fc 100644
--- a/meta/recipes-extended/lsof/lsof_4.91.bb
+++ b/meta/recipes-extended/lsof/lsof_4.91.bb
@@ -3,7 +3,7 @@ DESCRIPTION = "Lsof is a Unix-specific diagnostic tool. \
 Its name stands for LiSt Open Files, and it does just that."
 HOMEPAGE = "http://people.freebsd.org/~abe/;
 SECTION = "devel"
-LICENSE = "BSD"
+LICENSE = "Spencer-94"
 LIC_FILES_CHKSUM = 
"file://00README;beginline=645;endline=679;md5=964df275d26429ba3b39dbb9f205172a"
 
 # Upstream lsof releases are hosted on an ftp server which times out download
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161146): 
https://lists.openembedded.org/g/openembedded-core/message/161146
Mute This Topic: https://lists.openembedded.org/mt/88827818/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] yocto-check-layer: add ability to perform tests from a global bbclass

2022-01-31 Thread Denys Dmytriyenko 
This is useful when needing to test layer's recipes, where this special
bbclass can define a global python function that gets called on each
recipe parsing during "bitbake -S none world" signature dump and be able
to fail layer's check accordingly.

First test being added is to detect recipes skipping "installed-vs-shipped"
QA check. As "installed-vs-shipped" is a packaging QA check, it happens very
late in the build process and failing it could mean some potential issues
with packaging, especially when recipe uses BBCLASSEXTEND="nativesdk" and
resulting package is used in an SDK.

In OE-Core failing this QA check leads to an error, but other layers can
suppress it or change it to a warning. Detecting weird packaging problems
with SDKs is quite difficult and time consuming. Also, waiting for the
actual "installed-vs-shipped" packaging QA check to fail means that all
recipes in the layer under test have to run through all standard tasks in
the build chain, equivalent to a multi-hour world-build.

Hence yocto-check-layer takes a shortcut and only detects a mere attempt
at skipping "installed-vs-shipped" QA check in the INSANE_SKIP list during
initial parsing when dumping the signature information for the layer.

Signed-off-by: Denys Dmytriyenko 
---
 meta/classes/yocto-check-layer.bbclass | 16 
 scripts/lib/checklayer/__init__.py |  5 -
 scripts/lib/checklayer/cases/common.py | 15 +++
 3 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 meta/classes/yocto-check-layer.bbclass

diff --git a/meta/classes/yocto-check-layer.bbclass 
b/meta/classes/yocto-check-layer.bbclass
new file mode 100644
index 000..329d3f8
--- /dev/null
+++ b/meta/classes/yocto-check-layer.bbclass
@@ -0,0 +1,16 @@
+#
+# This class is used by yocto-check-layer script for additional per-recipe 
tests
+# The first test ensures that the layer has no recipes skipping 
'installed-vs-shipped' QA checks
+#
+
+WARN_QA:remove = "installed-vs-shipped"
+ERROR_QA:append = " installed-vs-shipped"
+
+python () {
+packages = set((d.getVar('PACKAGES') or '').split())
+for package in packages:
+skip = set((d.getVar('INSANE_SKIP') or "").split() +
+   (d.getVar('INSANE_SKIP:' + package) or "").split())
+if 'installed-vs-shipped' in skip:
+oe.qa.handle_error("installed-vs-shipped", 'Package %s is skipping 
"installed-vs-shipped" QA test.' % package, d)
+}
diff --git a/scripts/lib/checklayer/__init__.py 
b/scripts/lib/checklayer/__init__.py
index e69a10f..9186160 100644
--- a/scripts/lib/checklayer/__init__.py
+++ b/scripts/lib/checklayer/__init__.py
@@ -261,7 +261,7 @@ def check_command(error_msg, cmd, cwd=None):
 raise RuntimeError(msg)
 return output
 
-def get_signatures(builddir, failsafe=False, machine=None):
+def get_signatures(builddir, failsafe=False, machine=None, extravars=None):
 import re
 
 # some recipes needs to be excluded like meta-world-pkgdata
@@ -273,6 +273,9 @@ def get_signatures(builddir, failsafe=False, machine=None):
 tune2tasks = {}
 
 cmd = 'BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE BB_SIGNATURE_HANDLER" 
BB_SIGNATURE_HANDLER="OEBasicHash" '
+if extravars:
+cmd += extravars
+cmd += ' '
 if machine:
 cmd += 'MACHINE=%s ' % machine
 cmd += 'bitbake '
diff --git a/scripts/lib/checklayer/cases/common.py 
b/scripts/lib/checklayer/cases/common.py
index 9f15e05..318cda1 100644
--- a/scripts/lib/checklayer/cases/common.py
+++ b/scripts/lib/checklayer/cases/common.py
@@ -54,6 +54,21 @@ class CommonCheckLayer(OECheckLayerTestCase):
 '''
 get_signatures(self.td['builddir'], failsafe=False)
 
+def test_world_inherit_class(self):
+'''
+This also does "bitbake -S none world" along with inheriting 
"yocto-check-layer"
+class, which can do additional per-recipe test cases.
+'''
+msg = []
+try:
+get_signatures(self.td['builddir'], failsafe=False, machine=None, 
extravars='BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE INHERIT" 
INHERIT="yocto-check-layer"')
+except RuntimeError as ex:
+msg.append(str(ex))
+if msg:
+msg.insert(0, 'Layer %s failed additional checks from 
yocto-check-layer.bbclass\nSee below log for specific recipe parsing errors:\n' 
% \
+self.tc.layer['name'])
+self.fail('\n'.join(msg))
+
 def test_signatures(self):
 if self.tc.layer['type'] == LayerType.SOFTWARE and \
not self.tc.test_software_layer_signatures:
-- 
2.7.4


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161145): 
https://lists.openembedded.org/g/openembedded-core/message/161145
Mute This Topic: https://lists.openembedded.org/mt/88825434/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-01-31 Thread Stephen Jolley 
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 398
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "3.5, "3.6", "3.99" and "Future", the more pressing/urgent
issues being in "3.4" and then "3.5".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161144): 
https://lists.openembedded.org/g/openembedded-core/message/161144
Mute This Topic: https://lists.openembedded.org/mt/88824851/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 WW05`22

2022-01-31 Thread Stephen Jolley 
Current Dev Position: YP 3.5 M3

Next Deadline: 21th Feb. 2022 YP 3.5 M3 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Feb. 3rd 7:30 am PDT (

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

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

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

 

Key Status/Updates:

*   YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to
vacations in Asia the release, if approved, will be made next week.
*   YP 3.1.14 is ready for QA but the release will also be delayed until
next week.
*   Upstream glibc are now planning to remove prelink support in 2.36. I
think we will still want to remove prelink from OE-Core before our next
release though, particularly as it is an LTS.
*   An
 email
proposing inclusive language changes for bitbake and OE-Core has been sent
to the community for review. The aim is to implement this before M3.
*   We are seeing networking issues during image testing on the
centos8/stream8 workers, possibly due to recent changes in the distro. Help
with debugging this welcome.
*   We have also realized there is an issue with hash equivalence where
the current mechanism will not account for different headers inside the
sysroot added through indirect dependencies (e.g. linux-libc-headers via
glibc). This means something like rtcwake in util-linux which uses rtc.h can
have differing debug symbols due to differing line numbers yet otherwise be
identical. There is a potential fix with downsides in master-next.
*
 CVE metrics are still under control for master with
pending patches accounted for (thanks Ross!) but work still remains on the
various stable branches which have high counts.
*   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.

 

YP 3.5 Milestone Dates:

*   YP 3.5 M2 is out of QA
*   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 built
*   YP 3.1.14 Release date 2022/02/04
*   YP 3.4.2 build date 2022/02/07
*   YP 3.4.2 Release date 2022/02/18
*   YP 3.3.5 build date 2022/02/14
*   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 2705 (last week 2700) (

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

*   Total patches found: 1236 (last week 123.)
*   Patches in the Pending State: 342 (28%) [last week 340 (28%)]

 

The Yocto Project's technical governance is through its Technical

[OE-Core][PATCH] connman: update 1.40 -> 1.41

2022-01-31 Thread Changhyeok Bae 
Signed-off-by: Changhyeok Bae 
---
 .../connman/{connman_1.40.bb => connman_1.41.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-connectivity/connman/{connman_1.40.bb => connman_1.41.bb} 
(85%)

diff --git a/meta/recipes-connectivity/connman/connman_1.40.bb 
b/meta/recipes-connectivity/connman/connman_1.41.bb
similarity index 85%
rename from meta/recipes-connectivity/connman/connman_1.40.bb
rename to meta/recipes-connectivity/connman/connman_1.41.bb
index edb23a1267..736b78eaeb 100644
--- a/meta/recipes-connectivity/connman/connman_1.40.bb
+++ b/meta/recipes-connectivity/connman/connman_1.41.bb
@@ -9,7 +9,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
 
 SRC_URI:append:libc-musl = " 
file://0002-resolve-musl-does-not-implement-res_ninit.patch"
 
-SRC_URI[sha256sum] = 
"1a57ae7ce234aa3a1744aac3be5c2121d98dce999440ef8ab9cc4edfd5edcb12"
+SRC_URI[sha256sum] = 
"79fb40f4fdd5530c45aa8e592fb16ba23d3674f3a98cf10b89a6576f198de589"
 
 RRECOMMENDS:${PN} = "connman-conf"
 RCONFLICTS:${PN} = "networkmanager"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161141): 
https://lists.openembedded.org/g/openembedded-core/message/161141
Mute This Topic: https://lists.openembedded.org/mt/88820491/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] [poky][dunfell][PATCH 1/6] lsof: correct LICENSE

2022-01-31 Thread Steve Sakoman 
On Mon, Jan 31, 2022 at 10:22 AM Nisha Parrakat  wrote:
>
> ack. I will submit a new patch set.

You can see the ones I've already pulled in here, so no need to resubmit those:

https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Steve

> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161140): 
https://lists.openembedded.org/g/openembedded-core/message/161140
Mute This Topic: https://lists.openembedded.org/mt/88651664/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 2/2] packages.bbclass: Break out the debug info styles to bitbake variables

2022-01-31 Thread Peter Kjellerstedt 
Break out the hardcoded values for the various debug info styles from
split_and_strip_files() into bitbake variables. This allows the debug
info styles to be adopted, and also allows new styles to be added
(within the limits of the available variables).

Signed-off-by: Peter Kjellerstedt 
---
 meta/classes/package.bbclass | 95 ++--
 1 file changed, 58 insertions(+), 37 deletions(-)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 4927fb99ff..a5358d5851 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1065,6 +1065,51 @@ python fixup_perms () {
 fix_perms(each_file, fs_perms_table[dir].fmode, 
fs_perms_table[dir].fuid, fs_perms_table[dir].fgid, dir)
 }
 
+# Debug info
+PACKAGE_DEBUG_APPEND = "${@d.getVarFlag('PACKAGE_DEBUG_APPEND', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+PACKAGE_DEBUG_STATICAPPEND = "${@d.getVarFlag('PACKAGE_DEBUG_STATICAPPEND', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+PACKAGE_DEBUG_DIR = "${@d.getVarFlag('PACKAGE_DEBUG_DIR', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+PACKAGE_DEBUG_STATICDIR = "${@d.getVarFlag('PACKAGE_DEBUG_STATICDIR', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+PACKAGE_DEBUG_LIBDIR = "${@d.getVarFlag('PACKAGE_DEBUG_LIBDIR', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+PACKAGE_DEBUG_STATICLIBDIR = "${@d.getVarFlag('PACKAGE_DEBUG_STATICLIBDIR', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+PACKAGE_DEBUG_SRCDIR = "${@d.getVarFlag('PACKAGE_DEBUG_SRCDIR', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE'))}"
+
+# Original OE-core, a.k.a. ".debug", style debug info
+PACKAGE_DEBUG_APPEND[.debug] = ""
+PACKAGE_DEBUG_STATICAPPEND[.debug] = ""
+PACKAGE_DEBUG_DIR[.debug] = "/.debug"
+PACKAGE_DEBUG_STATICDIR[.debug] = "/.debug-static"
+PACKAGE_DEBUG_LIBDIR[.debug] = ""
+PACKAGE_DEBUG_STATICLIBDIR[.debug] = ""
+PACKAGE_DEBUG_SRCDIR[.debug] = "/usr/src/debug"
+
+# Single debug-file-directory style debug info
+PACKAGE_DEBUG_APPEND[debug-file-directory] = ".debug"
+PACKAGE_DEBUG_STATICAPPEND[debug-file-directory] = ""
+PACKAGE_DEBUG_DIR[debug-file-directory] = ""
+PACKAGE_DEBUG_STATICDIR[debug-file-directory] = ""
+PACKAGE_DEBUG_LIBDIR[debug-file-directory] = "/usr/lib/debug"
+PACKAGE_DEBUG_STATICLIBDIR[debug-file-directory] = "/usr/lib/debug-static"
+PACKAGE_DEBUG_SRCDIR[debug-file-directory] = "/usr/src/debug"
+
+# Debug info without sources in /usr/src/debug
+PACKAGE_DEBUG_APPEND[debug-without-src] = ""
+PACKAGE_DEBUG_STATICAPPEND[debug-without-src] = ""
+PACKAGE_DEBUG_DIR[debug-without-src] = "/.debug"
+PACKAGE_DEBUG_STATICDIR[debug-without-src] = "/.debug-static"
+PACKAGE_DEBUG_LIBDIR[debug-without-src] = ""
+PACKAGE_DEBUG_STATICLIBDIR[debug-without-src] = ""
+PACKAGE_DEBUG_SRCDIR[debug-without-src] = ""
+
+# Debug info with separate -src packages
+PACKAGE_DEBUG_APPEND[debug-with-srcpkg] = ""
+PACKAGE_DEBUG_STATICAPPEND[debug-with-srcpkg] = ""
+PACKAGE_DEBUG_DIR[debug-with-srcpkg] = "/.debug"
+PACKAGE_DEBUG_STATICDIR[debug-with-srcpkg] = "/.debug-static"
+PACKAGE_DEBUG_LIBDIR[debug-with-srcpkg] = ""
+PACKAGE_DEBUG_STATICLIBDIR[debug-with-srcpkg] = ""
+PACKAGE_DEBUG_SRCDIR[debug-with-srcpkg] = "/usr/src/debug"
+
 python split_and_strip_files () {
 import stat, errno
 import subprocess
@@ -1076,42 +1121,18 @@ python split_and_strip_files () {
 oldcwd = os.getcwd()
 os.chdir(dvar)
 
-# We default to '.debug' style
-if d.getVar('PACKAGE_DEBUG_SPLIT_STYLE') == 'debug-file-directory':
-# Single debug-file-directory style debug info
-debugappend = ".debug"
-debugstaticappend = ""
-debugdir = ""
-debugstaticdir = ""
-debuglibdir = "/usr/lib/debug"
-debugstaticlibdir = "/usr/lib/debug-static"
-debugsrcdir = "/usr/src/debug"
-elif d.getVar('PACKAGE_DEBUG_SPLIT_STYLE') == 'debug-without-src':
-# Original OE-core, a.k.a. ".debug", style debug info, but without 
sources in /usr/src/debug
-debugappend = ""
-debugstaticappend = ""
-debugdir = "/.debug"
-debugstaticdir = "/.debug-static"
-debuglibdir = ""
-debugstaticlibdir = ""
-debugsrcdir = ""
-elif d.getVar('PACKAGE_DEBUG_SPLIT_STYLE') == 'debug-with-srcpkg':
-debugappend = ""
-debugstaticappend = ""
-debugdir = "/.debug"
-debugstaticdir = "/.debug-static"
-debuglibdir = ""
-debugstaticlibdir = ""
-debugsrcdir = "/usr/src/debug"
-else:
-# Original OE-core, a.k.a. ".debug", style debug info
-debugappend = ""
-debugstaticappend = ""
-debugdir = "/.debug"
-debugstaticdir = "/.debug-static"
-debuglibdir = ""
-debugstaticlibdir = ""
-debugsrcdir = "/usr/src/debug"
+# Sanity test that PACKAGE_DEBUG_SPLIT_STYLE has a valid value.
+if d.getVarFlag('PACKAGE_DEBUG_APPEND', 
d.getVar('PACKAGE_DEBUG_SPLIT_STYLE')) is None:
+bb.fatal("Unknown

[OE-core] [PATCH 1/2] glibc-tests: Correct PACKAGE_DEBUG_SPLIT_STYLE

2022-01-31 Thread Peter Kjellerstedt 
It was set to "debug", but the officially supported value is ".debug".

Signed-off-by: Peter Kjellerstedt 
---
 meta/recipes-core/glibc/glibc-tests_2.34.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/glibc/glibc-tests_2.34.bb 
b/meta/recipes-core/glibc/glibc-tests_2.34.bb
index 9cbf8776dd..8c7ecf89ba 100644
--- a/meta/recipes-core/glibc/glibc-tests_2.34.bb
+++ b/meta/recipes-core/glibc/glibc-tests_2.34.bb
@@ -102,7 +102,7 @@ EXCLUDE_FROM_SHLIBS = "1"
 # It is more handy to have _all_ the sources and symbols in one
 # place (package) as this recipe will be used for validation and
 # debugging.
-PACKAGE_DEBUG_SPLIT_STYLE = "debug"
+PACKAGE_DEBUG_SPLIT_STYLE = ".debug"
 
 # glibc test cases violate by default some Yocto/OE checks (staticdev,
 # textrel)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161138): 
https://lists.openembedded.org/g/openembedded-core/message/161138
Mute This Topic: https://lists.openembedded.org/mt/88819086/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] initramfs-framework: Add overlayroot module

2022-01-31 Thread Vyacheslav Yurkov 

Hi Alejandro,
Thanks for the v2, but my questions from v1 are still left unanswered.

1. Do you really need the whole rootfs to be in overlay? Perhaps you 
have another use case in mind, but the more scope overlay has, the more 
migration effort you need in order to update upper layer on image upgrade.
2. I was thinking if perhaps that would be better to extend 
files/overlayfs-etc-preinit.sh.in to suit your needs and re-use common 
parts rather then having a good part of it copied to initramfs-framework?


Cheers,
Vyacheslav

On 29.01.2022 20:48, Alejandro Hernandez Samaniego wrote:

When installed, this module mounts a read-write (RW) overlay on
top of a root filesystem, which is kept read-only (RO), free
from modifications by the user, this might prove to be useful
if we want to access or restore the original unmodified rootfs.

The existing overlay-etc.bbclass does something similar, it
mounts an overlay on top of the /etc directory, however doing
the same for root causes the original root to be inaccessible
once the system is booted, hence why this module is added to
the initramfs boot flow, allowing us to mount the RW overlay,
while keeping the original rootfs mounted at /rofs once the
system finishes booting. This script is loosely based on that
class.

This module requires rootrw= to be passed as a kernel
parameter to specify the device/partition to be used as RW by the
overlay and has a dependency on overlayfs support being present
in the running kernel.

It does not require the read-only IMAGE_FEATURE to be enabled.

The module needs to be executed after the initramfs-module-rootfs
since it relies on it to mount the filesystem at initramfs startup
but before the finish module which normally switches root.
After overlayroot is executed the usual boot flow continues from
the real init process.

If something goes wrong while running this module, the rootfs
is still mounted RO (with no overlay) and the finish module is
executed to continue booting normally.

Its worth noting that, on purpose, this isnt installed by default
on any images that use initramfs-framework to keep the boot flow
unmodified, only when a user manually requests to install it,
then it becomes functional.

Signed-off-by: Alejandro Enedino Hernandez Samaniego 
---
  .../initramfs-framework/overlayroot   | 112 ++
  .../initrdscripts/initramfs-framework_1.0.bb  |   9 ++
  2 files changed, 121 insertions(+)
  create mode 100644 
meta/recipes-core/initrdscripts/initramfs-framework/overlayroot

diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/overlayroot 
b/meta/recipes-core/initrdscripts/initramfs-framework/overlayroot
new file mode 100644
index 00..d40342dc59
--- /dev/null
+++ b/meta/recipes-core/initrdscripts/initramfs-framework/overlayroot
@@ -0,0 +1,112 @@
+#!/bin/sh
+
+# SPDX-License-Identifier: MIT
+#
+# Copyright 2022 (C), Microsoft Corporation
+
+# Simple initramfs module intended to mount a read-write (RW)
+# overlayfs on top of /, keeping the original root filesystem
+# as read-only (RO), free from modifications by the user.
+#
+# NOTE: The read-only IMAGE_FEATURE is not required for this to work
+#
+# This script is based on the overlay-etc.bbclass, which sets up
+# an overlay on top of the /etc directory, but in this case allows
+# accessing the original, unmodified rootfs at /rofs after boot.
+#
+# It relies on the initramfs-module-rootfs to mount the original
+# root filesystem, and requires 'rootrw=' to be passed as a
+# kernel parameter, specifying the device/partition intended to
+# use as RW.
+#
+# This module needs to be executed after the initramfs-module-rootfs
+# since it relies on it to mount the filesystem at initramfs startup
+# but before the finish module which normally switches root.
+# After overlayroot is executed the usual boot flow continues from
+# the real init process.
+#
+# If something goes wrong while running this module, the rootfs
+# is still mounted RO (with no overlay) and the finish module is
+# executed to continue booting normally.
+#
+# It also has a dependency on overlayfs being enabled in the
+# running kernel via KERNEL_FEATURES (kmeta) or any other means.
+
+
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+
+# We get OLDROOT from the rootfs module
+OLDROOT="/rootfs"
+
+NEWROOT="${RWMOUNT}/root"
+RWMOUNT="/overlay"
+ROMOUNT="${RWMOUNT}/rofs"
+UPPER_DIR="${RWMOUNT}/upper"
+WORK_DIR="${RWMOUNT}/work"
+
+MODULES_DIR=/init.d
+
+# Something went wrong, make sure / is mounted as read only anyway.
+exit_gracefully() {
+echo $1 >/dev/console
+echo >/dev/console
+echo "OverlayRoot mounting failed, starting system as read-only" 
>/dev/console
+echo >/dev/console
+
+# The following is borrowed from rootfs-postcommands.bbclass
+# This basically looks at the real rootfs mounting options and
+# replaces them with "ro"
+
+# Tweak the mount option and fs_passno for rootfs in fstab
+if [ -f ${OLDROOT}/etc/fstab ]; then
+

Re: [OE-core] [poky][dunfell][PATCH 1/6] lsof: correct LICENSE

2022-01-31 Thread Nisha Parrakat 
ack. I will submit a new patch set.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161136): 
https://lists.openembedded.org/g/openembedded-core/message/161136
Mute This Topic: https://lists.openembedded.org/mt/88651664/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] libxml2: Backport python3-lxml workaround patch

2022-01-31 Thread Carlos Rafael Giani via lists.openembedded.org 
This is a workaround for the following issue that affects python3-lxml:

https://gitlab.gnome.org/GNOME/libxml2/-/issues/255

Signed-off-by: Carlos Rafael Giani 
---
 .../0002-Work-around-lxml-API-abuse.patch | 213 ++
 meta/recipes-core/libxml/libxml2_2.9.12.bb|   1 +
 2 files changed, 214 insertions(+)
 create mode 100644 
meta/recipes-core/libxml/libxml2/0002-Work-around-lxml-API-abuse.patch

diff --git 
a/meta/recipes-core/libxml/libxml2/0002-Work-around-lxml-API-abuse.patch 
b/meta/recipes-core/libxml/libxml2/0002-Work-around-lxml-API-abuse.patch
new file mode 100644
index 00..f09ce9707a
--- /dev/null
+++ b/meta/recipes-core/libxml/libxml2/0002-Work-around-lxml-API-abuse.patch
@@ -0,0 +1,213 @@
+From 85b1792e37b131e7a51af98a37f92472e8de5f3f Mon Sep 17 00:00:00 2001
+From: Nick Wellnhofer 
+Date: Tue, 18 May 2021 20:08:28 +0200
+Subject: [PATCH] Work around lxml API abuse
+
+Make xmlNodeDumpOutput and htmlNodeDumpFormatOutput work with corrupted
+parent pointers. This used to work with the old recursive code but the
+non-recursive rewrite required parent pointers to be set correctly.
+
+Unfortunately, lxml relies on the old behavior and passes subtrees with
+a corrupted structure. Fall back to a recursive function call if an
+invalid parent pointer is detected.
+
+Fixes #255.
+
+Upstream-Status: Backport [85b1792e37b131e7a51af98a37f92472e8de5f3f]
+---
+ HTMLtree.c | 46 --
+ xmlsave.c  | 31 +--
+ 2 files changed, 49 insertions(+), 28 deletions(-)
+
+diff --git a/HTMLtree.c b/HTMLtree.c
+index 24434d45..bdd639c7 100644
+--- a/HTMLtree.c
 b/HTMLtree.c
+@@ -744,7 +744,7 @@ void
+ htmlNodeDumpFormatOutput(xmlOutputBufferPtr buf, xmlDocPtr doc,
+xmlNodePtr cur, const char *encoding ATTRIBUTE_UNUSED,
+  int format) {
+-xmlNodePtr root;
++xmlNodePtr root, parent;
+ xmlAttrPtr attr;
+ const htmlElemDesc * info;
+ 
+@@ -755,6 +755,7 @@ htmlNodeDumpFormatOutput(xmlOutputBufferPtr buf, xmlDocPtr 
doc,
+ }
+ 
+ root = cur;
++parent = cur->parent;
+ while (1) {
+ switch (cur->type) {
+ case XML_HTML_DOCUMENT_NODE:
+@@ -762,13 +763,25 @@ htmlNodeDumpFormatOutput(xmlOutputBufferPtr buf, 
xmlDocPtr doc,
+ if (((xmlDocPtr) cur)->intSubset != NULL) {
+ htmlDtdDumpOutput(buf, (xmlDocPtr) cur, NULL);
+ }
+-if (cur->children != NULL) {
++/* Always validate cur->parent when descending. */
++if ((cur->parent == parent) && (cur->children != NULL)) {
++parent = cur;
+ cur = cur->children;
+ continue;
+ }
+ break;
+ 
+ case XML_ELEMENT_NODE:
++/*
++ * Some users like lxml are known to pass nodes with a corrupted
++ * tree structure. Fall back to a recursive call to handle this
++ * case.
++ */
++if ((cur->parent != parent) && (cur->children != NULL)) {
++htmlNodeDumpFormatOutput(buf, doc, cur, encoding, format);
++break;
++}
++
+ /*
+  * Get specific HTML info for that node.
+  */
+@@ -817,6 +830,7 @@ htmlNodeDumpFormatOutput(xmlOutputBufferPtr buf, xmlDocPtr 
doc,
+ (cur->name != NULL) &&
+ (cur->name[0] != 'p')) /* p, pre, param */
+ xmlOutputBufferWriteString(buf, "\n");
++parent = cur;
+ cur = cur->children;
+ continue;
+ }
+@@ -825,9 +839,9 @@ htmlNodeDumpFormatOutput(xmlOutputBufferPtr buf, xmlDocPtr 
doc,
+ (info != NULL) && (!info->isinline)) {
+ if ((cur->next->type != HTML_TEXT_NODE) &&
+ (cur->next->type != HTML_ENTITY_REF_NODE) &&
+-(cur->parent != NULL) &&
+-(cur->parent->name != NULL) &&
+-(cur->parent->name[0] != 'p')) /* p, pre, param */
++(parent != NULL) &&
++(parent->name != NULL) &&
++(parent->name[0] != 'p')) /* p, pre, param */
+ xmlOutputBufferWriteString(buf, "\n");
+ }
+ 
+@@ -842,9 +856,9 @@ htmlNodeDumpFormatOutput(xmlOutputBufferPtr buf, xmlDocPtr 
doc,
+ break;
+ if (((cur->name == (const xmlChar *)xmlStringText) ||
+  (cur->name != (const xmlChar *)xmlStringTextNoenc)) &&
+-((cur->parent == NULL) ||
+- ((xmlStrcasecmp(cur->parent->name, BAD_CAST "script")) &&
+-  (xmlStrcasecmp(cur->parent->name, BAD_CAST "style") {
++((parent == NULL) ||
++ ((xmlStrcasecmp(parent->name, BAD_CAST "script")) &&
++  (xmlStrcasecmp(parent->name, BAD_CAST

[OE-core] [PATCH 2/3] shaderc: upgrade 2021.3 -> 2021.4

2022-01-31 Thread Jose Quaresma 
- Support Vulkan 1.3
- Support targeting SPIR-V 1.6, which is the default for Vulkan 1.3
- Updated copyright check: Excludes Glslang generated files when
  building in source tree
- Fix Android.mk rules for building libshaderc_combined, to adapt to more
  recent NDKs that have removed the GNU binutils.

Signed-off-by: Jose Quaresma 
---
 .../shaderc/{shaderc_2021.3.bb => shaderc_2021.4.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/shaderc/{shaderc_2021.3.bb => shaderc_2021.4.bb} 
(95%)

diff --git a/meta/recipes-graphics/shaderc/shaderc_2021.3.bb 
b/meta/recipes-graphics/shaderc/shaderc_2021.4.bb
similarity index 95%
rename from meta/recipes-graphics/shaderc/shaderc_2021.3.bb
rename to meta/recipes-graphics/shaderc/shaderc_2021.4.bb
index cc2cfc18a8..a35a41ab00 100644
--- a/meta/recipes-graphics/shaderc/shaderc_2021.3.bb
+++ b/meta/recipes-graphics/shaderc/shaderc_2021.4.bb
@@ -6,7 +6,7 @@ HOMEPAGE = "https://github.com/google/shaderc;
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
 
-SRCREV = "6fabc36fbebacfcef8cf82463df2a8247120ebf0"
+SRCREV = "9d0b3848b054d62b5b1e0eba9a50e386c9de3e2b"
 SRC_URI = "git://github.com/google/shaderc.git;protocol=https;branch=main \
file://0001-cmake-disable-building-external-dependencies.patch \
file://0002-libshaderc_util-fix-glslang-header-file-location.patch \
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161133): 
https://lists.openembedded.org/g/openembedded-core/message/161133
Mute This Topic: https://lists.openembedded.org/mt/88814853/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 3/3] shaderc: upgrade 2021.4 -> 2022.0

2022-01-31 Thread Jose Quaresma 
- Update to Glslang 11.8.0

Signed-off-by: Jose Quaresma 
---
 .../shaderc/{shaderc_2021.4.bb => shaderc_2022.0.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/shaderc/{shaderc_2021.4.bb => shaderc_2022.0.bb} 
(95%)

diff --git a/meta/recipes-graphics/shaderc/shaderc_2021.4.bb 
b/meta/recipes-graphics/shaderc/shaderc_2022.0.bb
similarity index 95%
rename from meta/recipes-graphics/shaderc/shaderc_2021.4.bb
rename to meta/recipes-graphics/shaderc/shaderc_2022.0.bb
index a35a41ab00..f5ad0bf3bb 100644
--- a/meta/recipes-graphics/shaderc/shaderc_2021.4.bb
+++ b/meta/recipes-graphics/shaderc/shaderc_2022.0.bb
@@ -6,7 +6,7 @@ HOMEPAGE = "https://github.com/google/shaderc;
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
 
-SRCREV = "9d0b3848b054d62b5b1e0eba9a50e386c9de3e2b"
+SRCREV = "b0aa18323d65d2ca885d0affeef2aa0b56eb45f7"
 SRC_URI = "git://github.com/google/shaderc.git;protocol=https;branch=main \
file://0001-cmake-disable-building-external-dependencies.patch \
file://0002-libshaderc_util-fix-glslang-header-file-location.patch \
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161134): 
https://lists.openembedded.org/g/openembedded-core/message/161134
Mute This Topic: https://lists.openembedded.org/mt/88814854/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 1/3] glslang: upgrade 11.7.1 -> 11.8.0

2022-01-31 Thread Jose Quaresma 
* Add support for SPIR-V 1.6
* Add support for Vulkan 1.3
* Add --hlsl-dx-position-w option

Update LICENSE.txt
- Expand the GPL 3 with special bison exception to the fully expanded license.

Signed-off-by: Jose Quaresma 
---
 .../glslang/{glslang_11.7.1.bb => glslang_11.8.0.bb}  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/glslang/{glslang_11.7.1.bb => glslang_11.8.0.bb} 
(89%)

diff --git a/meta/recipes-graphics/glslang/glslang_11.7.1.bb 
b/meta/recipes-graphics/glslang/glslang_11.8.0.bb
similarity index 89%
rename from meta/recipes-graphics/glslang/glslang_11.7.1.bb
rename to meta/recipes-graphics/glslang/glslang_11.8.0.bb
index 30d9954ea5..a77d8bdf88 100644
--- a/meta/recipes-graphics/glslang/glslang_11.7.1.bb
+++ b/meta/recipes-graphics/glslang/glslang_11.8.0.bb
@@ -6,9 +6,9 @@ either from a command line or programmatically."
 SECTION = "graphics"
 HOMEPAGE = "https://www.khronos.org/opengles/sdk/tools/Reference-Compiler;
 LICENSE = "BSD-3-Clause & BSD-2-Clause & MIT & Apache-2.0 & 
GPL-3-with-bison-exception"
-LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=c5ce49c0456e9b413b98a4368c378229"
+LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2a2b5acd7bc4844964cfda45fe807dc3"
 
-SRCREV = "c9706bdda0ac22b9856f1aa8261e5b9e15cd20c5"
+SRCREV = "c34bb3b6c55f6ab084124ad964be95a699700d34"
 SRC_URI = 
"git://github.com/KhronosGroup/glslang.git;protocol=https;branch=master \
file://0001-generate-glslang-pkg-config.patch"
 UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161132): 
https://lists.openembedded.org/g/openembedded-core/message/161132
Mute This Topic: https://lists.openembedded.org/mt/88814851/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] xwayland: Add xkbcomp runtime dependency

2022-01-31 Thread Tom Hochstein 
Ping.

> -Original Message-
> From: Tom Hochstein
> Sent: Wednesday, January 19, 2022 5:49 PM
> To: openembedded-core@lists.openembedded.org
> Cc: Tom Hochstein 
> Subject: [PATCH] xwayland: Add xkbcomp runtime dependency
> 
> Trying to run an xterm fails with the error:
> xterm: Xt error: Can't open display: :0
> 
> Checking systemctl status weston shows an error:
> Jan 19 21:24:16 imx8mq-evk weston[396]: sh: line 1: /usr/bin/xkbcomp: No such
> file or directory
> 
> Adding xkbcomp to the rootfs fixes these errors. Checking the history one 
> finds
> that the runtime dependency for the old xserver was removed because it wasn't
> in the correct location [1], then restored because it was still needed [2].
> 
> [1] https://github.com/openembedded/openembedded-
> core/commit/bdcc5e8f1286d288baf410458efc39a59b68d751
> [2] https://github.com/openembedded/openembedded-
> core/commit/f2330ebc3071d780cbc6d1ddab5c54bfadf8fffc
> 
> Signed-off-by: Tom Hochstein 
> ---
>  meta/recipes-graphics/xwayland/xwayland_21.1.3.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-graphics/xwayland/xwayland_21.1.3.bb
> b/meta/recipes-graphics/xwayland/xwayland_21.1.3.bb
> index 5d083e8ada..7ea40d9486 100644
> --- a/meta/recipes-graphics/xwayland/xwayland_21.1.3.bb
> +++ b/meta/recipes-graphics/xwayland/xwayland_21.1.3.bb
> @@ -42,3 +42,4 @@ do_install:append() {
> 
>  FILES:${PN} += "${libdir}/xorg/protocol.txt"
> 
> +RDEPENDS:${PN} += "xkbcomp"
> --
> 2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161131): 
https://lists.openembedded.org/g/openembedded-core/message/161131
Mute This Topic: https://lists.openembedded.org/mt/88548155/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 1/2] strace: remove obsolete musl-on-MIPS patch

2022-01-31 Thread Ross Burton 
This patch was added as musl doesn't define SIGEMT on MIPS, but this was
a mistake in musl and has been  fixed in cabc369, available in musl
1.2.1 onwards (August 2020).

Signed-off-by: Ross Burton 
---
 .../strace/strace/mips-SIGEMT.patch   | 33 ---
 meta/recipes-devtools/strace/strace_5.16.bb   |  1 -
 2 files changed, 34 deletions(-)
 delete mode 100644 meta/recipes-devtools/strace/strace/mips-SIGEMT.patch

diff --git a/meta/recipes-devtools/strace/strace/mips-SIGEMT.patch 
b/meta/recipes-devtools/strace/strace/mips-SIGEMT.patch
deleted file mode 100644
index e86da9707c9..000
--- a/meta/recipes-devtools/strace/strace/mips-SIGEMT.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From 794648d84672bbda30a920a05540b56cd155ed9d Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Sun, 7 Aug 2016 23:47:57 -0700
-Subject: [PATCH] strace: Fix build with mips/mips64 on musl
-
-SIGEMT is not defined everywhere e.g musl does
-not define it. Therefore check it being defined
-before using it.
-
-Fixes errors e.g.
-../../strace-4.13/tests/signal2name.c:45:7: error: 'SIGEMT' undeclared (first 
use in this function)
-
-Signed-off-by: Khem Raj 
-Upstream-Status: Pending
-

- tests/signal2name.c | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/tests/signal2name.c b/tests/signal2name.c
-index 1d8e7c5..6722aa1 100644
 a/tests/signal2name.c
-+++ b/tests/signal2name.c
-@@ -49,7 +49,9 @@ signal2name(int sig)
-   CASE(SIGEMT);
-   CASE(SIGLOST);
- #elif defined MIPS
-+#ifdef SIGEMT
-   CASE(SIGEMT);
-+#endif
-   CASE(SIGIOT);
-   CASE(SIGPWR);
- #else
diff --git a/meta/recipes-devtools/strace/strace_5.16.bb 
b/meta/recipes-devtools/strace/strace_5.16.bb
index 1874ef1017c..1574b8e7773 100644
--- a/meta/recipes-devtools/strace/strace_5.16.bb
+++ b/meta/recipes-devtools/strace/strace_5.16.bb
@@ -9,7 +9,6 @@ SRC_URI = "https://strace.io/files/${PV}/strace-${PV}.tar.xz \
file://update-gawk-paths.patch \
file://Makefile-ptest.patch \
file://run-ptest \
-   file://mips-SIGEMT.patch \
file://0001-caps-abbrev.awk-fix-gawk-s-path.patch \
file://ptest-spacesave.patch \
file://0001-strace-fix-reproducibilty-issues.patch \
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161130): 
https://lists.openembedded.org/g/openembedded-core/message/161130
Mute This Topic: https://lists.openembedded.org/mt/88813316/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 2/2] strace: skip a number of load-sensitive tests

2022-01-31 Thread Ross Burton 
Some tests are very load-sensitive as they depend on sleep() calls to
take a precise amount of time. These will randomly fail in the automated
QA, so skip them.

Signed-off-by: Ross Burton 
---
 .../strace/strace/skip-load.patch | 55 +++
 meta/recipes-devtools/strace/strace_5.16.bb   |  1 +
 2 files changed, 56 insertions(+)
 create mode 100644 meta/recipes-devtools/strace/strace/skip-load.patch

diff --git a/meta/recipes-devtools/strace/strace/skip-load.patch 
b/meta/recipes-devtools/strace/strace/skip-load.patch
new file mode 100644
index 000..fa3ddb8ddc3
--- /dev/null
+++ b/meta/recipes-devtools/strace/strace/skip-load.patch
@@ -0,0 +1,55 @@
+Skip tests which are known to be unreliable under load, typically because they
+care about timing.
+
+Upstream-Status: Inappropriate
+Signed-off-by: Ross Burton 
+
+diff --git a/tests/clock_nanosleep.gen.test b/tests/clock_nanosleep.gen.test
+index 7a6025b..f0e6dbb 100755
+--- a/tests/clock_nanosleep.gen.test
 b/tests/clock_nanosleep.gen.test
+@@ -1,4 +1,5 @@
+ #!/bin/sh -efu
+ # Generated by ./tests/gen_tests.sh from ./tests/gen_tests.in 
(clock_nanosleep -e trace=clock_nanosleep,clock_gettime); do not edit.
+ . "${srcdir=.}/init.sh"
++skip_ "Test not reliable under load"
+ run_strace_match_diff -e trace=clock_nanosleep,clock_gettime
+diff --git a/tests/delay.test b/tests/delay.test
+index f74e27f..328087e 100755
+--- a/tests/delay.test
 b/tests/delay.test
+@@ -9,6 +9,8 @@
+ 
+ . "${srcdir=.}/init.sh"
+ 
++skip_ "Test not reliable under load"
++
+ while read -r denter dexit denter_us dexit_us; do
+   [ -n "$denter" ] || continue
+ 
+diff --git a/tests/strace-T.test b/tests/strace-T.test
+index adca3e8..d4acfe9 100755
+--- a/tests/strace-T.test
 b/tests/strace-T.test
+@@ -9,6 +9,8 @@
+ 
+ . "${srcdir=.}/init.sh"
+ 
++skip_ "Test not reliable under load"
++
+ T_opt="${1:--T}"
+ 
+ run_prog ../sleep 0
+diff --git a/tests/strace-r.test b/tests/strace-r.test
+index 8299737..c360344 100755
+--- a/tests/strace-r.test
 b/tests/strace-r.test
+@@ -9,6 +9,8 @@
+ 
+ . "${srcdir=.}/init.sh"
+ 
++skip_ "Test not reliable under load"
++
+ r_opt="${1:--r}"
+ 
+ run_prog ../sleep 0
diff --git a/meta/recipes-devtools/strace/strace_5.16.bb 
b/meta/recipes-devtools/strace/strace_5.16.bb
index 1574b8e7773..a9c22d9ae0a 100644
--- a/meta/recipes-devtools/strace/strace_5.16.bb
+++ b/meta/recipes-devtools/strace/strace_5.16.bb
@@ -12,6 +12,7 @@ SRC_URI = "https://strace.io/files/${PV}/strace-${PV}.tar.xz \
file://0001-caps-abbrev.awk-fix-gawk-s-path.patch \
file://ptest-spacesave.patch \
file://0001-strace-fix-reproducibilty-issues.patch \
+   file://skip-load.patch \
"
 SRC_URI[sha256sum] = 
"dc7db230ff3e57c249830ba94acab2b862da1fcaac55417e9b85041a833ca285"
 
-- 
2.25.1


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

[OE-Core][RFC] kernel-devicetree: fix KERNEL_DEVICETREE_BUNDLE

2022-01-31 Thread Vivien Didelot 
When KERNEL_DEVICETREE_BUNDLE is set to "1", do_deploy tries to cat
zImage from ${KERNEL_IMAGEDEST}, but only zImage-${KERNEL_VERSION}
is present in this directory.

Signed-off-by: Vivien Didelot 
---
 meta/classes/kernel-devicetree.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel-devicetree.bbclass 
b/meta/classes/kernel-devicetree.bbclass
index b4338da1b1..2fad475f05 100644
--- a/meta/classes/kernel-devicetree.bbclass
+++ b/meta/classes/kernel-devicetree.bbclass
@@ -91,7 +91,7 @@ do_deploy:append() {
fi
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
if [ "$type" = "zImage" ] && [ 
"${KERNEL_DEVICETREE_BUNDLE}" = "1" ]; then
-   cat ${D}/${KERNEL_IMAGEDEST}/$type \
+   cat 
${D}/${KERNEL_IMAGEDEST}/$type-${KERNEL_VERSION} \

$deployDir/$dtb_base_name-${KERNEL_DTB_NAME}.$dtb_ext \
> 
$deployDir/$type-$dtb_base_name-${KERNEL_DTB_NAME}.$dtb_ext${KERNEL_DTB_BIN_EXT}
if [ -n "${KERNEL_DTB_LINK_NAME}" ]; then
-- 
2.35.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161128): 
https://lists.openembedded.org/g/openembedded-core/message/161128
Mute This Topic: https://lists.openembedded.org/mt/88809310/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 3/3] oeqa/runtime/stap: improve systemtap test

2022-01-31 Thread Ross Burton 
Split the test up into compile and execute phases, as the stap binary
is known to be quite memory-hungry and this can result in the probe
being unable to allocate enough memory for the buffers it needs.

If the test fails, dump the dmesg as any useful messages will be there.

Signed-off-by: Ross Burton 
---
 meta/lib/oeqa/runtime/cases/stap.py | 22 +++---
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/meta/lib/oeqa/runtime/cases/stap.py 
b/meta/lib/oeqa/runtime/cases/stap.py
index 615c290ce61..480eaabf2db 100644
--- a/meta/lib/oeqa/runtime/cases/stap.py
+++ b/meta/lib/oeqa/runtime/cases/stap.py
@@ -14,11 +14,19 @@ class StapTest(OERuntimeTestCase):
 @OEHasPackage(['gcc-symlinks'])
 @OEHasPackage(['kernel-devsrc'])
 def test_stap(self):
-cmd = 'make -C /usr/src/kernel scripts prepare'
-status, output = self.target.run(cmd, 900)
-self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
+try:
+cmd = 'make -j -C /usr/src/kernel scripts prepare'
+status, output = self.target.run(cmd, 900)
+self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
 
-cmd = 'stap -v --disable-cache -DSTP_NO_VERREL_CHECK -s1 -e \'probe 
oneshot { print("Hello, "); println("world!") }\''
-status, output = self.target.run(cmd, 900)
-self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
-self.assertIn('Hello, world!', output, msg='\n'.join([cmd, output]))
+cmd = 'stap -v -p4 -m stap-hello --disable-cache 
-DSTP_NO_VERREL_CHECK -e \'probe oneshot { print("Hello, "); 
println("SystemTap!") }\''
+status, output = self.target.run(cmd, 900)
+self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
+
+cmd = 'staprun -v -R -b1 stap-hello.ko'
+self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
+self.assertIn('Hello, SystemTap!', output, msg='\n'.join([cmd, 
output]))
+except:
+status, dmesg = self.target.run('dmesg')
+if status == 0:
+print(dmesg)
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161127): 
https://lists.openembedded.org/g/openembedded-core/message/161127
Mute This Topic: https://lists.openembedded.org/mt/88807664/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 2/3] systemtap: backport buffer size tuning patches

2022-01-31 Thread Ross Burton 
Backport a nunber of patches from upstream to tune the buffer size on
machines with a "small amount" of memory, which appears to mean less
than 4GB.

Signed-off-by: Ross Burton 
---
 ...ault-stap-s-buffer-size-on-small-RAM.patch | 84 +++
 .../systemtap/systemtap_git.inc   |  1 +
 2 files changed, 85 insertions(+)
 create mode 100644 
meta/recipes-kernel/systemtap/systemtap/0001-PR28804-tune-default-stap-s-buffer-size-on-small-RAM.patch

diff --git 
a/meta/recipes-kernel/systemtap/systemtap/0001-PR28804-tune-default-stap-s-buffer-size-on-small-RAM.patch
 
b/meta/recipes-kernel/systemtap/systemtap/0001-PR28804-tune-default-stap-s-buffer-size-on-small-RAM.patch
new file mode 100644
index 000..931310db53e
--- /dev/null
+++ 
b/meta/recipes-kernel/systemtap/systemtap/0001-PR28804-tune-default-stap-s-buffer-size-on-small-RAM.patch
@@ -0,0 +1,84 @@
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+PR28804: tune default stap -s ## buffer size on small RAM machines
+
+Insert a forgotten division by num_online_cpu() to adjust downward the
+calculated bufsize.  Tweak normal defaults back to 128 * 2 * 64K
+(16MB) per CPU, as the stap man page indicates.  This may need further
+tweaking when balancing against staprun consumption performance, but
+at least we have the docs lined up with the code at the moment.
+
+PR28804: tune default stap -s ## buffer size on small RAM machines
+
+Use si_meminfo to limit default buffer size.  Note in the man page
+that the "-s ##" parameter is per-CPU.
+
+diff --git a/man/stap.1.in b/man/stap.1.in
+index 55dbc2c93..285a27b34 100644
+--- a/man/stap.1.in
 b/man/stap.1.in
+@@ -239,8 +239,8 @@ and average amount of time spent in each probe-point. Also 
shows
+ the derivation for each probe-point.
+ .TP
+ .BI \-s " NUM"
+-Use NUM megabyte buffers for kernel-to-user data transfer.  On a
+-multiprocessor in bulk mode, this is a per-processor amount.
++Use NUM megabyte buffers for kernel-to-user data transfer per processor.
++The default is 16MB, or less on smaller memory machines.
+ .TP
+ .BI \-I " DIR"
+ Add the given directory to the tapset search directory.  See the
+diff --git a/runtime/transport/transport.c b/runtime/transport/transport.c
+index 18ecccea2..44afff814 100644
+--- a/runtime/transport/transport.c
 b/runtime/transport/transport.c
+@@ -72,8 +72,11 @@ static inline void _stp_unlock_inode(struct inode *inode);
+ #include "procfs.c"
+ #include "control.c"
+ 
+-static unsigned _stp_nsubbufs = 256;
+-static unsigned _stp_subbuf_size = 8 * STP_BUFFER_SIZE; /* 64K */
++/* set default buffer parameters.  User may override these via stap -s #, and
++   the runtime may auto-shrink it on low memory machines too. */
++/* NB: Note default in man/stap.1.in */
++static unsigned _stp_nsubbufs = 128;
++static unsigned _stp_subbuf_size = 2 * STP_BUFFER_SIZE; /* 2 * 64K */
+ 
+ /* module parameters */
+ static int _stp_bufsize;
+@@ -602,17 +605,30 @@ static int _stp_transport_init(void)
+ _stp_need_kallsyms_stext = 0;
+ #endif
+ 
+-  if (_stp_bufsize) {
+-  unsigned size = _stp_bufsize * 1024 * 1024;
++if (_stp_bufsize == 0) { // option not specified?
++  struct sysinfo si;
++long _stp_bufsize_avail;
++si_meminfo();
++_stp_bufsize_avail = (long)((si.freeram + si.bufferram) / 4 / 
num_online_cpus())
++<< PAGE_SHIFT; // limit to quarter of free ram total
++if ((_stp_nsubbufs * _stp_subbuf_size * num_online_cpus()) > 
_stp_bufsize_avail) {
++_stp_bufsize = max_t (int, 1, _stp_bufsize_avail / 
1024 / 1024);
++dbug_trans(1, "Shrinking default _stp_bufsize to %d 
MB/cpu due to low free memory\n", _stp_bufsize);
++}
++}  
++
++  if (_stp_bufsize) { // overridden by user or by si_meminfo heuristic?
++  long size = _stp_bufsize * 1024 * 1024;
+   _stp_subbuf_size = 65536;
++// bump up subbuf size from 64K to 1M to keep _stp_nsubbufs 
not too large
+   while (size / _stp_subbuf_size > 64 &&
+  _stp_subbuf_size < 1024 * 1024) {
+   _stp_subbuf_size <<= 1;
+   }
+   _stp_nsubbufs = size / _stp_subbuf_size;
+-  dbug_trans(1, "Using %d subbufs of size %d\n", _stp_nsubbufs, 
_stp_subbuf_size);
+   }
+-
++dbug_trans(1, "Using %d subbufs of size %d\n", _stp_nsubbufs, 
_stp_subbuf_size);
++
+   ret = _stp_transport_fs_init(THIS_MODULE->name);
+   if (ret)
+   goto err0;
diff --git a/meta/recipes-kernel/systemtap/systemtap_git.inc 
b/meta/recipes-kernel/systemtap/systemtap_git.inc
index 36c934c2fa7..a7c8bbc589a 100644
--- a/meta/recipes-kernel/systemtap/systemtap_git.inc
+++ b/meta/recipes-kernel/systemtap/systemtap_git.inc
@@ -8,6 +8,7 @@ SRC_URI =

[OE-core] [PATCH 1/3] core-image-sato-sdk: allocate more memory when in qemu

2022-01-31 Thread Ross Burton 
Compiling code is memory-intensive, especially kernel modules like the
SystemTap probes, so give the VM 768MB of RAM.  Using 1GB appears to
cause PCI error, interestingly.

Hopefully this solves the intermittent failures caused by OOMs during
the SystemTap test.

[ YOCTO #14673 ]

Signed-off-by: Ross Burton 
---
 meta/recipes-sato/images/core-image-sato-sdk.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-sato/images/core-image-sato-sdk.bb 
b/meta/recipes-sato/images/core-image-sato-sdk.bb
index b52de0def02..afab473b52c 100644
--- a/meta/recipes-sato/images/core-image-sato-sdk.bb
+++ b/meta/recipes-sato/images/core-image-sato-sdk.bb
@@ -10,3 +10,6 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \
 
 IMAGE_INSTALL += "kernel-devsrc"
 
+# Compiling stuff, specifically SystemTap probes, can require lots of memory
+# See https://bugzilla.yoctoproject.org/show_bug.cgi?id=14673
+QB_MEM = "-m 768"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161125): 
https://lists.openembedded.org/g/openembedded-core/message/161125
Mute This Topic: https://lists.openembedded.org/mt/88807662/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] vim: upgrade to patch 4269

2022-01-31 Thread Ross Burton 
Upgrade to the latest patch release to fix the following CVEs:

- CVE-2022-0261
- CVE-2022-0318
- CVE-2022-0319

Signed-off-by: Ross Burton 
---
 meta/recipes-support/vim/vim.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 3a5eca41114..f044be504b6 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -20,8 +20,8 @@ SRC_URI = 
"git://github.com/vim/vim.git;branch=master;protocol=https \
file://racefix.patch \
"
 
-PV .= ".4118"
-SRCREV = "0023f82a76cf43a12b41e71f97a2e860d0444e1b"
+PV .= ".4269"
+SRCREV = "48a604845e33399893d6bf293e71bcd2a412800d"
 
 # Remove when 8.3 is out
 UPSTREAM_VERSION_UNKNOWN = "1"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161124): 
https://lists.openembedded.org/g/openembedded-core/message/161124
Mute This Topic: https://lists.openembedded.org/mt/88806482/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] expat: upgrade to 2.4.4

2022-01-31 Thread Ross Burton 
Fixes CVE-2022-23852 and CVE-2022-23990.

Signed-off-by: Ross Burton 
---
 meta/recipes-core/expat/{expat_2.4.3.bb => expat_2.4.4.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/expat/{expat_2.4.3.bb => expat_2.4.4.bb} (91%)

diff --git a/meta/recipes-core/expat/expat_2.4.3.bb 
b/meta/recipes-core/expat/expat_2.4.4.bb
similarity index 91%
rename from meta/recipes-core/expat/expat_2.4.3.bb
rename to meta/recipes-core/expat/expat_2.4.4.bb
index cc50f90f70b..14080220d2c 100644
--- a/meta/recipes-core/expat/expat_2.4.3.bb
+++ b/meta/recipes-core/expat/expat_2.4.4.bb
@@ -14,7 +14,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] = 
"6f262e216a494fbf42d8c22bc841b3e117c21f2467a19dc4c27c991b5622f986"
+SRC_URI[sha256sum] = 
"14c58c2a0b5b8b31836514dfab41bd191836db7aa7b84ae5c47bc0327a20d64a"
 
 EXTRA_OECMAKE:class-native += "-DEXPAT_BUILD_DOCS=OFF"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161123): 
https://lists.openembedded.org/g/openembedded-core/message/161123
Mute This Topic: https://lists.openembedded.org/mt/88806170/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] [poky][dunfell][PATCH 1/6] lsof: correct LICENSE

2022-01-31 Thread Ross Burton 
On 29/01/2022, 15:21, "Steve Sakoman"  wrote:

On Mon, Jan 24, 2022 at 7:16 AM Nisha Parrakat  
wrote:
>
> From: Ross Burton 
>
> The lsof LICENSE is superficially BSD-like, but it isn't BSD.  Now that
> we have the full SPDX license set in oe-core, use Spencer-94.

Results in following warning:

WARNING: build-appliance-image-15.0.0-r0 do_rootfs: The license listed
Spencer-94 was not in the licenses collected for recipe lsof

If you're going to backport these license fixes, then you'll really need 
oe-core e2f9092c37395f4e3ee9d0777e28c83cce6007ee too which adds the new license 
files.

Ross

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161122): 
https://lists.openembedded.org/g/openembedded-core/message/161122
Mute This Topic: https://lists.openembedded.org/mt/88651664/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] [honister PATCH] kernel: introduce python3-dtschema-wrapper

2022-01-31 Thread Paul Barker 

On 14/01/2022 13:21, Paul Barker wrote:

From: Bruce Ashfield 

The 5.16 kernel introduced mandatory schema checking on any dtb file
built through the kernel.

That funcionality is provided via python3-dt-schema.

The dependencies to enable that functionality is not small, and may
not always be desired (in particular on architectures that do not
support dtbs, or in development cycles). It may also be useful for
allowing a non-conformant dts to be compiled.

This commit introduces a set of wrapper scripts that when added
as a depenency to the kernel, can pass both the validation testing
and validation steps of a dts.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie 

Backported from oe-core commit 2566563ad49d.
Signed-off-by: Paul Barker 


I'm sending a gentle ping on this as I haven't heard any reply or seen 
this land in honister yet. Any feedback?


Thanks,

--
Paul Barker
Principal Software Engineer
SanCloud Ltd

e: paul.bar...@sancloud.com
w: https://sancloud.co.uk/


OpenPGP_0xA67255DFCCE62ECD.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161121): 
https://lists.openembedded.org/g/openembedded-core/message/161121
Mute This Topic: https://lists.openembedded.org/mt/88420169/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] Revert "featimage: refactor style"

2022-01-31 Thread Marek Vasut 

On 1/31/22 08:01, Valek, Andrej wrote:

Hi,


Hello Andrej,

(please avoid top-posting)


Sorry, but personally I don't like your idea. What's the benefit of
reverting this? I would keep the ${} for bitbake and $ for shell. The
{} has to be placed only for variables like $a${b}c.


That's exactly the benefit of using ${} in shell scripts consistently -- 
you don't have to worry about variable names being accidentally 
conflated with surrounding strings, either due to your own mistake, or 
some automated transformation that was applied incorrectly .



We should respect the workflow on all recipes otherwise we're braking
the "unwritten" rules.


The workflow on all recipes ? What does this mean ?

The "unwritten" rules ? If they are unwritten, of course they will be 
broken by people. Better update the documentation.


There is one technical counter-argument to this revert from Peter, quote:
"
There is actually a technical reason to not use ${foo} for shell
variables unless necessary in bitbake files and it is because
bitbake will treat them all as potential bitbake variables. This
means they are unnecessarily included in the taskhashes that
bitbake calculates.
"

But the patch being reverted here addresses the problem only partly, 
because it still contains remnants like this:

"
conf_desc="$conf_desc${sep}setup"
"

[...]


third alternative ? I mean, besides rewriting the fitimage
generation into python, which might make it more flexible too.


Replacing shell code that has grown beyond a couple of hundred
(tens?) lines with something written in a better language is
almost always a good idea.


It's grown to almost 800 LoC, so maybe it is time to reevaluate the
python conversion then.


So a rewrite into something more suitable might be a good idea ^ , 
probably python in this case.

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

[OE-core] ERROR: _exec_cmd: bitbake -e returned '-6' instead of 0

2022-01-31 Thread qais . sunna 
this error gets thrown while building a petalinux image:
ERROR: _exec_cmd: bitbake -e returned '-6' instead of 0

Full terminal output:

> 
> INFO: Sourcing build environment
> INFO: Extracting rootfs, This may take time!
> INFO: Creating wic image...
> INFO: wic create
> /home/peptech/petalinux_projects/test_board/build/rootfs.wks --rootfs-dir
> /home/peptech/petalinux_projects/test_board/build/wic/rootfs --bootimg-dir
> /home/peptech/petalinux_projects/test_board/images/linux/ --kernel-dir
> /home/peptech/petalinux_projects/test_board/images/linux/ --outdir
> /tmp/tmp.QgxurHEIGu -n
> /home/peptech/petalinux_projects/test_board/build/tmp/work/cortexa9t2hf-neon-xilinx-linux-gnueabi/wic-tools/1.0-r0/recipe-sysroot-native
> 
> INFO: Creating image(s)...
> 
> 
> ERROR: _exec_cmd: bitbake -e returned '-6' instead of 0
> output: abort()ing pseudo client by server request. See
> https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
> Check logfile:
> /home/peptech/petalinux_projects/test_board/build/wic/pseudo/pseudo.log
> ERROR: Failed to create wic image
> 
> 
> 

Unfortunately, log file is automatically deleted after the error gets thrown 
and tracking it shows nothing beneficial
Any suggestion? Many thanks in advance!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161119): 
https://lists.openembedded.org/g/openembedded-core/message/161119
Mute This Topic: https://lists.openembedded.org/mt/88803841/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] staging: use relative path in sysroot_stage_dir()

2022-01-31 Thread ahussain 
From: Ahsan Hussain 

A regression form cpio CVE-2021-38185 caused the tool to hang for paths
greater than 128 character long. It was reported here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992098

We were able to reliable reproduce this with dunfell, meta-freescale
recipe imx-boot

https://github.com/Freescale/meta-freescale/blob/dunfell/recipes-bsp/imx-mkimage/imx-boot_1.0.bb

Using relative path on the affected host fixes the issue as this is
always short, being in the same work dir. It would be harmless, and
useful to generally use the relative path for sysroot_stage_dir()

Signed-off-by: Ahsan Hussain 
---
 meta/classes/staging.bbclass | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
index 25f77c7735..4f278b2205 100644
--- a/meta/classes/staging.bbclass
+++ b/meta/classes/staging.bbclass
@@ -49,9 +49,10 @@ sysroot_stage_dir() {
fi
 
mkdir -p "$dest"
+   rdest=$(realpath --relative-to="$src" "$dest")
(
cd $src
-   find . -print0 | cpio --null -pdlu $dest
+   find . -print0 | cpio --null -pdlu $rdest
)
 }
 
-- 
2.17.1


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