Re: [OE-core] [PATCH V3] glibc: stable 2.38 branch updates.

2023-10-02 Thread Deepthi . Hemraj
Regression testing is done and below are the test results.

Before glibc update
Summary of test results:
213 FAIL
4805 PASS
16 XFAIL
4 XPASS
218 UNSUPPORTED

After glibc update
Summary of test results:
216 FAIL
4805 PASS
16 XFAIL
4 XPASS
218 UNSUPPORTED

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
FAIL: nss/tst-nss-gai-hv2-canonname
PASS: resolv/tst-resolv-no-vc
And below are new failures
FAIL: nptl/tst-thread-affinity-sched
FAIL: malloc/tst-malloc_info-malloc-check

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188623): 
https://lists.openembedded.org/g/openembedded-core/message/188623
Mute This Topic: https://lists.openembedded.org/mt/101727838/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] glibc: stable 2.38 branch updates.

2023-10-02 Thread Deepthi . Hemraj
I have sent a V3 dropping the 0024-CVE-2023-4527.patch

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188622): 
https://lists.openembedded.org/g/openembedded-core/message/188622
Mute This Topic: https://lists.openembedded.org/mt/101614434/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][kirkstone][PATCH 1/1] python3-jinja2: fix for the ptest result format

2023-10-02 Thread Narpat Mali via lists.openembedded.org

On 02-10-2023 20:04, Steve Sakoman wrote:

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know 
the content is safe.

On Thu, Sep 28, 2023 at 10:24 PM Narpat Mali via
lists.openembedded.org
 wrote:

From: Narpat Mali 

The output of python3-jinja2 ptest should follow a unified format as below
result: testname

Reference:
https://wiki.yoctoproject.org/wiki/Ptest

Is this also an issue with the version in the master branch?

If so, please submit a patch for master branch too.  We don't want to
fix this in a stable branch without also fixing it in master.


Hi Steve,

In master branch, it has been already fixed using 
"python3-unittest-automake-output" instead of sed to reformat the output.


https://git.openembedded.org/openembedded-core/commit/?id=def25193748fac40c4120e9a6e8861ae4c7ae760

../Narpat



Thanks!

Steve


Signed-off-by: Narpat Mali 
---
  meta/recipes-devtools/python/python3-jinja2/run-ptest | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-jinja2/run-ptest 
b/meta/recipes-devtools/python/python3-jinja2/run-ptest
index 5cec711696..3004024619 100644
--- a/meta/recipes-devtools/python/python3-jinja2/run-ptest
+++ b/meta/recipes-devtools/python/python3-jinja2/run-ptest
@@ -1,3 +1,3 @@
  #!/bin/sh

-pytest
+pytest -o log_cli=true -o log_cli_level=INFO | sed -e 's/\[...%\]//g'| sed -e 's/PASSED/PASS/g'| sed -e 's/FAILED/FAIL/g'| sed -e 's/SKIPPED/SKIP/g'| awk '{if ($NF=="PASS" || 
$NF=="FAIL" || $NF=="SKIP" || $NF=="XFAIL" || $NF=="XPASS"){printf "%s : %s\n", $NF, $0}else{print}}'| awk '{if ($NF=="PASS" || 
$NF=="FAIL" || $NF=="SKIP" || $NF=="XFAIL" || $NF=="XPASS") {$NF="";print $0}else{print}}'
--
2.40.0





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188621): 
https://lists.openembedded.org/g/openembedded-core/message/188621
Mute This Topic: https://lists.openembedded.org/mt/101653794/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] cups: Backport fix for CVE-2023-32360 and CVE-2023-4504

2023-10-02 Thread Vijay Anusuri via lists.openembedded.org
From: Vijay Anusuri 

Upstream commits:
https://github.com/OpenPrinting/cups/commit/a0c8b9c9556882f00c68b9727a95a1b6d1452913
& 
https://github.com/OpenPrinting/cups/commit/2431caddb7e6a87f04ac90b5c6366ad268b6ff31

Signed-off-by: Vijay Anusuri 
---
 meta/recipes-extended/cups/cups.inc   |  2 +
 .../cups/cups/CVE-2023-32360.patch| 31 ++
 .../cups/cups/CVE-2023-4504.patch | 40 +++
 3 files changed, 73 insertions(+)
 create mode 100644 meta/recipes-extended/cups/cups/CVE-2023-32360.patch
 create mode 100644 meta/recipes-extended/cups/cups/CVE-2023-4504.patch

diff --git a/meta/recipes-extended/cups/cups.inc 
b/meta/recipes-extended/cups/cups.inc
index 1d2377486a..6cfe314f20 100644
--- a/meta/recipes-extended/cups/cups.inc
+++ b/meta/recipes-extended/cups/cups.inc
@@ -16,6 +16,8 @@ SRC_URI = 
"https://github.com/apple/cups/releases/download/v${PV}/${BP}-source.t
file://CVE-2022-26691.patch \
file://CVE-2023-32324.patch \
file://CVE-2023-34241.patch \
+   file://CVE-2023-32360.patch \
+   file://CVE-2023-4504.patch \
"
 
 UPSTREAM_CHECK_URI = "https://github.com/apple/cups/releases;
diff --git a/meta/recipes-extended/cups/cups/CVE-2023-32360.patch 
b/meta/recipes-extended/cups/cups/CVE-2023-32360.patch
new file mode 100644
index 00..4d39e1e57f
--- /dev/null
+++ b/meta/recipes-extended/cups/cups/CVE-2023-32360.patch
@@ -0,0 +1,31 @@
+From a0c8b9c9556882f00c68b9727a95a1b6d1452913 Mon Sep 17 00:00:00 2001
+From: Michael R Sweet 
+Date: Tue, 6 Dec 2022 09:04:01 -0500
+Subject: [PATCH] Require authentication for CUPS-Get-Document.
+
+Upstream-Status: Backport 
[https://github.com/OpenPrinting/cups/commit/a0c8b9c9556882f00c68b9727a95a1b6d1452913]
+CVE: CVE-2023-32360
+Signed-off-by: Vijay Anusuri 
+---
+ conf/cupsd.conf.in | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/conf/cupsd.conf.in b/conf/cupsd.conf.in
+index b258849078..a07536f3e4 100644
+--- a/conf/cupsd.conf.in
 b/conf/cupsd.conf.in
+@@ -68,7 +68,13 @@ IdleExitTimeout @EXIT_TIMEOUT@
+ Order deny,allow
+   
+ 
+-  
++  
++Require user @OWNER @SYSTEM
++Order deny,allow
++  
++
++  
++AuthType Default
+ Require user @OWNER @SYSTEM
+ Order deny,allow
+   
diff --git a/meta/recipes-extended/cups/cups/CVE-2023-4504.patch 
b/meta/recipes-extended/cups/cups/CVE-2023-4504.patch
new file mode 100644
index 00..be0db1fbd4
--- /dev/null
+++ b/meta/recipes-extended/cups/cups/CVE-2023-4504.patch
@@ -0,0 +1,40 @@
+From a9a7daa77699bd58001c25df8a61a8029a217ddf Mon Sep 17 00:00:00 2001
+From: Zdenek Dohnal 
+Date: Fri, 1 Sep 2023 16:47:29 +0200
+Subject: [PATCH] raster-interpret.c: Fix CVE-2023-4504
+
+We didn't check for end of buffer if it looks there is an escaped
+character - check for NULL terminator there and if found, return NULL
+as return value and in `ptr`, because a lone backslash is not
+a valid PostScript character.
+
+Upstream-Status: Backport 
[https://github.com/OpenPrinting/cups/commit/2431caddb7e6a87f04ac90b5c6366ad268b6ff31]
+CVE: CVE-2023-4504
+Signed-off-by: Vijay Anusuri 
+---
+ cups/raster-interpret.c | 14 +-
+ 1 file changed, 13 insertions(+), 1 deletion(-)
+
+--- a/cups/raster-interpret.c
 b/cups/raster-interpret.c
+@@ -1113,7 +1113,19 @@ scan_ps(_cups_ps_stack_t *st,   /* I  - S
+ 
+   cur ++;
+ 
+-if (*cur == 'b')
++ /*
++  * Return NULL if we reached NULL terminator, a lone backslash
++* is not a valid character in PostScript.
++  */
++
++  if (!*cur)
++  {
++*ptr = NULL;
++
++return (NULL);
++  }
++
++  if (*cur == 'b')
+ *valptr++ = '\b';
+   else if (*cur == 'f')
+ *valptr++ = '\f';
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188620): 
https://lists.openembedded.org/g/openembedded-core/message/188620
Mute This Topic: https://lists.openembedded.org/mt/101728136/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] glibc: stable 2.38 branch updates.

2023-10-02 Thread Hemraj, Deepthi via lists.openembedded.org
From: Deepthi Hemraj 

Below commits on glibc-2.38 stable branch are updated.
0e1ef6779a (HEAD -> release/2.38/master, origin/release/2.38/master) 
manual/jobs.texi: Add missing @item EPERM for getpgid
d94461bb86 string: Fix tester build with fortify enable with gcc < 12
63250e9c57 iconv: restore verbosity with unrecognized encoding names (bug 30694)
00ae4f10b5 getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806)
b25508dd77 CVE-2023-4527: Stack read overflow with large TCP responses in 
no- mode
89da8bc588 NEWS: Add the 2.38.1 bug list
d3ba6c1333 elf: Move l_init_called_next to old place of l_text_end in link map
750f19526a elf: Remove unused l_text_end field from struct link_map
a3189f66a5 elf: Always call destructors in reverse constructor order (bug 30785)
7ae211a01b elf: Do not run constructors for proxy objects
92201f16cb libio: Fix oversized __io_vtables
5bdef6f27c io: Fix record locking contants for powerpc64 with 
__USE_FILE_OFFSET64

0024-CVE-2023-4527.patch is dropped

Signed-off-by: Deepthi Hemraj 
---
 meta/recipes-core/glibc/glibc-version.inc |   2 +-
 .../glibc/glibc/0024-CVE-2023-4527.patch  | 219 --
 meta/recipes-core/glibc/glibc_2.38.bb |   1 -
 3 files changed, 1 insertion(+), 221 deletions(-)
 delete mode 100644 meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch

diff --git a/meta/recipes-core/glibc/glibc-version.inc 
b/meta/recipes-core/glibc/glibc-version.inc
index a907444f50..f5ebbb2ee6 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.38/master"
 PV = "2.38+git"
-SRCREV_glibc ?= "1aed90c9c8f8be9f68b58e96b6e4cd0fc08eb2b1"
+SRCREV_glibc ?= "0e1ef6779a90bc0f8a05bc367796df2793deecaa"
 SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
diff --git a/meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch 
b/meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch
deleted file mode 100644
index 7d9adf6a66..00
--- a/meta/recipes-core/glibc/glibc/0024-CVE-2023-4527.patch
+++ /dev/null
@@ -1,219 +0,0 @@
-From 4ea972b7edd7e36610e8cde18bf7a8149d7bac4f Mon Sep 17 00:00:00 2001
-From: Florian Weimer 
-Date: Wed, 13 Sep 2023 14:10:56 +0200
-Subject: [PATCH] CVE-2023-4527: Stack read overflow with large TCP responses
- in no- mode
-
-Without passing alt_dns_packet_buffer, __res_context_search can only
-store 2048 bytes (what fits into dns_packet_buffer).  However,
-the function returns the total packet size, and the subsequent
-DNS parsing code in _nss_dns_gethostbyname4_r reads beyond the end
-of the stack-allocated buffer.
-
-Fixes commit f282cdbe7f436c75864e5640a4 ("resolv: Implement no-
-stub resolver option") and bug 30842.
-
-(cherry picked from commit bd77dd7e73e3530203be1c52c8a29d08270cb25d)
-
-Upstream-Status: Backport 
[https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=4ea972b7edd7e36610e8cde18bf7a8149d7bac4f]
-CVE: CVE-2023-4527
-
-Signed-off-by: Yash Shinde 
-

- NEWS  |   7 ++
- resolv/Makefile   |   2 +
- resolv/nss_dns/dns-host.c |   2 +-
- resolv/tst-resolv-no-vc.c | 129 ++
- 4 files changed, 139 insertions(+), 1 deletion(-)
- create mode 100644 resolv/tst-resolv-no-vc.c
-
-diff --git a/NEWS b/NEWS
 a/NEWS
-+++ b/NEWS
-@@ -126,6 +126,7 @@
-   [30477] libc: [RISCV]: time64 does not work on riscv32
-   [30515] dynamic-link: _dl_find_object incorrectly returns 1 during
- early startup
-+  [30842] Stack read overflow in getaddrinfo in no- mode (CVE-2023-4527)
-   [30527] network: resolv_conf lock not unlocked on allocation failure
-   [30550] math: powerpc64le: GCC-specific code for isinf() is being used
- on clang
-@@ -157,6 +158,12 @@
-   heap and prints it to the target log file, potentially revealing a
-   portion of the contents of the heap.
-
-+  CVE-2023-4527: If the system is configured in no- mode via
-+  /etc/resolv.conf, getaddrinfo is called for the AF_UNSPEC address
-+  family, and a DNS response is received over TCP that is larger than
-+  2048 bytes, getaddrinfo may potentially disclose stack contents via
-+  the returned address data, or crash.
-+
- The following bugs are resolved with this release:
-
-   [12154] network: Cannot resolve hosts which have wildcard aliases
-diff --git a/resolv/Makefile b/resolv/Makefile
 a/resolv/Makefile
-+++ b/resolv/Makefile
-@@ -102,6 +102,7 @@
-   tst-resolv-invalid-cname \
-   tst-resolv-network \
-   tst-resolv-no \
-+  tst-resolv-no-vc \
-   tst-resolv-nondecimal \
-   tst-resolv-res_init-multi \
-   tst-resolv-search \
-@@ -293,6 +294,7 @@
- $(objpfx)tst-resolv-invalid-cname: $(objpfx)libresolv.so \
-   $(shared-thread-library)
- $(objpfx)tst-resolv-no: $(objpfx)libresolv.so $(shared-thread-library)
-+$(objpfx)tst-resolv-no-vc: $(objpfx)libresolv.so 

[OE-core] [PATCH 1/3] externalsrc.bbclass: Support specifying patterns in CONFIGURE_FILES

2023-10-02 Thread Peter Kjellerstedt
This allows, e.g., *.cmake to be added to CONFIGURE_FILES to make the
do_configure task depend on changes to any cmake file.

Signed-off-by: Peter Kjellerstedt 
---
 meta/classes/externalsrc.bbclass | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
index cba80bb1d4..a54f316aa0 100644
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -252,6 +252,8 @@ def srctree_configure_hash_files(d):
 Get the list of files that should trigger do_configure to re-execute,
 based on the value of CONFIGURE_FILES
 """
+import fnmatch
+
 in_files = (d.getVar('CONFIGURE_FILES') or '').split()
 out_items = []
 search_files = []
@@ -263,8 +265,8 @@ def srctree_configure_hash_files(d):
 if search_files:
 s_dir = d.getVar('EXTERNALSRC')
 for root, _, files in os.walk(s_dir):
-for f in files:
-if f in search_files:
+for p in search_files:
+for f in fnmatch.filter(files, p):
 out_items.append('%s:True' % os.path.join(root, f))
 return ' '.join(out_items)
 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188616): 
https://lists.openembedded.org/g/openembedded-core/message/188616
Mute This Topic: https://lists.openembedded.org/mt/101726168/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] autotools.bbclass: Add *.m4 to CONFIGURE_FILES

2023-10-02 Thread Peter Kjellerstedt
This makes do_configure depend on changes to any m4 file when
externalsrc is active.

Signed-off-by: Peter Kjellerstedt 
---
 meta/classes-recipe/autotools.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/autotools.bbclass 
b/meta/classes-recipe/autotools.bbclass
index a4c1c4be41..5ed21a3d68 100644
--- a/meta/classes-recipe/autotools.bbclass
+++ b/meta/classes-recipe/autotools.bbclass
@@ -157,7 +157,7 @@ python autotools_aclocals () {
 
 do_configure[file-checksums] += "${@' '.join(siteinfo_get_files(d, 
sysrootcache=False)[1])}"
 
-CONFIGURE_FILES = "${S}/configure.in ${S}/configure.ac ${S}/config.h.in 
${S}/acinclude.m4 Makefile.am"
+CONFIGURE_FILES = "${S}/configure.in ${S}/configure.ac ${S}/config.h.in *.m4 
Makefile.am"
 
 autotools_do_configure() {
# WARNING: gross hack follows:

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188618): 
https://lists.openembedded.org/g/openembedded-core/message/188618
Mute This Topic: https://lists.openembedded.org/mt/101726170/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] cmake.bbclass: Add *.cmake to CONFIGURE_FILES

2023-10-02 Thread Peter Kjellerstedt
This makes do_configure depend on changes to any cmake file when
externalsrc is active.

Signed-off-by: Peter Kjellerstedt 
---
 meta/classes-recipe/cmake.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/cmake.bbclass 
b/meta/classes-recipe/cmake.bbclass
index 41748b0820..d978b88944 100644
--- a/meta/classes-recipe/cmake.bbclass
+++ b/meta/classes-recipe/cmake.bbclass
@@ -156,7 +156,7 @@ EOF
 
 addtask generate_toolchain_file after do_patch before do_configure
 
-CONFIGURE_FILES = "CMakeLists.txt"
+CONFIGURE_FILES = "CMakeLists.txt *.cmake"
 
 do_configure[cleandirs] = "${@d.getVar('B') if d.getVar('S') != d.getVar('B') 
else ''}"
 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188617): 
https://lists.openembedded.org/g/openembedded-core/message/188617
Mute This Topic: https://lists.openembedded.org/mt/101726169/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] u-boot: Upgrade to 2023.10

2023-10-02 Thread Fabio Estevam
Upgrade to U-Boot 2023.10.

The U-Boot 2023.10 tag is in the master branch, so switch the branch
back to master.

Signed-off-by: Fabio Estevam 
---
 meta/recipes-bsp/u-boot/u-boot-common.inc | 4 ++--
 .../{u-boot-tools_2023.07.02.bb => u-boot-tools_2023.10.bb}   | 0
 .../u-boot/{u-boot_2023.07.02.bb => u-boot_2023.10.bb}| 0
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-bsp/u-boot/{u-boot-tools_2023.07.02.bb => 
u-boot-tools_2023.10.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2023.07.02.bb => u-boot_2023.10.bb} 
(100%)

diff --git a/meta/recipes-bsp/u-boot/u-boot-common.inc 
b/meta/recipes-bsp/u-boot/u-boot-common.inc
index 111914827d..ab1a7c2a67 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common.inc
@@ -12,9 +12,9 @@ PE = "1"
 
 # We use the revision in order to avoid having to fetch it from the
 # repo during parse
-SRCREV = "83cdab8b2c6ea0fc0860f8444d083353b47f1d5c"
+SRCREV = "4459ed60cb1e0562bc5b40405e2b4b9bbf766d57"
 
-SRC_URI = 
"git://source.denx.de/u-boot/u-boot.git;protocol=https;branch=u-boot-2023.07.y"
+SRC_URI = "git://source.denx.de/u-boot/u-boot.git;protocol=https;branch=master"
 
 S = "${WORKDIR}/git"
 B = "${WORKDIR}/build"
diff --git a/meta/recipes-bsp/u-boot/u-boot-tools_2023.07.02.bb 
b/meta/recipes-bsp/u-boot/u-boot-tools_2023.10.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-tools_2023.07.02.bb
rename to meta/recipes-bsp/u-boot/u-boot-tools_2023.10.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot_2023.07.02.bb 
b/meta/recipes-bsp/u-boot/u-boot_2023.10.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot_2023.07.02.bb
rename to meta/recipes-bsp/u-boot/u-boot_2023.10.bb
-- 
2.37.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188615): 
https://lists.openembedded.org/g/openembedded-core/message/188615
Mute This Topic: https://lists.openembedded.org/mt/101714757/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][kirkstone][PATCH 1/1] python3-jinja2: fix for the ptest result format

2023-10-02 Thread Steve Sakoman
On Thu, Sep 28, 2023 at 10:24 PM Narpat Mali via
lists.openembedded.org
 wrote:
>
> From: Narpat Mali 
>
> The output of python3-jinja2 ptest should follow a unified format as below
> result: testname
>
> Reference:
> https://wiki.yoctoproject.org/wiki/Ptest

Is this also an issue with the version in the master branch?

If so, please submit a patch for master branch too.  We don't want to
fix this in a stable branch without also fixing it in master.

Thanks!

Steve

> Signed-off-by: Narpat Mali 
> ---
>  meta/recipes-devtools/python/python3-jinja2/run-ptest | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/python/python3-jinja2/run-ptest 
> b/meta/recipes-devtools/python/python3-jinja2/run-ptest
> index 5cec711696..3004024619 100644
> --- a/meta/recipes-devtools/python/python3-jinja2/run-ptest
> +++ b/meta/recipes-devtools/python/python3-jinja2/run-ptest
> @@ -1,3 +1,3 @@
>  #!/bin/sh
>
> -pytest
> +pytest -o log_cli=true -o log_cli_level=INFO | sed -e 's/\[...%\]//g'| sed 
> -e 's/PASSED/PASS/g'| sed -e 's/FAILED/FAIL/g'| sed -e 's/SKIPPED/SKIP/g'| 
> awk '{if ($NF=="PASS" || $NF=="FAIL" || $NF=="SKIP" || $NF=="XFAIL" || 
> $NF=="XPASS"){printf "%s : %s\n", $NF, $0}else{print}}'| awk '{if 
> ($NF=="PASS" || $NF=="FAIL" || $NF=="SKIP" || $NF=="XFAIL" || $NF=="XPASS") 
> {$NF="";print $0}else{print}}'
> --
> 2.40.0
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188614): 
https://lists.openembedded.org/g/openembedded-core/message/188614
Mute This Topic: https://lists.openembedded.org/mt/101653794/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] oeqa qemurunner.py: switch utf8 error handling from ignore to replace

2023-10-02 Thread Mikko Rapeli
Hi,

This is actually for the issues seen by Richard on master-next with 6.5 kernel.
Somehow login prompt detection is failing but raw log data shows it correctly.

Cheers,

-Mikko

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188613): 
https://lists.openembedded.org/g/openembedded-core/message/188613
Mute This Topic: https://lists.openembedded.org/mt/101712722/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] oeqa qemurunner.py: switch utf8 error handling from ignore to replace

2023-10-02 Thread Mikko Rapeli
It seems like "ignore" is stopping decoding and failing to detect
login prompts. Maybe "replace" works more reliably when reads from
serial console are incomplete and we're trying to detect the login
prompt. See logs like:

https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5833/steps/14/logs/stdio
https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/log.do_testimage.3051530
https://autobuilder.yocto.io/pub/failed-builds-data/6.5%20kernel/qemu_boot_log.20231001114436

Python documentation is not clear on how "ignore" and "replace" differ
and both should continue processing if there are errors in the stream:

https://docs.python.org/3/library/codecs.html#error-handlers

Signed-off-by: Mikko Rapeli 
---
 meta/lib/oeqa/utils/qemurunner.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index b24091e212..5c18ccbd3e 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -109,7 +109,7 @@ class QemuRunner:
 
 def decode_qemulog(self, todecode):
 # Sanitize the data received from qemu as it may contain control 
characters
-msg = todecode.decode("utf-8", errors='ignore')
+msg = todecode.decode("utf-8", errors='replace')
 msg = re_control_char.sub('', msg)
 return msg
 
@@ -474,7 +474,7 @@ class QemuRunner:
 self.logger.error('Invalid file type: %s\n%s' % (file))
 read = b''
 
-self.logger.debug2('Partial boot log:\n%s' % 
(read.decode('utf-8', errors='ignore')))
+self.logger.debug2('Partial boot log:\n%s' % 
(read.decode('utf-8', errors='replace')))
 data = data + read
 if data:
 bootlog += data
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188612): 
https://lists.openembedded.org/g/openembedded-core/message/188612
Mute This Topic: https://lists.openembedded.org/mt/101712722/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] python3-numpy: remove obsolete reproducible workaround

2023-10-02 Thread Ross Burton
On 2 Oct 2023, at 13:30, Richard Purdie  
wrote:
> 
> On Mon, 2023-10-02 at 12:04 +0100, Ross Burton wrote:
>> From: Ross Burton 
>> 
>> We currently delete some pycache files because frozenset wasn't able to
>> be reproducible, but this has been fixed in Python 3.11:
>> 
>> https://github.com/python/cpython/commit/33d95c6facdfda3c8c0feffa7a99184e4abc2f63
>> 
>> Signed-off-by: Ross Burton 
>> ---
>> meta/recipes-devtools/python/python3-numpy_1.26.0.bb | 9 -
>> 1 file changed, 9 deletions(-)
>> 
>> diff --git a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb 
>> b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
>> index 4e1e34e8df3..3ae40a33fb4 100644
>> --- a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
>> +++ b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
>> @@ -30,15 +30,6 @@ do_compile:prepend() {
>> export NPY_DISABLE_SVML=1
>> }
>> 
>> -# Unfortunately the following pyc files are non-deterministc due to 
>> 'frozenset'
>> -# being written without strict ordering, even with PYTHONHASHSEED = 0
>> -# Upstream is discussing ways to solve the issue properly, until then let's
>> -# just not install the problematic files.
>> -# More info: http://benno.id.au/blog/2013/01/15/python-determinism
>> -do_install:append() {
>> - rm 
>> ${D}${PYTHON_SITEPACKAGES_DIR}/numpy/typing/tests/data/pass/__pycache__/literal.cpython*
>> -}
>> -
>> FILES:${PN}-staticdev += "${PYTHON_SITEPACKAGES_DIR}/numpy/core/lib/*.a 
>> ${PYTHON_SITEPACKAGES_DIR}/numpy/random/lib/*.a"
>> 
> 
> Are you 100% sure we use python3-native to build the pyc files? I ask
> as I can't face chasing yet another reproducibility bug down!

For numpy, I’d hope so, but we can leave this for now :)

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188611): 
https://lists.openembedded.org/g/openembedded-core/message/188611
Mute This Topic: https://lists.openembedded.org/mt/101709250/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 v1 1/3] uboot-extlinux-config.bbclass: Remove repeated space character

2023-10-02 Thread Daniel Semkowicz
Signed-off-by: Daniel Semkowicz 
---
 meta/classes-recipe/uboot-extlinux-config.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/uboot-extlinux-config.bbclass 
b/meta/classes-recipe/uboot-extlinux-config.bbclass
index f752c16b9c..f99100708d 100644
--- a/meta/classes-recipe/uboot-extlinux-config.bbclass
+++ b/meta/classes-recipe/uboot-extlinux-config.bbclass
@@ -98,7 +98,7 @@ python do_create_extlinux_config() {
 if len(labels.split()) > 1:
 cfgfile.write('menu title Select the boot mode\n')
 
-timeout =  localdata.getVar('UBOOT_EXTLINUX_TIMEOUT')
+timeout = localdata.getVar('UBOOT_EXTLINUX_TIMEOUT')
 if timeout:
 cfgfile.write('TIMEOUT %s\n' % (timeout))
 
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188608): 
https://lists.openembedded.org/g/openembedded-core/message/188608
Mute This Topic: https://lists.openembedded.org/mt/101711771/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 v1 3/3] uboot-extlinux-config.bbclass: Add menu title configuration

2023-10-02 Thread Daniel Semkowicz
Add new UBOOT_EXTLINUX_MENU_TITLE variable that allows configuring
the "MENU TITLE" entry.

If set to empty, "MENU TITLE" will not be added to the output file.

Signed-off-by: Daniel Semkowicz 
---
 meta/classes-recipe/uboot-extlinux-config.bbclass | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta/classes-recipe/uboot-extlinux-config.bbclass 
b/meta/classes-recipe/uboot-extlinux-config.bbclass
index a7f325ff2d..30bbea57de 100644
--- a/meta/classes-recipe/uboot-extlinux-config.bbclass
+++ b/meta/classes-recipe/uboot-extlinux-config.bbclass
@@ -23,6 +23,8 @@
 #Measured in 1/10 of a second.
 # UBOOT_EXTLINUX_DEFAULT_LABEL - Target to be selected by default after
 #the timeout period.
+# UBOOT_EXTLINUX_MENU_TITLE- Menu title. If empty, MENU TITLE entry
+#will not be added to the output file.
 # UBOOT_EXTLINUX_CONFIG- Output file.
 #
 # If there's only one label system will boot automatically and menu won't be
@@ -68,6 +70,7 @@ UBOOT_EXTLINUX_FDTDIR ??= "../"
 UBOOT_EXTLINUX_KERNEL_IMAGE ??= "../${KERNEL_IMAGETYPE}"
 UBOOT_EXTLINUX_KERNEL_ARGS ??= "rootwait rw"
 UBOOT_EXTLINUX_MENU_DESCRIPTION:linux ??= "${DISTRO_NAME}"
+UBOOT_EXTLINUX_MENU_TITLE ??= "Select the boot mode"
 
 UBOOT_EXTLINUX_CONFIG = "${B}/extlinux.conf"
 
@@ -95,8 +98,9 @@ python do_create_extlinux_config() {
 with open(cfile, 'w') as cfgfile:
 cfgfile.write('# Generic Distro Configuration file generated by 
OpenEmbedded\n')
 
-if len(labels.split()) > 1:
-cfgfile.write('MENU TITLE Select the boot mode\n')
+menu_title = localdata.getVar('UBOOT_EXTLINUX_MENU_TITLE')
+if len(labels.split()) > 1 and menu_title:
+cfgfile.write('MENU TITLE %s\n' % (menu_title))
 
 timeout = localdata.getVar('UBOOT_EXTLINUX_TIMEOUT')
 if timeout:
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188610): 
https://lists.openembedded.org/g/openembedded-core/message/188610
Mute This Topic: https://lists.openembedded.org/mt/101711777/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 v1 2/3] uboot-extlinux-config.bbclass: Uppercase "menu title" entry

2023-10-02 Thread Daniel Semkowicz
All other extlinux.conf entries are written to the output file
in uppercase.

Signed-off-by: Daniel Semkowicz 
---
 meta/classes-recipe/uboot-extlinux-config.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/uboot-extlinux-config.bbclass 
b/meta/classes-recipe/uboot-extlinux-config.bbclass
index f99100708d..a7f325ff2d 100644
--- a/meta/classes-recipe/uboot-extlinux-config.bbclass
+++ b/meta/classes-recipe/uboot-extlinux-config.bbclass
@@ -96,7 +96,7 @@ python do_create_extlinux_config() {
 cfgfile.write('# Generic Distro Configuration file generated by 
OpenEmbedded\n')
 
 if len(labels.split()) > 1:
-cfgfile.write('menu title Select the boot mode\n')
+cfgfile.write('MENU TITLE Select the boot mode\n')
 
 timeout = localdata.getVar('UBOOT_EXTLINUX_TIMEOUT')
 if timeout:
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188609): 
https://lists.openembedded.org/g/openembedded-core/message/188609
Mute This Topic: https://lists.openembedded.org/mt/101711773/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 v1 0/3] uboot-extlinux-config.bbclass: Add menu title configuration

2023-10-02 Thread Daniel Semkowicz
Add new UBOOT_EXTLINUX_MENU_TITLE variable that allows configuring
the "MENU TITLE" entry.

Daniel Semkowicz (3):
  uboot-extlinux-config.bbclass: Remove repeated space character
  uboot-extlinux-config.bbclass: Uppercase "menu title" entry
  uboot-extlinux-config.bbclass: Add menu title configuration

 meta/classes-recipe/uboot-extlinux-config.bbclass | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188607): 
https://lists.openembedded.org/g/openembedded-core/message/188607
Mute This Topic: https://lists.openembedded.org/mt/101711766/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] wic: bootimg-partition: Allow root placeholder in custom config

2023-10-02 Thread Daniel Semkowicz
Hello Richard,


On Mon, Oct 2, 2023 at 2:24 PM Richard Purdie
 wrote:
>
> On Mon, 2023-10-02 at 14:19 +0200, Daniel Semkowicz wrote:
> > Allow using `<>` placeholder in the custom configuration
> > file. This placeholder is then replaced with the actual UUID of the
> > root partition, generated during do_image_wic().
> >
> > This allows making use of dynamically generated partition UUID instead
> > of hard-coding it in the WKS file.
> >
> > For consistency, the same root device placeholder tag was used
> > as in the `fs-uuid.bbclass`.
> >
> > Signed-off-by: Daniel Semkowicz 
> > ---
> >  scripts/lib/wic/engine.py   | 10 ++
> >  scripts/lib/wic/plugins/source/bootimg-partition.py |  4 ++--
> >  2 files changed, 12 insertions(+), 2 deletions(-)
> >
> > diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
> > index 674ccfc244..c68e5adacb 100644
> > --- a/scripts/lib/wic/engine.py
> > +++ b/scripts/lib/wic/engine.py
> > @@ -626,3 +626,13 @@ def get_custom_config(boot_file):
> >  with open(cfg_file, "r") as f:
> >  config = f.read()
> >  return config
> > +
> > +def configure_custom_config(config, creator):
> > +"""
> > +Replace placeholders in the configuration file with the actual values.
> > +Does nothing if no placeholder is found.
> > +"""
> > +rootdev_placeholder = '<>'
> > +if rootdev_placeholder in config:
> > +config = config.replace(rootdev_placeholder, creator.rootdev)
> > +return config
> > diff --git a/scripts/lib/wic/plugins/source/bootimg-partition.py 
> > b/scripts/lib/wic/plugins/source/bootimg-partition.py
> > index 58f6da72c3..969f99476b 100644
> > --- a/scripts/lib/wic/plugins/source/bootimg-partition.py
> > +++ b/scripts/lib/wic/plugins/source/bootimg-partition.py
> > @@ -19,7 +19,7 @@ import re
> >  from glob import glob
> >
> >  from wic import WicError
> > -from wic.engine import get_custom_config
> > +from wic.engine import get_custom_config, configure_custom_config
> >  from wic.pluginbase import SourcePlugin
> >  from wic.misc import exec_cmd, get_bitbake_var
> >
> > @@ -110,7 +110,7 @@ class BootimgPartitionPlugin(SourcePlugin):
> >  custom_cfg = get_custom_config(configfile)
> >  if custom_cfg:
> >  # Use a custom configuration for extlinux.conf
> > -extlinux_conf = custom_cfg
> > +extlinux_conf = configure_custom_config(custom_cfg, cr)
> >  logger.debug("Using custom configuration file "
> >   "%s for extlinux.conf", configfile)
> >  else:
>
> Do we need to add a test case to "oe-selftest -r wic" for this?

This makes sense. I will push v2 with a test case.

>
> Cheers,
>
> Richard

Best regards
Daniel

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188606): 
https://lists.openembedded.org/g/openembedded-core/message/188606
Mute This Topic: https://lists.openembedded.org/mt/101710329/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] python3-numpy: remove obsolete reproducible workaround

2023-10-02 Thread Richard Purdie
On Mon, 2023-10-02 at 12:04 +0100, Ross Burton wrote:
> From: Ross Burton 
> 
> We currently delete some pycache files because frozenset wasn't able to
> be reproducible, but this has been fixed in Python 3.11:
> 
> https://github.com/python/cpython/commit/33d95c6facdfda3c8c0feffa7a99184e4abc2f63
> 
> Signed-off-by: Ross Burton 
> ---
>  meta/recipes-devtools/python/python3-numpy_1.26.0.bb | 9 -
>  1 file changed, 9 deletions(-)
> 
> diff --git a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb 
> b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
> index 4e1e34e8df3..3ae40a33fb4 100644
> --- a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
> +++ b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
> @@ -30,15 +30,6 @@ do_compile:prepend() {
>  export NPY_DISABLE_SVML=1
>  }
>  
> -# Unfortunately the following pyc files are non-deterministc due to 
> 'frozenset'
> -# being written without strict ordering, even with PYTHONHASHSEED = 0
> -# Upstream is discussing ways to solve the issue properly, until then let's
> -# just not install the problematic files.
> -# More info: http://benno.id.au/blog/2013/01/15/python-determinism
> -do_install:append() {
> - rm 
> ${D}${PYTHON_SITEPACKAGES_DIR}/numpy/typing/tests/data/pass/__pycache__/literal.cpython*
> -}
> -
>  FILES:${PN}-staticdev += "${PYTHON_SITEPACKAGES_DIR}/numpy/core/lib/*.a 
> ${PYTHON_SITEPACKAGES_DIR}/numpy/random/lib/*.a"
>  

Are you 100% sure we use python3-native to build the pyc files? I ask
as I can't face chasing yet another reproducibility bug down!

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188605): 
https://lists.openembedded.org/g/openembedded-core/message/188605
Mute This Topic: https://lists.openembedded.org/mt/101709250/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] wic: bootimg-partition: Allow root placeholder in custom config

2023-10-02 Thread Richard Purdie
On Mon, 2023-10-02 at 14:19 +0200, Daniel Semkowicz wrote:
> Allow using `<>` placeholder in the custom configuration
> file. This placeholder is then replaced with the actual UUID of the
> root partition, generated during do_image_wic().
> 
> This allows making use of dynamically generated partition UUID instead
> of hard-coding it in the WKS file.
> 
> For consistency, the same root device placeholder tag was used
> as in the `fs-uuid.bbclass`.
> 
> Signed-off-by: Daniel Semkowicz 
> ---
>  scripts/lib/wic/engine.py   | 10 ++
>  scripts/lib/wic/plugins/source/bootimg-partition.py |  4 ++--
>  2 files changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
> index 674ccfc244..c68e5adacb 100644
> --- a/scripts/lib/wic/engine.py
> +++ b/scripts/lib/wic/engine.py
> @@ -626,3 +626,13 @@ def get_custom_config(boot_file):
>  with open(cfg_file, "r") as f:
>  config = f.read()
>  return config
> +
> +def configure_custom_config(config, creator):
> +"""
> +Replace placeholders in the configuration file with the actual values.
> +Does nothing if no placeholder is found.
> +"""
> +rootdev_placeholder = '<>'
> +if rootdev_placeholder in config:
> +config = config.replace(rootdev_placeholder, creator.rootdev)
> +return config
> diff --git a/scripts/lib/wic/plugins/source/bootimg-partition.py 
> b/scripts/lib/wic/plugins/source/bootimg-partition.py
> index 58f6da72c3..969f99476b 100644
> --- a/scripts/lib/wic/plugins/source/bootimg-partition.py
> +++ b/scripts/lib/wic/plugins/source/bootimg-partition.py
> @@ -19,7 +19,7 @@ import re
>  from glob import glob
>  
>  from wic import WicError
> -from wic.engine import get_custom_config
> +from wic.engine import get_custom_config, configure_custom_config
>  from wic.pluginbase import SourcePlugin
>  from wic.misc import exec_cmd, get_bitbake_var
>  
> @@ -110,7 +110,7 @@ class BootimgPartitionPlugin(SourcePlugin):
>  custom_cfg = get_custom_config(configfile)
>  if custom_cfg:
>  # Use a custom configuration for extlinux.conf
> -extlinux_conf = custom_cfg
> +extlinux_conf = configure_custom_config(custom_cfg, cr)
>  logger.debug("Using custom configuration file "
>   "%s for extlinux.conf", configfile)
>  else:

Do we need to add a test case to "oe-selftest -r wic" for this?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188604): 
https://lists.openembedded.org/g/openembedded-core/message/188604
Mute This Topic: https://lists.openembedded.org/mt/101710329/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] wic: bootimg-partition: Allow root placeholder in custom config

2023-10-02 Thread Daniel Semkowicz
Allow using `<>` placeholder in the custom configuration
file. This placeholder is then replaced with the actual UUID of the
root partition, generated during do_image_wic().

This allows making use of dynamically generated partition UUID instead
of hard-coding it in the WKS file.

For consistency, the same root device placeholder tag was used
as in the `fs-uuid.bbclass`.

Signed-off-by: Daniel Semkowicz 
---
 scripts/lib/wic/engine.py   | 10 ++
 scripts/lib/wic/plugins/source/bootimg-partition.py |  4 ++--
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/scripts/lib/wic/engine.py b/scripts/lib/wic/engine.py
index 674ccfc244..c68e5adacb 100644
--- a/scripts/lib/wic/engine.py
+++ b/scripts/lib/wic/engine.py
@@ -626,3 +626,13 @@ def get_custom_config(boot_file):
 with open(cfg_file, "r") as f:
 config = f.read()
 return config
+
+def configure_custom_config(config, creator):
+"""
+Replace placeholders in the configuration file with the actual values.
+Does nothing if no placeholder is found.
+"""
+rootdev_placeholder = '<>'
+if rootdev_placeholder in config:
+config = config.replace(rootdev_placeholder, creator.rootdev)
+return config
diff --git a/scripts/lib/wic/plugins/source/bootimg-partition.py 
b/scripts/lib/wic/plugins/source/bootimg-partition.py
index 58f6da72c3..969f99476b 100644
--- a/scripts/lib/wic/plugins/source/bootimg-partition.py
+++ b/scripts/lib/wic/plugins/source/bootimg-partition.py
@@ -19,7 +19,7 @@ import re
 from glob import glob
 
 from wic import WicError
-from wic.engine import get_custom_config
+from wic.engine import get_custom_config, configure_custom_config
 from wic.pluginbase import SourcePlugin
 from wic.misc import exec_cmd, get_bitbake_var
 
@@ -110,7 +110,7 @@ class BootimgPartitionPlugin(SourcePlugin):
 custom_cfg = get_custom_config(configfile)
 if custom_cfg:
 # Use a custom configuration for extlinux.conf
-extlinux_conf = custom_cfg
+extlinux_conf = configure_custom_config(custom_cfg, cr)
 logger.debug("Using custom configuration file "
  "%s for extlinux.conf", configfile)
 else:
-- 
2.41.0



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



[OE-core][mickledore][PATCH] gcc: depend on zstd

2023-10-02 Thread Sean Nyekjaer
Add zstd LTO support for target and nativesdk compiler.

This also brings gcc into sync with gcc-cross.

% x86_64-oe-linux-gcc -v
[...]
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (GCC)
% x86_64-oesdk-linux-gcc -v
[...]
Supported LTO compression algorithms: zlib
gcc version 12.2.0 (GCC)

Signed-off-by: Sean Nyekjaer 
---
 meta/recipes-devtools/gcc/gcc-12.2.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-12.2.inc 
b/meta/recipes-devtools/gcc/gcc-12.2.inc
index 0dbbecad4a..5ff40a3b7f 100644
--- a/meta/recipes-devtools/gcc/gcc-12.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-12.2.inc
@@ -10,7 +10,7 @@ BINV = "12.2.0"
 
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
 
-DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
+DEPENDS =+ "mpfr gmp libmpc zlib zstd flex-native"
 NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native 
zstd-native"
 
 LICENSE = "GPL-3.0-with-GCC-exception & GPL-3.0-only"
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188602): 
https://lists.openembedded.org/g/openembedded-core/message/188602
Mute This Topic: https://lists.openembedded.org/mt/101709588/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 2/2] rust-cross-canadian: set CARGO_TARGET__RUNNER for nativesdk

2023-10-02 Thread Kasper
Hi Alexander

I am in the same team as Sean, and we really like the way it is solved in 
Rust/Cargo.
However, we have the issue also for C++, and as you state there is no obvious 
solution.
We are using cmaake for our C+++ projects and are discussing if a solution is 
to try to make
a cmake toolchain file for the oesdk environment as well.
If you have any experience/input it would be highly appreciated.

Br
Kasper

On September 28, 2023 at 2:47:27 pm +02:00, Alexander Kanavin 
 wrote:

> This seems like a good change (being able to easily run items built
> with c/c++ tolchains in yocto SDKs is a problem no one has
> satisfactorily resolved, and it's nice that rust got this right), but
> can you expand the test in meta/lib/oeqa/sdk/cases/rust.py to cover
> possible target options such as this one?
> 
> Alex
> 
> On Thu, 28 Sept 2023 at 10:10, Sean Nyekjaer <> wrote:
> 
> > 
> > This will enable us to build and run rust programs on the sdk host.
> > 
> > % cargo run --target x86_64-oesdk-linux-gnu -vv
> > Fresh hello v0.1.0 (~/development/hello)
> > Finished dev [unoptimized + debuginfo] target(s) in 0.02s
> > Running 
> > `/usr/local/sdk/sysroots/x86_64-oesdk-linux/lib/ld-linux-x86-64.so.2 
> > target/x86_64-oesdk-linux-gnu/debug/hello`
> > Hello, world
> > 
> > Signed-off-by: Sean Nyekjaer <>
> > ---
> > meta/recipes-devtools/rust/rust-cross-canadian.inc | 3 +++
> > 1 file changed, 3 insertions(+)
> > 
> > diff --git a/meta/recipes-devtools/rust/rust-cross-canadian.inc 
> > b/meta/recipes-devtools/rust/rust-cross-canadian.inc
> > index d25646237c..5b89216658 100644
> > --- a/meta/recipes-devtools/rust/rust-cross-canadian.inc
> > +++ b/meta/recipes-devtools/rust/rust-cross-canadian.inc
> > @@ -55,9 +55,12 @@ do_install () {
> > RUST_ENV_SETUP_SH="${ENV_SETUP_DIR}/rust.sh"
> > 
> > RUST_TARGET_TRIPLE=`echo ${RUST_TARGET_SYS} | tr '[:lower:]' '[:upper:]' | 
> > sed 's/-/_/g'`
> > + RUST_HOST_TRIPLE=`echo ${RUST_HOST_SYS} | tr '[:lower:]' '[:upper:]' | 
> > sed 's/-/_/g'`
> > + SDKARCH=`echo ${SDK_ARCH} | sed 's/_/-/g'`
> > 
> > cat <<- EOF > "${RUST_ENV_SETUP_SH}"
> > export 
> > CARGO_TARGET_${RUST_TARGET_TRIPLE}_RUSTFLAGS="--sysroot=\$OECORE_TARGET_SYSROOT/usr
> >  -C link-arg=--sysroot=\$OECORE_TARGET_SYSROOT"
> > + export 
> > CARGO_TARGET_${RUST_HOST_TRIPLE}_RUNNER="\$OECORE_NATIVE_SYSROOT/lib/ld-linux-${SDKARCH}.so.2"
> > export 
> > RUST_TARGET_PATH="\$OECORE_NATIVE_SYSROOT/usr/lib/${TARGET_SYS}/rustlib"
> > EOF
> > 
> > --
> > 2.42.0
> > 
> > 
> > 
> >


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188601): 
https://lists.openembedded.org/g/openembedded-core/message/188601
Mute This Topic: https://lists.openembedded.org/mt/101633983/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-numpy: remove obsolete reproducible workaround

2023-10-02 Thread Ross Burton
From: Ross Burton 

We currently delete some pycache files because frozenset wasn't able to
be reproducible, but this has been fixed in Python 3.11:

https://github.com/python/cpython/commit/33d95c6facdfda3c8c0feffa7a99184e4abc2f63

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/python/python3-numpy_1.26.0.bb | 9 -
 1 file changed, 9 deletions(-)

diff --git a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb 
b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
index 4e1e34e8df3..3ae40a33fb4 100644
--- a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
+++ b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
@@ -30,15 +30,6 @@ do_compile:prepend() {
 export NPY_DISABLE_SVML=1
 }
 
-# Unfortunately the following pyc files are non-deterministc due to 'frozenset'
-# being written without strict ordering, even with PYTHONHASHSEED = 0
-# Upstream is discussing ways to solve the issue properly, until then let's
-# just not install the problematic files.
-# More info: http://benno.id.au/blog/2013/01/15/python-determinism
-do_install:append() {
-   rm 
${D}${PYTHON_SITEPACKAGES_DIR}/numpy/typing/tests/data/pass/__pycache__/literal.cpython*
-}
-
 FILES:${PN}-staticdev += "${PYTHON_SITEPACKAGES_DIR}/numpy/core/lib/*.a 
${PYTHON_SITEPACKAGES_DIR}/numpy/random/lib/*.a"
 
 # install what is needed for numpy.test()
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188600): 
https://lists.openembedded.org/g/openembedded-core/message/188600
Mute This Topic: https://lists.openembedded.org/mt/101709250/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 1/2] remove obsolete workaround (https://github.com/python/cpython/commit/33d95c6facdfda3c8c0feffa7a99184e4abc2f63)

2023-10-02 Thread Ross Burton
This was meant to have a better commit message, v2 coming shortly

Ross

> On 2 Oct 2023, at 11:23, Ross Burton via lists.openembedded.org 
>  wrote:
> 
> From: Ross Burton 
> 
> ---
> meta/recipes-devtools/python/python3-numpy_1.26.0.bb | 9 -
> 1 file changed, 9 deletions(-)
> 
> diff --git a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb 
> b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
> index 4e1e34e8df3..3ae40a33fb4 100644
> --- a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
> +++ b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
> @@ -30,15 +30,6 @@ do_compile:prepend() {
> export NPY_DISABLE_SVML=1
> }
> 
> -# Unfortunately the following pyc files are non-deterministc due to 
> 'frozenset'
> -# being written without strict ordering, even with PYTHONHASHSEED = 0
> -# Upstream is discussing ways to solve the issue properly, until then let's
> -# just not install the problematic files.
> -# More info: http://benno.id.au/blog/2013/01/15/python-determinism
> -do_install:append() {
> - rm 
> ${D}${PYTHON_SITEPACKAGES_DIR}/numpy/typing/tests/data/pass/__pycache__/literal.cpython*
> -}
> -
> FILES:${PN}-staticdev += "${PYTHON_SITEPACKAGES_DIR}/numpy/core/lib/*.a 
> ${PYTHON_SITEPACKAGES_DIR}/numpy/random/lib/*.a"
> 
> # install what is needed for numpy.test()
> -- 
> 2.34.1
> 
> 
> 
> 


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



[OE-core] An insight into the kind of help we need/maintainer overload

2023-10-02 Thread Richard Purdie
It isn't any secret that I'm overloaded and struggle to keep up with
the demands of the project. People often ask me "how do you need
help?". Today, we have a fairly good example of the kind of problem I
struggle with. So it is documented, I'll describe my side of the
challenge.

We're supposed to be building the final release candidates for 4.3
today. We've also just found out that the 6.4 kernel is EOL much sooner
than we guessed. The choice is ship with a known working but
unsupportable kernel (no security updates), or try and switch to 6.5.

Over the weekend (when I should really be doing anything but work), I
tested the preliminary 6.5 patches Bruce was kind enough to prepare on
the autobuilder.

Just getting to this point is a ton of work for Bruce which goes on
quietly relatively unrecognised. The -dev kernel has been used to try
and prepare for the future kernel upgrades and without that we wouldn't
be at this point already. I'm going to focus on the challenges I have
but I want to recognise others have already faced issues just to get to
this point.

On the autobuilder we found that:

a) cryptodev breaks
b) LTP ARM testing OOMs and crashes badly
c) ARM ptests are hitting jitterentropy issues intermittently (~ a 
   third fail)
d) x86 qemu image tests are failing say 5% of the time which means 3-4 
   of 5 oe-selftest fail plus some other random failures
e) strace ptests are failing
f) meta-virtualization breaks

Bruce can't be expected to test or fix everything. Some of these issues
have all the hallmarks of being really painful to fix.

a) is trivial, there is a patch in master-next. Being selfish, f) isn't
my problem. It is Bruce's though and will distract him from other
kernel things. e) is probably deterministic and can either be fixed or
disabled.

This leaves b/c/d as the scary problems.

c) has already been reported on the kernel lists but nobody responded.
Not a good sign. I've looked to see if we can disable it but we'd have
to disable the bluetooth stack to do so.

The memory issues in b) if reported upstream will be pushed back with
"why not add more memory?" or "what is using the memory? Please debug
it and tell us how to fix it". Whilst I appreciate this is how the
world works, it is frustrating as we're effectively on our own until we
present it to upstream on a plate.

The issues in d) are the scariest of the lot. A rare ish non-
determinstic failure we can't talk to anyone about until we narrow the
issue down. If I try and share with others, they'll ask how to
reproduce and I simply don't know at this point. Engineers don't like
to touch problems without a reproduction mechanism.

Even just asking others about this has people asking "where is the bug
report I can look at?". Given most of this happened over the weekend, I
haven't written bug reports and that in itself is a lot of work even
collecting up the information from the failed builds.

So what do I do?

I have no engineers I can "assign" to this. Our kernel maintainer will
help but only has finite time they can spend on upstream work and the
shear number of issues means they are unlikely to get all the issues
resolved alone.

Can we afford to fix this in several weeks time? No, we can't as we
need to build 4.3 now so there is time pressure.

I can ask for help from others and I will/have but most people can't
drop everything and dive into this. This leaves my own time as about
the only thing I can directly control/contribute.

If these things happen very occasionally, they can be managed. It does
feel like other upstreams are getting stretched more thinly,, quality
is getting worse and they're pushing more bug resolution to their
consumers. Yocto Project users are also pulling their engineers to
internal/product focused work and I'm left in the middle with
increasing work and fewer resources.

I will likely take 48 hours to work out what we can do. If we can't
find a line of sight on resolving the issues, the outcode after that
time really has to be one of "ship 6.4, who cares about security" or
"delay the release X (4?) weeks and hope for the best".

If anyone has any idea of how to solve these process/resource issues,
or what I should be going differently, let me know. I am really tempted
just to stick with 6.4 as I really don't need these kind of problems.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188598): 
https://lists.openembedded.org/g/openembedded-core/message/188598
Mute This Topic: https://lists.openembedded.org/mt/101708983/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 v5 0/5] Add bblock helper scripts

2023-10-02 Thread Jose Quaresma
Hi Julien,

Julien Stephan  escreveu no dia sábado, 30/09/2023
à(s) 15:13:

> Le mer. 27 sept. 2023 à 23:17, Richard Purdie
>  a écrit :
> >
> > On Wed, 2023-09-27 at 14:47 +0200, Julien Stephan wrote:
> > > Le mer. 27 sept. 2023 à 12:16, Alexandre Belloni
> > >  a écrit :
> > > >
> > > > Hello,
> > > >
> > > > I had a build were all the tests passed, then I had this failure:
> > > >
> > > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5812/steps/14/logs/stdio
> > > >
> > >
> > > Hi Alexandre,
> > > I only see
> > >
> > >bblock.BBLock.test_lock_single_recipe_all_tasks: FAILED
> > >
> > > but I can't see the actual error :( Is it possible to have it
> somewhere?
> >
> > I am a bit worried this will be hard to reproduce/debug so I had a look
> > at things as I do really want to get things resolved.
> >
> > The error log says:
> >
> > WARNING: The quilt:do_build sig is computed to be
> 255536826e64d835fcc6b5a277e9a3dacaae75318e608fa2df289bdfa23df40e, but the
> sig is locked to
> 0f48875f011499948d53edc6abbe9e4efd617d5ef9233055e4b61411cf01cb87 in
> SIGGEN_LOCKEDSIGS_core2-64
> >
> > and I couldn't reproduce those stamps in a local build or on the
> > builder where it failed (once I got access which took a while).
> >
> > The "while" is important as I think in the meantime things changed
> > which effected the results.
> >
> > On the autobuilder, "bitbake quilt -S none" generated stamp files for
> > quilt. I did this for "build" and "build-st-3046552", the latter being
> > the one where the test failed. There were two different do_build stamps
> > generated. The diff:
> >
> > bitbake-diffsigs
> tmp/stamps/core2-64-poky-linux/quilt/0.67.do_build.sigdata.b502a759bb6bceb6c8ccd76b57db2612501bb66bd9c46ece5f99f8bf16d7ac4a
> ../build/tmp/stamps/core2-64-poky-linux/quilt/0.67.do_build.sigdata.7cf16a1f87d5058e134f3f6fc02612515e28784625413c87d3545e93ae0ab407
> > NOTE: Reconnecting to bitbake server...
> > Hash for task dependency diffstat:do_package_write_rpm changed from
> 41171f7938a2ddbe244372c1cc4300d91b7dca425eb8b214c19262e4949a7f18 to
> 2211ac20553e9dddc710970cf1a663412ece5b5a2071e47c5471b3ee01efa2ce
> > Hash for task dependency diffstat:do_package changed from
> f3fe486831eede23d2ebbc1efe2e2510f49f5df6d5d8a8ceb7aa2ddc6e11b1ec to
> e5ff0ed8a81d8022b0981162e9b4e286886d9e281adee81175725072c3d413ec
> > Unable to find matching sigdata for diffstat:do_package with hash
> e5ff0ed8a81d8022b0981162e9b4e286886d9e281adee81175725072c3d413ec
> >
> > i.e. a couple of dependencies were different.
> >
> > bitbake-diffsigs
> tmp/stamps/core2-64-poky-linux/diffstat/1.65.do_package.sigdata.f3fe486831eede23d2ebbc1efe2e2510f49f5df6d5d8a8ceb7aa2ddc6e11b1ec
> ../build/tmp/stamps/core2-64-poky-linux/diffstat/1.65.do_package.sigdata.af8ebe96c5cf424e1094c1599400a56096302e16d0f691daaeec380b963f37b2
> >
> > showed no output, i.e. they appear to be the same but different.
> >
> > My best guess at what is going on here is hash equivalence causing
> > problems.
> >
> > So in summary, I think the best solution will be to disable hash
> > equivalence for these tests.
> >
> >
>
> Hi Richard,
>
> Thank you a lot for digging into this!
> How can I disable the hash equivalence for these tests?
>

Can you try with BB_SIGNATURE_HANDLER using the bibake default config

self.write_config('BB_SIGNATURE_HANDLER = "OEBasicHash"')

Jose


> Should I use BB_BASEHASH_IGNORE_VARS for that?
>
> I tried the following:
> self.write_config("BB_BASEHASH_IGNORE_VARS += \"TOPDIR\"")
>
> But this doesn't work, I get a lot of errors like the following:
> ERROR: When reparsing
>
> /home/jstephan/upstream/yocto/poky/meta/recipes-devtools/quilt/quilt_0.67.bb:
> do_packagedata,
> the basehash value changed from
> 8b6adb69d1f05eddb3e86143bf9a51060f4fac153742964bb4a3d53bee93d377 to
> 9dee5dada20d7f8ccfc89ed3114c428af8c96d665234fead22c25fb118f9f62b. The
> metadata is not deterministic and this needs to be fixed.
> ERROR: The following commands may help:
> ERROR: $ bitbake quilt -cdo_packagedata -Snone
> ERROR: Then:
> ERROR: $ bitbake quilt -cdo_packagedata -Sprintdiff
>
>
>
> Cheers
> Julien
>
> > Cheers,
> >
>
> > Richard
>
> 
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188597): 
https://lists.openembedded.org/g/openembedded-core/message/188597
Mute This Topic: https://lists.openembedded.org/mt/101570279/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] remove obsolete workaround (https://github.com/python/cpython/commit/33d95c6facdfda3c8c0feffa7a99184e4abc2f63)

2023-10-02 Thread Ross Burton
From: Ross Burton 

---
 meta/recipes-devtools/python/python3-numpy_1.26.0.bb | 9 -
 1 file changed, 9 deletions(-)

diff --git a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb 
b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
index 4e1e34e8df3..3ae40a33fb4 100644
--- a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
+++ b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
@@ -30,15 +30,6 @@ do_compile:prepend() {
 export NPY_DISABLE_SVML=1
 }
 
-# Unfortunately the following pyc files are non-deterministc due to 'frozenset'
-# being written without strict ordering, even with PYTHONHASHSEED = 0
-# Upstream is discussing ways to solve the issue properly, until then let's
-# just not install the problematic files.
-# More info: http://benno.id.au/blog/2013/01/15/python-determinism
-do_install:append() {
-   rm 
${D}${PYTHON_SITEPACKAGES_DIR}/numpy/typing/tests/data/pass/__pycache__/literal.cpython*
-}
-
 FILES:${PN}-staticdev += "${PYTHON_SITEPACKAGES_DIR}/numpy/core/lib/*.a 
${PYTHON_SITEPACKAGES_DIR}/numpy/random/lib/*.a"
 
 # install what is needed for numpy.test()
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188595): 
https://lists.openembedded.org/g/openembedded-core/message/188595
Mute This Topic: https://lists.openembedded.org/mt/101708818/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] python3-numpy: remove unused CLEANBROKEN

2023-10-02 Thread Ross Burton
From: Ross Burton 

CLEANBROKEN isn't used by setuptools3, so remove it.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/python/python3-numpy_1.26.0.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb 
b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
index 3ae40a33fb4..92785d00a65 100644
--- a/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
+++ b/meta/recipes-devtools/python/python3-numpy_1.26.0.bb
@@ -24,8 +24,6 @@ inherit ptest setuptools3 github-releases
 
 S = "${WORKDIR}/numpy-${PV}"
 
-CLEANBROKEN = "1"
-
 do_compile:prepend() {
 export NPY_DISABLE_SVML=1
 }
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188596): 
https://lists.openembedded.org/g/openembedded-core/message/188596
Mute This Topic: https://lists.openembedded.org/mt/101708819/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] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M3.rc9)

2023-10-02 Thread Richard Purdie
On Mon, 2023-10-02 at 09:41 +, Jing Hui Tham wrote:
> Hi all,
>  
> Intel and WR YP QA is planning for QA execution for YP build 
> yocto-4.3_M3.rc9. We are planning to execute following tests for this cycle:
>  
> OEQA-manual tests for following module:
> 1. OE-Core
> 2. BSP-hw
>  
> Runtime auto test for following platforms:
>   1. MinnowBoard Turbot - 32bit
>   2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
>   3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
>   4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
>   5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
>   6. Beaglebone
> 
>  
> ETA for completion Friday, October 9th. Please do expect some delay due to 
> holiday in China, will proceed to submit test report once completed. 
> Sorry for any inconvenience caused.

Sorry, I thought I'd made it clear: M3 rc9 is a test build as we've
already tested and shipped M3. The rc9 is just to test the url
additions and QA reports fixes so we're ready for M4. There is
therefore no need to QA this.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188594): 
https://lists.openembedded.org/g/openembedded-core/message/188594
Mute This Topic: https://lists.openembedded.org/mt/101708430/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] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M3.rc9)

2023-10-02 Thread Jing Hui Tham
Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-4.3_M3.rc9. 
We are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
6. Beaglebone

 
ETA for completion Friday, October 9th. Please do expect some delay due to 
holiday in China, will proceed to submit test report once completed. 
Sorry for any inconvenience caused.
 

Best regards,
Jing Hui

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Thursday, September 28, 2023 12:01 AM
> To: yo...@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.3_M3.rc9)
> 
> 
> A build flagged for QA (yocto-4.3_M3.rc9) was completed on the
> autobuilder and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.3_M3.rc9
> 
> 
> Build URL:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5949
> 
> Build hash information:
> 
> bitbake: 612bdf09416ff96d08b22cf92b077516d23d0963
> meta-agl: 4a14356a535dcd47f16f788ac830d0d03457c9da
> meta-arm: be9bbaa16ed0d60490fb8f915fc48e40d14478a5
> meta-aws: ba6a653f0b5a4fa55e71646f0fe1fd0673d2c947
> meta-intel: cc04677a2717be485bf9cecf4a3d48f8a1e601cc
> meta-mingw: 65ef95a74f6ae815f63f636ed53e140a26a014ce
> meta-openembedded: c40aebd422e60126c3b18e35c20a1cb38a795a52
> meta-virtualization: b65fe24b8cbcf8797f31d058a79f8a21985e955d
> oecore: 1adf70729dafc9729e665986ad2e2250cbd25c5b
> poky: 6cb490713ed30f1f13d25978aa0d377ce66b1861
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188593): 
https://lists.openembedded.org/g/openembedded-core/message/188593
Mute This Topic: https://lists.openembedded.org/mt/101708430/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] gtk: Upgrade 4.12.1 -> 4.12.3

2023-10-02 Thread Markus Volk
Overview of Changes in 4.12.3, 28-09-2023
=

* GtkWindow:
 - Don't assume titlebars are GtkHeaderBar

* GtkTreeView:
 - Fix a crash in gtk_tree_view_is_blank_at_pos

* printing:
 - Fix some issues with the portal implementation

* GSK:
 - Some optimizations in the GL renderer
 - Fix memory leaks in the Broadway renderer

* demos:
 - Fix a crash in gtk4-demo

* Translation updates
 Basque
 Brazilian Portuguese
 Czech
 Galician
 Georgian
 German
 Hungarian
 Kazakh
 Lithuanian
 Persian
 Polish
 Spanish
 Swedish
 Turkish

Overview of Changes in 4.12.2, 20-09-2023
=

* GtkTooltip:
 - Don't cross native boundaries when looking for tooltips

* GtkCenterLayout, GtkEntry, GtkSearchEntry:
 - Fix some issues with baseline handling

* GtkSwitch:
 - Respect text direction

* Theme:
 - Use relative font sizes

* GSK:
 - Make repeated gradients match between GL and cairo
 - Make rounded rect shrinking match between Vulkan, GL and cairo
 - Fix parsing of text nodes with color glyphs
 - Restrict an optimization to the cases where it is correct
 - Fix rendering of shadows with opacity

* macOS:
 - Clamp damage regions to the surface size

* Windows:
 - Fix missing minimize and maximize buttons

* Translation updates
 Basque
 Brazilian Portuguese
 Catalan
 Chinese (China)
 Czech
 Danish
 Dutch
 Finnish
 Galician
 German
 Hungarian
 Italian
 Kazakh
 Latvian
 Lithuanian
 Slovenian
 Spanish
 Turkish

Signed-off-by: Markus Volk 
---
 meta/recipes-gnome/gtk+/{gtk4_4.12.1.bb => gtk4_4.12.3.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-gnome/gtk+/{gtk4_4.12.1.bb => gtk4_4.12.3.bb} (98%)

diff --git a/meta/recipes-gnome/gtk+/gtk4_4.12.1.bb 
b/meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
similarity index 98%
rename from meta/recipes-gnome/gtk+/gtk4_4.12.1.bb
rename to meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
index aa7115b11e..a547db8376 100644
--- a/meta/recipes-gnome/gtk+/gtk4_4.12.1.bb
+++ b/meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
@@ -37,7 +37,7 @@ MAJ_VER = "${@oe.utils.trim_version("${PV}", 2)}"
 UPSTREAM_CHECK_REGEX = "gtk-(?P\d+\.(\d*[02468])+(\.\d+)+)\.tar.xz"
 
 SRC_URI = 
"http://ftp.gnome.org/pub/gnome/sources/gtk/${MAJ_VER}/gtk-${PV}.tar.xz;
-SRC_URI[sha256sum] = 
"b8b61d6cf94fac64bf3a0bfc7af137c9dd2f8360033fdeb0cfe9612b77a99a72"
+SRC_URI[sha256sum] = 
"148ce262f6c86487455fb1d9793c3f58bc3e1da477a29617fadb0420f5870a89"
 
 S = "${WORKDIR}/gtk-${PV}"
 
-- 
2.42.0


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