[OE-core][PATCH V2] util-linux/util-linux-libuuid: upgrade from 2.39.3 to 2.40.1

2024-05-24 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

License-Update:
===
GPL-2.0 is changed to GPL-2.0-only in README.licensing.

The following two patches are removed as they've been there in new release:

  0001-login-utils-include-libgen.h-for-basename-API.patch
  mit-license.patch

Other existing patches are refreshed to avoid patch-fuzz error.

A new PACKAGECONFIG, lastlog2, is added, which serves as a switch to build Y2038
safe lastlog pam module. This is a new functionality added in 2.40.

This 2.40.1 version has the problem of unnecessary remake, causing
intermmittent errors at parallel make. The do_compile:prepend is a
workaround for this. Upstream issue and PR are:
https://github.com/util-linux/util-linux/issues/3061
https://github.com/util-linux/util-linux/pull/3064

do_install is changed to do_install:append, the legacy codes are
removed. They've been there since the born of oe-core. I tested
with ccache, there's no error.

Signed-off-by: Chen Qi 
---
 ...2.39.3.bb => util-linux-libuuid_2.40.1.bb} |  0
 meta/recipes-core/util-linux/util-linux.inc   |  8 +--
 ...ls-include-libgen.h-for-basename-API.patch | 60 ---
 .../util-linux/avoid_parallel_tests.patch |  5 +-
 .../util-linux/configure-sbindir.patch|  7 +--
 .../display_testname_for_subtest.patch|  7 +--
 .../util-linux/util-linux/mit-license.patch   | 45 --
 .../util-linux/util-linux/ptest.patch | 11 ++--
 ...l-linux_2.39.3.bb => util-linux_2.40.1.bb} | 21 ---
 9 files changed, 29 insertions(+), 135 deletions(-)
 rename meta/recipes-core/util-linux/{util-linux-libuuid_2.39.3.bb => 
util-linux-libuuid_2.40.1.bb} (100%)
 delete mode 100644 
meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
 delete mode 100644 meta/recipes-core/util-linux/util-linux/mit-license.patch
 rename meta/recipes-core/util-linux/{util-linux_2.39.3.bb => 
util-linux_2.40.1.bb} (95%)

diff --git a/meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb 
b/meta/recipes-core/util-linux/util-linux-libuuid_2.40.1.bb
similarity index 100%
rename from meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
rename to meta/recipes-core/util-linux/util-linux-libuuid_2.40.1.bb
diff --git a/meta/recipes-core/util-linux/util-linux.inc 
b/meta/recipes-core/util-linux/util-linux.inc
index d506783f9a..0f5f838e84 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -6,7 +6,7 @@ disk partitioning, kernel message management, filesystem 
creation, and system lo
 
 SECTION = "base"
 
-LICENSE = "GPL-1.0-or-later & GPL-2.0-or-later & LGPL-2.1-or-later & 
BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
+LICENSE = "GPL-1.0-or-later & GPL-2.0-only & GPL-2.0-or-later & 
LGPL-2.1-or-later & BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
 LICENSE:${PN}-fcntl-lock = "MIT"
 LICENSE:${PN}-fdisk = "GPL-1.0-or-later"
 LICENSE:${PN}-libblkid = "LGPL-2.1-or-later"
@@ -14,7 +14,7 @@ LICENSE:${PN}-libfdisk = "LGPL-2.1-or-later"
 LICENSE:${PN}-libmount = "LGPL-2.1-or-later"
 LICENSE:${PN}-libsmartcols = "LGPL-2.1-or-later"
 
-LIC_FILES_CHKSUM = 
"file://README.licensing;md5=cc80239f106687ab39ef0271ff5cf4ba \
+LIC_FILES_CHKSUM = 
"file://README.licensing;md5=ddd58b6c94da86ff4f03e91208eb9cfc \
 file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
 
file://Documentation/licenses/COPYING.GPL-2.0-or-later;md5=b234ee4d69f5fce4486a80fdaf4a4263
 \
 
file://Documentation/licenses/COPYING.LGPL-2.1-or-later;md5=4fbd65380cdd255951079008b364516c
 \
@@ -30,7 +30,6 @@ LIC_FILES_CHKSUM = 
"file://README.licensing;md5=cc80239f106687ab39ef0271ff5cf4ba
 FILESEXTRAPATHS:prepend := "${THISDIR}/util-linux:"
 MAJOR_VERSION = "${@'.'.join(d.getVar('PV').split('.')[0:2])}"
 SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-linux-${PV}.tar.xz
 \
-   file://mit-license.patch \
file://configure-sbindir.patch \
file://runuser.pamd \
file://runuser-l.pamd \
@@ -38,8 +37,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
file://run-ptest \
file://display_testname_for_subtest.patch \
file://avoid_parallel_tests.patch \
-   file://0001-login-utils-include-libgen.h-for-basename-API.patch \
file://fcntl-lock.c \
"
 
-SRC_URI[sha256sum] = 
"7b6605e48d1a49f43cc4b4cfc59f313d0dd5402fa40b96810bd572e167dfed0f"
+SRC_URI[sha256sum] = 
"59e676aa53ccb44b6c39f0ffe01a8fa274891c91bef1474752fad92461def24f"
diff --git 
a/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
 
b/meta/recipes-core/util-linux/util-linux

Re: [OE-core][PATCH 6/6] kmod: upgrade from 31 to 32

2024-05-21 Thread Chen Qi via lists.openembedded.org

Thanks. I'll fix it and send out V2.

Regards,
Qi

On 5/22/24 06:26, Richard Purdie wrote:

On Mon, 2024-05-20 at 16:10 +0800, Chen Qi via lists.openembedded.org wrote:

From: Chen Qi 

kmod now installs symlinks in 'make install'.
https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?
id=e98cef6f3f8cd6f8bfb26d147b2c209297453cca

With this change, we no longer need to deal with the symlinks in
do_install. Besides, as upstream chooses 'bin' instead of 'sbin'
to hold the tools, we'd better sync with it. That's the reason for
the sbindir -> bindir changes.

Signed-off-by: Chen Qi 
---
  .../kmod/{kmod_31.bb => kmod_32.bb}   | 24 +++
  1 file changed, 8 insertions(+), 16 deletions(-)
  rename meta/recipes-kernel/kmod/{kmod_31.bb => kmod_32.bb} (78%)

I think this is causing libnl ptest failures:

https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6437/steps/12/logs/stdio

https://autobuilder.yocto.io/pub/non-release/20240521-26/testresults/qemuarm64-ptest/libnl.log


Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199679): 
https://lists.openembedded.org/g/openembedded-core/message/199679
Mute This Topic: https://lists.openembedded.org/mt/106199577/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 2/6] util-linux/util-linux-libuuid: upgrade from 2.39.3 to 2.40.1

2024-05-21 Thread Chen Qi via lists.openembedded.org
Got it. I'll look into this error, and also the other one you pointed out in 
another email.

Regards,
Qi

-Original Message-
From: Alexandre Belloni  
Sent: Tuesday, May 21, 2024 5:32 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 2/6] util-linux/util-linux-libuuid: upgrade from 
2.39.3 to 2.40.1

This fails on the autobuilders:

ERROR: util-linux-2.40.1-r0 do_package: QA Issue: util-linux: Files/directories 
were installed but not shipped in any package:
  /lib/security/pam_lastlog2.so

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/9011/steps/15/logs/stdio

On 20/05/2024 16:10:36+0800, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi 
> 
> License-Update:
> ===
> GPL-2.0 is changed to GPL-2.0-only in README.licensing.
> 
> The following two patches are removed as they've been there in new release:
> 
>   0001-login-utils-include-libgen.h-for-basename-API.patch
>   mit-license.patch
> 
> Other existing patches are refreshed to avoid patch-fuzz error.
> 
> A new PACKAGECONFIG, lastlog2, is added, which serves as a switch to 
> build Y2038 safe lastlog pam module. This is a new functionality added in 
> 2.40.
> 
> Signed-off-by: Chen Qi 
> ---
>  ...2.39.3.bb => util-linux-libuuid_2.40.1.bb} |  0
>  meta/recipes-core/util-linux/util-linux.inc   |  8 +--
>  ...ls-include-libgen.h-for-basename-API.patch | 60 ---
>  .../util-linux/avoid_parallel_tests.patch |  5 +-
>  .../util-linux/configure-sbindir.patch|  7 +--
>  .../display_testname_for_subtest.patch|  7 +--
>  .../util-linux/util-linux/mit-license.patch   | 45 --
>  .../util-linux/util-linux/ptest.patch | 11 ++--
>  ...l-linux_2.39.3.bb => util-linux_2.40.1.bb} |  3 +-
>  9 files changed, 18 insertions(+), 128 deletions(-)  rename 
> meta/recipes-core/util-linux/{util-linux-libuuid_2.39.3.bb => 
> util-linux-libuuid_2.40.1.bb} (100%)  delete mode 100644 
> meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libge
> n.h-for-basename-API.patch  delete mode 100644 
> meta/recipes-core/util-linux/util-linux/mit-license.patch
>  rename meta/recipes-core/util-linux/{util-linux_2.39.3.bb => 
> util-linux_2.40.1.bb} (99%)
> 
> diff --git a/meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb 
> b/meta/recipes-core/util-linux/util-linux-libuuid_2.40.1.bb
> similarity index 100%
> rename from meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
> rename to meta/recipes-core/util-linux/util-linux-libuuid_2.40.1.bb
> diff --git a/meta/recipes-core/util-linux/util-linux.inc 
> b/meta/recipes-core/util-linux/util-linux.inc
> index d506783f9a..0f5f838e84 100644
> --- a/meta/recipes-core/util-linux/util-linux.inc
> +++ b/meta/recipes-core/util-linux/util-linux.inc
> @@ -6,7 +6,7 @@ disk partitioning, kernel message management, 
> filesystem creation, and system lo
>  
>  SECTION = "base"
>  
> -LICENSE = "GPL-1.0-or-later & GPL-2.0-or-later & LGPL-2.1-or-later & 
> BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
> +LICENSE = "GPL-1.0-or-later & GPL-2.0-only & GPL-2.0-or-later & 
> LGPL-2.1-or-later & BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
>  LICENSE:${PN}-fcntl-lock = "MIT"
>  LICENSE:${PN}-fdisk = "GPL-1.0-or-later"
>  LICENSE:${PN}-libblkid = "LGPL-2.1-or-later"
> @@ -14,7 +14,7 @@ LICENSE:${PN}-libfdisk = "LGPL-2.1-or-later"
>  LICENSE:${PN}-libmount = "LGPL-2.1-or-later"
>  LICENSE:${PN}-libsmartcols = "LGPL-2.1-or-later"
>  
> -LIC_FILES_CHKSUM = 
> "file://README.licensing;md5=cc80239f106687ab39ef0271ff5cf4ba \
> +LIC_FILES_CHKSUM = 
> +"file://README.licensing;md5=ddd58b6c94da86ff4f03e91208eb9cfc \
>  file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
>  
> file://Documentation/licenses/COPYING.GPL-2.0-or-later;md5=b234ee4d69f5fce4486a80fdaf4a4263
>  \
>  
> file://Documentation/licenses/COPYING.LGPL-2.1-or-later;md5=4fbd65380c
> dd255951079008b364516c \ @@ -30,7 +30,6 @@ LIC_FILES_CHKSUM = 
> "file://README.licensing;md5=cc80239f106687ab39ef0271ff5cf4ba
>  FILESEXTRAPATHS:prepend := "${THISDIR}/util-linux:"
>  MAJOR_VERSION = "${@'.'.join(d.getVar('PV').split('.')[0:2])}"
>  SRC_URI = 
> "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-linux-${PV}.tar.xz
>  \
> -   file://mit-license.patch \
> file://configure-sbindir.patch \
> file://runuser.pamd \
> file://runuser-l.pamd \
> @@ -38,8 +37,7 @@ SRC_URI = 
> 

Re: [OE-core][PATCH 1/6] systemd/systemd-boot: upgrade from 255.4 to 255.6

2024-05-21 Thread Chen Qi via lists.openembedded.org
I didn't find the 0001-basic-add-PIDFS-magic-31709.patch file in poky.
Is it from some other people's patch? If so, then that patch could be dropped 
as the error message says 'can be reverse-applied'.

Regards,
Qi

-Original Message-
From: Alexandre Belloni  
Sent: Tuesday, May 21, 2024 5:38 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/6] systemd/systemd-boot: upgrade from 255.4 to 
255.6

This also fails on the autobuilders:

ERROR: systemd-1_255.6-r0 do_patch: Applying patch 
'0001-basic-add-PIDFS-magic-31709.patch' on target directory 
'/home/pokybuild/yocto-worker/qemux86-alt/build/build/tmp/work/core2-32-poky-linux/systemd/255.6/git'
CmdError('quilt --quiltrc 
/home/pokybuild/yocto-worker/qemux86-alt/build/build/tmp/work/core2-32-poky-linux/systemd/255.6/recipe-sysroot-native/etc/quiltrc
 push', 0, 'stdout: Applying patch 0001-basic-add-PIDFS-magic-31709.patch
patching file src/basic/filesystems-gperf.gperf
Hunk #1 FAILED at 91.
1 out of 1 hunk FAILED -- rejects in file src/basic/filesystems-gperf.gperf
patching file src/basic/missing_magic.h
Hunk #1 succeeded at 133 with fuzz 1 (offset 5 lines).
Patch 0001-basic-add-PIDFS-magic-31709.patch can be reverse-applied
stderr: ')

https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/7736/steps/13/logs/stdio

On 20/05/2024 16:10:35+0800, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi 
> 
> musl patches are refreshed to avoid 'patch-fuzz' error.
> 
> Signed-off-by: Chen Qi 
> ---
>  ..._255.4.bb => systemd-boot-native_255.6.bb} |  0
>  ...md-boot_255.4.bb => systemd-boot_255.6.bb} |  0
>  meta/recipes-core/systemd/systemd.inc |  2 +-
>  ...1-missing_type.h-add-comparison_fn_t.patch |  7 +--
>  ...k-parse_printf_format-implementation.patch | 13 ++---
>  ...tall-dependency-links-at-install-tim.patch |  9 +--
>  ...missing.h-check-for-missing-strndupa.patch | 55 +--
>  ...OB_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch | 14 ++---
>  ...005-add-missing-FTW_-macros-for-musl.patch |  7 +--
>  ...06-Use-uintmax_t-for-handling-rlim_t.patch | 11 ++--
>  ...T_SYMLINK_NOFOLLOW-flag-to-faccessat.patch | 11 ++--
>  ...patible-basename-for-non-glibc-syste.patch |  8 +--
>  ...implment-systemd-sysv-install-for-OE.patch |  5 +-
>  ...uffering-when-writing-to-oom_score_a.patch |  9 +--
>  ...compliant-strerror_r-from-GNU-specif.patch | 13 ++---
>  ...definition-of-prctl_mm_map-structure.patch |  7 +--
>  ...-not-disable-buffer-in-writing-files.patch | 35 ++--
>  .../0013-Handle-__cpu_mask-usage.patch|  7 +--
>  .../systemd/0014-Handle-missing-gshadow.patch |  7 +--
>  ...l.h-Define-MIPS-ABI-defines-for-musl.patch | 11 ++--
>  ...ass-correct-parameters-to-getdents64.patch |  7 +--
>  .../0017-Adjust-for-musl-headers.patch| 17 +++---
>  ...trerror-is-assumed-to-be-GNU-specifi.patch |  9 +--
>  ...util-Make-STRERROR-portable-for-musl.patch |  7 +--
>  ...ake-malloc_trim-conditional-on-glibc.patch |  9 +--
>  ...hared-Do-not-use-malloc_info-on-musl.patch |  7 +--
>  ...22-avoid-missing-LOCK_EX-declaration.patch |  9 +--
>  .../{systemd_255.4.bb => systemd_255.6.bb}|  0
>  28 files changed, 111 insertions(+), 185 deletions(-)
>  rename meta/recipes-core/systemd/{systemd-boot-native_255.4.bb => 
> systemd-boot-native_255.6.bb} (100%)
>  rename meta/recipes-core/systemd/{systemd-boot_255.4.bb => 
> systemd-boot_255.6.bb} (100%)
>  rename meta/recipes-core/systemd/{systemd_255.4.bb => systemd_255.6.bb} 
> (100%)
> 
> diff --git a/meta/recipes-core/systemd/systemd-boot-native_255.4.bb 
> b/meta/recipes-core/systemd/systemd-boot-native_255.6.bb
> similarity index 100%
> rename from meta/recipes-core/systemd/systemd-boot-native_255.4.bb
> rename to meta/recipes-core/systemd/systemd-boot-native_255.6.bb
> diff --git a/meta/recipes-core/systemd/systemd-boot_255.4.bb 
> b/meta/recipes-core/systemd/systemd-boot_255.6.bb
> similarity index 100%
> rename from meta/recipes-core/systemd/systemd-boot_255.4.bb
> rename to meta/recipes-core/systemd/systemd-boot_255.6.bb
> diff --git a/meta/recipes-core/systemd/systemd.inc 
> b/meta/recipes-core/systemd/systemd.inc
> index a35db5091e..8bda47dd38 100644
> --- a/meta/recipes-core/systemd/systemd.inc
> +++ b/meta/recipes-core/systemd/systemd.inc
> @@ -15,7 +15,7 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
>  LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe 
> \
>  
> file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"
>  
> -SRCREV = "387a14a7b67b8b76adaed4175e14bb7e39b2f738"
> +SRCREV = "5810c25792d4268282dd3892af1a253b690423c9"
>  SRCBRANCH = "v255-stable"
>  SRC_URI = 
> "git://githu

[OE-core][PATCH 3/6] pciutils: upgrade from 3.11.1 to 3.12.0

2024-05-20 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

configure.patch is rebased against the new version.

Signed-off-by: Chen Qi 
---
 meta/recipes-bsp/pciutils/pciutils/configure.patch  | 13 -
 .../{pciutils_3.11.1.bb => pciutils_3.12.0.bb}  |  2 +-
 2 files changed, 9 insertions(+), 6 deletions(-)
 rename meta/recipes-bsp/pciutils/{pciutils_3.11.1.bb => pciutils_3.12.0.bb} 
(95%)

diff --git a/meta/recipes-bsp/pciutils/pciutils/configure.patch 
b/meta/recipes-bsp/pciutils/pciutils/configure.patch
index 5015cf4884..0ff151b8cf 100644
--- a/meta/recipes-bsp/pciutils/pciutils/configure.patch
+++ b/meta/recipes-bsp/pciutils/pciutils/configure.patch
@@ -1,4 +1,4 @@
-From 561216c8cbc280aaa9aecf30cb11835a4a0a78ed Mon Sep 17 00:00:00 2001
+From 6af07e1f812b2444d33ce199308c87e04b2f5dc7 Mon Sep 17 00:00:00 2001
 From: Richard Purdie 
 Date: Wed, 31 Dec 2008 17:20:38 +
 Subject: [PATCH] pciutils: Upgarde 2.2.4 -> 3.0.3
@@ -23,20 +23,20 @@ Upstream-Status: Inappropriate [embedded specific]
  2 files changed, 11 insertions(+), 5 deletions(-)
 
 diff --git a/Makefile b/Makefile
-index aaec04e..9c1dab0 100644
+index be23593..aa13be5 100644
 --- a/Makefile
 +++ b/Makefile
 @@ -123,7 +123,7 @@ pcilmr$(EXEEXT): pcilmr.o $(LMROBJS) $(COMMON) 
lib/$(PCIIMPLIB)
  pcilmr.o: pcilmr.c $(LMRINC)
  
  %$(EXEEXT): %.o
--  $(CC) $(LDFLAGS) $(TARGET_ARCH) $^ $(LDLIBS) -o $@
-+  $(CC) $(LDFLAGS) $(TARGET_ARCH) $^ $(LIB_LDLIBS) $(LDLIBS) -o $@
+-  $(CC) $(CFLAGS) $(LDFLAGS) $(TARGET_ARCH) $^ $(LDLIBS) -o $@
++  $(CC) $(CFLAGS) $(LDFLAGS) $(TARGET_ARCH) $^ $(LIB_LDLIBS) $(LDLIBS) -o 
$@
  
  ifdef PCI_OS_WINDOWS
  comma := ,
 diff --git a/lib/configure b/lib/configure
-index 3df057a..c87e71c 100755
+index d02160b..52c1eee 100755
 --- a/lib/configure
 +++ b/lib/configure
 @@ -9,6 +9,10 @@ echo_n() {
@@ -88,3 +88,6 @@ index 3df057a..c87e71c 100755
  c=config.h
  m=config.mk
  echo >$c '#define PCI_CONFIG_H'
+-- 
+2.42.0
+
diff --git a/meta/recipes-bsp/pciutils/pciutils_3.11.1.bb 
b/meta/recipes-bsp/pciutils/pciutils_3.12.0.bb
similarity index 95%
rename from meta/recipes-bsp/pciutils/pciutils_3.11.1.bb
rename to meta/recipes-bsp/pciutils/pciutils_3.12.0.bb
index 044074ccc3..480a338696 100644
--- a/meta/recipes-bsp/pciutils/pciutils_3.11.1.bb
+++ b/meta/recipes-bsp/pciutils/pciutils_3.12.0.bb
@@ -14,7 +14,7 @@ DEPENDS = "zlib kmod make-native"
 SRC_URI = "${KERNELORG_MIRROR}/software/utils/pciutils/pciutils-${PV}.tar.xz \
file://configure.patch"
 
-SRC_URI[sha256sum] = 
"3f472ad864473de5ba17f765cc96ef5f33e1b730918d3adda6f945a2a9290df4"
+SRC_URI[sha256sum] = 
"f185d116d5ff99b797497efce8f19f1ee8ccc5a668b97a159e3d13472f674154"
 
 inherit multilib_header pkgconfig update-alternatives
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199558): 
https://lists.openembedded.org/g/openembedded-core/message/199558
Mute This Topic: https://lists.openembedded.org/mt/106199573/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 5/6] cups: upgrade from 2.4.7 to 2.4.8

2024-05-20 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/cups/{cups_2.4.7.bb => cups_2.4.8.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/cups/{cups_2.4.7.bb => cups_2.4.8.bb} (51%)

diff --git a/meta/recipes-extended/cups/cups_2.4.7.bb 
b/meta/recipes-extended/cups/cups_2.4.8.bb
similarity index 51%
rename from meta/recipes-extended/cups/cups_2.4.7.bb
rename to meta/recipes-extended/cups/cups_2.4.8.bb
index f4b0282e4c..c0cddf7e99 100644
--- a/meta/recipes-extended/cups/cups_2.4.7.bb
+++ b/meta/recipes-extended/cups/cups_2.4.8.bb
@@ -2,4 +2,4 @@ require cups.inc
 
 LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
 
-SRC_URI[sha256sum] = 
"dd54228dd903526428ce7e37961afaed230ad310788141da75cebaa08362cf6c"
+SRC_URI[sha256sum] = 
"75c326b4ba73975efcc9a25078c4b04cdb4ee333caaad0d0823dbd522c6479a0"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199560): 
https://lists.openembedded.org/g/openembedded-core/message/199560
Mute This Topic: https://lists.openembedded.org/mt/106199576/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/6] systemd/systemd-boot: upgrade from 255.4 to 255.6

2024-05-20 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

musl patches are refreshed to avoid 'patch-fuzz' error.

Signed-off-by: Chen Qi 
---
 ..._255.4.bb => systemd-boot-native_255.6.bb} |  0
 ...md-boot_255.4.bb => systemd-boot_255.6.bb} |  0
 meta/recipes-core/systemd/systemd.inc |  2 +-
 ...1-missing_type.h-add-comparison_fn_t.patch |  7 +--
 ...k-parse_printf_format-implementation.patch | 13 ++---
 ...tall-dependency-links-at-install-tim.patch |  9 +--
 ...missing.h-check-for-missing-strndupa.patch | 55 +--
 ...OB_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch | 14 ++---
 ...005-add-missing-FTW_-macros-for-musl.patch |  7 +--
 ...06-Use-uintmax_t-for-handling-rlim_t.patch | 11 ++--
 ...T_SYMLINK_NOFOLLOW-flag-to-faccessat.patch | 11 ++--
 ...patible-basename-for-non-glibc-syste.patch |  8 +--
 ...implment-systemd-sysv-install-for-OE.patch |  5 +-
 ...uffering-when-writing-to-oom_score_a.patch |  9 +--
 ...compliant-strerror_r-from-GNU-specif.patch | 13 ++---
 ...definition-of-prctl_mm_map-structure.patch |  7 +--
 ...-not-disable-buffer-in-writing-files.patch | 35 ++--
 .../0013-Handle-__cpu_mask-usage.patch|  7 +--
 .../systemd/0014-Handle-missing-gshadow.patch |  7 +--
 ...l.h-Define-MIPS-ABI-defines-for-musl.patch | 11 ++--
 ...ass-correct-parameters-to-getdents64.patch |  7 +--
 .../0017-Adjust-for-musl-headers.patch| 17 +++---
 ...trerror-is-assumed-to-be-GNU-specifi.patch |  9 +--
 ...util-Make-STRERROR-portable-for-musl.patch |  7 +--
 ...ake-malloc_trim-conditional-on-glibc.patch |  9 +--
 ...hared-Do-not-use-malloc_info-on-musl.patch |  7 +--
 ...22-avoid-missing-LOCK_EX-declaration.patch |  9 +--
 .../{systemd_255.4.bb => systemd_255.6.bb}|  0
 28 files changed, 111 insertions(+), 185 deletions(-)
 rename meta/recipes-core/systemd/{systemd-boot-native_255.4.bb => 
systemd-boot-native_255.6.bb} (100%)
 rename meta/recipes-core/systemd/{systemd-boot_255.4.bb => 
systemd-boot_255.6.bb} (100%)
 rename meta/recipes-core/systemd/{systemd_255.4.bb => systemd_255.6.bb} (100%)

diff --git a/meta/recipes-core/systemd/systemd-boot-native_255.4.bb 
b/meta/recipes-core/systemd/systemd-boot-native_255.6.bb
similarity index 100%
rename from meta/recipes-core/systemd/systemd-boot-native_255.4.bb
rename to meta/recipes-core/systemd/systemd-boot-native_255.6.bb
diff --git a/meta/recipes-core/systemd/systemd-boot_255.4.bb 
b/meta/recipes-core/systemd/systemd-boot_255.6.bb
similarity index 100%
rename from meta/recipes-core/systemd/systemd-boot_255.4.bb
rename to meta/recipes-core/systemd/systemd-boot_255.6.bb
diff --git a/meta/recipes-core/systemd/systemd.inc 
b/meta/recipes-core/systemd/systemd.inc
index a35db5091e..8bda47dd38 100644
--- a/meta/recipes-core/systemd/systemd.inc
+++ b/meta/recipes-core/systemd/systemd.inc
@@ -15,7 +15,7 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
 LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe \
 
file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"
 
-SRCREV = "387a14a7b67b8b76adaed4175e14bb7e39b2f738"
+SRCREV = "5810c25792d4268282dd3892af1a253b690423c9"
 SRCBRANCH = "v255-stable"
 SRC_URI = 
"git://github.com/systemd/systemd-stable.git;protocol=https;branch=${SRCBRANCH}"
 
diff --git 
a/meta/recipes-core/systemd/systemd/0001-missing_type.h-add-comparison_fn_t.patch
 
b/meta/recipes-core/systemd/systemd/0001-missing_type.h-add-comparison_fn_t.patch
index 2aa5dee6b5..49871d16a8 100644
--- 
a/meta/recipes-core/systemd/systemd/0001-missing_type.h-add-comparison_fn_t.patch
+++ 
b/meta/recipes-core/systemd/systemd/0001-missing_type.h-add-comparison_fn_t.patch
@@ -1,7 +1,7 @@
-From 01195eb9f7d59139fb45df506ac6b3968c14a57f Mon Sep 17 00:00:00 2001
+From d4b0bb9c7651017985fdd75469f37c34ce2f2c50 Mon Sep 17 00:00:00 2001
 From: Chen Qi 
 Date: Mon, 25 Feb 2019 13:55:12 +0800
-Subject: [PATCH 01/22] missing_type.h: add comparison_fn_t
+Subject: [PATCH] missing_type.h: add comparison_fn_t
 
 Make it work with musl where comparison_fn_t and is not provided.
 
@@ -56,6 +56,3 @@ index ae91534198..7f67eea38b 100644
  
  const char * const catalog_file_dirs[] = {
  "/usr/local/lib/systemd/catalog/",
--- 
-2.34.1
-
diff --git 
a/meta/recipes-core/systemd/systemd/0002-add-fallback-parse_printf_format-implementation.patch
 
b/meta/recipes-core/systemd/systemd/0002-add-fallback-parse_printf_format-implementation.patch
index 900a931632..593d6261e1 100644
--- 
a/meta/recipes-core/systemd/systemd/0002-add-fallback-parse_printf_format-implementation.patch
+++ 
b/meta/recipes-core/systemd/systemd/0002-add-fallback-parse_printf_format-implementation.patch
@@ -1,7 +1,7 @@
-From 872b72739e62123867ce6c4f82aa37de24cc3f75 Mon Sep 17 00:00:00 2001
+From 776913624aaf696a3b2920b8d7506b3aae042bf1 Mon Sep 17 00:00:00 2001
 From: Alexander Kanavin 
 Date: Sat, 22 May 2021 20:26:24 +0200
-Subject: [PATCH 02/22] add fallback parse_printf_format implementat

[OE-core][PATCH 6/6] kmod: upgrade from 31 to 32

2024-05-20 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

kmod now installs symlinks in 'make install'.
https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?
id=e98cef6f3f8cd6f8bfb26d147b2c209297453cca

With this change, we no longer need to deal with the symlinks in
do_install. Besides, as upstream chooses 'bin' instead of 'sbin'
to hold the tools, we'd better sync with it. That's the reason for
the sbindir -> bindir changes.

Signed-off-by: Chen Qi 
---
 .../kmod/{kmod_31.bb => kmod_32.bb}   | 24 +++
 1 file changed, 8 insertions(+), 16 deletions(-)
 rename meta/recipes-kernel/kmod/{kmod_31.bb => kmod_32.bb} (78%)

diff --git a/meta/recipes-kernel/kmod/kmod_31.bb 
b/meta/recipes-kernel/kmod/kmod_32.bb
similarity index 78%
rename from meta/recipes-kernel/kmod/kmod_31.bb
rename to meta/recipes-kernel/kmod/kmod_32.bb
index 718a5565b4..1235bc1bf8 100644
--- a/meta/recipes-kernel/kmod/kmod_31.bb
+++ b/meta/recipes-kernel/kmod/kmod_32.bb
@@ -15,7 +15,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=a6f89e2100d9b6cdffcea4f398e37343 \
"
 inherit autotools bash-completion gtk-doc pkgconfig manpages 
update-alternatives
 
-SRCREV = "aff617ea871d0568cc491bd116c0be1e857463bb"
+SRCREV = "41faa59711742c1476d59985011ee0f27ed91d30"
 
 SRC_URI = 
"git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git;branch=master;protocol=https
 \
file://depmod-search.conf \
@@ -50,12 +50,6 @@ EXTRA_OECONF += "--bindir=${base_bindir} 
--sbindir=${base_sbindir}"
 
 do_install:append () {
 install -dm755 ${D}${base_bindir}
-install -dm755 ${D}${base_sbindir}
-# add symlinks to kmod
-ln -rs ${D}${base_bindir}/kmod ${D}${base_bindir}/lsmod
-for tool in insmod rmmod depmod modinfo modprobe; do
-ln -rs ${D}${base_bindir}/kmod ${D}${base_sbindir}/${tool}
-done
 # configuration directories
 install -dm755 ${D}${nonarch_base_libdir}/depmod.d
 install -dm755 ${D}${nonarch_base_libdir}/modprobe.d
@@ -71,16 +65,14 @@ do_install:append () {
 
 ALTERNATIVE_PRIORITY = "70"
 
-ALTERNATIVE:kmod = "insmod modprobe rmmod modinfo bin-lsmod lsmod depmod"
+ALTERNATIVE:kmod = "insmod modprobe rmmod modinfo lsmod depmod"
 
-ALTERNATIVE_LINK_NAME[depmod] = "${base_sbindir}/depmod"
-ALTERNATIVE_LINK_NAME[insmod] = "${base_sbindir}/insmod"
-ALTERNATIVE_LINK_NAME[modprobe] = "${base_sbindir}/modprobe"
-ALTERNATIVE_LINK_NAME[rmmod] = "${base_sbindir}/rmmod"
-ALTERNATIVE_LINK_NAME[modinfo] = "${base_sbindir}/modinfo"
-ALTERNATIVE_LINK_NAME[bin-lsmod] = "${base_bindir}/lsmod"
-ALTERNATIVE_LINK_NAME[lsmod] = "${base_sbindir}/lsmod"
-ALTERNATIVE_TARGET[lsmod] = "${base_bindir}/lsmod.${BPN}"
+ALTERNATIVE_LINK_NAME[depmod] = "${base_bindir}/depmod"
+ALTERNATIVE_LINK_NAME[insmod] = "${base_bindir}/insmod"
+ALTERNATIVE_LINK_NAME[modprobe] = "${base_bindir}/modprobe"
+ALTERNATIVE_LINK_NAME[rmmod] = "${base_bindir}/rmmod"
+ALTERNATIVE_LINK_NAME[modinfo] = "${base_bindir}/modinfo"
+ALTERNATIVE_LINK_NAME[lsmod] = "${base_bindir}/lsmod"
 
 PACKAGES =+ "libkmod"
 FILES:libkmod = "${base_libdir}/libkmod*${SOLIBS} ${libdir}/libkmod*${SOLIBS}"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199561): 
https://lists.openembedded.org/g/openembedded-core/message/199561
Mute This Topic: https://lists.openembedded.org/mt/106199577/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 4/6] shadow: upgrade from 4.15.0 to 4.15.1

2024-05-20 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch is dropped
as it has been merged and is in this new release.

Signed-off-by: Chen Qi 
---
 ...copy_entry-use-temporary-stat-buffer.patch | 37 ---
 meta/recipes-extended/shadow/shadow.inc   |  3 +-
 .../{shadow_4.15.0.bb => shadow_4.15.1.bb}|  0
 3 files changed, 1 insertion(+), 39 deletions(-)
 delete mode 100644 
meta/recipes-extended/shadow/files/0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch
 rename meta/recipes-extended/shadow/{shadow_4.15.0.bb => shadow_4.15.1.bb} 
(100%)

diff --git 
a/meta/recipes-extended/shadow/files/0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch
 
b/meta/recipes-extended/shadow/files/0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch
deleted file mode 100644
index 2e5503bfd4..00
--- 
a/meta/recipes-extended/shadow/files/0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch
+++ /dev/null
@@ -1,37 +0,0 @@
-From af4b8cb780587aa736692a3baa76b60474f19c5d Mon Sep 17 00:00:00 2001
-From: Enrico Scholz 
-Date: Mon, 18 Mar 2024 12:14:21 +0100
-Subject: [PATCH] lib/copydir:copy_entry(): use temporary stat buffer
-
-There are no guarantees that fstatat() does not clobber the stat
-buffer on errors.
-
-Use a temporary buffer so that the following code sees correct
-attributes of the source entry.
-
-Upstream-Status: Submitted [https://github.com/shadow-maint/shadow/pull/974]
-
-Signed-off-by: Enrico Scholz 

- lib/copydir.c | 3 ++-
- 1 file changed, 2 insertions(+), 1 deletion(-)
-
 a/lib/copydir.c
-+++ b/lib/copydir.c
-@@ -400,6 +400,7 @@ static int copy_entry (const struct path
- {
-   int err = 0;
-   struct stat sb;
-+  struct stat tmp_sb;
-   struct link_name *lp;
-   struct timespec mt[2];
- 
-@@ -423,7 +424,7 @@ static int copy_entry (const struct path
-   * If the destination already exists do nothing.
-   * This is after the copy_dir above to still iterate into subdirectories.
-   */
--  if (fstatat(dst->dirfd, dst->name, , AT_SYMLINK_NOFOLLOW) != -1) {
-+  if (fstatat(dst->dirfd, dst->name, _sb, AT_SYMLINK_NOFOLLOW) != -1) 
{
-   return err;
-   }
- 
diff --git a/meta/recipes-extended/shadow/shadow.inc 
b/meta/recipes-extended/shadow/shadow.inc
index 25930b64c1..3991006b43 100644
--- a/meta/recipes-extended/shadow/shadow.inc
+++ b/meta/recipes-extended/shadow/shadow.inc
@@ -12,7 +12,6 @@ DEPENDS = "virtual/crypt"
 
 GITHUB_BASE_URI = "https://github.com/shadow-maint/shadow/releases;
 SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BP}.tar.gz \
-   file://0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch \
${@bb.utils.contains('PACKAGECONFIG', 'pam', '${PAM_SRC_URI}', '', 
d)} \
file://useradd \
"
@@ -25,7 +24,7 @@ SRC_URI:append:class-target = " \
 SRC_URI:append:class-native = " \
file://commonio.c-fix-unexpected-open-failure-in-chroot-env.patch \
"
-SRC_URI[sha256sum] = 
"377fe0d7c1a0aa5e3514c08fdf5ddc70c9dcbb391678c2134445ed97326bcc26"
+SRC_URI[sha256sum] = 
"b34686b89b279887ffbf1f33128902ccc0fa1a998a3add44213bb12d7385b218"
 
 # Additional Policy files for PAM
 PAM_SRC_URI = "file://pam.d/chfn \
diff --git a/meta/recipes-extended/shadow/shadow_4.15.0.bb 
b/meta/recipes-extended/shadow/shadow_4.15.1.bb
similarity index 100%
rename from meta/recipes-extended/shadow/shadow_4.15.0.bb
rename to meta/recipes-extended/shadow/shadow_4.15.1.bb
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199559): 
https://lists.openembedded.org/g/openembedded-core/message/199559
Mute This Topic: https://lists.openembedded.org/mt/106199574/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/6] util-linux/util-linux-libuuid: upgrade from 2.39.3 to 2.40.1

2024-05-20 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

License-Update:
===
GPL-2.0 is changed to GPL-2.0-only in README.licensing.

The following two patches are removed as they've been there in new release:

  0001-login-utils-include-libgen.h-for-basename-API.patch
  mit-license.patch

Other existing patches are refreshed to avoid patch-fuzz error.

A new PACKAGECONFIG, lastlog2, is added, which serves as a switch to build Y2038
safe lastlog pam module. This is a new functionality added in 2.40.

Signed-off-by: Chen Qi 
---
 ...2.39.3.bb => util-linux-libuuid_2.40.1.bb} |  0
 meta/recipes-core/util-linux/util-linux.inc   |  8 +--
 ...ls-include-libgen.h-for-basename-API.patch | 60 ---
 .../util-linux/avoid_parallel_tests.patch |  5 +-
 .../util-linux/configure-sbindir.patch|  7 +--
 .../display_testname_for_subtest.patch|  7 +--
 .../util-linux/util-linux/mit-license.patch   | 45 --
 .../util-linux/util-linux/ptest.patch | 11 ++--
 ...l-linux_2.39.3.bb => util-linux_2.40.1.bb} |  3 +-
 9 files changed, 18 insertions(+), 128 deletions(-)
 rename meta/recipes-core/util-linux/{util-linux-libuuid_2.39.3.bb => 
util-linux-libuuid_2.40.1.bb} (100%)
 delete mode 100644 
meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
 delete mode 100644 meta/recipes-core/util-linux/util-linux/mit-license.patch
 rename meta/recipes-core/util-linux/{util-linux_2.39.3.bb => 
util-linux_2.40.1.bb} (99%)

diff --git a/meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb 
b/meta/recipes-core/util-linux/util-linux-libuuid_2.40.1.bb
similarity index 100%
rename from meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
rename to meta/recipes-core/util-linux/util-linux-libuuid_2.40.1.bb
diff --git a/meta/recipes-core/util-linux/util-linux.inc 
b/meta/recipes-core/util-linux/util-linux.inc
index d506783f9a..0f5f838e84 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -6,7 +6,7 @@ disk partitioning, kernel message management, filesystem 
creation, and system lo
 
 SECTION = "base"
 
-LICENSE = "GPL-1.0-or-later & GPL-2.0-or-later & LGPL-2.1-or-later & 
BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
+LICENSE = "GPL-1.0-or-later & GPL-2.0-only & GPL-2.0-or-later & 
LGPL-2.1-or-later & BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
 LICENSE:${PN}-fcntl-lock = "MIT"
 LICENSE:${PN}-fdisk = "GPL-1.0-or-later"
 LICENSE:${PN}-libblkid = "LGPL-2.1-or-later"
@@ -14,7 +14,7 @@ LICENSE:${PN}-libfdisk = "LGPL-2.1-or-later"
 LICENSE:${PN}-libmount = "LGPL-2.1-or-later"
 LICENSE:${PN}-libsmartcols = "LGPL-2.1-or-later"
 
-LIC_FILES_CHKSUM = 
"file://README.licensing;md5=cc80239f106687ab39ef0271ff5cf4ba \
+LIC_FILES_CHKSUM = 
"file://README.licensing;md5=ddd58b6c94da86ff4f03e91208eb9cfc \
 file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
 
file://Documentation/licenses/COPYING.GPL-2.0-or-later;md5=b234ee4d69f5fce4486a80fdaf4a4263
 \
 
file://Documentation/licenses/COPYING.LGPL-2.1-or-later;md5=4fbd65380cdd255951079008b364516c
 \
@@ -30,7 +30,6 @@ LIC_FILES_CHKSUM = 
"file://README.licensing;md5=cc80239f106687ab39ef0271ff5cf4ba
 FILESEXTRAPATHS:prepend := "${THISDIR}/util-linux:"
 MAJOR_VERSION = "${@'.'.join(d.getVar('PV').split('.')[0:2])}"
 SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-linux-${PV}.tar.xz
 \
-   file://mit-license.patch \
file://configure-sbindir.patch \
file://runuser.pamd \
file://runuser-l.pamd \
@@ -38,8 +37,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
file://run-ptest \
file://display_testname_for_subtest.patch \
file://avoid_parallel_tests.patch \
-   file://0001-login-utils-include-libgen.h-for-basename-API.patch \
file://fcntl-lock.c \
"
 
-SRC_URI[sha256sum] = 
"7b6605e48d1a49f43cc4b4cfc59f313d0dd5402fa40b96810bd572e167dfed0f"
+SRC_URI[sha256sum] = 
"59e676aa53ccb44b6c39f0ffe01a8fa274891c91bef1474752fad92461def24f"
diff --git 
a/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
 
b/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
deleted file mode 100644
index 6258710e1e..00
--- 
a/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
+++ /dev/null
@@ -1,60 +0,0 @@
-From d44e3ad1f6f8b5c1b3098bb7d537943a4c21d22f Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Sun, 3 Dec 2023 19:59:46 -0800
-Subject: [PATCH] login-utils: include libgen.h for basename API
-
-musl h

[OE-core][PATCH] ovmf: set CVE_STATUS for a few CVEs

2024-04-08 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

For all those CVE-2019-x CVEs, following the links in NVD, we
can see they have all been fixed.

For CVE-2014-4859 and CVE-2014-4860, there's no useful links in NVD,
but according to the following two links, they have also been fixed.

  https://security-tracker.debian.org/tracker/CVE-2014-4859
  https://security-tracker.debian.org/tracker/CVE-2014-4860

Signed-off-by: Chen Qi 
---
 meta/recipes-core/ovmf/ovmf_git.bb | 9 +
 1 file changed, 9 insertions(+)

diff --git a/meta/recipes-core/ovmf/ovmf_git.bb 
b/meta/recipes-core/ovmf/ovmf_git.bb
index 97651faf62..35ca8d1834 100644
--- a/meta/recipes-core/ovmf/ovmf_git.bb
+++ b/meta/recipes-core/ovmf/ovmf_git.bb
@@ -34,6 +34,15 @@ CVE_PRODUCT = "edk2"
 CVE_VERSION = "${@d.getVar('PV').split('stable')[1]}"
 
 CVE_STATUS[CVE-2014-8271] = "fixed-version: Fixed in svn_16280, which is an 
unusual versioning breaking version comparison."
+CVE_STATUS[CVE-2014-4859] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2014-4860] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14553] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14559] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14562] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14563] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14575] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14586] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
+CVE_STATUS[CVE-2019-14587] = "fixed-version: The CPE in the NVD database 
doesn't reflect correctly the vulnerable versions."
 
 inherit deploy
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#198015): 
https://lists.openembedded.org/g/openembedded-core/message/198015
Mute This Topic: https://lists.openembedded.org/mt/105402982/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] OE-core CVE metrics for master on Sun 07 Apr 2024 01:00:01 AM HST

2024-04-08 Thread Chen Qi via lists.openembedded.org
Yes, of course.
I've briefly checked all these CVE-2019-xxx links, they have all been fixed.
I'll send out a patch.

Regards,
Qi

-Original Message-
From: Richard Purdie  
Sent: Monday, April 8, 2024 7:57 PM
To: Steve Sakoman ; 
openembedded-core@lists.openembedded.org; yocto-secur...@lists.yoctoproject.org
Cc: Chen, Qi 
Subject: Re: [OE-core] OE-core CVE metrics for master on Sun 07 Apr 2024 
01:00:01 AM HST

On Sun, 2024-04-07 at 01:19 -1000, Steve Sakoman wrote:
> Branch: master
> 
> New this week: 21 CVEs
> CVE-2014-4859 (CVSS3: 6.8 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-4859 *
> CVE-2014-4860 (CVSS3: 6.8 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-4860 *

Qi sent a patch for this, thanks.

> CVE-2019-14553 (CVSS3: 4.9 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14553 *
> CVE-2019-14559 (CVSS3: 7.5 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14559 *
> CVE-2019-14562 (CVSS3: 5.5 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14562 *
> CVE-2019-14563 (CVSS3: 7.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14563 *
> CVE-2019-14575 (CVSS3: 7.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14575 *
> CVE-2019-14586 (CVSS3: 8.0 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14586 *
> CVE-2019-14587 (CVSS3: 6.5 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14587 *

I think we will need a patch for these for now as the CPE entries are missing 
in NVD. Would you be able to help there please Qi?

> CVE-2022-36763 (CVSS3: 7.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36763 *
> CVE-2022-36764 (CVSS3: 7.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36764 *
> CVE-2022-36765 (CVSS3: 7.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36765 *
> CVE-2023-45229 (CVSS3: 6.5 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45229 *
> CVE-2023-45230 (CVSS3: 8.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45230 *
> CVE-2023-45231 (CVSS3: 6.5 MEDIUM): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45231 *
> CVE-2023-45232 (CVSS3: 7.5 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45232 *
> CVE-2023-45233 (CVSS3: 7.5 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45233 *
> CVE-2023-45234 (CVSS3: 8.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45234 *
> CVE-2023-45235 (CVSS3: 8.8 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45235 *
> CVE-2023-45236 (CVSS3: 7.5 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45236 *
> CVE-2023-45237 (CVSS3: 7.5 HIGH): ovmf:ovmf-native 
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45237 *

These are genuine issues and I've merged an upgrade to address them.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#198014): 
https://lists.openembedded.org/g/openembedded-core/message/198014
Mute This Topic: https://lists.openembedded.org/mt/105380934/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 V2 1/2] ovmf: set CVE_PRODUCT and CVE_VERSION

2024-04-05 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Set CVE_PRODUCT and CVE_VERSION for ovmf. NVD uses 'edk2' and the
version should be the date only. Here's an example:
https://nvd.nist.gov/vuln/detail/CVE-2023-45232

Signed-off-by: Chen Qi 
---
 meta/recipes-core/ovmf/ovmf_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-core/ovmf/ovmf_git.bb 
b/meta/recipes-core/ovmf/ovmf_git.bb
index 3dc031d3b6..5b1353b8e8 100644
--- a/meta/recipes-core/ovmf/ovmf_git.bb
+++ b/meta/recipes-core/ovmf/ovmf_git.bb
@@ -30,6 +30,9 @@ PV = "edk2-stable202308"
 SRCREV = "819cfc6b42a68790a23509e4fcc58ceb70e1965e"
 UPSTREAM_CHECK_GITTAGREGEX = "(?Pedk2-stable.*)"
 
+CVE_PRODUCT = "edk2"
+CVE_VERSION = "${@d.getVar('PV').split('stable')[1]}"
+
 inherit deploy
 
 PARALLEL_MAKE = ""
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#197989): 
https://lists.openembedded.org/g/openembedded-core/message/197989
Mute This Topic: https://lists.openembedded.org/mt/105362148/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 V2 2/2] ovmf: set CVE_STATUS for CVE-2014-8271

2024-04-05 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

CVE-2014-8271 has an unusual versioning, svn_16280, which breaks
the version comparison and gives us warning like below:

  Failed to compare 202308 < svn_16280 for CVE-2014-8271

The fix has been there since 2014, our current version has included
the fix.

Signed-off-by: Chen Qi 
---
 meta/recipes-core/ovmf/ovmf_git.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/ovmf/ovmf_git.bb 
b/meta/recipes-core/ovmf/ovmf_git.bb
index 5b1353b8e8..f98cec8035 100644
--- a/meta/recipes-core/ovmf/ovmf_git.bb
+++ b/meta/recipes-core/ovmf/ovmf_git.bb
@@ -33,6 +33,8 @@ UPSTREAM_CHECK_GITTAGREGEX = "(?Pedk2-stable.*)"
 CVE_PRODUCT = "edk2"
 CVE_VERSION = "${@d.getVar('PV').split('stable')[1]}"
 
+CVE_STATUS[CVE-2014-8271] = "fixed-version: Fixed in svn_16280, which is an 
unusual versioning breaking version comparison."
+
 inherit deploy
 
 PARALLEL_MAKE = ""
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#197988): 
https://lists.openembedded.org/g/openembedded-core/message/197988
Mute This Topic: https://lists.openembedded.org/mt/105362147/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] ovmf: set CVE_PRODUCT and CVE_VERSION

2024-03-26 Thread Chen Qi via lists.openembedded.org

ping

On 3/6/24 14:54, Chen Qi via lists.openembedded.org wrote:

From: Chen Qi 

Set CVE_PRODUCT and CVE_VERSION for ovmf. NVD uses 'edk2' and the
version should be the date only. Here's an example:
https://nvd.nist.gov/vuln/detail/CVE-2023-45232

Signed-off-by: Chen Qi 
---
  meta/recipes-core/ovmf/ovmf_git.bb | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/meta/recipes-core/ovmf/ovmf_git.bb 
b/meta/recipes-core/ovmf/ovmf_git.bb
index 3dc031d3b6..5b1353b8e8 100644
--- a/meta/recipes-core/ovmf/ovmf_git.bb
+++ b/meta/recipes-core/ovmf/ovmf_git.bb
@@ -30,6 +30,9 @@ PV = "edk2-stable202308"
  SRCREV = "819cfc6b42a68790a23509e4fcc58ceb70e1965e"
  UPSTREAM_CHECK_GITTAGREGEX = "(?Pedk2-stable.*)"
  
+CVE_PRODUCT = "edk2"

+CVE_VERSION = "${@d.getVar('PV').split('stable')[1]}"
+
  inherit deploy
  
  PARALLEL_MAKE = ""







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#197547): 
https://lists.openembedded.org/g/openembedded-core/message/197547
Mute This Topic: https://lists.openembedded.org/mt/104761710/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] Yocto rpm packages do not keep the modified CONFFILES

2024-03-11 Thread Chen Qi via lists.openembedded.org
Packages + overrides are a very common way to configure/customize images.

Take OE itself as an example, the sshd_config is a conffile for openssh, but in 
rootfs-postcommands.bbclass, it is customized.
This means sshd_config might be different from the one that is recorded in rpm 
database. This is a similar situation with the original question.
The original question is basically equal to: are we going to keep the 
sshd_config we customized when we upgrade the openssh on target?

Ideally, packages should be designed to allow config snippets 
(/etc/xxx.conf.d/) or some override mechanism (default conf in /usr/lib and 
override in /etc). But there'll always be packages that lack such mechanisms. 
Using 'noreplace' seems a reasonable choice.

For the default behavior of OE, I'd suggest we change to use 'noreplace'. 
Because the more unlikely people modify their target files (as Alex pointed out 
for embedded devices), the more important those modifications might be.

Regards,
Qi

-Original Message-
From: openembedded-core@lists.openembedded.org 
 On Behalf Of Alexander Kanavin
Sent: Monday, March 11, 2024 6:20 PM
To: Böszörményi Zoltán 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

On Mon, 11 Mar 2024 at 11:09, Böszörményi Zoltán  wrote:
> Yes, I am aware. But why not use the package manager's own features 
> instead of adding a workaround?

Because I see it the opposite way: noreplace in this case is a workaround for a 
file name conflict between what the tool generates and what the package 
installs. If you're going to generate a file on target, then you shouldn't be 
installing it from a package.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196968): 
https://lists.openembedded.org/g/openembedded-core/message/196968
Mute This Topic: https://lists.openembedded.org/mt/104859795/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] dnf: remove log_lock.pid before exit

2024-03-07 Thread Chen Qi via lists.openembedded.org
Hi Alex,

You can see dnf's solution is: 
https://github.com/rpm-software-management/dnf/blob/master/etc/tmpfiles.d/dnf.conf

I don't think dnf community will look into this issue. And I would expect it to 
be a complicated one. Because dnf's own solution looks like more of a 
workaround. At the same time, yocto based systems will sometimes have 
log_lock.pid left in target filesystems. Users typing 'ls /' will notice it.

We have an OE specific patch: 
https://git.openembedded.org/openembedded-core/commit/?id=742a1b71249f4da1c8d8e13e270b0eb6128a3f66
I can see that this OE specific patch, 
0001-dnf-write-the-log-lock-to-root.patch, does solve some issue. 
Unfortunately, at the same time, it introduces this specific issue, a 
easy-to-notice one. 

My suggestion is that we merge this fix into 
0001-dnf-write-the-log-lock-to-root.patch, because they really belong together. 
I guess we can't expect dnf community to devote time into this, as they've 
already got a solution. And I'm not sure if anyone in OE community is familiar 
with dnf enough to solve this issue. So let's make things a little better, 
avoiding users of Yocto systems see this log_lock.pid file when they type 'ls 
/'.

If you have any other suggestion, please let us know.

Regards,
Qi


-Original Message-
From: openembedded-core@lists.openembedded.org 
 On Behalf Of Alexander Kanavin via 
lists.openembedded.org
Sent: Thursday, March 7, 2024 5:57 PM
To: Li, Changqing ; Richard Purdie 

Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V2] dnf: remove log_lock.pid before exit

On Thu, 7 Mar 2024 at 10:19, Changqing Li  
wrote:
> ++for arg in args:
> ++if arg.startswith("--installroot="):
> ++root=arg.split("=")[1]
> ++if os.path.exists(os.path.join(root, "log_lock.pid")):
> ++os.unlink(os.path.join(root, "log_lock.pid"))
> ++break

Apologies, but after looking at this more carefully I have to say no once more. 
The obstacle is that the code checks for existence before removing the lock, 
which means the issue of why the lock is left in place to begin with is still 
unresolved. This doesn't always happen, and we need to get to the bottom of 
*why*.

Alex

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



Re: Patchtest results for [OE-core][PATCH 2/2] systemd: remove systemd-bus-proxy settings

2024-03-06 Thread Chen Qi via lists.openembedded.org
Is this a patchtest bug? I can see the 'Signed-off-by:' is there.

Regards,
Qi

-Original Message-
From: patcht...@automation.yoctoproject.org 
 
Sent: Thursday, March 7, 2024 10:36 AM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Patchtest results for [OE-core][PATCH 2/2] systemd: remove 
systemd-bus-proxy settings

Thank you for your submission. Patchtest identified one or more issues with the 
patch. Please see the log below for more information:

---
Testing patch 
/home/patchtest/share/mboxes/2-2-systemd-remove-systemd-bus-proxy-settings.patch

FAIL: test Signed-off-by presence: Mbox is missing Signed-off-by. Add it 
manually or with "git commit --amend -s" 
(test_mbox.TestMbox.test_signed_off_by_presence)

PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence 
(test_mbox.TestMbox.test_commit_message_presence)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: pretest src uri left files: No modified recipes, skipping pretest 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
SKIP: test CVE check ignore: No modified recipes or older target branch, 
skipping test (test_metadata.TestMetadata.test_cve_check_ignore)
SKIP: test CVE tag format: No new CVE patches introduced 
(test_patch.TestPatch.test_cve_tag_format)
SKIP: test Signed-off-by presence: No new CVE patches introduced 
(test_patch.TestPatch.test_signed_off_by_presence)
SKIP: test Upstream-Status presence: No new CVE patches introduced 
(test_patch.TestPatch.test_upstream_status_presence_format)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum modified not mentioned: No modified recipes, 
skipping test 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
SKIP: test lic files chksum presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now 
(test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test src uri left files: No modified recipes, skipping pretest 
(test_metadata.TestMetadata.test_src_uri_left_files)
SKIP: test summary presence: No added recipes, skipping test 
(test_metadata.TestMetadata.test_summary_presence)
SKIP: test target mailing list: Series merged, no reason to check other mailing 
lists (test_mbox.TestMbox.test_target_mailing_list)

---

Please address the issues identified and submit a new revision of the patch, or 
alternatively, reply to this email with an explanation of why the patch should 
be accepted. If you believe these results are due to an error in patchtest, 
please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' 
category under 'Yocto Project Subprojects'). For more information on specific 
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196764): 
https://lists.openembedded.org/g/openembedded-core/message/196764
Mute This Topic: https://lists.openembedded.org/mt/104780624/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] systemd: use RDEPENDS for systemd-vconsole-setup

2024-03-06 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

With NO_RECOMMENDATIONS set to "1", systemd-vonsole-setup.service
will fail because it invokes /usr/bin/loadkeys, which is from kbd.

The RRECOMMENDATION should be changed to RDEPENDS, because it's not
a recommenation, instead it's necessary.

Signed-off-by: Chen Qi 
---
 meta/recipes-core/systemd/systemd_255.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd_255.1.bb 
b/meta/recipes-core/systemd/systemd_255.1.bb
index a907d60e84..d6fa99a5f8 100644
--- a/meta/recipes-core/systemd/systemd_255.1.bb
+++ b/meta/recipes-core/systemd/systemd_255.1.bb
@@ -490,7 +490,7 @@ FILES:${PN}-binfmt = "${sysconfdir}/binfmt.d/ \
   ${systemd_system_unitdir}/systemd-binfmt.service"
 RRECOMMENDS:${PN}-binfmt = "${@bb.utils.contains('PACKAGECONFIG', 'binfmt', 
'kernel-module-binfmt-misc', '', d)}"
 
-RRECOMMENDS:${PN}-vconsole-setup = "${@bb.utils.contains('PACKAGECONFIG', 
'vconsole', 'kbd kbd-consolefonts kbd-keymaps', '', d)}"
+RDEPENDS:${PN}-vconsole-setup = "${@bb.utils.contains('PACKAGECONFIG', 
'vconsole', 'kbd kbd-consolefonts kbd-keymaps', '', d)}"
 
 
 FILES:${PN}-journal-gatewayd = 
"${rootlibexecdir}/systemd/systemd-journal-gatewayd \
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196761): 
https://lists.openembedded.org/g/openembedded-core/message/196761
Mute This Topic: https://lists.openembedded.org/mt/104780513/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] systemd: remove systemd-bus-proxy settings

2024-03-06 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

systemd-bus-proxy was removed since v230.
>From the NEWS file:
"""
  * systemd-bus-proxyd has been removed, as kdbus is unlikely to still be
merged into the kernel in its current form.
"""

Signed-off-by: Chen Qi 
---
 meta/recipes-core/systemd/systemd_255.1.bb | 6 +-
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_255.1.bb 
b/meta/recipes-core/systemd/systemd_255.1.bb
index d6fa99a5f8..0f09c56fe2 100644
--- a/meta/recipes-core/systemd/systemd_255.1.bb
+++ b/meta/recipes-core/systemd/systemd_255.1.bb
@@ -437,7 +437,7 @@ SYSTEMD_PACKAGES = "${@bb.utils.contains('PACKAGECONFIG', 
'binfmt', '${PN}-binfm
 "
 SYSTEMD_SERVICE:${PN}-binfmt = "systemd-binfmt.service"
 
-USERADD_PACKAGES = "${PN} ${PN}-extra-utils \
+USERADD_PACKAGES = "${PN} \
 udev \
 ${@bb.utils.contains('PACKAGECONFIG', 'microhttpd', 
'${PN}-journal-gatewayd', '', d)} \
 ${@bb.utils.contains('PACKAGECONFIG', 'microhttpd', 
'${PN}-journal-remote', '', d)} \
@@ -452,7 +452,6 @@ USERADD_PARAM:${PN} += 
"${@bb.utils.contains('PACKAGECONFIG', 'polkit', '--syste
 USERADD_PARAM:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'resolved', 
'--system -d / -M --shell /sbin/nologin systemd-resolve;', '', d)}"
 USERADD_PARAM:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'timesyncd', 
'--system -d / -M --shell /sbin/nologin systemd-timesync;', '', d)}"
 USERADD_PARAM:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'oomd', 
'--system -d / -M --shell /sbin/nologin systemd-oom;', '', d)}"
-USERADD_PARAM:${PN}-extra-utils = "--system -d / -M --shell /sbin/nologin 
systemd-bus-proxy"
 USERADD_PARAM:${PN}-journal-gatewayd = "--system -d / -M --shell /sbin/nologin 
systemd-journal-gateway"
 USERADD_PARAM:${PN}-journal-remote = "--system -d / -M --shell /sbin/nologin 
systemd-journal-remote"
 USERADD_PARAM:${PN}-journal-upload = "--system -d / -M --shell /sbin/nologin 
systemd-journal-upload"
@@ -591,9 +590,6 @@ FILES:${PN}-extra-utils = "\
 ${rootlibexecdir}/systemd/systemd-resolve-host \
 ${rootlibexecdir}/systemd/systemd-ac-power \
 ${rootlibexecdir}/systemd/systemd-activate \
-${rootlibexecdir}/systemd/systemd-bus-proxyd \
-${systemd_system_unitdir}/systemd-bus-proxyd.service \
-${systemd_system_unitdir}/systemd-bus-proxyd.socket \
 ${rootlibexecdir}/systemd/systemd-measure \
 ${rootlibexecdir}/systemd/systemd-pcrphase \
 ${rootlibexecdir}/systemd/systemd-socket-proxyd \
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196762): 
https://lists.openembedded.org/g/openembedded-core/message/196762
Mute This Topic: https://lists.openembedded.org/mt/104780514/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 V2] ovmf: set CVE_PRODUCT and CVE_VERSION

2024-03-05 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Set CVE_PRODUCT and CVE_VERSION for ovmf. NVD uses 'edk2' and the
version should be the date only. Here's an example:
https://nvd.nist.gov/vuln/detail/CVE-2023-45232

Signed-off-by: Chen Qi 
---
 meta/recipes-core/ovmf/ovmf_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-core/ovmf/ovmf_git.bb 
b/meta/recipes-core/ovmf/ovmf_git.bb
index 3dc031d3b6..5b1353b8e8 100644
--- a/meta/recipes-core/ovmf/ovmf_git.bb
+++ b/meta/recipes-core/ovmf/ovmf_git.bb
@@ -30,6 +30,9 @@ PV = "edk2-stable202308"
 SRCREV = "819cfc6b42a68790a23509e4fcc58ceb70e1965e"
 UPSTREAM_CHECK_GITTAGREGEX = "(?Pedk2-stable.*)"
 
+CVE_PRODUCT = "edk2"
+CVE_VERSION = "${@d.getVar('PV').split('stable')[1]}"
+
 inherit deploy
 
 PARALLEL_MAKE = ""
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196659): 
https://lists.openembedded.org/g/openembedded-core/message/196659
Mute This Topic: https://lists.openembedded.org/mt/104761710/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] ovmf: set CVE_PRODUCT and CVE_VERSION

2024-03-05 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Set CVE_PRODUCT and CVE_VERSION for ovmf. NVD uses 'edk2' and the
version should be the date only. Here's an example:
https://nvd.nist.gov/vuln/detail/CVE-2023-45232

Signed-off-by: Chen Qi 
---
 meta/recipes-core/ovmf/ovmf_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-core/ovmf/ovmf_git.bb 
b/meta/recipes-core/ovmf/ovmf_git.bb
index 3dc031d3b6..6931536229 100644
--- a/meta/recipes-core/ovmf/ovmf_git.bb
+++ b/meta/recipes-core/ovmf/ovmf_git.bb
@@ -30,6 +30,9 @@ PV = "edk2-stable202308"
 SRCREV = "819cfc6b42a68790a23509e4fcc58ceb70e1965e"
 UPSTREAM_CHECK_GITTAGREGEX = "(?Pedk2-stable.*)"
 
+CVE_PRODUCT = "edk2"
+CVE_VERSION = "202308"
+
 inherit deploy
 
 PARALLEL_MAKE = ""
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196657): 
https://lists.openembedded.org/g/openembedded-core/message/196657
Mute This Topic: https://lists.openembedded.org/mt/104760677/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 OE-core][PATCH 3/3] goarch: disable dynamic linking globally

2024-02-27 Thread Chen Qi via lists.openembedded.org

Is this 1.21 upgrade going to be merged in LTS 5.0?
The reason I'm asking is that I'm going to upgrade some recipes in 
meta-virt and I'd like to check what would be the go version in the next 
release.


P.S.
Is this runtime error OE specific? Is it caused by some OE specific patch?

Regards,
Qi

On 2/27/24 18:07, Jose Quaresma wrote:

With go-1.21 dynamic linking cause a runtime panic:

| root@qemux86-64:~# go-helloworld
| panic: runtime error: index out of range [0] with length 0
|
| goroutine 1 [running]:
| flag.init()
| /usr/lib/go/src/flag/flag.go:1199 +0xf9

In my opinion, this would be a good trade-off so that we can update and
leave the version 1.20 for the next LTS 5.0 since we are already quite
behind on the version available upstream which already has the 1.22 available.

Signed-off-by: Jose Quaresma 
---
  meta/classes-recipe/goarch.bbclass | 14 +++---
  1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/meta/classes-recipe/goarch.bbclass 
b/meta/classes-recipe/goarch.bbclass
index 1ebe03864f..6899ec28e4 100644
--- a/meta/classes-recipe/goarch.bbclass
+++ b/meta/classes-recipe/goarch.bbclass
@@ -38,13 +38,13 @@ BASE_GOARM:armv5 = '5'
  # Go supports dynamic linking on a limited set of architectures.
  # See the supportsDynlink function in go/src/cmd/compile/internal/gc/main.go
  GO_DYNLINK = ""
-GO_DYNLINK:arm ?= "1"
-GO_DYNLINK:aarch64 ?= "1"
-GO_DYNLINK:x86 ?= "1"
-GO_DYNLINK:x86-64 ?= "1"
-GO_DYNLINK:powerpc64 ?= "1"
-GO_DYNLINK:powerpc64le ?= "1"
-GO_DYNLINK:class-native ?= ""
+GO_DYNLINK:arm = ""
+GO_DYNLINK:aarch64 = ""
+GO_DYNLINK:x86 = ""
+GO_DYNLINK:x86-64 = ""
+GO_DYNLINK:powerpc64 = ""
+GO_DYNLINK:powerpc64le = ""
+GO_DYNLINK:class-native = ""
  GO_DYNLINK:class-nativesdk = ""
  
  # define here because everybody inherits this class







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196319): 
https://lists.openembedded.org/g/openembedded-core/message/196319
Mute This Topic: https://lists.openembedded.org/mt/104600087/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/3] useradd.bbclass: Fix order of postinst-useradd-*

2024-02-23 Thread Chen Qi via lists.openembedded.org
1. I can see what this patch mainly does is ensuring groups first, then 
user, then groupmems. But the current useradd_preinst, which is called 
by useradd_sysroot has already ensured this. Is that not working?


2. You're using bb.warn as a method of outputting debugging information, 
which I don't think is appropriate.


Regards,
Qi

On 2/22/24 22:53, Eilís 'pidge' Ní Fhlannagáin wrote:

From: Piotr Łobacz 

postinst-useradd-* haven't been running in order of dependency.

This patch is reworked from Piotr Łobacz's patch and fixes:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15084
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13904

It ensures that groups, users and groupmems are all run in the correct order.

Signed-off-by: Eilís 'pidge' Ní Fhlannagáin 
---
  meta/classes-global/staging.bbclass |  7 +--
  meta/classes/useradd.bbclass| 72 ++---
  2 files changed, 49 insertions(+), 30 deletions(-)

diff --git a/meta/classes-global/staging.bbclass 
b/meta/classes-global/staging.bbclass
index ab3e1d71b5..6c21510377 100644
--- a/meta/classes-global/staging.bbclass
+++ b/meta/classes-global/staging.bbclass
@@ -245,8 +245,9 @@ def staging_populate_sysroot_dir(targetsysroot, 
nativesysroot, native, d):
  continue
  
  staging_processfixme(fixme, targetdir, targetsysroot, nativesysroot, d)

-for p in postinsts:
-bb.note("Running postinst {}, output:\n{}".format(p, 
subprocess.check_output(p, shell=True, stderr=subprocess.STDOUT)))
+bb.warn(sorted(postinsts))
+for p in sorted(postinsts):
+bb.warn("Running postinst {}, output:\n{}".format(p, 
subprocess.check_output(p, shell=True, stderr=subprocess.STDOUT)))
  
  #

  # Manifests here are complicated. The main sysroot area has the unpacked 
sstate
@@ -629,7 +630,7 @@ python extend_recipe_sysroot() {
  for f in fixme:
  staging_processfixme(fixme[f], f, recipesysroot, recipesysrootnative, 
d)
  
-for p in postinsts:

+for p in sorted(postinsts):
  bb.note("Running postinst {}, output:\n{}".format(p, 
subprocess.check_output(p, shell=True, stderr=subprocess.STDOUT)))
  
  for dep in manifests:

diff --git a/meta/classes/useradd.bbclass b/meta/classes/useradd.bbclass
index a58f8287c9..924eeadf9c 100644
--- a/meta/classes/useradd.bbclass
+++ b/meta/classes/useradd.bbclass
@@ -103,6 +103,18 @@ fi
  }
  
  useradd_sysroot () {

+   user_group_groupmems_add_sysroot user
+}
+
+groupadd_sysroot () {
+   user_group_groupmems_add_sysroot group
+}
+
+groupmemsadd_sysroot () {
+   user_group_groupmems_add_sysroot groupmems
+}
+
+user_group_groupmems_add_sysroot () {
# Pseudo may (do_prepare_recipe_sysroot) or may not 
(do_populate_sysroot_setscene) be running
# at this point so we're explicit about the environment so pseudo can 
load if
# not already present.
@@ -130,10 +142,19 @@ useradd_sysroot () {
exit 0
fi
  
-	# Add groups and users defined for all recipe packages

-   GROUPADD_PARAM="${@get_all_cmd_params(d, 'groupadd')}"
-   USERADD_PARAM="${@get_all_cmd_params(d, 'useradd')}"
-   GROUPMEMS_PARAM="${@get_all_cmd_params(d, 'groupmems')}"
+   # Add groups and users defined for all recipe packages
+   if test "x$1" = "xgroup"; then
+   GROUPADD_PARAM="${@get_all_cmd_params(d, 'groupadd')}"
+   fi
+   if test "x$1" = "xuser"; then
+   USERADD_PARAM="${@get_all_cmd_params(d, 'useradd')}"
+   fi
+   if test "x$1" = "xgroupmems"; then
+   GROUPMEMS_PARAM="${@get_all_cmd_params(d, 'groupmems')}"
+   fi
+   if test "x$1" = "x"; then
+   bbwarn "missing type of passwd db action"
+fi 
  
  	# Tell the system to use the environment vars

UA_SYSROOT=1
@@ -148,29 +169,26 @@ useradd_sysroot () {
  EXTRA_STAGING_FIXMES += "PSEUDO_SYSROOT PSEUDO_LOCALSTATEDIR LOGFIFO"
  
  python useradd_sysroot_sstate () {

-scriptfile = None
-task = d.getVar("BB_CURRENTTASK")
-if task == "package_setscene":
-bb.build.exec_func("useradd_sysroot", d)
-elif task == "prepare_recipe_sysroot":
-# Used to update this recipe's own sysroot so the user/groups are 
available to do_install
-
-# If do_populate_sysroot is triggered and we write the file here, 
there would be an overlapping
-# files. See 
usergrouptests.UserGroupTests.test_add_task_between_p_sysroot_and_package
-scriptfile = 
d.expand("${RECIPE_SYSROOT}${bindir}/postinst-useradd-${PN}-recipedebug")
-
-bb.build.exec_func("useradd_sysroot", d)
-elif task == "populate_sysroot":
-# Used when installed in dependent task sysroots
-scriptfile = 
d.expand("${SYSROOT_DESTDIR}${bindir}/postinst-useradd-${PN}")
-
-if scriptfile:
-bb.utils.mkdirhier(os.path.dirname(scriptfile))
-with open(scriptfile, 'w') as script:
-script.write("#!/bin/sh -e\n")
- 

Re: [OE-core] [PATCH] sanity.bbclass: raise_sanity_error if /tmp is noexec

2024-02-20 Thread Chen Qi via lists.openembedded.org

Hi Michal,

I just noticed the change. I can't find the V2 in my mailbox, so I'm 
going to reply here.
I'm a little concerned about forcing such requirement here. It does not 
seem *necessary*.
As far as I know, the whole oe-core does not need /tmp to be exec. The 
commit message says 'old meson', this means the current version of meson 
works well, right?
Also, why is there 'no simple way to workaround'? Is the recipe 
hardcoding '/tmp' instead of using API or command? Does exporting TMPDIR 
work?

e.g.,
export TMPDIR="${B}/tmp"

Regards,
Qi

On 2/9/24 23:57, Ross Burton wrote:

On 9 Feb 2024, at 14:09, Michal Sieron via lists.openembedded.org 
 wrote:

+# Ensure /tmp is NOT mounted with noexec
+with open("/proc/mounts", "r") as f:
+for line in f:
+# format is described in fstab(5)
+_, fs_file, _, fs_mntops, *_ = line.split()
+
+# we only want to check /tmp
+if fs_file != "/tmp":
+continue
+
+# iterate through the options from the end
+for opt in reversed(fs_mntops.split(",")):
+if opt == "noexec":
+raise_sanity_error("/tmp shouldn't be mounted with 
noexec.", d)
+

Alternatively, this is neater:

os.statvfs("/tmp").f_flag & os.ST_NOEXEC

Ross






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195957): 
https://lists.openembedded.org/g/openembedded-core/message/195957
Mute This Topic: https://lists.openembedded.org/mt/104258828/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] systemd-firstboot not triggered on read/write /etc folder

2024-02-18 Thread Chen Qi via lists.openembedded.org

Does adding 'stateless-rootfs' to IMAGE_FEATURES work for you?

meta/classes-recipe/image.bbclass:IMAGE_PREPROCESS_COMMAND:append = " 
${@ 'systemd_preset_all systemd_disable_units' if 
bb.utils.contains('DISTRO_FEATURES', 'systemd', True, False, d) and not 
bb.utils.contains('IMAGE_FEATURES', 'stateless-rootfs', True, False, d) 
else ''} reproducible_final_image_task "


Regards,
Qi

On 2/18/24 17:43, dave.elek...@gmail.com wrote:

Hi!

In the systemd-systemctl there is a *systemctl* script used for some 
configuration/settings for the systemd services (e.g. enabling services).


In this script if we call the *preset_all* command, it will create an 
empty //etc/machine-id/ file. This is required on read-only //etc/ 
folder, otherwise the systemd will fail to boot. However on read-write 
/etc folder this file is still created, which prevents systemd to 
satisfy the ConditionFirstBoot condition. This is used in systemd 
services, for example for systemd-firstboot, where you can configure 
the root password, localization, hostname, etc.


The preset_all command is triggered from the /image.bbclass/ file. A 
quick solution in my case was to add a task in my own layer, which 
deletes the //etc/machine-id/ file, but I think it would be great, to 
prevent others from the headache it can cause to investigate/fix this.


I attached the patch file about my proposed solution.

Waiting for you reply soon,
David




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195861): 
https://lists.openembedded.org/g/openembedded-core/message/195861
Mute This Topic: https://lists.openembedded.org/mt/104425254/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] gnupg: disable tests to avoid running target binaries at build time

2024-02-17 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

By default, the tests are built and run at do_compile and we can see
errors like below in log.do_compile:

  gnupg-2.4.4/tests/cms/inittests: line 99: ../../sm/gpgsm: cannot execute 
binary file: Exec format error

Note that the do_compile process still succeeds. However, we'd better avoid
executing these target binaries at build time.

Signed-off-by: Chen Qi 
---
 meta/recipes-support/gnupg/gnupg_2.4.4.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/gnupg/gnupg_2.4.4.bb 
b/meta/recipes-support/gnupg/gnupg_2.4.4.bb
index 5b9869b4f3..fff7d8c6da 100644
--- a/meta/recipes-support/gnupg/gnupg_2.4.4.bb
+++ b/meta/recipes-support/gnupg/gnupg_2.4.4.bb
@@ -32,6 +32,7 @@ EXTRA_OECONF = "--disable-ldap \
--with-readline=${STAGING_LIBDIR}/.. \
--with-mailprog=${sbindir}/sendmail \
--enable-gpg-is-gpg2 \
+   --disable-tests \
"
 # yat2m can be found from recipe-sysroot-native non-deterministically with 
different versioning otherwise
 CACHED_CONFIGUREVARS += "ac_cv_path_YAT2M=./yat2m"
-- 
2.34.1


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

2024-01-22 Thread Chen Qi via lists.openembedded.org

On 1/22/24 16:04, Alexandre Belloni wrote:

On 22/01/2024 12:38:15+0800, ChenQi wrote:

On 1/20/24 02:14, Alexandre Belloni wrote:

On 19/01/2024 19:13:25+0100, Alexandre Belloni wrote:

On 19/01/2024 11:09:20+0800, Chen Qi via lists.openembedded.org wrote:

What's the status of this patch series?
Is there any issue or concern that I missed?

I'm glad you asked, I got this today:

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466/steps/26/logs/warnings

and I know you sent a patch for this but it didn't make it yet.

I just double checked with the following settings from the "Sysvinit with
systemd" entry in config.json, there's no warning.

DISTRO_FEATURES:append = ' systemd usrmerge'
ROOT_HOME = '/root'
VIRTUAL-RUNTIME_init_manager = 'sysvinit'

So I further checked the build's settings.
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466

In the second step, "Fetch yocto-autobuilder-helper", I can see the
following logs:

HEAD is now at ebb7e65 config.json: Fix syntax errors

So the build is not using the latest repo. The latest commit is:

This is not correct, it was using the latest commit at the time, the
patch was applied after my email.


OK... Do you mean that the warning appeared in autobuilder, and then you 
applied the patch to yocto-autobuilder-helper to make the warning 
disappear? I thought you meant that the warning continued to exist even 
with the patch.


To clarify, we can now wait for autobuiler's results and I don't need to 
do anything more, right?


Regards,

Qi


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194121): 
https://lists.openembedded.org/g/openembedded-core/message/194121
Mute This Topic: https://lists.openembedded.org/mt/103380516/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] devtool/standard: avoid KeyError

2024-01-21 Thread Chen Qi via lists.openembedded.org

On 1/22/24 13:00, Chen Qi via lists.openembedded.org wrote:

On 1/20/24 01:19, Richard Purdie wrote:

On Tue, 2023-12-26 at 12:44 +0800, Chen Qi via lists.openembedded.org
wrote:

From: Chen Qi 

The initial_revs["."] does not have an initial value, resulting
in the following error:

   KeyError: '.'

The problem could be reproduced by running:

   devtool modify -n systemd 

Signed-off-by: Chen Qi 
---
  scripts/lib/devtool/standard.py | 1 +
  1 file changed, 1 insertion(+)

diff --git a/scripts/lib/devtool/standard.py 
b/scripts/lib/devtool/standard.py

index 559fd45676..5d9b86ed6a 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -905,6 +905,7 @@ def modify(args, config, basepath, workspace):
  (stdout, _) = bb.process.run('git rev-list 
--reverse devtool-base..HEAD', cwd=submodule_path)

  commits[submodule] = stdout.split()
  else:
+    initial_revs["."] = None
  if os.path.exists(os.path.join(srctree, '.git')):
  # Check if it's a tree previously extracted by us. 
This is done
  # by ensuring that devtool-base and args.branch 
(devtool) exist.

Why aren't we seeing other reports of this? How is it reproduced?


I checked the devtool OEQA, there' no test case to cover this.

You can see my reproduce step in my commit message.

When I was trying to add an oeqa to this case just now, I found the 
problem has been fixed by the following commit.


"""

commit 64d5db2f89b4f3712b55127215ae02ce50dd747a
Author: Jamin Lin 
Date:   Wed Jan 3 18:13:44 2024 +0800

    devtool: modify: fix exception

    Root Cause:
    initial_revs is an empty dictionary and do not have "." key.

    Traceback (most recent call last):
  File "scripts/devtool", line 349, in 
    ret = main()
  File "scripts/devtool", line 336, in main
    ret = args.func(args, config, basepath, workspace)
  File "scripts/lib/devtool/standard.py", line 922, in modify
    if not initial_revs["."]:
    KeyError: '.'

    Solution:
    check key exists, then get its value.

    (From OE-Core rev: fb0db5c48abb4d56233a175fdd349d18b972e452)

    Signed-off-by: Jamin Lin 
    Signed-off-by: Alexandre Belloni 
    Signed-off-by: Richard Purdie 

"""

So my patch can be ignored.

Regards,

Qi


To avoid any regression, I just sent out a patch to add a test case, 
devtool.DevtoolModifyTests.test_devtool_modify_git_no_extract.


Regards,

Qi




Should we be adding an extra test to improve coverage?

I'm assuming this isn't related to:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15318

?

Cheers,

Richard








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194115): 
https://lists.openembedded.org/g/openembedded-core/message/194115
Mute This Topic: https://lists.openembedded.org/mt/10330/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/selftest: add test case to cover 'devtool modify -n' for a git recipe

2024-01-21 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Add a test case to ensure the following error does not happen again for
'devtool modify -n'.

Traceback (most recent call last):
  File "/buildarea2/chenqi/poky/scripts/devtool", line 349, in 
ret = main()
  File "/buildarea2/chenqi/poky/scripts/devtool", line 336, in main
ret = args.func(args, config, basepath, workspace)
  File "/buildarea2/chenqi/poky/scripts/lib/devtool/standard.py", line 924, in 
modify
if not initial_revs["."]:
KeyError: '.'

Signed-off-by: Chen Qi 
---
 meta/lib/oeqa/selftest/cases/devtool.py | 22 ++
 1 file changed, 22 insertions(+)

diff --git a/meta/lib/oeqa/selftest/cases/devtool.py 
b/meta/lib/oeqa/selftest/cases/devtool.py
index a877720769..22ea0ecba9 100644
--- a/meta/lib/oeqa/selftest/cases/devtool.py
+++ b/meta/lib/oeqa/selftest/cases/devtool.py
@@ -917,6 +917,28 @@ class DevtoolModifyTests(DevtoolBase):
 # Try building
 bitbake(testrecipe)
 
+def test_devtool_modify_git_no_extract(self):
+# Check preconditions
+testrecipe = 'psplash'
+src_uri = get_bb_var('SRC_URI', testrecipe)
+self.assertIn('git://', src_uri, 'This test expects the %s recipe to 
be a git recipe' % testrecipe)
+# Clean up anything in the workdir/sysroot/sstate cache
+bitbake('%s -c cleansstate' % testrecipe)
+# Try modifying a recipe
+tempdir = tempfile.mkdtemp(prefix='devtoolqa')
+self.track_for_cleanup(tempdir)
+self.track_for_cleanup(self.workspacedir)
+self.add_command_to_tearDown('bitbake -c clean %s' % testrecipe)
+self.add_command_to_tearDown('bitbake-layers remove-layer */workspace')
+result = runCmd('git clone https://git.yoctoproject.org/psplash %s && 
devtool modify -n %s %s' % (tempdir, testrecipe, tempdir))
+self.assertExists(os.path.join(self.workspacedir, 'conf', 
'layer.conf'), 'Workspace directory not created. devtool output: %s' % 
result.output)
+matches = glob.glob(os.path.join(self.workspacedir, 'appends', 
'psplash_*.bbappend'))
+self.assertTrue(matches, 'bbappend not created')
+# Test devtool status
+result = runCmd('devtool status')
+self.assertIn(testrecipe, result.output)
+self.assertIn(tempdir, result.output)
+
 def test_devtool_modify_git_crates_subpath(self):
 # This tests two things in devtool context:
 #   - that we support local git dependencies for cargo based recipe
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194114): 
https://lists.openembedded.org/g/openembedded-core/message/194114
Mute This Topic: https://lists.openembedded.org/mt/103881323/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] devtool/standard: avoid KeyError

2024-01-21 Thread Chen Qi via lists.openembedded.org

On 1/20/24 01:19, Richard Purdie wrote:

On Tue, 2023-12-26 at 12:44 +0800, Chen Qi via lists.openembedded.org
wrote:

From: Chen Qi 

The initial_revs["."] does not have an initial value, resulting
in the following error:

   KeyError: '.'

The problem could be reproduced by running:

   devtool modify -n systemd 

Signed-off-by: Chen Qi 
---
  scripts/lib/devtool/standard.py | 1 +
  1 file changed, 1 insertion(+)

diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 559fd45676..5d9b86ed6a 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -905,6 +905,7 @@ def modify(args, config, basepath, workspace):
  (stdout, _) = bb.process.run('git rev-list --reverse 
devtool-base..HEAD', cwd=submodule_path)
  commits[submodule] = stdout.split()
  else:
+initial_revs["."] = None
  if os.path.exists(os.path.join(srctree, '.git')):
  # Check if it's a tree previously extracted by us. This is 
done
  # by ensuring that devtool-base and args.branch (devtool) 
exist.

Why aren't we seeing other reports of this? How is it reproduced?


I checked the devtool OEQA, there' no test case to cover this.

You can see my reproduce step in my commit message.

When I was trying to add an oeqa to this case just now, I found the 
problem has been fixed by the following commit.


"""

commit 64d5db2f89b4f3712b55127215ae02ce50dd747a
Author: Jamin Lin 
Date:   Wed Jan 3 18:13:44 2024 +0800

    devtool: modify: fix exception

    Root Cause:
    initial_revs is an empty dictionary and do not have "." key.

    Traceback (most recent call last):
  File "scripts/devtool", line 349, in 
    ret = main()
  File "scripts/devtool", line 336, in main
    ret = args.func(args, config, basepath, workspace)
  File "scripts/lib/devtool/standard.py", line 922, in modify
    if not initial_revs["."]:
    KeyError: '.'

    Solution:
    check key exists, then get its value.

    (From OE-Core rev: fb0db5c48abb4d56233a175fdd349d18b972e452)

    Signed-off-by: Jamin Lin 
    Signed-off-by: Alexandre Belloni 
    Signed-off-by: Richard Purdie 

"""

So my patch can be ignored.

Regards,

Qi


Should we be adding an extra test to improve coverage?

I'm assuming this isn't related to:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15318

?

Cheers,

Richard



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

2024-01-21 Thread Chen Qi via lists.openembedded.org

On 1/20/24 02:14, Alexandre Belloni wrote:

On 19/01/2024 19:13:25+0100, Alexandre Belloni wrote:

On 19/01/2024 11:09:20+0800, Chen Qi via lists.openembedded.org wrote:

What's the status of this patch series?
Is there any issue or concern that I missed?

I'm glad you asked, I got this today:

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466/steps/26/logs/warnings

and I know you sent a patch for this but it didn't make it yet.


I just double checked with the following settings from the "Sysvinit 
with systemd" entry in config.json, there's no warning.


DISTRO_FEATURES:append = ' systemd usrmerge'
ROOT_HOME = '/root'
VIRTUAL-RUNTIME_init_manager = 'sysvinit'

So I further checked the build's settings. 
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466


In the second step, "Fetch yocto-autobuilder-helper", I can see the 
following logs:


HEAD is now at ebb7e65 config.json: Fix syntax errors

So the build is not using the latest repo. The latest commit is:

97bb07f (HEAD -> master, origin/master, origin/HEAD) config.json: set 
ROOT_HOME to /root for sysvinit with systemd


Regards,

Qi





Regards,
Qi

On 12/27/23 12:20, Chen Qi via lists.openembedded.org wrote:

From: Chen Qi

1. Patch changes:

0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
is removed because it has no real effect now. The /lib is now
/usr/lib because 'usrmerge' is a required distro feature for systemd.

0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is
refreshed for the new version to avoid patch-fuzz issue.

2. root user's home directory now defaults to "/root":

The sysuers.d/basic.conf is still modified to respect the ROOT_HOME
value, so if users set ROOT_HOME to "/home/root", the behavior is the
same as before. However, this is only for backward compatibility. With
this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
This is because systemd's source codes are hardcoding "/root", and other
values are not officially supported. See the list below.
$ grep -rl '"/root"' src/ | grep -v 'src/test'
src/core/namespace.c
src/basic/user-util.c
src/nss-systemd/nss-systemd.c
src/nspawn/nspawn.c
src/firstboot/firstboot.c
src/shared/userdb.c
src/shared/user-record.c
$ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ tmpfiles.d/ 
units/ xorg/ tools/
sysusers.d/basic.conf.in
tmpfiles.d/provision.conf
units/emergency.service.in
units/rescue.service.in
tools/list-discoverable-partitions.py
Previously, the recipe was just substituting sysusers.d/basic.conf.in,
which is not enough to be treated as 'fully support'. I deliberately put
a warning message in do_install to warn users about non "/root" ROOT_HOME
value. Don't remove it until all above places are handled.

3. cgroupv2 is now the default.
cgroupv2 is the default for systemd for many years and it's the default
for distros such as ubuntu and fedora. Let's also use it as the default.

Signed-off-by: Chen Qi
---
   .../distro/include/init-manager-systemd.inc   |  2 +
   meta/recipes-core/systemd/systemd.inc |  4 +-
   ...tall-dependency-links-at-install-tim.patch | 22 +++---
   ...sysctl.d-binfmt.d-modules-load.d-to-.patch | 73 ---
   .../systemd/systemd/basic.conf.in | 40 --
   .../{systemd_254.4.bb => systemd_255.1.bb}| 16 ++--
   6 files changed, 25 insertions(+), 132 deletions(-)
   delete mode 100644 
meta/recipes-core/systemd/systemd/0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
   delete mode 100644 meta/recipes-core/systemd/systemd/basic.conf.in
   rename meta/recipes-core/systemd/{systemd_254.4.bb => systemd_255.1.bb} (98%)

diff --git a/meta/conf/distro/include/init-manager-systemd.inc 
b/meta/conf/distro/include/init-manager-systemd.inc
index 595d1f2644..0a76647459 100644
--- a/meta/conf/distro/include/init-manager-systemd.inc
+++ b/meta/conf/distro/include/init-manager-systemd.inc
@@ -5,3 +5,5 @@ VIRTUAL-RUNTIME_init_manager ??= "systemd"
   VIRTUAL-RUNTIME_initscripts ??= "systemd-compat-units"
   VIRTUAL-RUNTIME_login_manager ??= "shadow-base"
   VIRTUAL-RUNTIME_dev_manager ??= "systemd"
+# systemd hardcodes /root in its source codes, other values are not offically 
supported
+ROOT_HOME ?= "/root"
diff --git a/meta/recipes-core/systemd/systemd.inc 
b/meta/recipes-core/systemd/systemd.inc
index ccc3236457..1417e0150f 100644
--- a/meta/recipes-core/systemd/systemd.inc
+++ b/meta/recipes-core/systemd/systemd.inc
@@ -15,8 +15,8 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
   LIC_FILES_CHKSUM ="file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe \ 
file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"

-SRCREV = "2e7504449a51fb38db9cd2da391c6434f82def51"
-SRCBRANCH = "v254-stable"
+SRCREV = "2018ccef6645ce00c78436

Re: [OE-core] [PATCH v3 1/2] shadow: update 4.13 -> 4.14.2

2024-01-19 Thread Chen Qi via lists.openembedded.org
I didn't do anything particular, but as several people are sharing the server, 
it's possible that its environment is somewhat messed up. I'll check more and 
fix the environment. Thanks for your double check.

Regards,
Qi

-Original Message-
From: Alexander Kanavin  
Sent: Friday, January 19, 2024 6:12 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin 

Subject: Re: [OE-core] [PATCH v3 1/2] shadow: update 4.13 -> 4.14.2

I just tried poky master on ubuntu 20.04, and the issues do not appear. Do you 
have a custom setup?

Alex

On Fri, 19 Jan 2024 at 04:06, ChenQi  wrote:
>
> I'm seeing build failures on Ubuntu 20.04.
> GCC version: 9.4.0
>
> 1. error: parameter name omitted
> The problem is that the active_sessions_count function's definition 
> lacks parameter. I did change like below:
> -unsigned long active_sessions_count(const char *name, unsigned long 
> unused)
> +unsigned long active_sessions_count(const char *name, unsigned long
> unused unused_parameter)
> But then I observed another error, as shown below.
>
> 2. undefined reference to `dlsym'.
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> ../lib/.libs/libshadow.a(libshadow_la-nss.o): in function `nss_exit':
> | nss.c:(.text+0x32): undefined reference to `dlclose'
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> ../lib/.libs/libshadow.a(libshadow_la-nss.o): in function `nss_init':
> | nss.c:(.text+0x1dd): undefined reference to `dlopen'
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> nss.c:(.text+0x21c): undefined reference to `dlsym'
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> nss.c:(.text+0x237): undefined reference to `dlsym'
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> nss.c:(.text+0x253): undefined reference to `dlsym'
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> nss.c:(.text+0x365): undefined reference to `dlclose'
> | /ala-lpggp72/qichen/Yocto/builds/build-master/tmp/hosttools/ld:
> nss.c:(.text+0x3b2): undefined reference to `dlerror'
> | collect2: error: ld returned 1 exit status
> | make[2]: *** [Makefile:1130: su] Error 1
>
> On Ubuntu22.04, there's no such issue.
>
> Regards,
> Qi
>
> On 1/11/24 21:15, Alexander Kanavin wrote:
> > License-Update: formatting, spdx conversion
> >
> > Drop:
> > 0001-Disable-use-of-syslog-for-sysroot.patch
> > (issue fixed upstream)
> >
> > 0001-Fix-can-not-print-full-login.patch
> > 0001-Overhaul-valid_field.patch
> > CVE-2023-29383.patch
> > (backports)
> >
> > libbsd is a new native dependency, as otherwise glibc >= 2.38 is 
> > needed.
> >
> > A similar fix is added to musl in order to define non-standard 
> > __BEGIN_DECLS/__END_DECLS.
> >
> > Signed-off-by: Alexander Kanavin 
> > ---
> >   ...01-Disable-use-of-syslog-for-sysroot.patch |  52 ---
> >   .../0001-Fix-can-not-print-full-login.patch   |  41 -
> >   .../files/0001-Overhaul-valid_field.patch |  65 
> >   .../shadow/files/CVE-2023-29383.patch |  53 ---
> >   .../shadow/files/CVE-2023-4641.patch  | 147 --
> >   ...nexpected-open-failure-in-chroot-env.patch |  16 +-
> >   meta/recipes-extended/shadow/shadow.inc   |  20 +--
> >   .../{shadow_4.13.bb => shadow_4.14.2.bb}  |   0
> >   8 files changed, 16 insertions(+), 378 deletions(-)
> >   delete mode 100644 
> > meta/recipes-extended/shadow/files/0001-Disable-use-of-syslog-for-sysroot.patch
> >   delete mode 100644 
> > meta/recipes-extended/shadow/files/0001-Fix-can-not-print-full-login.patch
> >   delete mode 100644 
> > meta/recipes-extended/shadow/files/0001-Overhaul-valid_field.patch
> >   delete mode 100644 meta/recipes-extended/shadow/files/CVE-2023-29383.patch
> >   delete mode 100644 meta/recipes-extended/shadow/files/CVE-2023-4641.patch
> >   rename meta/recipes-extended/shadow/{shadow_4.13.bb => 
> > shadow_4.14.2.bb} (100%)
> >
> > diff --git 
> > a/meta/recipes-extended/shadow/files/0001-Disable-use-of-syslog-for-
> > sysroot.patch 
> > b/meta/recipes-extended/shadow/files/0001-Disable-use-of-syslog-for-
> > sysroot.patch
> > deleted file mode 100644
> > index fa1532c8317..000
> > --- 
> > a/meta/recipes-extended/shadow/files/0001-Disable-use-of-syslog-for-
> > sysroot.patch
> > +++ /dev/null
> > @@ -1,52 +0,0 @@
> > -From 85d0444229ee3d14fefcf10d093f49c862826f82 Mon Sep 17 00:00:00 
> > 2001
> > -From: Richard Purdie 
> > -Date: Thu, 14 Apr 2022 23:11:53 +
> > -Subject

Re: [OE-core][PATCH] devtool/standard: avoid KeyError

2024-01-18 Thread Chen Qi via lists.openembedded.org

ping

On 12/26/23 12:44, Chen Qi via lists.openembedded.org wrote:

From: Chen Qi 

The initial_revs["."] does not have an initial value, resulting
in the following error:

   KeyError: '.'

The problem could be reproduced by running:

   devtool modify -n systemd 

Signed-off-by: Chen Qi 
---
  scripts/lib/devtool/standard.py | 1 +
  1 file changed, 1 insertion(+)

diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 559fd45676..5d9b86ed6a 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -905,6 +905,7 @@ def modify(args, config, basepath, workspace):
  (stdout, _) = bb.process.run('git rev-list --reverse 
devtool-base..HEAD', cwd=submodule_path)
  commits[submodule] = stdout.split()
  else:
+initial_revs["."] = None
  if os.path.exists(os.path.join(srctree, '.git')):
  # Check if it's a tree previously extracted by us. This is 
done
  # by ensuring that devtool-base and args.branch (devtool) 
exist.






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

2024-01-18 Thread Chen Qi via lists.openembedded.org

What's the status of this patch series?
Is there any issue or concern that I missed?

Regards,
Qi

On 12/27/23 12:20, Chen Qi via lists.openembedded.org wrote:

From: Chen Qi 

1. Patch changes:

0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
is removed because it has no real effect now. The /lib is now
/usr/lib because 'usrmerge' is a required distro feature for systemd.

0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is
refreshed for the new version to avoid patch-fuzz issue.

2. root user's home directory now defaults to "/root":

The sysuers.d/basic.conf is still modified to respect the ROOT_HOME
value, so if users set ROOT_HOME to "/home/root", the behavior is the
same as before. However, this is only for backward compatibility. With
this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
This is because systemd's source codes are hardcoding "/root", and other
values are not officially supported. See the list below.
$ grep -rl '"/root"' src/ | grep -v 'src/test'
src/core/namespace.c
src/basic/user-util.c
src/nss-systemd/nss-systemd.c
src/nspawn/nspawn.c
src/firstboot/firstboot.c
src/shared/userdb.c
src/shared/user-record.c
$ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ tmpfiles.d/ 
units/ xorg/ tools/
sysusers.d/basic.conf.in
tmpfiles.d/provision.conf
units/emergency.service.in
units/rescue.service.in
tools/list-discoverable-partitions.py
Previously, the recipe was just substituting sysusers.d/basic.conf.in,
which is not enough to be treated as 'fully support'. I deliberately put
a warning message in do_install to warn users about non "/root" ROOT_HOME
value. Don't remove it until all above places are handled.

3. cgroupv2 is now the default.
cgroupv2 is the default for systemd for many years and it's the default
for distros such as ubuntu and fedora. Let's also use it as the default.

Signed-off-by: Chen Qi 
---
  .../distro/include/init-manager-systemd.inc   |  2 +
  meta/recipes-core/systemd/systemd.inc |  4 +-
  ...tall-dependency-links-at-install-tim.patch | 22 +++---
  ...sysctl.d-binfmt.d-modules-load.d-to-.patch | 73 ---
  .../systemd/systemd/basic.conf.in | 40 --
  .../{systemd_254.4.bb => systemd_255.1.bb}| 16 ++--
  6 files changed, 25 insertions(+), 132 deletions(-)
  delete mode 100644 
meta/recipes-core/systemd/systemd/0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
  delete mode 100644 meta/recipes-core/systemd/systemd/basic.conf.in
  rename meta/recipes-core/systemd/{systemd_254.4.bb => systemd_255.1.bb} (98%)

diff --git a/meta/conf/distro/include/init-manager-systemd.inc 
b/meta/conf/distro/include/init-manager-systemd.inc
index 595d1f2644..0a76647459 100644
--- a/meta/conf/distro/include/init-manager-systemd.inc
+++ b/meta/conf/distro/include/init-manager-systemd.inc
@@ -5,3 +5,5 @@ VIRTUAL-RUNTIME_init_manager ??= "systemd"
  VIRTUAL-RUNTIME_initscripts ??= "systemd-compat-units"
  VIRTUAL-RUNTIME_login_manager ??= "shadow-base"
  VIRTUAL-RUNTIME_dev_manager ??= "systemd"
+# systemd hardcodes /root in its source codes, other values are not offically 
supported
+ROOT_HOME ?= "/root"
diff --git a/meta/recipes-core/systemd/systemd.inc 
b/meta/recipes-core/systemd/systemd.inc
index ccc3236457..1417e0150f 100644
--- a/meta/recipes-core/systemd/systemd.inc
+++ b/meta/recipes-core/systemd/systemd.inc
@@ -15,8 +15,8 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
  LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe \
  
file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"
  
-SRCREV = "2e7504449a51fb38db9cd2da391c6434f82def51"

-SRCBRANCH = "v254-stable"
+SRCREV = "2018ccef6645ce00c784369a22dc4e98f6d7061d"
+SRCBRANCH = "v255-stable"
  SRC_URI = 
"git://github.com/systemd/systemd-stable.git;protocol=https;branch=${SRCBRANCH}"
  
  S = "${WORKDIR}/git"

diff --git 
a/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
 
b/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
index 085f1e9052..be231cf6b2 100644
--- 
a/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
+++ 
b/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
@@ -1,8 +1,8 @@
-From ca7d9a8d9c81702af9c599bb79706f12b1a465cf Mon Sep 17 00:00:00 2001
+From 29a58009a172e369ad7166e16dab2f4945c6b0d2 Mon Sep 17 00:00:00 2001
  From: Chen Qi 
  Date: Thu, 21 Feb 2019 16:23:24 +0800
-Subject: [PATCH] binfmt: Don't install dependency links at install time for
- the binfmt services
+Subject: [PATCH 1/2] binfmt: Don't install dependency links at install time
+ for the binfmt serv

Re: [OE-core] [PATCH v3 1/2] shadow: update 4.13 -> 4.14.2

2024-01-18 Thread Chen Qi via lists.openembedded.org
available with Secure Boot)
-> -  /proc/pid/mem (requires ptrace privileges, mediated by YAMA)
-> -  ptrace (requires ptrace privileges, mediated by YAMA)
-> -  causing memory to be swapped to disk, and then inspecting the swap
->
-> These all require a certain amount of privileges.
-
-How to fix it?
-~~
-
-memzero(), which internally calls explicit_bzero(3), or whatever
-alternative the system provides with a slightly different name, will
-make sure that the buffer is zeroed in memory, and optimizations are not
-allowed to impede this zeroing.
-
-This is not really 100% effective, since compilers may place copies of
-the string somewhere hidden in the stack.  Those copies won't get zeroed
-by explicit_bzero(3).  However, that's arguably a compiler bug, since
-compilers should make everything possible to avoid optimizing strings
-that are later passed to explicit_bzero(3).  But we all know that
-sometimes it's impossible to have perfect knowledge in the compiler, so
-this is plausible.  Nevertheless, there's nothing we can do against such
-issues, except minimizing the time such passwords are stored in plain
-text.
-
-Security concerns
-~
-
-We believe this isn't easy to exploit.  Nevertheless, and since the fix
-is trivial, this fix should probably be applied soon, and backported to
-all supported distributions, to prevent someone else having more
-imagination than us to find a way.
-
-Affected versions
-~
-
-All.  Bug introduced in shadow 19990709.  That's the second commit in
-the git history.
-
-Fixes: 45c6603cc86c ("[svn-upgrade] Integrating new upstream version, shadow 
(19990709)")
-
-CVE: CVE-2023-4641
-Upstream-Status: Backport 
[https://github.com/shadow-maint/shadow/commit/65c88a43a23c2391dcc90c0abda3e839e9c57904]
-
-Reported-by: Alejandro Colomar 
-Cc: Serge Hallyn 
-Cc: Iker Pedrosa 
-Cc: Seth Arnold 
-Cc: Christian Brauner 
-Cc: Balint Reczey 
-Cc: Sam James 
-Cc: David Runge 
-Cc: Andreas Jaeger 
-Cc: <~hallyn/sha...@lists.sr.ht>
-Signed-off-by: Alejandro Colomar 
-Signed-off-by: Xiangyu Chen 

- src/gpasswd.c | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/src/gpasswd.c b/src/gpasswd.c
-index 5983f787..2d8869ef 100644
 a/src/gpasswd.c
-+++ b/src/gpasswd.c
-@@ -896,6 +896,7 @@ static void change_passwd (struct group *gr)
-   strzero (cp);
-   cp = getpass (_("Re-enter new password: "));
-   if (NULL == cp) {
-+  memzero (pass, sizeof pass);
-   exit (1);
-   }
-
---
-2.34.1
-
diff --git 
a/meta/recipes-extended/shadow/files/commonio.c-fix-unexpected-open-failure-in-chroot-env.patch
 
b/meta/recipes-extended/shadow/files/commonio.c-fix-unexpected-open-failure-in-chroot-env.patch
index 85d91751056..4a932d2dbb1 100644
--- 
a/meta/recipes-extended/shadow/files/commonio.c-fix-unexpected-open-failure-in-chroot-env.patch
+++ 
b/meta/recipes-extended/shadow/files/commonio.c-fix-unexpected-open-failure-in-chroot-env.patch
@@ -1,4 +1,4 @@
-From 21583da072aa66901d859ac00ce209bac87ddecc Mon Sep 17 00:00:00 2001
+From a773c6b240d27e23d6be41decef0edf24fcee523 Mon Sep 17 00:00:00 2001
  From: Chen Qi 
  Date: Thu, 17 Jul 2014 15:53:34 +0800
  Subject: [PATCH] commonio.c-fix-unexpected-open-failure-in-chroot-env
@@ -15,35 +15,37 @@ Note that this patch doesn't change the logic in the code, 
it just expands
  the codes.
  
  Signed-off-by: Chen Qi 

-
  ---
   lib/commonio.c | 16 
   1 file changed, 12 insertions(+), 4 deletions(-)
  
  diff --git a/lib/commonio.c b/lib/commonio.c

-index 9a02ce1..61384ec 100644
+index 73fdb3a..d1231e9 100644
  --- a/lib/commonio.c
  +++ b/lib/commonio.c
-@@ -616,10 +616,18 @@ int commonio_open (struct commonio_db *db, int mode)
+@@ -606,10 +606,18 @@ int commonio_open (struct commonio_db *db, int mode)
db->cursor = NULL;
db->changed = false;
   
  -	fd = open (db->filename,

  -  (db->readonly ? O_RDONLY : O_RDWR)
-- | O_NOCTTY | O_NONBLOCK | O_NOFOLLOW);
+- | O_NOCTTY | O_NONBLOCK | O_NOFOLLOW | O_CLOEXEC);
  - saved_errno = errno;
  + if (db->readonly) {
  + fd = open (db->filename,
  +(true ? O_RDONLY : O_RDWR)
-+ | O_NOCTTY | O_NONBLOCK | O_NOFOLLOW);
++ | O_NOCTTY | O_NONBLOCK | O_NOFOLLOW | O_CLOEXEC);
  + saved_errno = errno;
  + } else {
  + fd = open (db->filename,
  +(false ? O_RDONLY : O_RDWR)
-+ | O_NOCTTY | O_NONBLOCK | O_NOFOLLOW);
++ | O_NOCTTY | O_NONBLOCK | O_NOFOLLOW| O_CLOEXEC);
  + saved_errno = errno;
  + }
  +
db->fp = NULL;
if (fd >= 0) {
   #ifdef WITH_TCB
+--
+2.30.2
+
diff --git a/meta/recipes-extended/shadow/shadow.inc 
b/meta/recipes-extended/shadow/sh

Re: [OE-core] [PATCH 2/2] openssl: Fix ptest dependencies on perl-module-* being ignored by COMPLEMENTARY_GLOB

2024-01-16 Thread Chen Qi via lists.openembedded.org

Can we change the perl recipe to simply use 'RDEPENDS' for perl-modules?
I don't see what benefit the 'RRECOMMENDS' could give us.

Regards,
Qi


On 1/17/24 02:56, Tim Orling wrote:



On Tue, Jan 16, 2024 at 9:21 AM Alexander Kanavin 
 wrote:


How about simple depending on specific module packages? I don’t
think OpenSSL truly needs all modules.


Agreed. I don’t see a compelling reason to add the 
perl-modules-force-all complication. This will add confusion in my 
opinion.


Iterate the tests and add the required perl-module-* sub-packages one 
by one (or by inspection if the test cases)


In almost all cases, RDEPENDS on perl-modules is a short cut and 
should be avoided in favor of being explicit.



Alex

On Tue 16. Jan 2024 at 17.56, Lyu, William via
lists.openembedded.org


 wrote:

From: William Lyu 

Change the openssl-ptest RDEPENDS from perl-modules to
perl-modules-force-all which RDEPENDS on the same set of packages
perl-module-* recommended by perl-modules. So, when
openssl-ptest is
added via COMPLEMENTARY_GLOB "ptest-pkgs", its dependencies on
these
perl-module-* packages still get added.

Signed-off-by: William Lyu 
---
 meta/recipes-connectivity/openssl/openssl_3.2.0.bb


| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git
a/meta/recipes-connectivity/openssl/openssl_3.2.0.bb


b/meta/recipes-connectivity/openssl/openssl_3.2.0.bb


index d041d2d214..7076bd3a7b 100644
--- a/meta/recipes-connectivity/openssl/openssl_3.2.0.bb


+++ b/meta/recipes-connectivity/openssl/openssl_3.2.0.bb


@@ -247,7 +247,7 @@ CONFFILES:openssl-conf =
"${sysconfdir}/ssl/openssl.cnf"

 RRECOMMENDS:libcrypto += "openssl-conf ${PN}-ossl-module-legacy"
 RDEPENDS:${PN}-misc = "perl"
-RDEPENDS:${PN}-ptest += "openssl-bin perl perl-modules bash sed"
+RDEPENDS:${PN}-ptest += "openssl-bin perl
perl-modules-force-all bash sed"

 RDEPENDS:${PN}-bin += "openssl-conf"

-- 
2.43.0












-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193888): 
https://lists.openembedded.org/g/openembedded-core/message/193888
Mute This Topic: https://lists.openembedded.org/mt/103766390/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] kernel-devsrc: copy source files under tools/

2024-01-11 Thread Chen Qi via lists.openembedded.org

On 1/12/24 11:22, Bruce Ashfield wrote:

On Thu, Jan 11, 2024 at 10:12 PM ChenQi  wrote:

On 1/12/24 10:50, Bruce Ashfield wrote:

On Thu, Jan 11, 2024 at 9:44 PM Chen Qi via lists.openembedded.org
 wrote:

From: Chen Qi 

The source files under tools/ also need to be copied because in
some case, they'll be needed. For example, in case that the
CONFIG_DEBUG_INFO_BTF is enabled, we'll get the following error
without this patch when doing 'make prepare'.

No rule to make target '/.../tools/bpf/resolve_btfids/main.o',
needed by '/.../tools/bpf/resolve_btfids/resolve_btfids-in.o'. Stop.


Tools has been excluded on purpose, as it is relatively large
(and complex) compared to the rest of the curated files.

Figure out just what you need for bpf, and copy only those
files.

Bruce

I can do that. However, I want to raise my concern here first. Does the
30M really matter, compared to the potential errors that would possibly
give users bad impression?

Yes, it actually does matter.

That's the entire design principle behind devsrc. It is carefully curated.

Considering something like this pops up every couple of years, I'm
quite confident that there are very few bad impressions to be made.

As you could see from the file that there are many specific copies from
the tools/ directory structure. That should be the hint that if we wanted
to copy tools in its entirety .. we would have done that long ago.


Before enabling CONFIG_DEBUG_INFO_BTF, things were working pretty well
for us. In fact, I was a little surprised that adding extra configs
would result in failure of 'make prepare'.

Not sure if CONFIG_DEBUG_INFO_BTF is the last one. I guess it's probably
not.

Again, if users are using kernel-devsrc for compiling things, do they
really care about the 30M size?

It's not relevant if they do or don't care. It is the principle of keeping it
as minimal as possible and not doing things "just in case".

There's a bugzilla that I've attached a patch that creates a parallel
full source copy of the kernel, but we've never merged it as keeping
to the low footprint design principle is important.

Bruce


Got it. Thanks for the info.

Regards,

Qi


Regards,

Qi



Signed-off-by: Chen Qi 
---
   meta/recipes-kernel/linux/kernel-devsrc.bb | 1 +
   1 file changed, 1 insertion(+)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb 
b/meta/recipes-kernel/linux/kernel-devsrc.bb
index ce5777fbe9..c2aeb8e216 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -62,6 +62,7 @@ do_install() {
  cd ${S}
  cp --parents $(find  -type f -name "Makefile*" -o -name "Kconfig*") 
$kerneldir/build
  cp --parents $(find  -type f -name "Build" -o -name "Build.include") 
$kerneldir/build
+   cp --parents $(find tools/  -type f -name "*.c" -o -name "*.h") 
$kerneldir/build
   )

   # then drop all but the needed Makefiles/Kconfig files
--
2.34.1









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193568): 
https://lists.openembedded.org/g/openembedded-core/message/193568
Mute This Topic: https://lists.openembedded.org/mt/103676210/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] kernel-devsrc: copy source files under tools/

2024-01-11 Thread Chen Qi via lists.openembedded.org

On 1/12/24 10:50, Bruce Ashfield wrote:

On Thu, Jan 11, 2024 at 9:44 PM Chen Qi via lists.openembedded.org
 wrote:

From: Chen Qi 

The source files under tools/ also need to be copied because in
some case, they'll be needed. For example, in case that the
CONFIG_DEBUG_INFO_BTF is enabled, we'll get the following error
without this patch when doing 'make prepare'.

   No rule to make target '/.../tools/bpf/resolve_btfids/main.o',
   needed by '/.../tools/bpf/resolve_btfids/resolve_btfids-in.o'. Stop.


Tools has been excluded on purpose, as it is relatively large
(and complex) compared to the rest of the curated files.

Figure out just what you need for bpf, and copy only those
files.

Bruce


I can do that. However, I want to raise my concern here first. Does the 
30M really matter, compared to the potential errors that would possibly 
give users bad impression?


Before enabling CONFIG_DEBUG_INFO_BTF, things were working pretty well 
for us. In fact, I was a little surprised that adding extra configs 
would result in failure of 'make prepare'.


Not sure if CONFIG_DEBUG_INFO_BTF is the last one. I guess it's probably 
not.


Again, if users are using kernel-devsrc for compiling things, do they 
really care about the 30M size?


Regards,

Qi



Signed-off-by: Chen Qi 
---
  meta/recipes-kernel/linux/kernel-devsrc.bb | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb 
b/meta/recipes-kernel/linux/kernel-devsrc.bb
index ce5777fbe9..c2aeb8e216 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -62,6 +62,7 @@ do_install() {
 cd ${S}
 cp --parents $(find  -type f -name "Makefile*" -o -name "Kconfig*") 
$kerneldir/build
 cp --parents $(find  -type f -name "Build" -o -name "Build.include") 
$kerneldir/build
+   cp --parents $(find tools/  -type f -name "*.c" -o -name "*.h") 
$kerneldir/build
  )

  # then drop all but the needed Makefiles/Kconfig files
--
2.34.1









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193566): 
https://lists.openembedded.org/g/openembedded-core/message/193566
Mute This Topic: https://lists.openembedded.org/mt/103676210/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] kernel-devsrc: copy source files under tools/

2024-01-11 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The source files under tools/ also need to be copied because in
some case, they'll be needed. For example, in case that the
CONFIG_DEBUG_INFO_BTF is enabled, we'll get the following error
without this patch when doing 'make prepare'.

  No rule to make target '/.../tools/bpf/resolve_btfids/main.o',
  needed by '/.../tools/bpf/resolve_btfids/resolve_btfids-in.o'. Stop.

Signed-off-by: Chen Qi 
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb 
b/meta/recipes-kernel/linux/kernel-devsrc.bb
index ce5777fbe9..c2aeb8e216 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -62,6 +62,7 @@ do_install() {
cd ${S}
cp --parents $(find  -type f -name "Makefile*" -o -name "Kconfig*") 
$kerneldir/build
cp --parents $(find  -type f -name "Build" -o -name "Build.include") 
$kerneldir/build
+   cp --parents $(find tools/  -type f -name "*.c" -o -name "*.h") 
$kerneldir/build
 )
 
 # then drop all but the needed Makefiles/Kconfig files
-- 
2.34.1


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

2024-01-09 Thread Chen Qi via lists.openembedded.org
I just sent out a patch for the yocto-autobuilder-helper repo to use '/root' as 
the ROOT_HOME's value in case of 'sysvinit with systemd'.

Regards,
Qi

-Original Message-
From: Alexandre Belloni  
Sent: Tuesday, January 9, 2024 3:47 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

I got this today:

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8420/steps/25/logs/stdio

WARNING: systemd-1_255.1-r0 do_install: Using /home/root as root user's home 
directory is not fully supported by systemd

On 07/01/2024 14:05:35+, Chen Qi via lists.openembedded.org wrote:
> Another patch in this series fixes the warning:
> rootfs-postcommands.bbclass: ignore comment mismatch in 
> systemd_user_check
> 
> Is that patch also staged?
> 
> Regards,
> Qi
> 
> -Original Message-
> From: Alexandre Belloni 
> Sent: Saturday, January 6, 2024 12:02 AM
> To: Chen, Qi 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1
> 
> Hello,
> 
> This fails with:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/736
> 1/steps/12/logs/warnings
> 
> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: User root has been 
> defined as (root, 0, 0, root, /root, /bin/sh) but sysusers.d expects 
> it as (root, 0, 0, Super User, /root, -)
> WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: User nobody has 
> been defined as (nobody, 65534, 65534, nobody, /nonexistent, 
> /usr/sbin/nologin) but sysusers.d expects it as (nobody, 65534, 65534, 
> Kernel Overflow User, -, -)
> WARNING: core-image-sato-1.0-r0 do_rootfs: User root has been defined 
> as (root, 0, 0, root, /root, /bin/sh) but sysusers.d expects it as 
> (root, 0, 0, Super User, /root, -)
> WARNING: core-image-sato-1.0-r0 do_rootfs: User nobody has been 
> defined as (nobody, 65534, 65534, nobody, /nonexistent, 
> /usr/sbin/nologin) but sysusers.d expects it as (nobody, 65534, 65534, 
> Kernel Overflow User, -, -)
> WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: User root has been 
> defined as (root, 0, 0, root, /root, /bin/sh) but sysusers.d expects 
> it as (root, 0, 0, Super User, /root, -)
> WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: User nobody has been 
> defined as (nobody, 65534, 65534, nobody, /nonexistent, 
> /usr/sbin/nologin) but sysusers.d expects it as (nobody, 65534, 65534, 
> Kernel Overflow User, -, -)
> 
> On 27/12/2023 12:20:34+0800, Chen Qi via lists.openembedded.org wrote:
> > From: Chen Qi 
> > 
> > 1. Patch changes:
> > 
> > 0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
> > is removed because it has no real effect now. The /lib is now 
> > /usr/lib because 'usrmerge' is a required distro feature for systemd.
> > 
> > 0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is 
> > refreshed for the new version to avoid patch-fuzz issue.
> > 
> > 2. root user's home directory now defaults to "/root":
> > 
> > The sysuers.d/basic.conf is still modified to respect the ROOT_HOME 
> > value, so if users set ROOT_HOME to "/home/root", the behavior is 
> > the same as before. However, this is only for backward 
> > compatibility. With this patch, The ROOT_HOME value is set to "/root" in 
> > init-manager-systemd.inc.
> > This is because systemd's source codes are hardcoding "/root", and 
> > other values are not officially supported. See the list below.
> > $ grep -rl '"/root"' src/ | grep -v 'src/test'
> > src/core/namespace.c
> > src/basic/user-util.c
> > src/nss-systemd/nss-systemd.c
> > src/nspawn/nspawn.c
> > src/firstboot/firstboot.c
> > src/shared/userdb.c
> > src/shared/user-record.c
> > $ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ 
> > tmpfiles.d/ units/ xorg/ tools/ sysusers.d/basic.conf.in 
> > tmpfiles.d/provision.conf units/emergency.service.in 
> > units/rescue.service.in tools/list-discoverable-partitions.py
> > Previously, the recipe was just substituting 
> > sysusers.d/basic.conf.in, which is not enough to be treated as 
> > 'fully support'. I deliberately put a warning message in do_install to warn 
> > users about non "/root"
> > ROOT_HOME value. Don't remove it until all above places are handled.
> > 
> > 3. cgroupv2 is now the default.
> > cgroupv2 is the default for systemd for many years and it's the 
> > default for distros such as ubuntu and fedora. Let's also use it as the 
> > default.
> > 
> > Signed-off-by: Chen Qi 
> > ---
> >  .../dis

Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

2024-01-07 Thread Chen Qi via lists.openembedded.org
Another patch in this series fixes the warning:
rootfs-postcommands.bbclass: ignore comment mismatch in systemd_user_check

Is that patch also staged?

Regards,
Qi

-Original Message-
From: Alexandre Belloni  
Sent: Saturday, January 6, 2024 12:02 AM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

Hello,

This fails with:

https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/7361/steps/12/logs/warnings

WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: User root has been defined 
as (root, 0, 0, root, /root, /bin/sh) but sysusers.d expects it as (root, 0, 0, 
Super User, /root, -)
WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: User nobody has been defined 
as (nobody, 65534, 65534, nobody, /nonexistent, /usr/sbin/nologin) but 
sysusers.d expects it as (nobody, 65534, 65534, Kernel Overflow User, -, -)
WARNING: core-image-sato-1.0-r0 do_rootfs: User root has been defined as (root, 
0, 0, root, /root, /bin/sh) but sysusers.d expects it as (root, 0, 0, Super 
User, /root, -)
WARNING: core-image-sato-1.0-r0 do_rootfs: User nobody has been defined as 
(nobody, 65534, 65534, nobody, /nonexistent, /usr/sbin/nologin) but sysusers.d 
expects it as (nobody, 65534, 65534, Kernel Overflow User, -, -)
WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: User root has been defined as 
(root, 0, 0, root, /root, /bin/sh) but sysusers.d expects it as (root, 0, 0, 
Super User, /root, -)
WARNING: core-image-sato-sdk-1.0-r0 do_rootfs: User nobody has been defined as 
(nobody, 65534, 65534, nobody, /nonexistent, /usr/sbin/nologin) but sysusers.d 
expects it as (nobody, 65534, 65534, Kernel Overflow User, -, -)

On 27/12/2023 12:20:34+0800, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi 
> 
> 1. Patch changes:
> 
> 0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
> is removed because it has no real effect now. The /lib is now /usr/lib 
> because 'usrmerge' is a required distro feature for systemd.
> 
> 0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is 
> refreshed for the new version to avoid patch-fuzz issue.
> 
> 2. root user's home directory now defaults to "/root":
> 
> The sysuers.d/basic.conf is still modified to respect the ROOT_HOME 
> value, so if users set ROOT_HOME to "/home/root", the behavior is the 
> same as before. However, this is only for backward compatibility. With 
> this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
> This is because systemd's source codes are hardcoding "/root", and 
> other values are not officially supported. See the list below.
> $ grep -rl '"/root"' src/ | grep -v 'src/test'
> src/core/namespace.c
> src/basic/user-util.c
> src/nss-systemd/nss-systemd.c
> src/nspawn/nspawn.c
> src/firstboot/firstboot.c
> src/shared/userdb.c
> src/shared/user-record.c
> $ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ 
> tmpfiles.d/ units/ xorg/ tools/ sysusers.d/basic.conf.in 
> tmpfiles.d/provision.conf units/emergency.service.in 
> units/rescue.service.in tools/list-discoverable-partitions.py
> Previously, the recipe was just substituting sysusers.d/basic.conf.in, 
> which is not enough to be treated as 'fully support'. I deliberately 
> put a warning message in do_install to warn users about non "/root" 
> ROOT_HOME value. Don't remove it until all above places are handled.
> 
> 3. cgroupv2 is now the default.
> cgroupv2 is the default for systemd for many years and it's the 
> default for distros such as ubuntu and fedora. Let's also use it as the 
> default.
> 
> Signed-off-by: Chen Qi 
> ---
>  .../distro/include/init-manager-systemd.inc   |  2 +
>  meta/recipes-core/systemd/systemd.inc |  4 +-
>  ...tall-dependency-links-at-install-tim.patch | 22 +++---  
> ...sysctl.d-binfmt.d-modules-load.d-to-.patch | 73 ---
>  .../systemd/systemd/basic.conf.in | 40 --
>  .../{systemd_254.4.bb => systemd_255.1.bb}| 16 ++--
>  6 files changed, 25 insertions(+), 132 deletions(-)  delete mode 
> 100644 
> meta/recipes-core/systemd/systemd/0004-Move-sysusers.d-sysctl.d-binfmt
> .d-modules-load.d-to-.patch  delete mode 100644 
> meta/recipes-core/systemd/systemd/basic.conf.in
>  rename meta/recipes-core/systemd/{systemd_254.4.bb => 
> systemd_255.1.bb} (98%)
> 
> diff --git a/meta/conf/distro/include/init-manager-systemd.inc 
> b/meta/conf/distro/include/init-manager-systemd.inc
> index 595d1f2644..0a76647459 100644
> --- a/meta/conf/distro/include/init-manager-systemd.inc
> +++ b/meta/conf/distro/include/init-manager-systemd.inc
> @@ -5,3 +5,5 @@ VIRTUAL-RUNTIME_init_manager ??= "systemd"
>  VIRTUAL-RUNTIME_initscripts ??=

Re: [OE-core][PATCH] debugedit: add UPSTREAM_CHECK settings

2024-01-03 Thread Chen Qi via lists.openembedded.org

On 1/3/24 16:28, Alexander Kanavin wrote:

On Wed, 3 Jan 2024 at 08:45, Chen Qi via lists.openembedded.org
 wrote:

On 1/3/24 15:21, Alexander Kanavin via lists.openembedded.org wrote:

This works as expected. What made you think it’s broken and needs changing?

The 404 ERROR that 'devtool check-ugprade-status' prints out to me 
unconditionally, which is all upper case to catch people's notice and can't be 
avoided by any option.

The version check detects if the tarball is in a versioned directory,
and if so, it goes one level up, and tries to list all subdirectories
from there, attempting to find a newer tarball. So the real issue is,
why is it trying to go into a non-existent 'sha512' directory? There's
a sha512.sum file in here:
https://sourceware.org/ftp/debugedit/
but it's a file.

If this patch is applied, on the other hand, it would only check the
names of those versioned directories, and not the actual tarballs.
Which could produce bogus results if for example 5.0/ directory would
contain 5.0.0, 5.0.1, etc tarballs.

Sounds reasonable.


It would also help to suppress the noisy output from wget altogether
by default, but last time I looked into it, it turned into invasive
changes at the heart of bitbake logging, so I abandoned the attempt.

Alex


Thanks for the info.

Regards,

Qi


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193278): 
https://lists.openembedded.org/g/openembedded-core/message/193278
Mute This Topic: https://lists.openembedded.org/mt/103478272/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] debugedit: add UPSTREAM_CHECK settings

2024-01-02 Thread Chen Qi via lists.openembedded.org

On 1/3/24 15:21, Alexander Kanavin via lists.openembedded.org wrote:
This works as expected. What made you think it’s broken and needs 
changing?


The 404 ERROR that 'devtool check-ugprade-status' prints out to me 
unconditionally, which is all upper case to catch people's notice and 
can't be avoided by any option.




Alex

On Wed 3. Jan 2024 at 3.47, ChenQi  wrote:

On 1/3/24 00:54, Alexander Kanavin wrote:
> The check already works, at least for me it correctly checks
both the
> top level directory and the 'latest' directory:
> ...
> --2024-01-02 16:51:30-- https://sourceware.org/ftp/debugedit/
> ...
> --2024-01-02 16:51:30-- https://sourceware.org/ftp/debugedit/5.0/
> ...
> INFO: debugedit                 5.0             MATCH          Chen
> Qi 
>
> What does devtool output for you, without the patch?
>
> Alex

The command and output are as below. Pure poky master. No local
patches.

$ devtool check-upgrade-status debugedit
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)... (18:44:43.533538)
Loading cache: 100%

|###|

Time: 0:00:00
Loaded 1848 entries from dependency cache.
--2024-01-02 18:44:46-- https://sourceware.org/ftp/debugedit/
Resolving sourceware.org <http://sourceware.org> (sourceware.org
<http://sourceware.org>)... 8.43.85.97,
2620:52:3:1:0:246e:9693:128c
Connecting to sourceware.org <http://sourceware.org>
(sourceware.org <http://sourceware.org>)|8.43.85.97|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2602 (2.5K) [text/html]
Saving to: ‘/tmp/wget-index-e1dsj90e/wget-listing-vrofeac4’


2024-01-02 18:44:46 (330 MB/s) -
‘/tmp/wget-index-e1dsj90e/wget-listing-vrofeac4’ saved [2602/2602]

--2024-01-02 18:44:46-- https://sourceware.org/ftp/debugedit/5.0/
Resolving sourceware.org <http://sourceware.org> (sourceware.org
<http://sourceware.org>)... 8.43.85.97,
2620:52:3:1:0:246e:9693:128c
Connecting to sourceware.org <http://sourceware.org>
(sourceware.org <http://sourceware.org>)|8.43.85.97|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1353 (1.3K) [text/html]
Saving to: ‘/tmp/wget-index-qwu98rgj/wget-listing-8esd1gn0’


2024-01-02 18:44:47 (179 MB/s) -
‘/tmp/wget-index-qwu98rgj/wget-listing-8esd1gn0’ saved [1353/1353]

--2024-01-02 18:44:47-- https://sourceware.org/ftp/debugedit/sha512/
Resolving sourceware.org <http://sourceware.org> (sourceware.org
<http://sourceware.org>)... 8.43.85.97,
2620:52:3:1:0:246e:9693:128c
Connecting to sourceware.org <http://sourceware.org>
(sourceware.org <http://sourceware.org>)|8.43.85.97|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-01-02 18:44:47 ERROR 404: Not Found.


>
> On Tue, 2 Jan 2024 at 09:38, Chen Qi via lists.openembedded.org
<http://lists.openembedded.org>
>  wrote:
>> From: Chen Qi 
>>
>> Add UPSTREAM_CHECK_URI(REGEX) to allow for checking new releases
>> for debugedit recipe.
>>
>> Signed-off-by: Chen Qi 
>> ---
>>   meta/recipes-devtools/debugedit/debugedit_5.0.bb
<http://debugedit_5.0.bb> | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/meta/recipes-devtools/debugedit/debugedit_5.0.bb
<http://debugedit_5.0.bb>
b/meta/recipes-devtools/debugedit/debugedit_5.0.bb
<http://debugedit_5.0.bb>
>> index 63ad7babd9..3a596f5fea 100644
>> --- a/meta/recipes-devtools/debugedit/debugedit_5.0.bb
<http://debugedit_5.0.bb>
>> +++ b/meta/recipes-devtools/debugedit/debugedit_5.0.bb
<http://debugedit_5.0.bb>
>> @@ -9,6 +9,9 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
>> file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 \
>> file://COPYING3;md5=d32239bcb673463ab874e80d47fae504"
>>
>> +UPSTREAM_CHECK_URI = "https://sourceware.org/ftp/debugedit/;
>> +UPSTREAM_CHECK_REGEX = "(?P(\d\.\d))/"
>> +
>>   SRC_URI =
"https://sourceware.org/ftp/debugedit/${PV}/debugedit-${PV}.tar.xz
<https://sourceware.org/ftp/debugedit/$%7BPV%7D/debugedit-$%7BPV%7D.tar.xz>"
>>
>>   SRC_URI:append:libc-musl = "\
>> --
>> 2.34.1
>>
>>
>>
>>





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193273): 
https://lists.openembedded.org/g/openembedded-core/message/193273
Mute This Topic: https://lists.openembedded.org/mt/103478272/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] sudo: upgrade from 1.9.15p2 to 1.9.15p5

2024-01-02 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Signed-off-by: Chen Qi 
---
 .../sudo/{sudo_1.9.15p2.bb => sudo_1.9.15p5.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/sudo/{sudo_1.9.15p2.bb => sudo_1.9.15p5.bb} (96%)

diff --git a/meta/recipes-extended/sudo/sudo_1.9.15p2.bb 
b/meta/recipes-extended/sudo/sudo_1.9.15p5.bb
similarity index 96%
rename from meta/recipes-extended/sudo/sudo_1.9.15p2.bb
rename to meta/recipes-extended/sudo/sudo_1.9.15p5.bb
index 431dfba3c2..8e542015ad 100644
--- a/meta/recipes-extended/sudo/sudo_1.9.15p2.bb
+++ b/meta/recipes-extended/sudo/sudo_1.9.15p5.bb
@@ -7,7 +7,7 @@ SRC_URI = "https://www.sudo.ws/dist/sudo-${PV}.tar.gz \
 
 PAM_SRC_URI = "file://sudo.pam"
 
-SRC_URI[sha256sum] = 
"199c0cdbfa7efcfffa9c88684a8e2fb206a62b70a316507e4a91c89c873bbcc8"
+SRC_URI[sha256sum] = 
"558d10b9a1991fb3b9fa7fa7b07ec4405b7aefb5b3cb0b0871dbc81e3a88e558"
 
 DEPENDS += " virtual/crypt ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 
'libpam', '', d)}"
 RDEPENDS:${PN} += " ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 
'pam-plugin-limits pam-plugin-keyinit', '', d)}"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193271): 
https://lists.openembedded.org/g/openembedded-core/message/193271
Mute This Topic: https://lists.openembedded.org/mt/103497078/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] util-linux/util-linux-libuuid: ugprade from 2.39.2 to 2.39.3

2024-01-02 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

License-Update:
===
GPL-1.0-or-later is added. fdisk.c is licensed under it.

0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch is dropped as
it's been in the new version.

Signed-off-by: Chen Qi 
---
 ...2.39.2.bb => util-linux-libuuid_2.39.3.bb} |  0
 meta/recipes-core/util-linux/util-linux.inc   |  8 ++--
 ...ls-include-libgen.h-for-basename-API.patch |  9 +++--
 ...Use-4K-buffer-size-instead-of-BUFSIZ.patch | 38 ---
 .../util-linux/avoid_parallel_tests.patch |  4 +-
 .../util-linux/configure-sbindir.patch| 19 +++---
 .../display_testname_for_subtest.patch| 12 +++---
 .../util-linux/util-linux/ptest.patch |  4 +-
 ...l-linux_2.39.2.bb => util-linux_2.39.3.bb} |  0
 9 files changed, 34 insertions(+), 60 deletions(-)
 rename meta/recipes-core/util-linux/{util-linux-libuuid_2.39.2.bb => 
util-linux-libuuid_2.39.3.bb} (100%)
 delete mode 100644 
meta/recipes-core/util-linux/util-linux/0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch
 rename meta/recipes-core/util-linux/{util-linux_2.39.2.bb => 
util-linux_2.39.3.bb} (100%)

diff --git a/meta/recipes-core/util-linux/util-linux-libuuid_2.39.2.bb 
b/meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
similarity index 100%
rename from meta/recipes-core/util-linux/util-linux-libuuid_2.39.2.bb
rename to meta/recipes-core/util-linux/util-linux-libuuid_2.39.3.bb
diff --git a/meta/recipes-core/util-linux/util-linux.inc 
b/meta/recipes-core/util-linux/util-linux.inc
index e3bef5acfc..4e9d22f269 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -6,13 +6,14 @@ disk partitioning, kernel message management, filesystem 
creation, and system lo
 
 SECTION = "base"
 
-LICENSE = "GPL-2.0-or-later & LGPL-2.1-or-later & BSD-2-Clause & BSD-3-Clause 
& BSD-4-Clause"
+LICENSE = "GPL-1.0-or-later & GPL-2.0-or-later & LGPL-2.1-or-later & 
BSD-2-Clause & BSD-3-Clause & BSD-4-Clause"
+LICENSE:${PN}-fdisk = "GPL-1.0-or-later"
 LICENSE:${PN}-libblkid = "LGPL-2.1-or-later"
 LICENSE:${PN}-libfdisk = "LGPL-2.1-or-later"
 LICENSE:${PN}-libmount = "LGPL-2.1-or-later"
 LICENSE:${PN}-libsmartcols = "LGPL-2.1-or-later"
 
-LIC_FILES_CHKSUM = 
"file://README.licensing;md5=12ae7768a65ec8f2e44d930df9cb43fa \
+LIC_FILES_CHKSUM = 
"file://README.licensing;md5=6b0e0a2320e66e62eef9b8149a6faec4 \
 file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
 
file://Documentation/licenses/COPYING.GPL-2.0-or-later;md5=b234ee4d69f5fce4486a80fdaf4a4263
 \
 
file://Documentation/licenses/COPYING.LGPL-2.1-or-later;md5=4fbd65380cdd255951079008b364516c
 \
@@ -35,8 +36,7 @@ SRC_URI = 
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
file://run-ptest \
file://display_testname_for_subtest.patch \
file://avoid_parallel_tests.patch \
-   file://0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch \
file://0001-login-utils-include-libgen.h-for-basename-API.patch \
"
 
-SRC_URI[sha256sum] = 
"87abdfaa8e490f8be6dde976f7c80b9b5ff9f301e1b67e3899e1f05a59a1531f"
+SRC_URI[sha256sum] = 
"7b6605e48d1a49f43cc4b4cfc59f313d0dd5402fa40b96810bd572e167dfed0f"
diff --git 
a/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
 
b/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
index 2b9897ade1..6258710e1e 100644
--- 
a/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
+++ 
b/meta/recipes-core/util-linux/util-linux/0001-login-utils-include-libgen.h-for-basename-API.patch
@@ -1,4 +1,4 @@
-From 6581cf8ac95b99b5a35fea88c52646558d05b5e7 Mon Sep 17 00:00:00 2001
+From d44e3ad1f6f8b5c1b3098bb7d537943a4c21d22f Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Sun, 3 Dec 2023 19:59:46 -0800
 Subject: [PATCH] login-utils: include libgen.h for basename API
@@ -17,10 +17,13 @@ Fixes
 
 Upstream-Status: Submitted [https://github.com/util-linux/util-linux/pull/2615]
 Signed-off-by: Khem Raj 
+
 ---
- login-utils/su-common.c | 8 ++--
- 1 file changed, 6 insertions(+), 2 deletions(-)
+ login-utils/su-common.c | 10 +++---
+ 1 file changed, 7 insertions(+), 3 deletions(-)
 
+diff --git a/login-utils/su-common.c b/login-utils/su-common.c
+index b674920..3297c78 100644
 --- a/login-utils/su-common.c
 +++ b/login-utils/su-common.c
 @@ -26,6 +26,7 @@
diff --git 
a/meta/recipes-core/util-linux/util-linux/0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch
 
b/meta/recipes-core/util-linux/util-linux/0001-lscpu-Use-4K-buffer-size-instead-of-BUFSIZ.patch
deleted file mode 100644
index 4d7487c4f7..00
--- 
a/meta/recipes-core/util-linux/util-linux/

[OE-core][PATCH 2/3] dbus-wait: bump srcrev

2024-01-02 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

This upgrade only includes one new commit:
64bc7c8 SECURITY.md: Add file

Signed-off-by: Chen Qi 
---
 meta/recipes-core/dbus-wait/dbus-wait_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/dbus-wait/dbus-wait_git.bb 
b/meta/recipes-core/dbus-wait/dbus-wait_git.bb
index 1cdf07d03d..39363b9b3a 100644
--- a/meta/recipes-core/dbus-wait/dbus-wait_git.bb
+++ b/meta/recipes-core/dbus-wait/dbus-wait_git.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 DEPENDS = "dbus"
 
-SRCREV = "6cc6077a36fe2648a5f993fe7c16c9632f946517"
+SRCREV = "64bc7c8fae61ded0c4e555aa775911f84c56e438"
 PV = "0.1+git"
 
 SRC_URI = "git://git.yoctoproject.org/${BPN};branch=master;protocol=https"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193269): 
https://lists.openembedded.org/g/openembedded-core/message/193269
Mute This Topic: https://lists.openembedded.org/mt/103497076/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] debugedit: add UPSTREAM_CHECK settings

2024-01-02 Thread Chen Qi via lists.openembedded.org

On 1/3/24 00:54, Alexander Kanavin wrote:

The check already works, at least for me it correctly checks both the
top level directory and the 'latest' directory:
...
--2024-01-02 16:51:30--  https://sourceware.org/ftp/debugedit/
...
--2024-01-02 16:51:30--  https://sourceware.org/ftp/debugedit/5.0/
...
INFO: debugedit 5.0 MATCH   Chen
Qi 

What does devtool output for you, without the patch?

Alex


The command and output are as below. Pure poky master. No local patches.

$ devtool check-upgrade-status debugedit
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)... (18:44:43.533538)
Loading cache: 100% 
|###| 
Time: 0:00:00

Loaded 1848 entries from dependency cache.
--2024-01-02 18:44:46--  https://sourceware.org/ftp/debugedit/
Resolving sourceware.org (sourceware.org)... 8.43.85.97, 
2620:52:3:1:0:246e:9693:128c

Connecting to sourceware.org (sourceware.org)|8.43.85.97|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2602 (2.5K) [text/html]
Saving to: ‘/tmp/wget-index-e1dsj90e/wget-listing-vrofeac4’


2024-01-02 18:44:46 (330 MB/s) - 
‘/tmp/wget-index-e1dsj90e/wget-listing-vrofeac4’ saved [2602/2602]


--2024-01-02 18:44:46--  https://sourceware.org/ftp/debugedit/5.0/
Resolving sourceware.org (sourceware.org)... 8.43.85.97, 
2620:52:3:1:0:246e:9693:128c

Connecting to sourceware.org (sourceware.org)|8.43.85.97|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1353 (1.3K) [text/html]
Saving to: ‘/tmp/wget-index-qwu98rgj/wget-listing-8esd1gn0’


2024-01-02 18:44:47 (179 MB/s) - 
‘/tmp/wget-index-qwu98rgj/wget-listing-8esd1gn0’ saved [1353/1353]


--2024-01-02 18:44:47-- https://sourceware.org/ftp/debugedit/sha512/
Resolving sourceware.org (sourceware.org)... 8.43.85.97, 
2620:52:3:1:0:246e:9693:128c

Connecting to sourceware.org (sourceware.org)|8.43.85.97|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-01-02 18:44:47 ERROR 404: Not Found.




On Tue, 2 Jan 2024 at 09:38, Chen Qi via lists.openembedded.org
 wrote:

From: Chen Qi 

Add UPSTREAM_CHECK_URI(REGEX) to allow for checking new releases
for debugedit recipe.

Signed-off-by: Chen Qi 
---
  meta/recipes-devtools/debugedit/debugedit_5.0.bb | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/debugedit/debugedit_5.0.bb 
b/meta/recipes-devtools/debugedit/debugedit_5.0.bb
index 63ad7babd9..3a596f5fea 100644
--- a/meta/recipes-devtools/debugedit/debugedit_5.0.bb
+++ b/meta/recipes-devtools/debugedit/debugedit_5.0.bb
@@ -9,6 +9,9 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
  file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 \
  file://COPYING3;md5=d32239bcb673463ab874e80d47fae504"

+UPSTREAM_CHECK_URI = "https://sourceware.org/ftp/debugedit/;
+UPSTREAM_CHECK_REGEX = "(?P(\d\.\d))/"
+
  SRC_URI = "https://sourceware.org/ftp/debugedit/${PV}/debugedit-${PV}.tar.xz;

  SRC_URI:append:libc-musl = "\
--
2.34.1







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193263): 
https://lists.openembedded.org/g/openembedded-core/message/193263
Mute This Topic: https://lists.openembedded.org/mt/103478272/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] devtool: use straight print in check-upgrade-status output

2024-01-02 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

'devtool check-upgrade-status' is for reporting upgradable
status for recipes. The output should always be printed out. So
we should just use 'print' instead of 'logger.info' as the latter
will be suppressed if '-q' parameter is supplied to devtool.

Signed-off-by: Chen Qi 
---
 scripts/lib/devtool/upgrade.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/devtool/upgrade.py b/scripts/lib/devtool/upgrade.py
index a98370bc10..ef58523dc8 100644
--- a/scripts/lib/devtool/upgrade.py
+++ b/scripts/lib/devtool/upgrade.py
@@ -631,7 +631,7 @@ def check_upgrade_status(args, config, basepath, workspace):
 for result in results:
 # pn, update_status, current, latest, maintainer, latest_commit, 
no_update_reason
 if args.all or result[1] != 'MATCH':
-logger.info("{:25} {:15} {:15} {} {} {}".format(   result[0],
+print("{:25} {:15} {:15} {} {} {}".format(   result[0],
result[2],
result[1] if 
result[1] != 'UPDATE' else (result[3] if not 
result[3].endswith("new-commits-available") else "new commits"),
result[4],
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193221): 
https://lists.openembedded.org/g/openembedded-core/message/193221
Mute This Topic: https://lists.openembedded.org/mt/103478277/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] debugedit: add UPSTREAM_CHECK settings

2024-01-02 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Add UPSTREAM_CHECK_URI(REGEX) to allow for checking new releases
for debugedit recipe.

Signed-off-by: Chen Qi 
---
 meta/recipes-devtools/debugedit/debugedit_5.0.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/debugedit/debugedit_5.0.bb 
b/meta/recipes-devtools/debugedit/debugedit_5.0.bb
index 63ad7babd9..3a596f5fea 100644
--- a/meta/recipes-devtools/debugedit/debugedit_5.0.bb
+++ b/meta/recipes-devtools/debugedit/debugedit_5.0.bb
@@ -9,6 +9,9 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
 file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 \
 file://COPYING3;md5=d32239bcb673463ab874e80d47fae504"
 
+UPSTREAM_CHECK_URI = "https://sourceware.org/ftp/debugedit/;
+UPSTREAM_CHECK_REGEX = "(?P(\d\.\d))/"
+
 SRC_URI = "https://sourceware.org/ftp/debugedit/${PV}/debugedit-${PV}.tar.xz;
 
 SRC_URI:append:libc-musl = "\
-- 
2.34.1


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

2024-01-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/gawk/{gawk_5.2.2.bb => gawk_5.3.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/gawk/{gawk_5.2.2.bb => gawk_5.3.0.bb} (97%)

diff --git a/meta/recipes-extended/gawk/gawk_5.2.2.bb 
b/meta/recipes-extended/gawk/gawk_5.3.0.bb
similarity index 97%
rename from meta/recipes-extended/gawk/gawk_5.2.2.bb
rename to meta/recipes-extended/gawk/gawk_5.3.0.bb
index 3c18b6911a..3d652da6e5 100644
--- a/meta/recipes-extended/gawk/gawk_5.2.2.bb
+++ b/meta/recipes-extended/gawk/gawk_5.3.0.bb
@@ -19,7 +19,7 @@ SRC_URI = "${GNU_MIRROR}/gawk/gawk-${PV}.tar.gz \
file://run-ptest \
"
 
-SRC_URI[sha256sum] = 
"945aef7ccff101f20b22a10802bc005e994ab2b8ea3e724cc1a197c62f41f650"
+SRC_URI[sha256sum] = 
"378f8864ec21cfceaa048f7e1869ac9b4597b449087caf1eb55e440d30273336"
 
 inherit autotools gettext texinfo update-alternatives
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193205): 
https://lists.openembedded.org/g/openembedded-core/message/193205
Mute This Topic: https://lists.openembedded.org/mt/103477344/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] systemd-bootchart: upgrade from 234 to 235

2024-01-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

0001-architecture-Recognise-RISCV-32-RISCV-64.patch is dropped because
it has some problem. It's a patch from systemd repo, yet it's marked
as 'Backport' for systemd-bootchart. systemd and systemd-bootchart are
two different projects. Now in 235, RISCV64 has been officially supported,
but RISCV32 is not. So drop this patch. People who want RISCV32 support
need to work with systemd-bootchart upstream first.

Signed-off-by: Chen Qi 
---
 ...itecture-Recognise-RISCV-32-RISCV-64.patch | 45 ---
 ...tchart_234.bb => systemd-bootchart_235.bb} |  5 +--
 2 files changed, 2 insertions(+), 48 deletions(-)
 delete mode 100644 
meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-architecture-Recognise-RISCV-32-RISCV-64.patch
 rename meta/recipes-devtools/systemd-bootchart/{systemd-bootchart_234.bb => 
systemd-bootchart_235.bb} (90%)

diff --git 
a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-architecture-Recognise-RISCV-32-RISCV-64.patch
 
b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-architecture-Recognise-RISCV-32-RISCV-64.patch
deleted file mode 100644
index fc03812bb9..00
--- 
a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-architecture-Recognise-RISCV-32-RISCV-64.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From 4a6ace0a965965ea15e88c3418c7158ca5cc9f8f Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Thu, 21 Nov 2019 10:12:05 -0800
-Subject: [PATCH] architecture: Recognise RISCV-32/RISCV-64
-
-Upstream-Status: Backport 
[https://github.com/systemd/systemd/commit/171b53380085b1288b03b19a2b978f36a5c003d0]
-Signed-off-by: Khem Raj 

- src/architecture.h | 13 +
- 1 file changed, 13 insertions(+)
-
-diff --git a/src/architecture.h b/src/architecture.h
-index 26679e2..89c7d32 100644
 a/src/architecture.h
-+++ b/src/architecture.h
-@@ -57,6 +57,8 @@ enum {
- ARCHITECTURE_M68K,
- ARCHITECTURE_TILEGX,
- ARCHITECTURE_CRIS,
-+   ARCHITECTURE_RISCV32,
-+   ARCHITECTURE_RISCV64,
- _ARCHITECTURE_MAX,
- _ARCHITECTURE_INVALID = -1
- };
-@@ -194,6 +196,17 @@ int uname_architecture(void);
- #elif defined(__cris__)
- #  define native_architecture() ARCHITECTURE_CRIS
- #  error "Missing LIB_ARCH_TUPLE for CRIS"
-+#elif defined(__riscv)
-+#  if __SIZEOF_POINTER__ == 4
-+#define native_architecture() ARCHITECTURE_RISCV32
-+#define LIB_ARCH_TUPLE "riscv32-linux-gnu"
-+#  elif __SIZEOF_POINTER__ == 8
-+#define native_architecture() ARCHITECTURE_RISCV64
-+#define LIB_ARCH_TUPLE "riscv64-linux-gnu"
-+#  else
-+#error "Unrecognized riscv architecture variant"
-+#  endif
-+#  define PROC_CPUINFO_MODEL "cpu model"
- #else
- #  error "Please register your architecture here!"
- #endif
--- 
-2.24.0
-
diff --git a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_234.bb 
b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_235.bb
similarity index 90%
rename from meta/recipes-devtools/systemd-bootchart/systemd-bootchart_234.bb
rename to meta/recipes-devtools/systemd-bootchart/systemd-bootchart_235.bb
index bc3eee2093..25544029d5 100644
--- a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_234.bb
+++ b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_235.bb
@@ -8,8 +8,7 @@ LICENSE = "LGPL-2.1-only & GPL-2.0-only"
 LIC_FILES_CHKSUM = 
"file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c \
 file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe"
 
-SRC_URI = 
"git://github.com/systemd/systemd-bootchart.git;protocol=https;branch=master \
-   file://0001-architecture-Recognise-RISCV-32-RISCV-64.patch \
+SRC_URI = 
"git://github.com/systemd/systemd-bootchart.git;protocol=https;branch=main \
file://mips64.patch \
file://no_lto.patch \
 "
@@ -21,7 +20,7 @@ SRC_URI:append:libc-musl = " \
 "
 
 
-SRCREV = "8183cfd9dad8beca5434d625cf6b2df87775e956"
+SRCREV = "8ab9680a1bd5eb8fe7a7dcc44897af7ee41e56e7"
 
 S = "${WORKDIR}/git"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193206): 
https://lists.openembedded.org/g/openembedded-core/message/193206
Mute This Topic: https://lists.openembedded.org/mt/103477345/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] systemd: refresh musl patches for v255.1

2024-01-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The current patches are refreshed. A new patch is added:
0022-avoid-missing-LOCK_EX-declaration.patch

Signed-off-by: Chen Qi 
---
 ...-missing_type.h-add-comparison_fn_t.patch} |  10 +-
 ...-parse_printf_format-implementation.patch} |  27 +-
 ...issing.h-check-for-missing-strndupa.patch} | 157 ++-
 ...B_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch} |  19 +-
 ...05-add-missing-FTW_-macros-for-musl.patch} |  10 +-
 ...6-Use-uintmax_t-for-handling-rlim_t.patch} |  23 +-
 ..._SYMLINK_NOFOLLOW-flag-to-faccessat.patch} |  10 +-
 ...atible-basename-for-non-glibc-syste.patch} |  14 +-
 ...ffering-when-writing-to-oom_score_a.patch} |  10 +-
 ...ompliant-strerror_r-from-GNU-specif.patch} |  12 +-
 ...efinition-of-prctl_mm_map-structure.patch} |   8 +-
 ...not-disable-buffer-in-writing-files.patch} | 255 ++
 ...tch => 0013-Handle-__cpu_mask-usage.patch} |  11 +-
 ...atch => 0014-Handle-missing-gshadow.patch} |  10 +-
 h-Define-MIPS-ABI-defines-for-musl.patch} |  10 +-
 ...ss-correct-parameters-to-getdents64.patch} |   6 +-
 ...tch => 0017-Adjust-for-musl-headers.patch} |  92 ---
 ...rerror-is-assumed-to-be-GNU-specifi.patch} |  10 +-
 ...til-Make-STRERROR-portable-for-musl.patch} |  17 +-
 ...ke-malloc_trim-conditional-on-glibc.patch} |  18 +-
 ...ared-Do-not-use-malloc_info-on-musl.patch} |  15 +-
 ...22-avoid-missing-LOCK_EX-declaration.patch |  43 +++
 meta/recipes-core/systemd/systemd_255.1.bb|  43 +--
 23 files changed, 559 insertions(+), 271 deletions(-)
 rename 
meta/recipes-core/systemd/systemd/{0009-missing_type.h-add-comparison_fn_t.patch
 => 0001-missing_type.h-add-comparison_fn_t.patch} (89%)
 rename 
meta/recipes-core/systemd/systemd/{0010-add-fallback-parse_printf_format-implementation.patch
 => 0002-add-fallback-parse_printf_format-implementation.patch} (93%)
 rename 
meta/recipes-core/systemd/systemd/{0011-src-basic-missing.h-check-for-missing-strndupa.patch
 => 0003-src-basic-missing.h-check-for-missing-strndupa.patch} (86%)
 rename 
meta/recipes-core/systemd/systemd/{0012-don-t-fail-if-GLOB_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch
 => 0004-don-t-fail-if-GLOB_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch} (90%)
 rename 
meta/recipes-core/systemd/systemd/{0013-add-missing-FTW_-macros-for-musl.patch 
=> 0005-add-missing-FTW_-macros-for-musl.patch} (84%)
 rename 
meta/recipes-core/systemd/systemd/{0014-Use-uintmax_t-for-handling-rlim_t.patch 
=> 0006-Use-uintmax_t-for-handling-rlim_t.patch} (83%)
 rename 
meta/recipes-core/systemd/systemd/{0016-don-t-pass-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch
 => 0007-don-t-pass-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch} (95%)
 rename 
meta/recipes-core/systemd/systemd/{0017-Define-glibc-compatible-basename-for-non-glibc-syste.patch
 => 0008-Define-glibc-compatible-basename-for-non-glibc-syste.patch} (70%)
 rename 
meta/recipes-core/systemd/systemd/{0018-Do-not-disable-buffering-when-writing-to-oom_score_a.patch
 => 0009-Do-not-disable-buffering-when-writing-to-oom_score_a.patch} (82%)
 rename 
meta/recipes-core/systemd/systemd/{0019-distinguish-XSI-compliant-strerror_r-from-GNU-specif.patch
 => 0010-distinguish-XSI-compliant-strerror_r-from-GNU-specif.patch} (89%)
 rename 
meta/recipes-core/systemd/systemd/{0020-avoid-redefinition-of-prctl_mm_map-structure.patch
 => 0011-avoid-redefinition-of-prctl_mm_map-structure.patch} (79%)
 rename 
meta/recipes-core/systemd/systemd/{0021-do-not-disable-buffer-in-writing-files.patch
 => 0012-do-not-disable-buffer-in-writing-files.patch} (55%)
 rename meta/recipes-core/systemd/systemd/{0022-Handle-__cpu_mask-usage.patch 
=> 0013-Handle-__cpu_mask-usage.patch} (83%)
 rename meta/recipes-core/systemd/systemd/{0023-Handle-missing-gshadow.patch => 
0014-Handle-missing-gshadow.patch} (96%)
 rename 
meta/recipes-core/systemd/systemd/{0024-missing_syscall.h-Define-MIPS-ABI-defines-for-musl.patch
 => 0015-missing_syscall.h-Define-MIPS-ABI-defines-for-musl.patch} (84%)
 rename 
meta/recipes-core/systemd/systemd/{0005-pass-correct-parameters-to-getdents64.patch
 => 0016-pass-correct-parameters-to-getdents64.patch} (92%)
 rename meta/recipes-core/systemd/systemd/{0001-Adjust-for-musl-headers.patch 
=> 0017-Adjust-for-musl-headers.patch} (89%)
 rename 
meta/recipes-core/systemd/systemd/{0006-test-bus-error-strerror-is-assumed-to-be-GNU-specifi.patch
 => 0018-test-bus-error-strerror-is-assumed-to-be-GNU-specifi.patch} (89%)
 rename 
meta/recipes-core/systemd/systemd/{0003-errno-util-Make-STRERROR-portable-for-musl.patch
 => 0019-errno-util-Make-STRERROR-portable-for-musl.patch} (81%)
 rename 
meta/recipes-core/systemd/systemd/{0028-sd-event-Make-malloc_trim-conditional-on-glibc.patch
 => 0020-sd-event-Make-malloc_trim-conditional-on-glibc.patch} (85%)
 rename 
meta/recipes-core/systemd/systemd/{0029-shared-Do-not-use-malloc_info-on-musl.patch
 => 0021-shared-Do-not-use-malloc_info-on-musl.patch} (68%)
 create m

Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

2023-12-29 Thread Chen Qi via lists.openembedded.org
OK, I'll do it after New Year's Day.

Regards,
Qi


-Original Message-
From: Alexander Kanavin  
Sent: Friday, December 29, 2023 4:04 PM
To: Chen, Qi 
Cc: Alexandre Belloni ; 
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

On Fri, 29 Dec 2023 at 03:38, Chen Qi via lists.openembedded.org 
 wrote:
> > TEST_SUITES:append = ' systemd'
> > DISTRO_FEATURES:append = ' pam systemd usrmerge'
> > VIRTUAL-RUNTIME_init_manager = 'systemd'
> > DISTRO_FEATURES_BACKFILL_CONSIDERED = 'sysvinit'
>
> OK, I see.
>
> I'd suggest replacing the above 4 lines with a single line:
>
> INIT_MANAGER = "systemd"
>
> The INIT_MANAGER mechanism was added to make switching init managers easier.

I agree. The 4 lines are defined in two places here:
https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json

Can you send a patch to replace them with INIT_MANAGER?

Alex

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

2023-12-28 Thread Chen Qi via lists.openembedded.org

On 12/29/23 05:14, Alexandre Belloni wrote:

On 28/12/2023 03:00:08+, Chen, Qi wrote:

I double checked it in my environment, setting INIT_MANAGER to "systemd" and then 
'bitbake systemd' will not generate this warning. In this case ROOT_HOME's value is 
"/root".
I checked 
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354, but I 
couldn't find the configuration items that set the init manager to systemd.
Does the build use the variable 'INIT_MANAGER'? Does it set ROOT_HOME to 
"/home/root" somewhere?


This is the config that is used:

MACHINE = "qemux86-64"
DISTRO = "poky"
SDKMACHINE = "x86_64"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
DL_DIR = '/srv/autobuilder/autobuilder.yocto.io/current_sources'
SSTATE_DIR ?= '/srv/autobuilder/autobuilder.yocto.io/pub/sstate'



TEST_SUITES:append = ' systemd'
DISTRO_FEATURES:append = ' pam systemd usrmerge'
VIRTUAL-RUNTIME_init_manager = 'systemd'
DISTRO_FEATURES_BACKFILL_CONSIDERED = 'sysvinit'


OK, I see.

I'd suggest replacing the above 4 lines with a single line:

INIT_MANAGER = "systemd"

The INIT_MANAGER mechanism was added to make switching init managers easier.

Another choice is adding the following line to sync with the 
meta/conf/distro/include/init-manager-systemd.inc settings.


ROOT_HOME ?= "/root"

Regards,

Qi



DISTRO_FEATURES:remove = 'x11'
QEMU_USE_KVM = 'True'
INHERIT += 'report-error'
PREMIRRORS = ''
BB_GENERATE_MIRROR_TARBALLS = '1'
BB_NUMBER_THREADS = '16'
BB_NUMBER_PARSE_THREADS = '16'
PARALLEL_MAKE = '-j 16 -l 52'
BB_PRESSURE_MAX_CPU = '1'
BB_PRESSURE_MAX_IO = '1'
XZ_MEMLIMIT = '5%'
XZ_THREADS = '8'
ZSTD_THREADS = '8'
BB_TASK_NICE_LEVEL = '5'
BB_TASK_NICE_LEVEL:task-testimage = '0'
BB_TASK_IONICE_LEVEL = '2.7'
BB_TASK_IONICE_LEVEL:task-testimage = '2.1'
IMAGE_CLASSES += 'testimage'
TEST_QEMUBOOT_TIMEOUT = '1500'
SANITY_TESTED_DISTROS = ''
SDK_EXT_TYPE = 'minimal'
SDK_INCLUDE_TOOLCHAIN = '1'
ESDK_LOCAL_CONF_REMOVE:append = 'BB_HASHSERVE'
BB_DISKMON_DIRS = 'STOPTASKS,${TMPDIR},1G,100K STOPTASKS,${DL_DIR},1G 
STOPTASKS,${SSTATE_DIR},1G STOPTASKS,/tmp,100M,30K HALT,${TMPDIR},100M,1K 
HALT,${DL_DIR},100M HALT,${SSTATE_DIR},100M HALT,/tmp,10M,1K'
BB_HASHSERVE = 'hashserv.yocto.io:8686'
RUNQEMU_TMPFS_DIR = '/home/pokybuild/tmp'
BB_HEARTBEAT_EVENT = '60'
BB_LOG_HOST_STAT_ON_INTERVAL = '1'
BB_LOG_HOST_STAT_CMDS_INTERVAL = 'oe-time-dd-test.sh -c 100 -t 3'
BB_LOG_HOST_STAT_ON_FAILURE = '1'
BB_LOG_HOST_STAT_CMDS_FAILURE = 'oe-time-dd-test.sh -l'
SDK_TOOLCHAIN_LANGS += 'rust'
BB_SERVER_TIMEOUT = '60'

It is in auto.conf and it is displayed in the first lines of
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354/steps/14/logs/stdio


Regards,
Qi

-Original Message-
From: Alexandre Belloni 
Sent: Wednesday, December 27, 2023 7:59 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

We hit the added warning on the autobuilders:

WARNING: systemd-1_255.1-r0 do_install: Using /home/root as root user's home 
directory is not fully supported by systemd

https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354/steps/14/logs/warnings

On 27/12/2023 12:20:34+0800, Chen Qi via lists.openembedded.org wrote:

From: Chen Qi 

1. Patch changes:

0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
is removed because it has no real effect now. The /lib is now /usr/lib
because 'usrmerge' is a required distro feature for systemd.

0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is
refreshed for the new version to avoid patch-fuzz issue.

2. root user's home directory now defaults to "/root":

The sysuers.d/basic.conf is still modified to respect the ROOT_HOME
value, so if users set ROOT_HOME to "/home/root", the behavior is the
same as before. However, this is only for backward compatibility. With
this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
This is because systemd's source codes are hardcoding "/root", and
other values are not officially supported. See the list below.
$ grep -rl '"/root"' src/ | grep -v 'src/test'
src/core/namespace.c
src/basic/user-util.c
src/nss-systemd/nss-systemd.c
src/nspawn/nspawn.c
src/firstboot/firstboot.c
src/shared/userdb.c
src/shared/user-record.c
$ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/
tmpfiles.d/ units/ xorg/ tools/ sysusers.d/basic.conf.in
tmpfiles.d/provision.conf units/emergency.service.in
units/rescue.service.in tools/list-discoverable-partitions.py
Previously, the recipe was just substituting sysusers.d/basic.conf.in,
which is not enough to be treated as 'fully support'. I deliberately
put a warning message in do_install to warn users about non "/root"
ROOT_HOME value. Don't remove it until all above places are handled.

3. cgro

Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

2023-12-27 Thread Chen Qi via lists.openembedded.org
Hi Khem,

I'm working on some other issue these two days. But I think I can send out a 
follow-up patch to handle those musl patches after New Year's Day.

Regards,
Qi

-Original Message-
From: Khem Raj  
Sent: Thursday, December 28, 2023 11:20 AM
To: Chen, Qi 
Cc: Alexandre Belloni ; 
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

Please do a musl build too. We might have some patch conflicts to address.

On Wed, Dec 27, 2023 at 7:00 PM Chen Qi via lists.openembedded.org 
 wrote:
>
> I double checked it in my environment, setting INIT_MANAGER to "systemd" and 
> then 'bitbake systemd' will not generate this warning. In this case 
> ROOT_HOME's value is "/root".
> I checked 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354, but I 
> couldn't find the configuration items that set the init manager to systemd.
> Does the build use the variable 'INIT_MANAGER'? Does it set ROOT_HOME to 
> "/home/root" somewhere?
>
> Regards,
> Qi
>
> -Original Message-
> From: Alexandre Belloni 
> Sent: Wednesday, December 27, 2023 7:59 PM
> To: Chen, Qi 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1
>
> We hit the added warning on the autobuilders:
>
> WARNING: systemd-1_255.1-r0 do_install: Using /home/root as root 
> user's home directory is not fully supported by systemd
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354
> /steps/14/logs/warnings
>
> On 27/12/2023 12:20:34+0800, Chen Qi via lists.openembedded.org wrote:
> > From: Chen Qi 
> >
> > 1. Patch changes:
> >
> > 0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
> > is removed because it has no real effect now. The /lib is now 
> > /usr/lib because 'usrmerge' is a required distro feature for systemd.
> >
> > 0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is 
> > refreshed for the new version to avoid patch-fuzz issue.
> >
> > 2. root user's home directory now defaults to "/root":
> >
> > The sysuers.d/basic.conf is still modified to respect the ROOT_HOME 
> > value, so if users set ROOT_HOME to "/home/root", the behavior is 
> > the same as before. However, this is only for backward 
> > compatibility. With this patch, The ROOT_HOME value is set to "/root" in 
> > init-manager-systemd.inc.
> > This is because systemd's source codes are hardcoding "/root", and 
> > other values are not officially supported. See the list below.
> > $ grep -rl '"/root"' src/ | grep -v 'src/test'
> > src/core/namespace.c
> > src/basic/user-util.c
> > src/nss-systemd/nss-systemd.c
> > src/nspawn/nspawn.c
> > src/firstboot/firstboot.c
> > src/shared/userdb.c
> > src/shared/user-record.c
> > $ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ 
> > tmpfiles.d/ units/ xorg/ tools/ sysusers.d/basic.conf.in 
> > tmpfiles.d/provision.conf units/emergency.service.in 
> > units/rescue.service.in tools/list-discoverable-partitions.py
> > Previously, the recipe was just substituting 
> > sysusers.d/basic.conf.in, which is not enough to be treated as 
> > 'fully support'. I deliberately put a warning message in do_install to warn 
> > users about non "/root"
> > ROOT_HOME value. Don't remove it until all above places are handled.
> >
> > 3. cgroupv2 is now the default.
> > cgroupv2 is the default for systemd for many years and it's the 
> > default for distros such as ubuntu and fedora. Let's also use it as the 
> > default.
> >
> > Signed-off-by: Chen Qi 
> > ---
> >  .../distro/include/init-manager-systemd.inc   |  2 +
> >  meta/recipes-core/systemd/systemd.inc |  4 +-
> >  ...tall-dependency-links-at-install-tim.patch | 22 +++--- 
> > ...sysctl.d-binfmt.d-modules-load.d-to-.patch | 73 ---
> >  .../systemd/systemd/basic.conf.in | 40 --
> >  .../{systemd_254.4.bb => systemd_255.1.bb}| 16 ++--
> >  6 files changed, 25 insertions(+), 132 deletions(-)  delete mode
> > 100644
> > meta/recipes-core/systemd/systemd/0004-Move-sysusers.d-sysctl.d-binf
> > mt .d-modules-load.d-to-.patch  delete mode 100644 
> > meta/recipes-core/systemd/systemd/basic.conf.in
> >  rename meta/recipes-core/systemd/{systemd_254.4.bb => 
> > systemd_255.1.bb} (98%)
> >
> > diff --git a/meta/conf/distro/include/init-manager-systemd.inc
> > b/meta/conf/distro/include/init-manager-systemd.inc
> > index 595d1f2644.

Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

2023-12-27 Thread Chen Qi via lists.openembedded.org
I double checked it in my environment, setting INIT_MANAGER to "systemd" and 
then 'bitbake systemd' will not generate this warning. In this case ROOT_HOME's 
value is "/root".
I checked 
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354, but I 
couldn't find the configuration items that set the init manager to systemd.
Does the build use the variable 'INIT_MANAGER'? Does it set ROOT_HOME to 
"/home/root" somewhere?

Regards,
Qi

-Original Message-
From: Alexandre Belloni  
Sent: Wednesday, December 27, 2023 7:59 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1

We hit the added warning on the autobuilders:

WARNING: systemd-1_255.1-r0 do_install: Using /home/root as root user's home 
directory is not fully supported by systemd

https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/8354/steps/14/logs/warnings

On 27/12/2023 12:20:34+0800, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi 
> 
> 1. Patch changes:
> 
> 0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
> is removed because it has no real effect now. The /lib is now /usr/lib 
> because 'usrmerge' is a required distro feature for systemd.
> 
> 0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is 
> refreshed for the new version to avoid patch-fuzz issue.
> 
> 2. root user's home directory now defaults to "/root":
> 
> The sysuers.d/basic.conf is still modified to respect the ROOT_HOME 
> value, so if users set ROOT_HOME to "/home/root", the behavior is the 
> same as before. However, this is only for backward compatibility. With 
> this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
> This is because systemd's source codes are hardcoding "/root", and 
> other values are not officially supported. See the list below.
> $ grep -rl '"/root"' src/ | grep -v 'src/test'
> src/core/namespace.c
> src/basic/user-util.c
> src/nss-systemd/nss-systemd.c
> src/nspawn/nspawn.c
> src/firstboot/firstboot.c
> src/shared/userdb.c
> src/shared/user-record.c
> $ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ 
> tmpfiles.d/ units/ xorg/ tools/ sysusers.d/basic.conf.in 
> tmpfiles.d/provision.conf units/emergency.service.in 
> units/rescue.service.in tools/list-discoverable-partitions.py
> Previously, the recipe was just substituting sysusers.d/basic.conf.in, 
> which is not enough to be treated as 'fully support'. I deliberately 
> put a warning message in do_install to warn users about non "/root" 
> ROOT_HOME value. Don't remove it until all above places are handled.
> 
> 3. cgroupv2 is now the default.
> cgroupv2 is the default for systemd for many years and it's the 
> default for distros such as ubuntu and fedora. Let's also use it as the 
> default.
> 
> Signed-off-by: Chen Qi 
> ---
>  .../distro/include/init-manager-systemd.inc   |  2 +
>  meta/recipes-core/systemd/systemd.inc |  4 +-
>  ...tall-dependency-links-at-install-tim.patch | 22 +++---  
> ...sysctl.d-binfmt.d-modules-load.d-to-.patch | 73 ---
>  .../systemd/systemd/basic.conf.in | 40 --
>  .../{systemd_254.4.bb => systemd_255.1.bb}| 16 ++--
>  6 files changed, 25 insertions(+), 132 deletions(-)  delete mode 
> 100644 
> meta/recipes-core/systemd/systemd/0004-Move-sysusers.d-sysctl.d-binfmt
> .d-modules-load.d-to-.patch  delete mode 100644 
> meta/recipes-core/systemd/systemd/basic.conf.in
>  rename meta/recipes-core/systemd/{systemd_254.4.bb => 
> systemd_255.1.bb} (98%)
> 
> diff --git a/meta/conf/distro/include/init-manager-systemd.inc 
> b/meta/conf/distro/include/init-manager-systemd.inc
> index 595d1f2644..0a76647459 100644
> --- a/meta/conf/distro/include/init-manager-systemd.inc
> +++ b/meta/conf/distro/include/init-manager-systemd.inc
> @@ -5,3 +5,5 @@ VIRTUAL-RUNTIME_init_manager ??= "systemd"
>  VIRTUAL-RUNTIME_initscripts ??= "systemd-compat-units"
>  VIRTUAL-RUNTIME_login_manager ??= "shadow-base"
>  VIRTUAL-RUNTIME_dev_manager ??= "systemd"
> +# systemd hardcodes /root in its source codes, other values are not 
> +offically supported ROOT_HOME ?= "/root"
> diff --git a/meta/recipes-core/systemd/systemd.inc 
> b/meta/recipes-core/systemd/systemd.inc
> index ccc3236457..1417e0150f 100644
> --- a/meta/recipes-core/systemd/systemd.inc
> +++ b/meta/recipes-core/systemd/systemd.inc
> @@ -15,8 +15,8 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
>  LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe 
> \
>  
> file://LICENSE

[OE-core][PATCH V2] dbus: upgrade to 1.15.8

2023-12-27 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

License-Update:
===
The license checksums are changed, but the license remains the same.
The contents change are only about description changes, e.g., not
copying the whole licenses and instead telling people to go check them.

Signed-off-by: Chen Qi 
---
 .../dbus/{dbus_1.14.10.bb => dbus_1.15.8.bb}   | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta/recipes-core/dbus/{dbus_1.14.10.bb => dbus_1.15.8.bb} (94%)

diff --git a/meta/recipes-core/dbus/dbus_1.14.10.bb 
b/meta/recipes-core/dbus/dbus_1.15.8.bb
similarity index 94%
rename from meta/recipes-core/dbus/dbus_1.14.10.bb
rename to meta/recipes-core/dbus/dbus_1.15.8.bb
index 2a256beabf..4ff115186c 100644
--- a/meta/recipes-core/dbus/dbus_1.14.10.bb
+++ b/meta/recipes-core/dbus/dbus_1.15.8.bb
@@ -6,8 +6,8 @@ SECTION = "base"
 inherit autotools pkgconfig gettext upstream-version-is-even ptest-gnome
 
 LICENSE = "AFL-2.1 | GPL-2.0-or-later"
-LIC_FILES_CHKSUM = "file://COPYING;md5=6423dcd74d7be9715b0db247fd889da3 \
-
file://dbus/dbus.h;beginline=6;endline=20;md5=866739837ccd835350af94dccd6457d8 \
+LIC_FILES_CHKSUM = "file://COPYING;md5=eb0ffc69a965797a3d6686baa153ef05 \
+
file://dbus/dbus.h;beginline=6;endline=22;md5=df4251a6c6e15e6a9e3c77b2ac30065d \
 "
 
 SRC_URI = "https://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.xz \
@@ -16,7 +16,7 @@ SRC_URI = 
"https://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.xz \
file://dbus-1.init \
"
 
-SRC_URI[sha256sum] = 
"ba1f21d2bd9d339da2d4aa8780c09df32fea87998b73da24f49ab9df1e36a50f"
+SRC_URI[sha256sum] = 
"84fc597e6ec82f05dc18a7d12c17046f95bad7be99fc03c15bc254c4701ed204"
 
 EXTRA_OECONF = "--disable-xml-docs \
 --disable-doxygen-docs \
@@ -160,8 +160,8 @@ do_install() {
# Remove empty testexec directory as we don't build tests
rm -rf ${D}${libdir}/dbus-1.0/test
 
-   # Remove /var/run as it is created on startup
-   rm -rf ${D}${localstatedir}/run
+   # Remove /var/run and /run as it is created on startup
+   rm -rf ${D}${localstatedir}/run rm -rf ${D}/run
 }
 
 do_install:class-native() {
-- 
2.34.1


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

2023-12-27 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The license checksums are changed, but he license remains the same.

Signed-off-by: Chen Qi 
---
 .../dbus/{dbus_1.14.10.bb => dbus_1.15.8.bb}   | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta/recipes-core/dbus/{dbus_1.14.10.bb => dbus_1.15.8.bb} (94%)

diff --git a/meta/recipes-core/dbus/dbus_1.14.10.bb 
b/meta/recipes-core/dbus/dbus_1.15.8.bb
similarity index 94%
rename from meta/recipes-core/dbus/dbus_1.14.10.bb
rename to meta/recipes-core/dbus/dbus_1.15.8.bb
index 2a256beabf..4ff115186c 100644
--- a/meta/recipes-core/dbus/dbus_1.14.10.bb
+++ b/meta/recipes-core/dbus/dbus_1.15.8.bb
@@ -6,8 +6,8 @@ SECTION = "base"
 inherit autotools pkgconfig gettext upstream-version-is-even ptest-gnome
 
 LICENSE = "AFL-2.1 | GPL-2.0-or-later"
-LIC_FILES_CHKSUM = "file://COPYING;md5=6423dcd74d7be9715b0db247fd889da3 \
-
file://dbus/dbus.h;beginline=6;endline=20;md5=866739837ccd835350af94dccd6457d8 \
+LIC_FILES_CHKSUM = "file://COPYING;md5=eb0ffc69a965797a3d6686baa153ef05 \
+
file://dbus/dbus.h;beginline=6;endline=22;md5=df4251a6c6e15e6a9e3c77b2ac30065d \
 "
 
 SRC_URI = "https://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.xz \
@@ -16,7 +16,7 @@ SRC_URI = 
"https://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.xz \
file://dbus-1.init \
"
 
-SRC_URI[sha256sum] = 
"ba1f21d2bd9d339da2d4aa8780c09df32fea87998b73da24f49ab9df1e36a50f"
+SRC_URI[sha256sum] = 
"84fc597e6ec82f05dc18a7d12c17046f95bad7be99fc03c15bc254c4701ed204"
 
 EXTRA_OECONF = "--disable-xml-docs \
 --disable-doxygen-docs \
@@ -160,8 +160,8 @@ do_install() {
# Remove empty testexec directory as we don't build tests
rm -rf ${D}${libdir}/dbus-1.0/test
 
-   # Remove /var/run as it is created on startup
-   rm -rf ${D}${localstatedir}/run
+   # Remove /var/run and /run as it is created on startup
+   rm -rf ${D}${localstatedir}/run rm -rf ${D}/run
 }
 
 do_install:class-native() {
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192926): 
https://lists.openembedded.org/g/openembedded-core/message/192926
Mute This Topic: https://lists.openembedded.org/mt/103382183/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] rootfs-postcommands.bbclass: ignore comment mismatch in systemd_user_check

2023-12-26 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The check was forcing every field to be identical, this is too
strict. For example, if the comment differs, there's really no
impact. For example, root user's comment is 'root' in passwd,
and it's 'Super User' in sysusers.d/basic.conf. Such difference is
not worth a warning. In fact, previous codes use 'lower()' to
avoid warning between 'nobody' and 'Nobody', and what's more, another
patch puts its own basic.conf.in in systemd's SRC_URI, but it changes
'Super User' to 'root'. Such changes are all unnecessary. We should
just ignore comment mismatch.

Signed-off-by: Chen Qi 
---
 meta/classes-recipe/rootfs-postcommands.bbclass | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/classes-recipe/rootfs-postcommands.bbclass 
b/meta/classes-recipe/rootfs-postcommands.bbclass
index 29ee74932a..f996b6c71a 100644
--- a/meta/classes-recipe/rootfs-postcommands.bbclass
+++ b/meta/classes-recipe/rootfs-postcommands.bbclass
@@ -111,12 +111,11 @@ def compare_users(user, e_user):
 # user and e_user must not have None values. Unset values must be '-'.
 (name, uid, gid, comment, homedir, ushell) = user
 (e_name, e_uid, e_gid, e_comment, e_homedir, e_ushell) = e_user
-# Ignore 'uid', 'gid' or 'comment' if they are not set
+# Ignore 'uid', 'gid' or 'homedir' if they are not set
 # Ignore 'shell' and 'ushell' if one is not set
 return name == e_name \
 and (uid == '-' or uid == e_uid) \
 and (gid == '-' or gid == e_gid) \
-and (comment == '-' or e_comment == '-' or comment.lower() == 
e_comment.lower()) \
 and (homedir == '-' or e_homedir == '-' or homedir == e_homedir) \
 and (ushell == '-' or e_ushell == '-' or ushell == e_ushell)
 
-- 
2.34.1


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

2023-12-26 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

1. Patch changes:

0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
is removed because it has no real effect now. The /lib is now
/usr/lib because 'usrmerge' is a required distro feature for systemd.

0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch is
refreshed for the new version to avoid patch-fuzz issue.

2. root user's home directory now defaults to "/root":

The sysuers.d/basic.conf is still modified to respect the ROOT_HOME
value, so if users set ROOT_HOME to "/home/root", the behavior is the
same as before. However, this is only for backward compatibility. With
this patch, The ROOT_HOME value is set to "/root" in init-manager-systemd.inc.
This is because systemd's source codes are hardcoding "/root", and other
values are not officially supported. See the list below.
$ grep -rl '"/root"' src/ | grep -v 'src/test'
src/core/namespace.c
src/basic/user-util.c
src/nss-systemd/nss-systemd.c
src/nspawn/nspawn.c
src/firstboot/firstboot.c
src/shared/userdb.c
src/shared/user-record.c
$ grep -rl /root network/ factory/ sysctl.d/ sysusers.d/ rules.d/ tmpfiles.d/ 
units/ xorg/ tools/
sysusers.d/basic.conf.in
tmpfiles.d/provision.conf
units/emergency.service.in
units/rescue.service.in
tools/list-discoverable-partitions.py
Previously, the recipe was just substituting sysusers.d/basic.conf.in,
which is not enough to be treated as 'fully support'. I deliberately put
a warning message in do_install to warn users about non "/root" ROOT_HOME
value. Don't remove it until all above places are handled.

3. cgroupv2 is now the default.
cgroupv2 is the default for systemd for many years and it's the default
for distros such as ubuntu and fedora. Let's also use it as the default.

Signed-off-by: Chen Qi 
---
 .../distro/include/init-manager-systemd.inc   |  2 +
 meta/recipes-core/systemd/systemd.inc |  4 +-
 ...tall-dependency-links-at-install-tim.patch | 22 +++---
 ...sysctl.d-binfmt.d-modules-load.d-to-.patch | 73 ---
 .../systemd/systemd/basic.conf.in | 40 --
 .../{systemd_254.4.bb => systemd_255.1.bb}| 16 ++--
 6 files changed, 25 insertions(+), 132 deletions(-)
 delete mode 100644 
meta/recipes-core/systemd/systemd/0004-Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-to-.patch
 delete mode 100644 meta/recipes-core/systemd/systemd/basic.conf.in
 rename meta/recipes-core/systemd/{systemd_254.4.bb => systemd_255.1.bb} (98%)

diff --git a/meta/conf/distro/include/init-manager-systemd.inc 
b/meta/conf/distro/include/init-manager-systemd.inc
index 595d1f2644..0a76647459 100644
--- a/meta/conf/distro/include/init-manager-systemd.inc
+++ b/meta/conf/distro/include/init-manager-systemd.inc
@@ -5,3 +5,5 @@ VIRTUAL-RUNTIME_init_manager ??= "systemd"
 VIRTUAL-RUNTIME_initscripts ??= "systemd-compat-units"
 VIRTUAL-RUNTIME_login_manager ??= "shadow-base"
 VIRTUAL-RUNTIME_dev_manager ??= "systemd"
+# systemd hardcodes /root in its source codes, other values are not offically 
supported
+ROOT_HOME ?= "/root"
diff --git a/meta/recipes-core/systemd/systemd.inc 
b/meta/recipes-core/systemd/systemd.inc
index ccc3236457..1417e0150f 100644
--- a/meta/recipes-core/systemd/systemd.inc
+++ b/meta/recipes-core/systemd/systemd.inc
@@ -15,8 +15,8 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
 LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe \
 
file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"
 
-SRCREV = "2e7504449a51fb38db9cd2da391c6434f82def51"
-SRCBRANCH = "v254-stable"
+SRCREV = "2018ccef6645ce00c784369a22dc4e98f6d7061d"
+SRCBRANCH = "v255-stable"
 SRC_URI = 
"git://github.com/systemd/systemd-stable.git;protocol=https;branch=${SRCBRANCH}"
 
 S = "${WORKDIR}/git"
diff --git 
a/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
 
b/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
index 085f1e9052..be231cf6b2 100644
--- 
a/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
+++ 
b/meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-links-at-install-tim.patch
@@ -1,8 +1,8 @@
-From ca7d9a8d9c81702af9c599bb79706f12b1a465cf Mon Sep 17 00:00:00 2001
+From 29a58009a172e369ad7166e16dab2f4945c6b0d2 Mon Sep 17 00:00:00 2001
 From: Chen Qi 
 Date: Thu, 21 Feb 2019 16:23:24 +0800
-Subject: [PATCH] binfmt: Don't install dependency links at install time for
- the binfmt services
+Subject: [PATCH 1/2] binfmt: Don't install dependency links at install time
+ for the binfmt services
 
 use [Install] blocks so that they get created when the service is enabled
 like a traditional service.
@@ -25,10 +25,10 @@ Signed-off-by: Scott Murray 
  3 files changed, 7

[OE-core][PATCH 2/3] systemd-boot: upgrade to 255.1

2023-12-26 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

0030-meson-Pass-all-static-pie-args-to-linker.patch is dropped as
it's a backported patch and is now in the new 255.1 version.

Signed-off-by: Chen Qi 
---
 ...md-boot_254.4.bb => systemd-boot_255.1.bb} |  4 ---
 ...n-Pass-all-static-pie-args-to-linker.patch | 35 ---
 2 files changed, 39 deletions(-)
 rename meta/recipes-core/systemd/{systemd-boot_254.4.bb => 
systemd-boot_255.1.bb} (94%)
 delete mode 100644 
meta/recipes-core/systemd/systemd/0030-meson-Pass-all-static-pie-args-to-linker.patch

diff --git a/meta/recipes-core/systemd/systemd-boot_254.4.bb 
b/meta/recipes-core/systemd/systemd-boot_255.1.bb
similarity index 94%
rename from meta/recipes-core/systemd/systemd-boot_254.4.bb
rename to meta/recipes-core/systemd/systemd-boot_255.1.bb
index 2b43ccf243..4ee25ee72f 100644
--- a/meta/recipes-core/systemd/systemd-boot_254.4.bb
+++ b/meta/recipes-core/systemd/systemd-boot_255.1.bb
@@ -8,10 +8,6 @@ DEPENDS = "intltool-native libcap util-linux gperf-native 
python3-jinja2-native
 inherit meson pkgconfig gettext
 inherit deploy
 
-SRC_URI += " \
-   file://0030-meson-Pass-all-static-pie-args-to-linker.patch \
-   "
-
 LDFLAGS:prepend = "${@ " ".join(d.getVar('LD').split()[1:])} "
 
 EFI_LD = "bfd"
diff --git 
a/meta/recipes-core/systemd/systemd/0030-meson-Pass-all-static-pie-args-to-linker.patch
 
b/meta/recipes-core/systemd/systemd/0030-meson-Pass-all-static-pie-args-to-linker.patch
deleted file mode 100644
index 8e563238ef..00
--- 
a/meta/recipes-core/systemd/systemd/0030-meson-Pass-all-static-pie-args-to-linker.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From f85a387a67900b02c69abccb88c2ef7191c67277 Mon Sep 17 00:00:00 2001
-From: Jan Janssen 
-Date: Sun, 1 Oct 2023 09:55:48 +0200
-Subject: [PATCH] meson: Pass all -static-pie args to linker
-
-Fixes: #29381
-
-Upstream-Status: Backport 
[https://github.com/systemd/systemd/commit/cecbb162a3134b43d2ca160e13198c73ff34c3ef]
-Signed-off-by: Viswanath Kraleti 

- src/boot/efi/meson.build | 11 ---
- 1 file changed, 8 insertions(+), 3 deletions(-)
-
-diff --git a/src/boot/efi/meson.build b/src/boot/efi/meson.build
-index 2773eaf286..9a60a57329 100644
 a/src/boot/efi/meson.build
-+++ b/src/boot/efi/meson.build
-@@ -161,9 +161,14 @@ efi_c_ld_args = [
- '-Wl,--entry=efi_main',
- '-Wl,--fatal-warnings',
- 
--# These flags should be passed by -static-pie, but seem to be missing 
sometimes.
--'-Wl,--no-dynamic-linker',
--'-z', 'text',
-+# These flags should be passed by -static-pie, but for whatever 
reason the flag translation
-+# is not enabled on all architectures. Not passing `-static` would 
just allow the linker to
-+# use dynamic libraries, (which we can't/don't use anyway). But if 
`-pie` is missing and the
-+# gcc build does not default to `-pie` we get a regular (no-pie) 
binary that will be
-+# rightfully rejected by elf2efi. Note that meson also passes `-pie` 
to the linker driver,
-+# but it is overridden by our `-static-pie`. We also need to pass 
these directly to the
-+# linker as `-static`+`-pie` seem to get translated differently.
-+'-Wl,-static,-pie,--no-dynamic-linker,-z,text',
- 
- # EFI has 4KiB pages.
- '-z', 'common-page-size=4096',
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192924): 
https://lists.openembedded.org/g/openembedded-core/message/192924
Mute This Topic: https://lists.openembedded.org/mt/103380517/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] devtool/standard: avoid KeyError

2023-12-25 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The initial_revs["."] does not have an initial value, resulting
in the following error:

  KeyError: '.'

The problem could be reproduced by running:

  devtool modify -n systemd 

Signed-off-by: Chen Qi 
---
 scripts/lib/devtool/standard.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index 559fd45676..5d9b86ed6a 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -905,6 +905,7 @@ def modify(args, config, basepath, workspace):
 (stdout, _) = bb.process.run('git rev-list --reverse 
devtool-base..HEAD', cwd=submodule_path)
 commits[submodule] = stdout.split()
 else:
+initial_revs["."] = None
 if os.path.exists(os.path.join(srctree, '.git')):
 # Check if it's a tree previously extracted by us. This is done
 # by ensuring that devtool-base and args.branch (devtool) 
exist.
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192906): 
https://lists.openembedded.org/g/openembedded-core/message/192906
Mute This Topic: https://lists.openembedded.org/mt/10330/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] rootfs.py generates wrong ld.so.cache in case of usrmerge distro feature

2023-11-30 Thread Chen Qi via lists.openembedded.org

Could you check if your /lib is a symlink to /usr/lib on target?
/lib/libxxx.so.x should be fine if /lib is a symlink to /usr/lib. Right?
Or am I missing something?

Regards,
Qi

On 11/24/23 18:34, Johannes Pointner wrote:

Hello,

I did recently my first Nanbield build which required the distro
feature usrmerge because of using systemd and as a result QtWebEngine
didn't work anymore.
I reported this to Qt(https://bugreports.qt.io/browse/QTBUG-119140),
but looking deeper into this it turned out to be an issue related to
the generated ld.so.cache in the rootfs.py.
At the moment in the ldconfig-native which is used to generate this,
are the paths to LIBDIR("/usr/lib") and SLIBDIR("/lib") hardcoded, but
that isn't correct if usrmerge is enabled, at least I think so.
The resulting ld.so.cache looks like this:
236 libs found in cache `/etc/ld.so.cache'
libzstd.so.1 (libc6) => /lib/libzstd.so.1
libz.so.1 (libc6) => /lib/libz.so.1
libxtables.so.12 (libc6) => /lib/libxtables.so.12
libxslt.so.1 (libc6) => /lib/libxslt.so.1
libxml2.so.2 (libc6) => /lib/libxml2.so.2
...

Would it be OK to configure the paths LIBDIR SLIBDIR using base_libdir
and libdir?

Thanks,
Hannes






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191556): 
https://lists.openembedded.org/g/openembedded-core/message/191556
Mute This Topic: https://lists.openembedded.org/mt/102778802/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] systemd: backport patch to fix warning in systemd-vconsole-setup

2023-11-07 Thread Chen Qi via lists.openembedded.org
The backported patch fixes the following warning:
systemd-vconsole-setup[221]: Failed to import credentials, ignoring: No such 
file or directory

Signed-off-by: Chen Qi 
---
 ...l-return-0-for-missing-creds-in-read.patch | 139 ++
 meta/recipes-core/systemd/systemd_253.1.bb|   1 +
 2 files changed, 140 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-shared-creds-util-return-0-for-missing-creds-in-read.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0001-shared-creds-util-return-0-for-missing-creds-in-read.patch
 
b/meta/recipes-core/systemd/systemd/0001-shared-creds-util-return-0-for-missing-creds-in-read.patch
new file mode 100644
index 00..953afd20b4
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0001-shared-creds-util-return-0-for-missing-creds-in-read.patch
@@ -0,0 +1,139 @@
+From 78fc42be73d81ff625f6479784ce1950bd4741b3 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= 
+Date: Tue, 25 Apr 2023 17:58:34 +0200
+Subject: [PATCH] shared/creds-util: return 0 for missing creds in
+ read_credential_strings_many
+
+Realistically, the only thing that the caller can do is ignore failures related
+to missing credentials. If the caller requires some credentials to be present,
+they should just check which output variables are not NULL. One of the callers
+was already doing that, and the other wanted to, but missed -ENOENT. By
+suppressing -ENOENT and -ENXIO, both callers are simplified.
+
+Fixes a warning at boot:
+systemd-vconsole-setup[221]: Failed to import credentials, ignoring: No such 
file or directory
+
+(cherry picked from commit 55ace8e5c58441d1a2c64b297a38b232ef0c0e28)
+
+Upstream-Status: Backport [1575f1d9e78ab44beedd4eae4af3a14d45312d76]
+
+Signed-off-by: Chen Qi 
+---
+ src/resolve/resolved-conf.c   |  7 +++
+ src/shared/creds-util.c   | 18 +++---
+ src/test/test-creds.c |  8 
+ src/vconsole/vconsole-setup.c |  2 +-
+ 4 files changed, 19 insertions(+), 16 deletions(-)
+
+diff --git a/src/resolve/resolved-conf.c b/src/resolve/resolved-conf.c
+index d6929984e9..52e65caffa 100644
+--- a/src/resolve/resolved-conf.c
 b/src/resolve/resolved-conf.c
+@@ -476,10 +476,9 @@ static void read_credentials(Manager *m) {
+ if (!m->read_resolv_conf)
+ return;
+ 
+-r = read_credential_strings_many(
+-"network.dns", ,
+-"network.search_domains", );
+-if (r < 0 && !IN_SET(r, -ENXIO, -ENOENT))
++r = read_credential_strings_many("network.dns", ,
++ "network.search_domains", );
++if (r < 0)
+ log_warning_errno(r, "Failed to read credentials, ignoring: 
%m");
+ 
+ if (dns) {
+diff --git a/src/shared/creds-util.c b/src/shared/creds-util.c
+index 750ee2571e..617bae4205 100644
+--- a/src/shared/creds-util.c
 b/src/shared/creds-util.c
+@@ -96,17 +96,21 @@ int read_credential_strings_many_internal(
+ 
+ /* Reads a bunch of credentials into the specified buffers. If the 
specified buffers are already
+  * non-NULL frees them if a credential is found. Only supports 
string-based credentials
+- * (i.e. refuses embedded NUL bytes) */
++ * (i.e. refuses embedded NUL bytes).
++ *
++ * 0 is returned when some or all credentials are missing.
++ */
+ 
+ if (!first_name)
+ return 0;
+ 
+ r = read_credential(first_name, , NULL);
+-if (r == -ENXIO) /* no creds passed at all? propagate this */
+-return r;
+-if (r < 0)
+-ret = r;
+-else
++if (r == -ENXIO) /* No creds passed at all? Bail immediately. */
++return 0;
++if (r < 0) {
++if (r != -ENOENT)
++ret = r;
++} else
+ free_and_replace(*first_value, b);
+ 
+ va_list ap;
+@@ -127,7 +131,7 @@ int read_credential_strings_many_internal(
+ 
+ r = read_credential(name, , NULL);
+ if (r < 0) {
+-if (ret >= 0)
++if (ret >= 0 && r != -ENOENT)
+ ret = r;
+ } else
+ free_and_replace(*value, bb);
+diff --git a/src/test/test-creds.c b/src/test/test-creds.c
+index 44022e7324..25b0c34a59 100644
+--- a/src/test/test-creds.c
 b/src/test/test-creds.c
+@@ -16,7 +16,7 @@ TEST(read_credential_strings) {
+ if (e)
+ assert_se(saved = strdup(e));
+ 
+-assert_se(read_credential_strings_many("foo", , "bar", ) == 
-ENXIO);
++assert_se(read_credential_strings_many("foo", , "bar", ) == 0);
+ assert_se(x == NULL);
+ assert_se(y == NULL

[OE-core] [PATCH V2] systemd: fix DynamicUser issue

2023-11-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The DynamicUser needs libnss-systemd to be installed to function
well. The tweaks to nsswitch.conf should be conditional on PACKAGECONFIG
values.

Signed-off-by: Chen Qi 
---
 meta/recipes-core/systemd/systemd_254.4.bb | 30 +-
 1 file changed, 23 insertions(+), 7 deletions(-)

Changes in V2:
Follow 
https://docs.yoctoproject.org/dev/dev-manual/new-recipe.html#recipe-syntax
to use taps in shell functions.

diff --git a/meta/recipes-core/systemd/systemd_254.4.bb 
b/meta/recipes-core/systemd/systemd_254.4.bb
index ef29116bf9..c3507d9033 100644
--- a/meta/recipes-core/systemd/systemd_254.4.bb
+++ b/meta/recipes-core/systemd/systemd_254.4.bb
@@ -179,7 +179,7 @@ PACKAGECONFIG[microhttpd] = 
"-Dmicrohttpd=true,-Dmicrohttpd=false,libmicrohttpd"
 PACKAGECONFIG[myhostname] = 
"-Dnss-myhostname=true,-Dnss-myhostname=false,,libnss-myhostname"
 PACKAGECONFIG[networkd] = "-Dnetworkd=true,-Dnetworkd=false"
 PACKAGECONFIG[no-dns-fallback] = "-Ddns-servers="
-PACKAGECONFIG[nss] = "-Dnss-systemd=true,-Dnss-systemd=false"
+PACKAGECONFIG[nss] = "-Dnss-systemd=true,-Dnss-systemd=false,,libnss-systemd"
 PACKAGECONFIG[nss-mymachines] = "-Dnss-mymachines=true,-Dnss-mymachines=false"
 PACKAGECONFIG[nss-resolve] = "-Dnss-resolve=true,-Dnss-resolve=false"
 PACKAGECONFIG[oomd] = "-Doomd=true,-Doomd=false"
@@ -839,15 +839,31 @@ ALTERNATIVE_LINK_NAME[runlevel] = 
"${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
 pkg_postinst:${PN}:libc-glibc () {
-   sed -e '/^hosts:/s/\s*\//' \
-   -e 's/\(^hosts:.*\)\(\\)\(.*\)\(\\)\(.*\)/\1\2 
myhostname \3\4\5/' \
-   -i $D${sysconfdir}/nsswitch.conf
+   if ${@bb.utils.contains('PACKAGECONFIG', 'myhostname', 'true', 'false', 
d)}; then
+   sed -e '/^hosts:/s/\s*\//' \
+   -e 
's/\(^hosts:.*\)\(\\)\(.*\)\(\\)\(.*\)/\1\2 myhostname \3\4\5/' \
+   -i $D${sysconfdir}/nsswitch.conf
+   fi
+   if ${@bb.utils.contains('PACKAGECONFIG', 'nss', 'true', 'false', d)}; 
then
+   sed -e 's#\(^passwd:.*\)#\1 systemd#' \
+   -e 's#\(^group:.*\)#\1 systemd#' \
+   -e 's#\(^shadow:.*\)#\1 systemd#' \
+   -i $D${sysconfdir}/nsswitch.conf
+   fi
 }
 
 pkg_prerm:${PN}:libc-glibc () {
-   sed -e '/^hosts:/s/\s*\//' \
-   -e '/^hosts:/s/\s*myhostname//' \
-   -i $D${sysconfdir}/nsswitch.conf
+   if ${@bb.utils.contains('PACKAGECONFIG', 'myhostname', 'true', 'false', 
d)}; then
+   sed -e '/^hosts:/s/\s*\//' \
+   -e '/^hosts:/s/\s*myhostname//' \
+   -i $D${sysconfdir}/nsswitch.conf
+   fi
+   if ${@bb.utils.contains('PACKAGECONFIG', 'nss', 'true', 'false', d)}; 
then
+   sed -e '/^passwd:/s#\s*systemd##' \
+   -e '/^group:/s#\s*systemd##' \
+   -e '/^shadow:/s#\s*systemd##' \
+   -i $D${sysconfdir}/nsswitch.conf
+   fi
 }
 
 PACKAGE_WRITE_DEPS += "qemu-native"
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#190055): 
https://lists.openembedded.org/g/openembedded-core/message/190055
Mute This Topic: https://lists.openembedded.org/mt/102333967/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] systemd: fix DynamicUser issue

2023-11-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The DynamicUser needs libnss-systemd to be installed to function
well. The tweaks to nsswitch.conf should be conditional on PACKAGECONFIG
values.

Signed-off-by: Chen Qi 
---
 meta/recipes-core/systemd/systemd_254.4.bb | 22 +++---
 1 file changed, 19 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_254.4.bb 
b/meta/recipes-core/systemd/systemd_254.4.bb
index ef29116bf9..b3066b7c42 100644
--- a/meta/recipes-core/systemd/systemd_254.4.bb
+++ b/meta/recipes-core/systemd/systemd_254.4.bb
@@ -179,7 +179,7 @@ PACKAGECONFIG[microhttpd] = 
"-Dmicrohttpd=true,-Dmicrohttpd=false,libmicrohttpd"
 PACKAGECONFIG[myhostname] = 
"-Dnss-myhostname=true,-Dnss-myhostname=false,,libnss-myhostname"
 PACKAGECONFIG[networkd] = "-Dnetworkd=true,-Dnetworkd=false"
 PACKAGECONFIG[no-dns-fallback] = "-Ddns-servers="
-PACKAGECONFIG[nss] = "-Dnss-systemd=true,-Dnss-systemd=false"
+PACKAGECONFIG[nss] = "-Dnss-systemd=true,-Dnss-systemd=false,,libnss-systemd"
 PACKAGECONFIG[nss-mymachines] = "-Dnss-mymachines=true,-Dnss-mymachines=false"
 PACKAGECONFIG[nss-resolve] = "-Dnss-resolve=true,-Dnss-resolve=false"
 PACKAGECONFIG[oomd] = "-Doomd=true,-Doomd=false"
@@ -839,15 +839,31 @@ ALTERNATIVE_LINK_NAME[runlevel] = 
"${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
 pkg_postinst:${PN}:libc-glibc () {
+if ${@bb.utils.contains('PACKAGECONFIG', 'myhostname', 'true', 'false', 
d)}; then
sed -e '/^hosts:/s/\s*\//' \
-   -e 's/\(^hosts:.*\)\(\\)\(.*\)\(\\)\(.*\)/\1\2 
myhostname \3\4\5/' \
-   -i $D${sysconfdir}/nsswitch.conf
+   -e 's/\(^hosts:.*\)\(\\)\(.*\)\(\\)\(.*\)/\1\2 
myhostname \3\4\5/' \
+   -i $D${sysconfdir}/nsswitch.conf
+fi
+if ${@bb.utils.contains('PACKAGECONFIG', 'nss', 'true', 'false', d)}; then
+   sed -e 's#\(^passwd:.*\)#\1 systemd#' \
+   -e 's#\(^group:.*\)#\1 systemd#' \
+   -e 's#\(^shadow:.*\)#\1 systemd#' \
+   -i $D${sysconfdir}/nsswitch.conf
+fi
 }
 
 pkg_prerm:${PN}:libc-glibc () {
+if ${@bb.utils.contains('PACKAGECONFIG', 'myhostname', 'true', 'false', 
d)}; then
sed -e '/^hosts:/s/\s*\//' \
-e '/^hosts:/s/\s*myhostname//' \
-i $D${sysconfdir}/nsswitch.conf
+fi
+if ${@bb.utils.contains('PACKAGECONFIG', 'nss', 'true', 'false', d)}; then
+   sed -e '/^passwd:/s#\s*systemd##' \
+   -e '/^group:/s#\s*systemd##' \
+   -e '/^shadow:/s#\s*systemd##' \
+   -i $D${sysconfdir}/nsswitch.conf
+fi
 }
 
 PACKAGE_WRITE_DEPS += "qemu-native"
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189898): 
https://lists.openembedded.org/g/openembedded-core/message/189898
Mute This Topic: https://lists.openembedded.org/mt/102314885/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] kernel.bbclass: add preceding space in appendVar setting

2023-10-30 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The appendVar setting should have a preceding space, otherwise, when
KERNEL_MODULE_SPLIT is set to "0", we'll sometimes get dependency error
due to lacking of space.

Signed-off-by: Chen Qi 
---
 meta/classes-recipe/kernel.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/kernel.bbclass 
b/meta/classes-recipe/kernel.bbclass
index 2ec9ea2091..5eee87fee9 100644
--- a/meta/classes-recipe/kernel.bbclass
+++ b/meta/classes-recipe/kernel.bbclass
@@ -111,7 +111,7 @@ python __anonymous () {
 d.appendVar('RDEPENDS:%s-image' % kname, ' %s-modules (= 
${EXTENDPKGV})' % kname)
 d.appendVar('RDEPENDS:%s-image-%s' % (kname, typelower), ' 
%s-modules-${KERNEL_VERSION_PKG_NAME} (= ${EXTENDPKGV})' % kname)
 d.setVar('PKG:%s-modules' % kname, 
'%s-modules-${KERNEL_VERSION_PKG_NAME}' % kname)
-d.appendVar('RPROVIDES:%s-modules' % kname, 
'%s-modules-${KERNEL_VERSION_PKG_NAME}' % kname)
+d.appendVar('RPROVIDES:%s-modules' % kname, ' 
%s-modules-${KERNEL_VERSION_PKG_NAME}' % kname)
 
 d.setVar('PKG:%s-image-%s' % (kname,typelower), 
'%s-image-%s-${KERNEL_VERSION_PKG_NAME}' % (kname, typelower))
 d.setVar('ALLOW_EMPTY:%s-image-%s' % (kname, typelower), '1')
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189791): 
https://lists.openembedded.org/g/openembedded-core/message/189791
Mute This Topic: https://lists.openembedded.org/mt/102270002/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: add cpython to CVE_PRODUCT

2023-09-27 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

https://nvd.nist.gov/vuln/detail/CVE-2023-33595 uses 'cpython'.
Although it's currently the only one that uses cpython, let's add
cpython to CVE_PRODUCT, just in case.

Signed-off-by: Chen Qi 
---
 meta/recipes-devtools/python/python3_3.11.5.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3_3.11.5.bb 
b/meta/recipes-devtools/python/python3_3.11.5.bb
index 6c624c9d3d..8e023c7dfb 100644
--- a/meta/recipes-devtools/python/python3_3.11.5.bb
+++ b/meta/recipes-devtools/python/python3_3.11.5.bb
@@ -46,7 +46,7 @@ SRC_URI[sha256sum] = 
"85cd12e9cf1d6d5a45f17f7afe1cebe7ee628d3282281c492e86adf636
 UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P\d+(\.\d+)+).tar"
 UPSTREAM_CHECK_URI = "https://www.python.org/downloads/source/;
 
-CVE_PRODUCT = "python"
+CVE_PRODUCT = "python cpython"
 
 CVE_STATUS[CVE-2007-4559] = "disputed: Upstream consider this expected 
behaviour"
 CVE_STATUS[CVE-2019-18348] = "not-applicable-config: This is not exploitable 
when glibc has CVE-2016-10739 fixed"
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188292): 
https://lists.openembedded.org/g/openembedded-core/message/188292
Mute This Topic: https://lists.openembedded.org/mt/101613209/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] oe-find-native-sysroot: avoid warning message messing things up

2023-09-26 Thread Chen Qi via lists.openembedded.org
Just noticed your patches. Yes, this patch is not needed.

Regards,
Qi

From: Peter Kjellerstedt 
Sent: Tuesday, September 26, 2023 9:10 PM
To: Jose Quaresma ; Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: RE: [OE-core][PATCH] oe-find-native-sysroot: avoid warning message 
messing things up

NAK

This is no longer needed since commit 6b7883533 (bitbake-getvar: Make --value 
imply –quiet) landed in bitbake.

//Peter

From: 
openembedded-core@lists.openembedded.org<mailto:openembedded-core@lists.openembedded.org>
 
mailto:openembedded-core@lists.openembedded.org>>
 On Behalf Of Jose Quaresma
Sent: den 26 september 2023 12:21
To: qi.c...@windriver.com<mailto:qi.c...@windriver.com>
Cc: 
openembedded-core@lists.openembedded.org<mailto:openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] oe-find-native-sysroot: avoid warning message 
messing things up

Hi Chen,

I have raised this when it lands
https://lists.openembedded.org/g/openembedded-core/message/187378<https://urldefense.com/v3/__https:/lists.openembedded.org/g/openembedded-core/message/187378__;!!AjveYdw8EvQ!adHqVF0IzEspqiDUyqlT-QC4Rdy_B_YAK8youCQ60fa96rN8B3AxjRCZmJ2VY3fr0uDPRoNXqypFyOI9RkIgINwfzZE$>

Tested.by<https://urldefense.com/v3/__http:/Tested.by__;!!AjveYdw8EvQ!adHqVF0IzEspqiDUyqlT-QC4Rdy_B_YAK8youCQ60fa96rN8B3AxjRCZmJ2VY3fr0uDPRoNXqypFyOI9RkIgVUqchqA$>:
 Jose Quaresma mailto:quaresma.j...@gmail.com>>
Jose
Chen Qi via 
lists.openembedded.org<https://urldefense.com/v3/__http:/lists.openembedded.org__;!!AjveYdw8EvQ!adHqVF0IzEspqiDUyqlT-QC4Rdy_B_YAK8youCQ60fa96rN8B3AxjRCZmJ2VY3fr0uDPRoNXqypFyOI9RkIgL6RxaeA$>
 
mailto:windriver@lists.openembedded.org>>
 escreveu no dia terça, 26/09/2023 à(s) 11:15:
From: Chen Qi mailto:qi.c...@windriver.com>>

Add '-q' option to bitbake-getvar to avoid warning messages contaminating
the actual result.

Signed-off-by: Chen Qi mailto:qi.c...@windriver.com>>
---
 scripts/oe-find-native-sysroot | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot
index 6228efcbee..541318b461 100755
--- a/scripts/oe-find-native-sysroot
+++ b/scripts/oe-find-native-sysroot
@@ -38,7 +38,7 @@ fi
 # Global vars
 set_oe_native_sysroot(){
 echo "Getting sysroot..."
-OECORE_NATIVE_SYSROOT=$(bitbake-getvar -r $1 --value STAGING_DIR_NATIVE)
+OECORE_NATIVE_SYSROOT=$(bitbake-getvar -q -r $1 --value STAGING_DIR_NATIVE)
 }

 if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
--
2.40.0




--
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188254): 
https://lists.openembedded.org/g/openembedded-core/message/188254
Mute This Topic: https://lists.openembedded.org/mt/101592501/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] oe-find-native-sysroot: avoid warning message messing things up

2023-09-26 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Add '-q' option to bitbake-getvar to avoid warning messages contaminating
the actual result.

Signed-off-by: Chen Qi 
---
 scripts/oe-find-native-sysroot | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot
index 6228efcbee..541318b461 100755
--- a/scripts/oe-find-native-sysroot
+++ b/scripts/oe-find-native-sysroot
@@ -38,7 +38,7 @@ fi
 # Global vars
 set_oe_native_sysroot(){
 echo "Getting sysroot..."
-OECORE_NATIVE_SYSROOT=$(bitbake-getvar -r $1 --value STAGING_DIR_NATIVE)
+OECORE_NATIVE_SYSROOT=$(bitbake-getvar -q -r $1 --value STAGING_DIR_NATIVE)
 }
 
 if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188242): 
https://lists.openembedded.org/g/openembedded-core/message/188242
Mute This Topic: https://lists.openembedded.org/mt/101592501/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 1/2] multilib.conf: explicitly make MULTILIB_VARIANTS vardeps on MULTILIBS

2023-09-18 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

This patch is to ensure recipes get rebuilt correctly and avoid
incorrect sstate cache reuse when toggling multilib.

The following steps show one example of such incorrect sstate cache reuse.
1. enable multilib && bitbake  -c populate_sdk
2. disable multilib && bitbake  -c populate_sdk

The error message is as below:
Error:
 Problem: conflicting requests
   - nothing provides binutils-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
   - nothing provides gcc-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
   - nothing provides gdb-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
 (try to add '--skip-broken' to skip uninstallable packages)

We get this error because packagegroup-cross-canadian recipe is
not rebuilt when it should be.

Current codes have tracked the dependency to MULTILIB_VARIANTS, as
shown in the following chain:
RDEPENDS:packagegroup-cross-canadian-intel-x86-64 ->
all_multilib_tune_values -> MULTILIB_VARIANTS.

However, MULTILIB_VARIANTS cannot automatically depend on MULTILIBS.
See some results from 'bitbake-dumpsigs' below:
List of dependencies for variable MULTILIB_VARIANTS is ['extend_variants']
Variable MULTILIB_VARIANTS value is 
${@extend_variants(d,'MULTILIBS','multilib')}

It's obvious that the value of MULTILIB_VARIANTS depend on the
value of MULTILIBS, so let's set this dependency manually.

(From OE-Core rev: 9f47d8eb51816d16078a23c0cef4d697555f913f)

Signed-off-by: Chen Qi 
Signed-off-by: Alexandre Belloni 
Signed-off-by: Richard Purdie 
---
 meta/conf/multilib.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/multilib.conf b/meta/conf/multilib.conf
index 7f3b9463ef..ef3605a73d 100644
--- a/meta/conf/multilib.conf
+++ b/meta/conf/multilib.conf
@@ -2,6 +2,7 @@
 baselib = "${@d.getVar('BASE_LIB:tune-' + (d.getVar('DEFAULTTUNE') or 
'INVALID')) or d.getVar('BASELIB')}"
 
 MULTILIB_VARIANTS = "${@extend_variants(d,'MULTILIBS','multilib')}"
+MULTILIB_VARIANTS[vardeps] += "MULTILIBS"
 MULTILIB_SAVE_VARNAME = "DEFAULTTUNE TARGET_ARCH TARGET_SYS TARGET_VENDOR"
 
 MULTILIBS ??= "multilib:lib32"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187848): 
https://lists.openembedded.org/g/openembedded-core/message/187848
Mute This Topic: https://lists.openembedded.org/mt/101447919/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 2/2] gcc-crosssdk: ignore MULTILIB_VARIANTS in signature computation

2023-09-18 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The gcc_multilib_setup function is a function that is run at the
do_configure step, so it's counted into the signature computation.
The MULTILIB_VARIANTS this function uses is also extracted to be
taken into consideration. After the change of setting MULTILIB_VARIANTS
explictly vardeps on MULTILIBS, the change of MULTILIBS changes the
signature, thus causing rebuilding. However, in case of gcc-crosssdk,
the setting of multilib should have no effect on it, as it's used
to build nativesdk packages, not the target packages. So ignore
MULTILIB_VARIANTS in signature computation. This fixes oe-selftest
case sstatetests.SStateHashSameSigs2.test_sstate_nativesdk_samesigs_multilib.

(From OE-Core rev: 537c71162a711dec32a63a657c4b101269a3e267)

Signed-off-by: Chen Qi 
Signed-off-by: Alexandre Belloni 
Signed-off-by: Richard Purdie 
---
 meta/recipes-devtools/gcc/gcc-crosssdk.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/gcc/gcc-crosssdk.inc 
b/meta/recipes-devtools/gcc/gcc-crosssdk.inc
index bd2e71d63f..74c4537f4f 100644
--- a/meta/recipes-devtools/gcc/gcc-crosssdk.inc
+++ b/meta/recipes-devtools/gcc/gcc-crosssdk.inc
@@ -10,3 +10,5 @@ GCCMULTILIB = "--disable-multilib"
 
 DEPENDS = "virtual/${TARGET_PREFIX}binutils-crosssdk gettext-native 
${NATIVEDEPS}"
 PROVIDES = "virtual/${TARGET_PREFIX}gcc-crosssdk 
virtual/${TARGET_PREFIX}g++-crosssdk"
+
+gcc_multilib_setup[vardepsexclude] = "MULTILIB_VARIANTS"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187847): 
https://lists.openembedded.org/g/openembedded-core/message/187847
Mute This Topic: https://lists.openembedded.org/mt/101447917/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] oe-depends-dot: improve '-w' behavior

2023-08-30 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The '-w' option is not giving very helpful information. For example,
if we add 'spice' to IMAGE_INSTALL, bitbake -g core-image-minimal,
and then run `oe-depends-dot -k nspr -w task-depends.dot', the result is:

  $ oe-depends-dot -k nspr -w task-depends.dot
  Because: core-image-minimal nss
  core-image-minimal -> nss -> nspr

The result is not showing the full dependency chain which brings in nspr.
With this patch, the result is:

  $ oe-depends-dot -k nspr -w task-depends.dot
  Because: core-image-minimal nss libcacard spice
  core-image-minimal -> spice -> libcacard -> nss -> nspr

This patch also fixes a typo in help message: recipe-depends.dot -> 
task-depends.dot.

Signed-off-by: Chen Qi 
---
 scripts/oe-depends-dot | 13 +
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/scripts/oe-depends-dot b/scripts/oe-depends-dot
index 1c2d51c6ec..d02ee455f6 100755
--- a/scripts/oe-depends-dot
+++ b/scripts/oe-depends-dot
@@ -14,7 +14,7 @@ import re
 class Dot(object):
 def __init__(self):
 parser = argparse.ArgumentParser(
-description="Analyse recipe-depends.dot generated by bitbake -g",
+description="Analyse task-depends.dot generated by bitbake -g",
 formatter_class=argparse.RawDescriptionHelpFormatter)
 parser.add_argument("dotfile",
 help = "Specify the dotfile", nargs = 1, action='store', 
default='')
@@ -159,9 +159,14 @@ Reduce the .dot file packages only, no tasks:
 
 reverse_deps = []
 if self.args.why:
-for k, v in depends.items():
-if self.args.key in v and not k in reverse_deps:
-reverse_deps.append(k)
+key_list = [self.args.key]
+current_key = self.args.key
+while (len(key_list) != 0):
+current_key = key_list.pop()
+for k, v in depends.items():
+if current_key in v and not k in reverse_deps:
+reverse_deps.append(k)
+key_list.append(k)
 print('Because: %s' % ' '.join(reverse_deps))
 Dot.print_dep_chains(self.args.key, reverse_deps, depends)
 
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186872): 
https://lists.openembedded.org/g/openembedded-core/message/186872
Mute This Topic: https://lists.openembedded.org/mt/101048342/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] stress-ng: disable DEBUG_BUILD

2023-08-30 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

We get do_compile error when DEBUG_BUILD is enabled:

  error: inlining failed in call to 'always_inline' '_mm512_storeu_si512': 
target specific option mismatch

To reproduce the issue, set the following lines in local.conf
and then `bitbake stress-ng'.

  MACHINE = "qemux86-64"
  DEBUG_BUILD = "1"

A new issue is filed for stress-ng to track it:
https://github.com/ColinIanKing/stress-ng/issues/315

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb 
b/meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb
index 6e5665cc3b..af8433975b 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb
@@ -31,3 +31,6 @@ do_install() {
 oe_runmake DESTDIR=${D} BINDIR=${bindir} install
 ln -s stress-ng ${D}${bindir}/stress
 }
+
+# upstream issue: https://github.com/ColinIanKing/stress-ng/issues/315
+DEBUG_BUILD = "0"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186869): 
https://lists.openembedded.org/g/openembedded-core/message/186869
Mute This Topic: https://lists.openembedded.org/mt/101046959/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 3/3] stress-ng: upgrade 0.15.08 -> 0.16.04

2023-08-29 Thread Chen Qi via lists.openembedded.org

This upgrade introduces a build failure when DEBUG_BUILD is enabled.
I've sent out a patch to disable it in this recipe as a workaround.
I've also filed a new issue for stress-ng upstream: 
https://github.com/ColinIanKing/stress-ng/issues/315


Regards,
Qi

On 8/17/23 15:38, Anuj Mittal wrote:

Signed-off-by: Anuj Mittal 
---
  .../stress-ng/{stress-ng_0.15.08.bb => stress-ng_0.16.04.bb}| 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
  rename meta/recipes-extended/stress-ng/{stress-ng_0.15.08.bb => 
stress-ng_0.16.04.bb} (94%)

diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.15.08.bb 
b/meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb
similarity index 94%
rename from meta/recipes-extended/stress-ng/stress-ng_0.15.08.bb
rename to meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb
index 9952c4ef8a5..6e5665cc3b9 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.15.08.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.16.04.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
  
  SRC_URI = "git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \

 "
-SRCREV = "4fc205238518cdaf80cf18e8bd411708f7ba3856"
+SRCREV = "95777d7cf32de9fc88c452a968ae2ae23ed269c2"
  S = "${WORKDIR}/git"
  
  DEPENDS = "coreutils-native libbsd"







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186868): 
https://lists.openembedded.org/g/openembedded-core/message/186868
Mute This Topic: https://lists.openembedded.org/mt/100796322/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] uninative.bbclass: sync to use UNINATIVE_STAGING_DIR

2023-08-29 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

All other places in this bbclass are using ${UNINATIVE_STAGING_DIR}-uninative,
we should sync to use that too, although UNINATIVE_STAGING_DIR's default
value is STAGING_DIR.

Signed-off-by: Chen Qi 
---
 meta/classes-global/uninative.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-global/uninative.bbclass 
b/meta/classes-global/uninative.bbclass
index 366f7ac793..9630726f33 100644
--- a/meta/classes-global/uninative.bbclass
+++ b/meta/classes-global/uninative.bbclass
@@ -146,7 +146,7 @@ def enable_uninative(d):
 d.appendVar("BUILD_LDFLAGS", " -Wl,--allow-shlib-undefined 
-Wl,--dynamic-linker=${UNINATIVE_LOADER}")
 d.appendVarFlag("BUILD_LDFLAGS", "vardepvalueexclude", "| 
-Wl,--allow-shlib-undefined -Wl,--dynamic-linker=${UNINATIVE_LOADER}")
 d.appendVarFlag("BUILD_LDFLAGS", "vardepsexclude", "UNINATIVE_LOADER")
-d.prependVar("PATH", 
"${STAGING_DIR}-uninative/${BUILD_ARCH}-linux${bindir_native}:")
+d.prependVar("PATH", 
"${UNINATIVE_STAGING_DIR}-uninative/${BUILD_ARCH}-linux${bindir_native}:")
 
 python uninative_changeinterp () {
 import subprocess
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186850): 
https://lists.openembedded.org/g/openembedded-core/message/186850
Mute This Topic: https://lists.openembedded.org/mt/101026853/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] cmake.bbclass: fix allarch override syntax

2023-08-21 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The override syntax should be ":allarch" instead of "_allarch".

Signed-off-by: Chen Qi 
---
 meta/classes-recipe/cmake.bbclass | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/classes-recipe/cmake.bbclass 
b/meta/classes-recipe/cmake.bbclass
index 0dda104a69..ea836d5c0d 100644
--- a/meta/classes-recipe/cmake.bbclass
+++ b/meta/classes-recipe/cmake.bbclass
@@ -51,10 +51,10 @@ OECMAKE_CXX_COMPILER ?= "${@oecmake_map_compiler('CXX', 
d)[0]}"
 OECMAKE_CXX_COMPILER_LAUNCHER ?= "${@oecmake_map_compiler('CXX', d)[1]}"
 
 # clear compiler vars for allarch to avoid sig hash difference
-OECMAKE_C_COMPILER_allarch = ""
-OECMAKE_C_COMPILER_LAUNCHER_allarch = ""
-OECMAKE_CXX_COMPILER_allarch = ""
-OECMAKE_CXX_COMPILER_LAUNCHER_allarch = ""
+OECMAKE_C_COMPILER:allarch = ""
+OECMAKE_C_COMPILER_LAUNCHER:allarch = ""
+OECMAKE_CXX_COMPILER:allarch = ""
+OECMAKE_CXX_COMPILER_LAUNCHER:allarch = ""
 
 OECMAKE_RPATH ?= ""
 OECMAKE_PERLNATIVE_DIR ??= ""
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186490): 
https://lists.openembedded.org/g/openembedded-core/message/186490
Mute This Topic: https://lists.openembedded.org/mt/100887367/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] cmake: drop OE specific environment variable support

2023-08-21 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

CMAKE_TOOLCHAIN_FILE is now also a supported environment
variable, we can export it directly. There's no need to
use a OE specific patch to add OE_CMAKE_TOOLCHAIN_FILE
support.

Signed-off-by: Chen Qi 
---
 .../cmake/cmake-native_3.26.4.bb  |  1 -
 ...stem-use-oe-environment-vars-to-load.patch | 44 ---
 .../cmake/cmake/environment.d-cmake.sh|  2 +-
 meta/recipes-devtools/cmake/cmake_3.26.4.bb   |  1 -
 4 files changed, 1 insertion(+), 47 deletions(-)
 delete mode 100644 
meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch

diff --git a/meta/recipes-devtools/cmake/cmake-native_3.26.4.bb 
b/meta/recipes-devtools/cmake/cmake-native_3.26.4.bb
index 2177aa81a4..26a3331cb0 100644
--- a/meta/recipes-devtools/cmake/cmake-native_3.26.4.bb
+++ b/meta/recipes-devtools/cmake/cmake-native_3.26.4.bb
@@ -5,7 +5,6 @@ DEPENDS += "bzip2-replacement-native xz-native zlib-native 
ncurses-native zstd-n
 
 SRC_URI += "file://OEToolchainConfig.cmake \
 file://environment.d-cmake.sh \
-
file://0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch \
 
file://0005-Disable-use-of-ext2fs-ext2_fs.h-by-cmake-s-internal-.patch \
 file://0001-CMakeLists.txt-disable-USE_NGHTTP2.patch \
 "
diff --git 
a/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch
 
b/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch
deleted file mode 100644
index d13c367e78..00
--- 
a/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch
+++ /dev/null
@@ -1,44 +0,0 @@
-From 5acfcb2aba1a5641d390558fdf288373f5e39cb5 Mon Sep 17 00:00:00 2001
-From: Cody P Schafer 
-Date: Thu, 27 Apr 2017 11:35:05 -0400
-Subject: [PATCH] CMakeDetermineSystem: use oe environment vars to load default
- toolchain file in sdk
-
-Passing the toolchain by:
-
- - shell aliases does not work if cmake is called by a script
- - unconditionally by a wrapper script causes cmake to believe it is
-   configuring things when it is not (for example, `cmake --build` breaks).
-
-The OE_CMAKE_TOOLCHAIN_FILE variable is only used as a default if no
-toolchain is explicitly specified.
-
-Setting the CMAKE_TOOLCHAIN_FILE cmake variable is marked as cached
-because '-D' options are cache entries themselves.
-
-Upstream-Status: Inappropriate [oe-core specific]
-Signed-off-by: Cody P Schafer 
-Signed-off-by: Otavio Salvador 
-

- Modules/CMakeDetermineSystem.cmake | 7 +++
- 1 file changed, 7 insertions(+)
-
-diff --git a/Modules/CMakeDetermineSystem.cmake 
b/Modules/CMakeDetermineSystem.cmake
-index 2c2c2ac3..fae4f97f 100644
 a/Modules/CMakeDetermineSystem.cmake
-+++ b/Modules/CMakeDetermineSystem.cmake
-@@ -112,6 +112,13 @@ else()
-   endif()
- endif()
- 
-+if(NOT DEFINED CMAKE_TOOLCHAIN_FILE)
-+  if(DEFINED ENV{OE_CMAKE_TOOLCHAIN_FILE})
-+set(CMAKE_TOOLCHAIN_FILE "$ENV{OE_CMAKE_TOOLCHAIN_FILE}" CACHE FILEPATH 
"toolchain file")
-+message(STATUS "Toolchain file defaulted to '${CMAKE_TOOLCHAIN_FILE}'")
-+  endif()
-+endif()
-+
- # if a toolchain file is used, the user wants to cross compile.
- # in this case read the toolchain file and keep the CMAKE_HOST_SYSTEM_*
- # variables around so they can be used in CMakeLists.txt.
diff --git a/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh 
b/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh
index 7bdb19fb6c..c94b6bb3e3 100644
--- a/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh
+++ b/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh
@@ -1,2 +1,2 @@
-export 
OE_CMAKE_TOOLCHAIN_FILE="$OECORE_NATIVE_SYSROOT/usr/share/cmake/OEToolchainConfig.cmake"
+export 
CMAKE_TOOLCHAIN_FILE="$OECORE_NATIVE_SYSROOT/usr/share/cmake/OEToolchainConfig.cmake"
 export OE_CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX="`echo $OECORE_BASELIB | sed -e 
s/lib//`"
diff --git a/meta/recipes-devtools/cmake/cmake_3.26.4.bb 
b/meta/recipes-devtools/cmake/cmake_3.26.4.bb
index bb7ed83e30..ae29a3a945 100644
--- a/meta/recipes-devtools/cmake/cmake_3.26.4.bb
+++ b/meta/recipes-devtools/cmake/cmake_3.26.4.bb
@@ -9,7 +9,6 @@ SRC_URI:append:class-nativesdk = " \
 file://SDKToolchainConfig.cmake.template \
 file://cmake-setup.py \
 file://environment.d-cmake.sh \
-file://0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch \
 "
 
 LICENSE:append = " & BSD-1-Clause & MIT"
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186489): 
https://lists.openembedded.org/g/openembedded-core/message/186489
Mute This Topic: https://lists.openembedded.org/mt/100887366/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] systemd issue with network commandline config and 6.4 kernel

2023-08-08 Thread Chen Qi via lists.openembedded.org
I found some clue, but not the root cause yet.
The eth0 is renamed to enp0s2 by 80-net-setup-link.rules udev rule in systemd. 
And the connman.conf only blacklists eth0.

The related log is:
Aug 08 15:18:16 qemux86-64 kernel[213]: [1.727332] virtio_net virtio0 
enp0s2: renamed from eth0 (while UP)

The systemd udev configuration file is:
root@qemux86-64:~# cat /lib/udev/rules.d/80-net-setup-link.rules
# do not edit this file, it will be overwritten on update
SUBSYSTEM!="net", GOTO="net_setup_link_end"
IMPORT{builtin}="path_id"
ACTION=="remove", GOTO="net_setup_link_end"
IMPORT{builtin}="net_setup_link"
NAME=="", ENV{ID_NET_NAME}!="", NAME="$env{ID_NET_NAME}"
LABEL="net_setup_link_end"

And the connman configuration file is:
root@qemux86-64:~# cat /etc/connman/main.conf
[General]
NetworkInterfaceBlacklist = eth0

In contrary, with 6.1 kernel, the renaming failed with the following message:
Aug 08 15:29:58 qemux86-64 (udev-worker)[206]: enp0s2: Network interface 'eth0' 
is already up, cannot rename to 'enp0s2'.

Maybe some changes in new kernel allows renaming network interface while it's 
up?

Regards,
Qi


-Original Message-
From: openembedded-core@lists.openembedded.org 
 On Behalf Of Richard Purdie
Sent: Tuesday, August 8, 2023 7:51 PM
To: openembedded-core 
Cc: Luca Boccassi ; Alexandre Belloni 

Subject: [OE-core] systemd issue with network commandline config and 6.4 kernel

Hi,

We'd like to switch to the 6.4 kernel and there are two blockers. One of them 
is that systemd appears to be breaking the network device config with 6.4 
kernels.

This happens with core-image-sato but not with core-image-minimal.

In the sato image, I can see the kernel gets the ip= commandline parameters and 
sets up the network (IP-Config: Complete: ) in the dmesg logs. When I look at the "ip addr" config, that
setup is gone though.

The autobuilder manifestation of this is for example:

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/7580/steps/23/logs/stdio

i.e. ping fails.

Does anyone know why updating from the 6.1 kernel to the the 6.4 kernel would 
cause this only for systemd images?

I couldn't spot anything in the journal but I'm not sure I'd know what to look 
for...

Thanks,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#185664): 
https://lists.openembedded.org/g/openembedded-core/message/185664
Mute This Topic: https://lists.openembedded.org/mt/100620069/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] openssh: sync with upstream's default

2023-08-03 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

This change sync the contents of this file with upstream's
ssh_config except for the locally added line
'Include /etc/ssh/ssh_config.d/*.conf'.

More specifically the ForwardXXX options are disabled by default,
this sync with what ssh_config(5) says about these two items.

In addition, the RSAAuthentication items are removed as they are v1 protocol.
See the contents of Changelog file in openssh project as below:
"""
commit bfe19197a92b7916f64a121fbd3c179abf15e218
Author: Darren Tucker 
Date:   Fri Jul 2 15:43:28 2021 +1000

Remove now-unused SSHv1 enums.

sRhostsRSAAuthentication and sRSAAuthentication are protocol 1 options
and are no longer used.
"""

Signed-off-by: Chen Qi 
---
 meta/recipes-connectivity/openssh/openssh/ssh_config | 8 +++-
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-connectivity/openssh/openssh/ssh_config 
b/meta/recipes-connectivity/openssh/openssh/ssh_config
index ca70f37375..cb2774a163 100644
--- a/meta/recipes-connectivity/openssh/openssh/ssh_config
+++ b/meta/recipes-connectivity/openssh/openssh/ssh_config
@@ -19,11 +19,9 @@
 
 Include /etc/ssh/ssh_config.d/*.conf
 
-Host *
-  ForwardAgent yes
-  ForwardX11 yes
-#   RhostsRSAAuthentication no
-#   RSAAuthentication yes
+# Host *
+#   ForwardAgent no
+#   ForwardX11 no
 #   PasswordAuthentication yes
 #   HostbasedAuthentication no
 #   GSSAPIAuthentication no
-- 
2.40.0


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

2023-08-02 Thread Chen Qi via lists.openembedded.org
When ' include conf/bblock.conf' line can be more flexibly added to/removed 
from local.conf, is there some specific reason why we should put it in 
bitbake.conf by default?

Regards,
Qi

-Original Message-
From: openembedded-core@lists.openembedded.org 
 On Behalf Of Julien Stephan
Sent: Wednesday, August 2, 2023 10:24 PM
To: openembedded-core@lists.openembedded.org
Cc: Julien Stephan 
Subject: [OE-core] [PATCH v4 0/5] Add bblock helper scripts

Hi all,

This is v4 for bblock script.

Improvement from v3:
* Add self test
* Add a new "info" level for SIGGEN_LOCKEDSIGS_TASKSIG_CHECK: this allows to
  display a Note when recipe contains locked task(s)

Limitations:
* Silently does nothing if given task doesn't exist
* Silently does nothing when resetting a recipe that doesn't exist

Improvement from v2:
* Add a function in bb.cooker to compute task signatures
* Replace the findSigInfo function by the new created one. This has the
  following advantages:
* findSigInfo needs the task to be already built to get the siginfo
  file, meaning we cannot lock a recipe on a fresh build
* we can now generate the signatures for all available task of a given
  recipe
* Check if a given task is already locked. If so, don't duplicate
  entry in bblock.conf

Limitations:
* Needs to taint tasks that are locked, to display a warning
* I may be still missing some checks on user input
* Silently does nothing if given task doesn't exist
* Silently does nothing when resetting a recipe that doesn't exist

I did some tests using qemux86-64 and qemuarm but I may be missing some corner 
cases.

Improvement from V1:
* Signatures are now package architecture specific meaning that if you
  switch MACHINE, the lock sig will not be taken into account
* I added the -r option to unlock recipes
* I added a -d option to display the current bblock.conf
* Added an include directive for conf/bblock.conf inside bitbake.conf
* Added -t option to specify the tasks to lock/unlock

Limitations:
* I may be still missing some checks on user input
* I need to find a way to get the list of tasks ( by default still lock
  only the do_compile for now, unless -t is specified)
* Do not check if a particular recipe/task is already locked when trying
  to add lock. So entries may appear multiple times
* We still need the signature of the tasks to be already computed before
  locking. Need to find a way to generate it if missing

V3: https://lists.openembedded.org/g/openembedded-core/message/184932
V2: https://lists.openembedded.org/g/openembedded-core/message/184697
V1: https://lists.openembedded.org/g/openembedded-core/message/184584

My branch is available here [1]

Cheers
Julien

[1]: https://git.yoctoproject.org/poky-contrib/commit/?h=jstephan/bblock
Julien Stephan (5):
  bitbake.conf: include bblock.conf
  bitbake: cooker: add a new function to retrieve task signatures
  sstatesig: add a new info level for SIGGEN_LOCKEDSIGS_TASKSIG_CHECK
  scripts/bblock: add a script to lock/unlock recipes
  oeqa/selftest/bblock: add self test for bblock tool

 bitbake/lib/bb/command.py  |   6 +
 bitbake/lib/bb/cooker.py   |  16 +++
 bitbake/lib/bb/event.py|   8 ++
 meta/conf/bitbake.conf |   1 +
 meta/lib/oe/sstatesig.py   |  13 +-
 meta/lib/oeqa/selftest/cases/bblock.py | 146 
 scripts/bblock | 182 +
 7 files changed, 371 insertions(+), 1 deletion(-)  create mode 100644 
meta/lib/oeqa/selftest/cases/bblock.py
 create mode 100755 scripts/bblock

--
2.41.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#185449): 
https://lists.openembedded.org/g/openembedded-core/message/185449
Mute This Topic: https://lists.openembedded.org/mt/100506390/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 V2 2/2] gcc-crosssdk: ignore MULTILIB_VARIANTS in signature computation

2023-07-31 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The gcc_multilib_setup function is a function that is run at the
do_configure step, so it's counted into the signature computation.
The MULTILIB_VARIANTS this function uses is also extracted to be
taken into consideration. After the change of setting MULTILIB_VARIANTS
explictly vardeps on MULTILIBS, the change of MULTILIBS changes the
signature, thus causing rebuilding. However, in case of gcc-crosssdk,
the setting of multilib should have no effect on it, as it's used
to build nativesdk packages, not the target packages. So ignore
MULTILIB_VARIANTS in signature computation. This fixes oe-selftest
case sstatetests.SStateHashSameSigs2.test_sstate_nativesdk_samesigs_multilib.

Signed-off-by: Chen Qi 
---
 meta/recipes-devtools/gcc/gcc-crosssdk.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/gcc/gcc-crosssdk.inc 
b/meta/recipes-devtools/gcc/gcc-crosssdk.inc
index bd65b1fed2..7eaad2314c 100644
--- a/meta/recipes-devtools/gcc/gcc-crosssdk.inc
+++ b/meta/recipes-devtools/gcc/gcc-crosssdk.inc
@@ -10,3 +10,5 @@ GCCMULTILIB = "--disable-multilib"
 
 DEPENDS = "virtual/${TARGET_PREFIX}binutils gettext-native ${NATIVEDEPS}"
 PROVIDES = "virtual/${TARGET_PREFIX}gcc virtual/${TARGET_PREFIX}g++"
+
+gcc_multilib_setup[vardepsexclude] = "MULTILIB_VARIANTS"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#185184): 
https://lists.openembedded.org/g/openembedded-core/message/185184
Mute This Topic: https://lists.openembedded.org/mt/100475642/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 V2 1/2] multilib.conf: explicitly make MULTILIB_VARIANTS vardeps on MULTILIBS

2023-07-31 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

This patch is to ensure recipes get rebuilt correctly and avoid
incorrect sstate cache reuse when toggling multilib.

The following steps show one example of such incorrect sstate cache reuse.
1. enable multilib && bitbake  -c populate_sdk
2. disable multilib && bitbake  -c populate_sdk

The error message is as below:
Error:
 Problem: conflicting requests
   - nothing provides binutils-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
   - nothing provides gcc-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
   - nothing provides gdb-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
 (try to add '--skip-broken' to skip uninstallable packages)

We get this error because packagegroup-cross-canadian recipe is
not rebuilt when it should be.

Current codes have tracked the dependency to MULTILIB_VARIANTS, as
shown in the following chain:
RDEPENDS:packagegroup-cross-canadian-intel-x86-64 ->
all_multilib_tune_values -> MULTILIB_VARIANTS.

However, MULTILIB_VARIANTS cannot automatically depend on MULTILIBS.
See some results from 'bitbake-dumpsigs' below:
List of dependencies for variable MULTILIB_VARIANTS is ['extend_variants']
Variable MULTILIB_VARIANTS value is 
${@extend_variants(d,'MULTILIBS','multilib')}

It's obvious that the value of MULTILIB_VARIANTS depend on the
value of MULTILIBS, so let's set this dependency manually.

Signed-off-by: Chen Qi 
---
 meta/conf/multilib.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/multilib.conf b/meta/conf/multilib.conf
index 7f3b9463ef..ef3605a73d 100644
--- a/meta/conf/multilib.conf
+++ b/meta/conf/multilib.conf
@@ -2,6 +2,7 @@
 baselib = "${@d.getVar('BASE_LIB:tune-' + (d.getVar('DEFAULTTUNE') or 
'INVALID')) or d.getVar('BASELIB')}"
 
 MULTILIB_VARIANTS = "${@extend_variants(d,'MULTILIBS','multilib')}"
+MULTILIB_VARIANTS[vardeps] += "MULTILIBS"
 MULTILIB_SAVE_VARNAME = "DEFAULTTUNE TARGET_ARCH TARGET_SYS TARGET_VENDOR"
 
 MULTILIBS ??= "multilib:lib32"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#185183): 
https://lists.openembedded.org/g/openembedded-core/message/185183
Mute This Topic: https://lists.openembedded.org/mt/100475641/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] ncurses: fix CVE-2023-29491

2023-07-30 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Backport patch to fix CVE-2023-29491.

Signed-off-by: Chen Qi 
---
 .../files/0001-Fix-CVE-2023-29491.patch   | 462 ++
 meta/recipes-core/ncurses/ncurses_6.4.bb  |   1 +
 2 files changed, 463 insertions(+)
 create mode 100644 
meta/recipes-core/ncurses/files/0001-Fix-CVE-2023-29491.patch

diff --git a/meta/recipes-core/ncurses/files/0001-Fix-CVE-2023-29491.patch 
b/meta/recipes-core/ncurses/files/0001-Fix-CVE-2023-29491.patch
new file mode 100644
index 00..1232c8c2a8
--- /dev/null
+++ b/meta/recipes-core/ncurses/files/0001-Fix-CVE-2023-29491.patch
@@ -0,0 +1,462 @@
+From 3d54a41f12e9aa059f06e66e72d872f2283395b6 Mon Sep 17 00:00:00 2001
+From: Chen Qi 
+Date: Sun, 30 Jul 2023 21:14:00 -0700
+Subject: [PATCH] Fix CVE-2023-29491
+
+CVE: CVE-2023-29491
+
+Upstream-Status: Backport 
[http://ncurses.scripts.mit.edu/?p=ncurses.git;a=commitdiff;h=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56]
+
+Signed-off-by: Chen Qi 
+---
+ ncurses/tinfo/lib_tgoto.c  |  10 +++-
+ ncurses/tinfo/lib_tparm.c  | 116 -
+ ncurses/tinfo/read_entry.c |   3 +
+ progs/tic.c|   6 ++
+ progs/tparm_type.c |   9 +++
+ progs/tparm_type.h |   2 +
+ progs/tput.c   |  61 ---
+ 7 files changed, 185 insertions(+), 22 deletions(-)
+
+diff --git a/ncurses/tinfo/lib_tgoto.c b/ncurses/tinfo/lib_tgoto.c
+index 9cf5e100..c50ed4df 100644
+--- a/ncurses/tinfo/lib_tgoto.c
 b/ncurses/tinfo/lib_tgoto.c
+@@ -207,6 +207,14 @@ tgoto(const char *string, int x, int y)
+   result = tgoto_internal(string, x, y);
+ else
+ #endif
+-  result = TIPARM_2(string, y, x);
++if ((result = TIPARM_2(string, y, x)) == NULL) {
++  /*
++   * Because termcap did not provide a more general solution such as
++   * tparm(), it was necessary to handle single-parameter capabilities
++   * using tgoto().  The internal _nc_tiparm() function returns a NULL
++   * for that case; retry for the single-parameter case.
++   */
++  result = TIPARM_1(string, y);
++}
+ returnPtr(result);
+ }
+diff --git a/ncurses/tinfo/lib_tparm.c b/ncurses/tinfo/lib_tparm.c
+index d9bdfd8f..a10a3877 100644
+--- a/ncurses/tinfo/lib_tparm.c
 b/ncurses/tinfo/lib_tparm.c
+@@ -1086,6 +1086,64 @@ tparam_internal(TPARM_STATE *tps, const char *string, 
TPARM_DATA *data)
+ return (TPS(out_buff));
+ }
+ 
++#ifdef CUR
++/*
++ * Only a few standard capabilities accept string parameters.  The others that
++ * are parameterized accept only numeric parameters.
++ */
++static bool
++check_string_caps(TPARM_DATA *data, const char *string)
++{
++bool result = FALSE;
++
++#define CHECK_CAP(name) (VALID_STRING(name) && !strcmp(name, string))
++
++/*
++ * Disallow string parameters unless we can check them against a terminal
++ * description.
++ */
++if (cur_term != NULL) {
++  int want_type = 0;
++
++  if (CHECK_CAP(pkey_key))
++  want_type = 2;  /* function key #1, type string #2 */
++  else if (CHECK_CAP(pkey_local))
++  want_type = 2;  /* function key #1, execute string #2 */
++  else if (CHECK_CAP(pkey_xmit))
++  want_type = 2;  /* function key #1, transmit string #2 */
++  else if (CHECK_CAP(plab_norm))
++  want_type = 2;  /* label #1, show string #2 */
++  else if (CHECK_CAP(pkey_plab))
++  want_type = 6;  /* function key #1, type string #2, show string 
#3 */
++#if NCURSES_XNAMES
++  else {
++  char *check;
++
++  check = tigetstr("Cs");
++  if (CHECK_CAP(check))
++  want_type = 1;  /* style #1 */
++
++  check = tigetstr("Ms");
++  if (CHECK_CAP(check))
++  want_type = 3;  /* storage unit #1, content #2 */
++  }
++#endif
++
++  if (want_type == data->tparm_type) {
++  result = TRUE;
++  } else {
++  T(("unexpected string-parameter"));
++  }
++}
++return result;
++}
++
++#define ValidCap() (myData.tparm_type == 0 || \
++  check_string_caps(, string))
++#else
++#define ValidCap() 1
++#endif
++
+ #if NCURSES_TPARM_VARARGS
+ 
+ NCURSES_EXPORT(char *)
+@@ -1100,7 +1158,7 @@ tparm(const char *string, ...)
+ tps->tname = "tparm";
+ #endif /* TRACE */
+ 
+-if (tparm_setup(cur_term, string, ) == OK) {
++if (tparm_setup(cur_term, string, ) == OK && ValidCap()) {
+   va_list ap;
+ 
+   va_start(ap, string);
+@@ -1135,7 +1193,7 @@ tparm(const char *string,
+ tps->tname = "tparm";
+ #endif /* TRACE */
+ 
+-if (tparm_setup(cur_term, string, ) == OK) {
++if (tparm_setup(cur_term, string, ) == OK && ValidCap()) {
+ 
+   myData.param[0] = a1;
+   myData.param[1] = a2;
+@@ -1166,7 +1224,7 @@ tiparm(const char *string, ...)
+ tps->tname = "tiparm";
+ #endif /* TRACE */
+ 
+-

Re: [OE-core][PATCH] multilib.conf: explicitly make MULTILIB_VARIANTS vardeps on MULTILIBS

2023-07-30 Thread Chen Qi via lists.openembedded.org
Got it. I'll check this failure.

Regards,
Qi

-Original Message-
From: Richard Purdie  
Sent: Saturday, July 29, 2023 6:08 AM
To: Chen, Qi ; openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] multilib.conf: explicitly make MULTILIB_VARIANTS 
vardeps on MULTILIBS

On Thu, 2023-07-27 at 14:15 +0800, Chen Qi via lists.openembedded.org
wrote:
> From: Chen Qi 
> 
> This patch is to ensure recipes get rebuilt correctly and avoid 
> incorrect sstate cache reuse when toggling multilib.
> 
> The following steps show one example of such incorrect sstate cache reuse.
> 1. enable multilib && bitbake  -c populate_sdk 2. disable 
> multilib && bitbake  -c populate_sdk
> 
> The error message is as below:
> Error:
>  Problem: conflicting requests
>- nothing provides binutils-cross-canadian-i686 needed by 
> packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
>- nothing provides gcc-cross-canadian-i686 needed by 
> packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
>- nothing provides gdb-cross-canadian-i686 needed by 
> packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
>  (try to add '--skip-broken' to skip uninstallable packages)
> 
> We get this error because packagegroup-cross-canadian recipe is not 
> rebuilt when it should be.
> 
> Current codes have tracked the dependency to MULTILIB_VARIANTS, as 
> shown in the following chain:
> RDEPENDS:packagegroup-cross-canadian-intel-x86-64 -> 
> all_multilib_tune_values -> MULTILIB_VARIANTS.
> 
> However, MULTILIB_VARIANTS cannot automatically depend on MULTILIBS.
> See some results from 'bitbake-dumpsigs' below:
> List of dependencies for variable MULTILIB_VARIANTS is 
> ['extend_variants'] Variable MULTILIB_VARIANTS value is 
> ${@extend_variants(d,'MULTILIBS','multilib')}
> 
> It's obvious that the value of MULTILIB_VARIANTS depend on the value 
> of MULTILIBS, so let's set this dependency manually.
> 
> Signed-off-by: Chen Qi 
> ---
>  meta/conf/multilib.conf | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/conf/multilib.conf b/meta/conf/multilib.conf index 
> 7f3b9463ef..ef3605a73d 100644
> --- a/meta/conf/multilib.conf
> +++ b/meta/conf/multilib.conf
> @@ -2,6 +2,7 @@
>  baselib = "${@d.getVar('BASE_LIB:tune-' + (d.getVar('DEFAULTTUNE') or 
> 'INVALID')) or d.getVar('BASELIB')}"
>  
>  MULTILIB_VARIANTS = "${@extend_variants(d,'MULTILIBS','multilib')}"
> +MULTILIB_VARIANTS[vardeps] += "MULTILIBS"
>  MULTILIB_SAVE_VARNAME = "DEFAULTTUNE TARGET_ARCH TARGET_SYS TARGET_VENDOR"
>  
>  MULTILIBS ??= "multilib:lib32"

I suspect this resulted in this selftest failure:

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5534/steps/15/logs/stdio

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#185115): 
https://lists.openembedded.org/g/openembedded-core/message/185115
Mute This Topic: https://lists.openembedded.org/mt/100385842/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] multilib.conf: explicitly make MULTILIB_VARIANTS vardeps on MULTILIBS

2023-07-27 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

This patch is to ensure recipes get rebuilt correctly and avoid
incorrect sstate cache reuse when toggling multilib.

The following steps show one example of such incorrect sstate cache reuse.
1. enable multilib && bitbake  -c populate_sdk
2. disable multilib && bitbake  -c populate_sdk

The error message is as below:
Error:
 Problem: conflicting requests
   - nothing provides binutils-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
   - nothing provides gcc-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
   - nothing provides gdb-cross-canadian-i686 needed by 
packagegroup-cross-canadian-intel-x86-64-1.0-r0.x86_64_nativesdk
 (try to add '--skip-broken' to skip uninstallable packages)

We get this error because packagegroup-cross-canadian recipe is
not rebuilt when it should be.

Current codes have tracked the dependency to MULTILIB_VARIANTS, as
shown in the following chain:
RDEPENDS:packagegroup-cross-canadian-intel-x86-64 ->
all_multilib_tune_values -> MULTILIB_VARIANTS.

However, MULTILIB_VARIANTS cannot automatically depend on MULTILIBS.
See some results from 'bitbake-dumpsigs' below:
List of dependencies for variable MULTILIB_VARIANTS is ['extend_variants']
Variable MULTILIB_VARIANTS value is 
${@extend_variants(d,'MULTILIBS','multilib')}

It's obvious that the value of MULTILIB_VARIANTS depend on the
value of MULTILIBS, so let's set this dependency manually.

Signed-off-by: Chen Qi 
---
 meta/conf/multilib.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/multilib.conf b/meta/conf/multilib.conf
index 7f3b9463ef..ef3605a73d 100644
--- a/meta/conf/multilib.conf
+++ b/meta/conf/multilib.conf
@@ -2,6 +2,7 @@
 baselib = "${@d.getVar('BASE_LIB:tune-' + (d.getVar('DEFAULTTUNE') or 
'INVALID')) or d.getVar('BASELIB')}"
 
 MULTILIB_VARIANTS = "${@extend_variants(d,'MULTILIBS','multilib')}"
+MULTILIB_VARIANTS[vardeps] += "MULTILIBS"
 MULTILIB_SAVE_VARNAME = "DEFAULTTUNE TARGET_ARCH TARGET_SYS TARGET_VENDOR"
 
 MULTILIBS ??= "multilib:lib32"
-- 
2.34.1


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

2023-07-26 Thread Chen Qi via lists.openembedded.org
Thanks for the info. I thought it was a stable version. The upgrade was 
intended for resolving CVE: https://nvd.nist.gov/vuln/detail/CVE-2023-29491.
But now it's clear that such version is a development version, I'll just send 
out patch to fix the CVE.

Regards,
Qi

-Original Message-
From: Alexander Kanavin  
Sent: Thursday, July 27, 2023 12:25 PM
To: Chen, Qi 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] ncurses: upgrade to 6.4+20230625

6.4+20230625 is a development snapshot, and not an actual stable release. We 
used to take them but that was due to misunderstanding about ncurses version 
policy. Is there a particular reason to move to it?

Alex

On Thu, 27 Jul 2023 at 04:25, Chen Qi via lists.openembedded.org 
 wrote:
>
> From: Chen Qi 
>
> The license checksum is updated because of the year change, the 
> license itself remains the same.
>
> The exit_prototype.patch is refreshed to avoid patch fuzz error.
>
> The repo is switched back to salsa.debian.org. It was switch from 
> salsa.debian.org to github mirror because, according to the commit 
> message, the github mirror was updated on a daily basis. But things 
> have changed and the github mirror hasn't been updated for months.
> So switch back to use salsa.debian.org.
>
> Signed-off-by: Chen Qi 
> ---
>  meta/recipes-core/ncurses/files/exit_prototype.patch | 10 +-
>  meta/recipes-core/ncurses/ncurses.inc|  4 ++--
>  meta/recipes-core/ncurses/ncurses_6.4.bb |  3 ++-
>  3 files changed, 9 insertions(+), 8 deletions(-)
>
> diff --git a/meta/recipes-core/ncurses/files/exit_prototype.patch 
> b/meta/recipes-core/ncurses/files/exit_prototype.patch
> index fd961512e0..9dddbbccf4 100644
> --- a/meta/recipes-core/ncurses/files/exit_prototype.patch
> +++ b/meta/recipes-core/ncurses/files/exit_prototype.patch
> @@ -1,4 +1,4 @@
> -From 4a769a441d7e57a23017c3037cde3e53fb9f35fe Mon Sep 17 00:00:00 
> 2001
> +From bc917b9bae0b11b02aa0ddd9ed62d9cd78ffc4f7 Mon Sep 17 00:00:00 
> +2001
>  From: Khem Raj 
>  Date: Tue, 30 Aug 2022 15:58:32 -0700
>  Subject: [PATCH] Add needed headers for including mbstate_t and 
> exit() @@ -11,18 +11,18 @@ Signed-off-by: Khem Raj 
>   1 file changed, 2 insertions(+)
>
>  diff --git a/configure b/configure
> -index f377f551..163f8899 100755
> +index c2462f7f..33668cf0 100755
>  --- a/configure
>  +++ b/configure
> -@@ -3423,6 +3423,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext"
> +@@ -3458,6 +3458,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext"
> cat >"conftest.$ac_ext" <<_ACEOF
> - #line 3424 "configure"
> + #line 3459 "configure"
>   #include "confdefs.h"
>  +#include 
>   $ac_declaration
>   int
>   main (void)
> -@@ -13111,6 +13112,7 @@ cat >"conftest.$ac_ext" <<_ACEOF
> +@@ -13526,6 +13527,7 @@ cat >"conftest.$ac_ext" <<_ACEOF
>   #include 
>   #include 
>   #include 
> diff --git a/meta/recipes-core/ncurses/ncurses.inc 
> b/meta/recipes-core/ncurses/ncurses.inc
> index 367f3b19f4..78d6f2619c 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -2,7 +2,7 @@ SUMMARY = "The New Curses library"
>  DESCRIPTION = "SVr4 and XSI-Curses compatible curses library and terminfo 
> tools including tic, infocmp, captoinfo. Supports color, multiple highlights, 
> forms-drawing characters, and automatic recognition of keypad and 
> function-key sequences. Extensions include resizable windows and mouse 
> support on both xterm and Linux console using the gpm library."
>  HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html;
>  LICENSE = "MIT"
> -LIC_FILES_CHKSUM = 
> "file://COPYING;md5=c5a4600fdef86384c41ca33ecc70a4b8;endline=27"
> +LIC_FILES_CHKSUM = 
> "file://COPYING;md5=8f2e5b99d5b6c0e6ee7cb39b992733b6;endline=27"
>  SECTION = "libs"
>  DEPENDS = "ncurses-native"
>  DEPENDS:class-native = ""
> @@ -13,7 +13,7 @@ BINCONFIG = "${bindir}/ncurses5-config 
> ${bindir}/ncursesw5-config \  inherit autotools binconfig-disabled 
> multilib_header pkgconfig
>
>  # Upstream has useful patches at times at 
> ftp://invisible-island.net/ncurses/
> -SRC_URI = "git://github.com/mirror/ncurses.git;protocol=https;branch=master"
> +SRC_URI = 
> "git://salsa.debian.org/debian/ncurses.git;protocol=https;branch=master"
>
>  EXTRA_AUTORECONF = "-I m4"
>
> diff --git a/meta/recipes-core/ncurses/ncurses_6.4.bb 
> b/meta/recipes-core/ncurses/ncurses_6.4.bb
> index 1eb15673d1..b875aee250 100644

[OE-core][PATCH] ncurses: upgrade to 6.4+20230625

2023-07-26 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The license checksum is updated because of the year change, the license
itself remains the same.

The exit_prototype.patch is refreshed to avoid patch fuzz error.

The repo is switched back to salsa.debian.org. It was switch from
salsa.debian.org to github mirror because, according to the commit
message, the github mirror was updated on a daily basis. But things
have changed and the github mirror hasn't been updated for months.
So switch back to use salsa.debian.org.

Signed-off-by: Chen Qi 
---
 meta/recipes-core/ncurses/files/exit_prototype.patch | 10 +-
 meta/recipes-core/ncurses/ncurses.inc|  4 ++--
 meta/recipes-core/ncurses/ncurses_6.4.bb |  3 ++-
 3 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/meta/recipes-core/ncurses/files/exit_prototype.patch 
b/meta/recipes-core/ncurses/files/exit_prototype.patch
index fd961512e0..9dddbbccf4 100644
--- a/meta/recipes-core/ncurses/files/exit_prototype.patch
+++ b/meta/recipes-core/ncurses/files/exit_prototype.patch
@@ -1,4 +1,4 @@
-From 4a769a441d7e57a23017c3037cde3e53fb9f35fe Mon Sep 17 00:00:00 2001
+From bc917b9bae0b11b02aa0ddd9ed62d9cd78ffc4f7 Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Tue, 30 Aug 2022 15:58:32 -0700
 Subject: [PATCH] Add needed headers for including mbstate_t and exit()
@@ -11,18 +11,18 @@ Signed-off-by: Khem Raj 
  1 file changed, 2 insertions(+)
 
 diff --git a/configure b/configure
-index f377f551..163f8899 100755
+index c2462f7f..33668cf0 100755
 --- a/configure
 +++ b/configure
-@@ -3423,6 +3423,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext"
+@@ -3458,6 +3458,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext"
cat >"conftest.$ac_ext" <<_ACEOF
- #line 3424 "configure"
+ #line 3459 "configure"
  #include "confdefs.h"
 +#include 
  $ac_declaration
  int
  main (void)
-@@ -13111,6 +13112,7 @@ cat >"conftest.$ac_ext" <<_ACEOF
+@@ -13526,6 +13527,7 @@ cat >"conftest.$ac_ext" <<_ACEOF
  #include 
  #include 
  #include 
diff --git a/meta/recipes-core/ncurses/ncurses.inc 
b/meta/recipes-core/ncurses/ncurses.inc
index 367f3b19f4..78d6f2619c 100644
--- a/meta/recipes-core/ncurses/ncurses.inc
+++ b/meta/recipes-core/ncurses/ncurses.inc
@@ -2,7 +2,7 @@ SUMMARY = "The New Curses library"
 DESCRIPTION = "SVr4 and XSI-Curses compatible curses library and terminfo 
tools including tic, infocmp, captoinfo. Supports color, multiple highlights, 
forms-drawing characters, and automatic recognition of keypad and function-key 
sequences. Extensions include resizable windows and mouse support on both xterm 
and Linux console using the gpm library."
 HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html;
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://COPYING;md5=c5a4600fdef86384c41ca33ecc70a4b8;endline=27"
+LIC_FILES_CHKSUM = 
"file://COPYING;md5=8f2e5b99d5b6c0e6ee7cb39b992733b6;endline=27"
 SECTION = "libs"
 DEPENDS = "ncurses-native"
 DEPENDS:class-native = ""
@@ -13,7 +13,7 @@ BINCONFIG = "${bindir}/ncurses5-config 
${bindir}/ncursesw5-config \
 inherit autotools binconfig-disabled multilib_header pkgconfig
 
 # Upstream has useful patches at times at ftp://invisible-island.net/ncurses/
-SRC_URI = "git://github.com/mirror/ncurses.git;protocol=https;branch=master"
+SRC_URI = 
"git://salsa.debian.org/debian/ncurses.git;protocol=https;branch=master"
 
 EXTRA_AUTORECONF = "-I m4"
 
diff --git a/meta/recipes-core/ncurses/ncurses_6.4.bb 
b/meta/recipes-core/ncurses/ncurses_6.4.bb
index 1eb15673d1..b875aee250 100644
--- a/meta/recipes-core/ncurses/ncurses_6.4.bb
+++ b/meta/recipes-core/ncurses/ncurses_6.4.bb
@@ -6,7 +6,8 @@ SRC_URI += "file://0001-tic-hang.patch \
file://exit_prototype.patch \
"
 # commit id corresponds to the revision in package version
-SRCREV = "79b9071f2be20a24c7be031655a5638f6032f29f"
+SRCREV = "964ec9f9c6e3ac3aaa1a9161c6fb75f6d7f589b5"
+PV = "6.4+20230625"
 S = "${WORKDIR}/git"
 EXTRA_OECONF += "--with-abi-version=5"
 UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+(\.\d+)+)$"
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184904): 
https://lists.openembedded.org/g/openembedded-core/message/184904
Mute This Topic: https://lists.openembedded.org/mt/100383999/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] sdk.py: error out when moving file fails

2023-06-19 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Instead of printing an error message and continuing, we should just
error out when moving file fails.

Signed-off-by: Chen Qi 
---
 meta/lib/oe/sdk.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oe/sdk.py b/meta/lib/oe/sdk.py
index 81fcf15371..3dc3672210 100644
--- a/meta/lib/oe/sdk.py
+++ b/meta/lib/oe/sdk.py
@@ -70,7 +70,7 @@ class Sdk(object, metaclass=ABCMeta):
 #FIXME: using umbrella exc catching because bb.utils method raises it
 except Exception as e:
 bb.debug(1, "printing the stack trace\n %s" 
%traceback.format_exc())
-bb.error("unable to place %s in final SDK location" % sourcefile)
+bb.fatal("unable to place %s in final SDK location" % sourcefile)
 
 def mkdirhier(self, dirpath):
 try:
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#183094): 
https://lists.openembedded.org/g/openembedded-core/message/183094
Mute This Topic: https://lists.openembedded.org/mt/99619163/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] rpm: write macros under libdir

2023-06-19 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

If we create a macros file under etc/, the populate_sdk task would
fail if 'package-management' is in SDKIMAGE_FEATURES and nativesdk-rpm-build
is installed.. The error message is like below:

  unable to place /.../sdk/image/etc/rpm in final SDK location

This is because it's trying to move the etc/rpm dictory into the
host sysroot but the /etc/rpm has already exists.

To solve this problem, avoid creating /etc/rpm/macros for nativesdk-rpm-build,
use ${libdir}/macros instead. In this way, the macros file is hold
in nativesdk-rpm. As nativesdk-rpm-build depends on nativesdk-rpm,
the 'rpmbuild' command inside SDK can still correctly find find-debuginfo
binary.

Signed-off-by: Chen Qi 
---
 meta/recipes-devtools/rpm/rpm_4.18.1.bb | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-devtools/rpm/rpm_4.18.1.bb 
b/meta/recipes-devtools/rpm/rpm_4.18.1.bb
index 6da2edddf3..83537d4761 100644
--- a/meta/recipes-devtools/rpm/rpm_4.18.1.bb
+++ b/meta/recipes-devtools/rpm/rpm_4.18.1.bb
@@ -134,8 +134,8 @@ do_install:append:class-target() {
 do_install:append:class-nativesdk() {
 rm -rf ${D}${SDKPATHNATIVE}/var
 # Ensure find-debuginfo is located correctly inside SDK
-mkdir -p ${D}${SDKPATHNATIVE}/etc/rpm
-echo "%__find_debuginfo   ${SDKPATHNATIVE}/usr/bin/find-debuginfo" >> 
${D}${SDKPATHNATIVE}/etc/rpm/macros
+mkdir -p ${D}${libdir}/rpm
+echo "%__find_debuginfo   ${SDKPATHNATIVE}/usr/bin/find-debuginfo" >> 
${D}${libdir}/rpm/macros
 }
 
 do_install:append () {
@@ -173,7 +173,6 @@ FILES:${PN}-build = "\
 ${libdir}/rpm/macros.p* \
 ${libdir}/rpm/fileattrs/* \
 "
-FILES:${PN}-build:append:class-nativesdk = " ${SDKPATHNATIVE}/etc/rpm/macros"
 
 FILES:${PN}-sign = "\
 ${bindir}/rpmsign \
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#183095): 
https://lists.openembedded.org/g/openembedded-core/message/183095
Mute This Topic: https://lists.openembedded.org/mt/99619164/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] sdk.py: fix moving dnf contents

2023-06-19 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The dnf contents should be moved to /etc/dnf/xxx
instead of just /etc.

Signed-off-by: Chen Qi 
---
 meta/lib/oe/package_manager/rpm/sdk.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oe/package_manager/rpm/sdk.py 
b/meta/lib/oe/package_manager/rpm/sdk.py
index 0726a18b91..85df6e949c 100644
--- a/meta/lib/oe/package_manager/rpm/sdk.py
+++ b/meta/lib/oe/package_manager/rpm/sdk.py
@@ -112,5 +112,6 @@ class PkgSdk(Sdk):
 for f in glob.glob(os.path.join(self.sdk_output, "etc", "rpm*")):
 self.movefile(f, native_sysconf_dir)
 for f in glob.glob(os.path.join(self.sdk_output, "etc", "dnf", "*")):
-self.movefile(f, native_sysconf_dir)
+self.mkdirhier(native_sysconf_dir + "/dnf")
+self.movefile(f, native_sysconf_dir + "/dnf")
 self.remove(os.path.join(self.sdk_output, "etc"), True)
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#183093): 
https://lists.openembedded.org/g/openembedded-core/message/183093
Mute This Topic: https://lists.openembedded.org/mt/99619162/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/4] zip: fix configure check by using _Static_assert

2023-06-18 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

It's incorrect to run a cross-compiled program on build machine
to check if some feature is available or not. As these two checks
in zip are basically just checking the size, we can use _Static_assert
and sizeof to do such check at compile time.

Signed-off-by: Chen Qi 
---
 ...se-_Static_assert-to-do-correct-dete.patch | 96 +++
 meta/recipes-extended/zip/zip_3.0.bb  |  1 +
 2 files changed, 97 insertions(+)
 create mode 100644 
meta/recipes-extended/zip/zip-3.0/0001-unix-configure-use-_Static_assert-to-do-correct-dete.patch

diff --git 
a/meta/recipes-extended/zip/zip-3.0/0001-unix-configure-use-_Static_assert-to-do-correct-dete.patch
 
b/meta/recipes-extended/zip/zip-3.0/0001-unix-configure-use-_Static_assert-to-do-correct-dete.patch
new file mode 100644
index 00..106f246a7c
--- /dev/null
+++ 
b/meta/recipes-extended/zip/zip-3.0/0001-unix-configure-use-_Static_assert-to-do-correct-dete.patch
@@ -0,0 +1,96 @@
+From 9916fc6f1f93f3e092e3c6937c30dc8137c26d34 Mon Sep 17 00:00:00 2001
+From: Chen Qi 
+Date: Thu, 15 Jun 2023 18:31:26 +0800
+Subject: [PATCH] unix/configure: use _Static_assert to do correct detection
+
+We're doing cross compilation, running a cross-compiled problem
+on host to detemine feature is not correct. Use _Static_assert
+to do the detection correctly.
+
+Upstream-Status: Inactive-Upstream
+
+Signed-off-by: Chen Qi 
+---
+ unix/configure | 42 --
+ 1 file changed, 12 insertions(+), 30 deletions(-)
+
+diff --git a/unix/configure b/unix/configure
+index f2b3d02..f917086 100644
+--- a/unix/configure
 b/unix/configure
+@@ -361,6 +361,10 @@ cat > conftest.c << _EOF_
+ #include 
+ #include 
+ #include 
++
++_Static_assert(sizeof((struct stat){0}.st_uid) == 2, "sizeof st_uid is not 16 
bit");
++_Static_assert(sizeof((struct stat){0}.st_gid) == 2, "sizeof st_gid is not 16 
bit");
++
+ int main()
+ {
+   struct stat s;
+@@ -385,21 +389,7 @@ if [ $? -ne 0 ]; then
+   echo -- UID/GID test failed on compile - disabling old 16-bit UID/GID 
support
+   CFLAGS="${CFLAGS} -DUIDGID_NOT_16BIT"
+ else
+-# run it
+-  ./conftest
+-  r=$?
+-  if [ $r -eq 1 ]; then
+-echo -- UID not 2 bytes - disabling old 16-bit UID/GID support
+-CFLAGS="${CFLAGS} -DUIDGID_NOT_16BIT"
+-  elif [ $r -eq 2 ]; then
+-echo -- GID not 2 bytes - disabling old 16-bit UID/GID support
+-CFLAGS="${CFLAGS} -DUIDGID_NOT_16BIT"
+-  elif [ $r -eq 3 ]; then
+-echo -- 16-bit UIDs and GIDs - keeping old 16-bit UID/GID support
+-  else
+-echo -- test failed - conftest returned $r - disabling old 16-bit UID/GID 
support
+-CFLAGS="${CFLAGS} -DUIDGID_NOT_16BIT"
+-  fi
++  echo -- 16-bit UIDs and GIDs - keeping old 16-bit UID/GID support
+ fi
+ 
+ 
+@@ -417,6 +407,10 @@ cat > conftest.c << _EOF_
+ #include 
+ #include 
+ #include 
++
++_Static_assert(sizeof(off_t) < 8, "sizeof off_t < 8 failed");
++_Static_assert(sizeof((struct stat){0}.st_size) < 8, "sizeof st_size < 8 
failed");
++
+ int main()
+ {
+   off_t offset;
+@@ -436,24 +430,12 @@ _EOF_
+ # compile it
+ $CC -o conftest conftest.c >/dev/null 2>/dev/null
+ if [ $? -ne 0 ]; then
+-  echo -- no Large File Support
++  echo -- yes we have Large File Support!
++  CFLAGS="${CFLAGS} -DLARGE_FILE_SUPPORT"
+ else
+-# run it
+-  ./conftest
+-  r=$?
+-  if [ $r -eq 1 ]; then
+-echo -- no Large File Support - no 64-bit off_t
+-  elif [ $r -eq 2 ]; then
+-echo -- no Large File Support - no 64-bit stat
+-  elif [ $r -eq 3 ]; then
+-echo -- yes we have Large File Support!
+-CFLAGS="${CFLAGS} -DLARGE_FILE_SUPPORT"
+-  else
+-echo -- no Large File Support - conftest returned $r
+-  fi
++  echo -- no Large File Support
+ fi
+ 
+-
+ # Check for wide char for Unicode support
+ # Added 11/24/2005 EG
+ 
+-- 
+2.34.1
+
diff --git a/meta/recipes-extended/zip/zip_3.0.bb 
b/meta/recipes-extended/zip/zip_3.0.bb
index 1930a40140..802877285f 100644
--- a/meta/recipes-extended/zip/zip_3.0.bb
+++ b/meta/recipes-extended/zip/zip_3.0.bb
@@ -19,6 +19,7 @@ SRC_URI = 
"${SOURCEFORGE_MIRROR}/infozip/Zip%203.x%20%28latest%29/3.0/zip30.tar.

file://0001-configure-Use-CFLAGS-and-LDFLAGS-when-doing-link-tes.patch \

file://0001-configure-Specify-correct-function-signatures-and-de.patch \
file://0002-unix.c-Do-not-redefine-DIR-as-FILE.patch \
+   
file://0001-unix-configure-use-_Static_assert-to-do-correct-dete.patch \
"
 UPSTREAM_VERSION_UNKNOWN = "1"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#183088): 
https://lists.openembedded.org/g/openembedded-core/message/183088
Mute This Topic: https://lists.openembedded.org/mt/99617721/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 4/4] unzip: remove hardcoded LARGE_FILE_SUPPORT

2023-06-18 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

Now that unzip's configure can correctly do the detection even in
case of cross compilation, there's no need to use this hardcoded
LARGE_FILE_SUPPORT flag.

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/unzip/unzip_6.0.bb | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/meta/recipes-extended/unzip/unzip_6.0.bb 
b/meta/recipes-extended/unzip/unzip_6.0.bb
index 391e5cd22a..3051e9b5bc 100644
--- a/meta/recipes-extended/unzip/unzip_6.0.bb
+++ b/meta/recipes-extended/unzip/unzip_6.0.bb
@@ -47,9 +47,6 @@ UPSTREAM_CHECK_REGEX = "unzip(?P(?!552).+)\.tgz"
 
 S = "${WORKDIR}/unzip60"
 
-# Enable largefile support
-CFLAGS += "-DLARGE_FILE_SUPPORT"
-
 # Makefile uses CF_NOOPT instead of CFLAGS.  We lifted the values from
 # Makefile and add CFLAGS.  Optimization will be overriden by unzip
 # configure to be -O3.
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#183087): 
https://lists.openembedded.org/g/openembedded-core/message/183087
Mute This Topic: https://lists.openembedded.org/mt/99617720/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/4] unzip: fix configure check for cross compilation

2023-06-18 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The original configure runs a generated binary to determine
features. This is not correct for cross compilation. So change
the runtime tests into compile-time tests to fix the issue.

Signed-off-by: Chen Qi 
---
 ...-fix-detection-for-cross-compilation.patch | 103 ++
 meta/recipes-extended/unzip/unzip_6.0.bb  |   1 +
 2 files changed, 104 insertions(+)
 create mode 100644 
meta/recipes-extended/unzip/unzip/0001-unix-configure-fix-detection-for-cross-compilation.patch

diff --git 
a/meta/recipes-extended/unzip/unzip/0001-unix-configure-fix-detection-for-cross-compilation.patch
 
b/meta/recipes-extended/unzip/unzip/0001-unix-configure-fix-detection-for-cross-compilation.patch
new file mode 100644
index 00..2fa7f481b7
--- /dev/null
+++ 
b/meta/recipes-extended/unzip/unzip/0001-unix-configure-fix-detection-for-cross-compilation.patch
@@ -0,0 +1,103 @@
+From 5cbf901b5c3b6a7d1d0ed91b6df4194bb6d25a40 Mon Sep 17 00:00:00 2001
+From: Chen Qi 
+Date: Thu, 15 Jun 2023 07:14:17 -0700
+Subject: [PATCH] unix/configure: fix detection for cross compilation
+
+We're doing cross compilation, running a cross-compiled problem
+on host to detemine feature is not correct. So we change runtime
+check into compile-time check to detect the features.
+
+Upstream-Status: Inactive-Upstream
+
+Signed-off-by: Chen Qi 
+---
+ unix/configure | 44 +++-
+ 1 file changed, 15 insertions(+), 29 deletions(-)
+
+diff --git a/unix/configure b/unix/configure
+index 8fd82dd..68dee98 100755
+--- a/unix/configure
 b/unix/configure
+@@ -259,6 +259,10 @@ cat > conftest.c << _EOF_
+ #include 
+ #include 
+ #include 
++
++_Static_assert(sizeof(off_t) < 8, "sizeof off_t < 8 failed");
++_Static_assert(sizeof((struct stat){0}.st_size) < 8, "sizeof st_size < 8 
failed");
++
+ int main()
+ {
+   off_t offset;
+@@ -278,21 +282,10 @@ _EOF_
+ # compile it
+ $CC $CFLAGS $LDFLAGS -o conftest conftest.c >/dev/null 2>/dev/null
+ if [ $? -ne 0 ]; then
+-  echo -- no Large File Support
++  echo -- yes we have Large File Support!
++  CFLAGSR="${CFLAGSR} -DLARGE_FILE_SUPPORT"
+ else
+-# run it
+-  ./conftest
+-  r=$?
+-  if [ $r -eq 1 ]; then
+-echo -- no Large File Support - no 64-bit off_t
+-  elif [ $r -eq 2 ]; then
+-echo -- no Large File Support - no 64-bit stat
+-  elif [ $r -eq 3 ]; then
+-echo -- yes we have Large File Support!
+-CFLAGSR="${CFLAGSR} -DLARGE_FILE_SUPPORT"
+-  else
+-echo -- no Large File Support - conftest returned $r
+-  fi
++  echo -- no Large File Support
+ fi
+ 
+ # Added 11/24/2005 EG
+@@ -302,6 +295,11 @@ cat > conftest.c << _EOF_
+ #include 
+ #include 
+ #include 
++
++#ifndef __STDC_ISO_10646__
++#error "__STDC_ISO_10646__ not defined
++#endif
++
+ int main()
+ {
+   size_t wsize;
+@@ -327,19 +325,8 @@ if [ $? -ne 0 ]; then
+   echo "-- no Unicode (wchar_t) support"
+ else
+ # have wide char support
+-# run it
+-  ./conftest
+-  r=$?
+-  if [ $r -eq 0 ]; then
+-echo -- no Unicode wchar_t support - wchar_t allocation error
+-  elif [ $r -eq 1 ]; then
+-echo -- no Unicode support - wchar_t encoding unspecified
+-  elif [ $r -eq 2 ]; then
+-echo -- have wchar_t with known UCS encoding - enabling Unicode support!
+-CFLAGSR="${CFLAGSR} -DUNICODE_SUPPORT -DUNICODE_WCHAR"
+-  else
+-echo "-- no Unicode (wchar_t) support - conftest returned $r"
+-  fi
++  echo -- have wchar_t with known UCS encoding - enabling Unicode support!
++  CFLAGSR="${CFLAGSR} -DUNICODE_SUPPORT -DUNICODE_WCHAR"
+ fi
+ 
+ echo "Check for setlocale support (needed for UNICODE Native check)"
+@@ -418,8 +405,7 @@ temp_link="link_$$"
+   echo "int main() { lchmod(\"${temp_file}\", 0666); }" \
+ ) > conftest.c
+ ln -s "${temp_link}" "${temp_file}" && \
+- $CC $BFLAG $LDFLAGS -o conftest conftest.c >/dev/null 2>/dev/null && \
+- ./conftest
++ $CC -Werror=implicit-function-declaration $BFLAG $LDFLAGS -o conftest 
conftest.c >/dev/null
+ [ $? -ne 0 ] && CFLAGSR="${CFLAGSR} -DNO_LCHMOD"
+ rm -f "${temp_file}"
+ 
+-- 
+2.34.1
+
diff --git a/meta/recipes-extended/unzip/unzip_6.0.bb 
b/meta/recipes-extended/unzip/unzip_6.0.bb
index a4d10c30aa..391e5cd22a 100644
--- a/meta/recipes-extended/unzip/unzip_6.0.bb
+++ b/meta/recipes-extended/unzip/unzip_6.0.bb
@@ -32,6 +32,7 @@ SRC_URI = 
"${SOURCEFORGE_MIRROR}/infozip/UnZip%206.x%20%28latest%29/UnZip%206.0/
 file://CVE-2022-0529.patch \
 file://CVE-2022-0530.patch \
 file://0001-configure-Add-correct-system-headers-and-prototypes-.patch 
\
+file://0001-unix-configure-fix-detection-for-cross-compilation.patch \
 "
 UPSTREAM_VERSION_UNKNOWN = "1"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sen

[OE-core][PATCH 2/4] zip: remove unnecessary LARGE_FILE_SUPPORT CLFAGS

2023-06-18 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

As the zip's configure has been updated to use compile-time
check, it now can do the check correctly, thus no need to
pass LARGE_FILE_SUPPORT to CFLAGS.

Signed-off-by: Chen Qi 
---
 meta/recipes-extended/zip/zip_3.0.bb | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/meta/recipes-extended/zip/zip_3.0.bb 
b/meta/recipes-extended/zip/zip_3.0.bb
index 802877285f..82153131b4 100644
--- a/meta/recipes-extended/zip/zip_3.0.bb
+++ b/meta/recipes-extended/zip/zip_3.0.bb
@@ -32,9 +32,6 @@ CVE_CHECK_IGNORE += "CVE-2018-13410"
 # Not for zip but for smart contract implementation for it
 CVE_CHECK_IGNORE += "CVE-2018-13684"
 
-# Enable largefile support
-CFLAGS += "-DLARGE_FILE_SUPPORT"
-
 # zip.inc sets CFLAGS, but what Makefile actually uses is
 # CFLAGS_NOOPT.  It will also force -O3 optimization, overriding
 # whatever we set.
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#183086): 
https://lists.openembedded.org/g/openembedded-core/message/183086
Mute This Topic: https://lists.openembedded.org/mt/99617719/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] qemurunner.py: fix error message about qmp

2023-06-05 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The error message is a little misleading as the qmp module is a
directory with __init__.py file, not qmp.py file. Also, put the
path where we try to import it from in the error message to make
the message more indicative.

Signed-off-by: Chen Qi 
---
 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 7f520d47c3..0ef8cf0a79 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -188,7 +188,7 @@ class QemuRunner:
 def launch(self, launch_cmd, get_ip = True, qemuparams = None, 
extra_bootparams = None, env = None):
 # use logfile to determine the recipe-sysroot-native path and
 # then add in the site-packages path components and add that
-# to the python sys.path so qmp.py can be found.
+# to the python sys.path so the qmp module can be found.
 python_path = os.path.dirname(os.path.dirname(self.logfile))
 python_path += "/recipe-sysroot-native/usr/lib/qemu-python"
 sys.path.append(python_path)
@@ -196,7 +196,7 @@ class QemuRunner:
 try:
 qmp = importlib.import_module("qmp")
 except Exception as e:
-self.logger.error("qemurunner: qmp.py missing, please ensure it's 
installed (%s)" % str(e))
+self.logger.error("qemurunner: qmp module missing, please ensure 
it's installed in %s (%s)" % (python_path, str(e)))
 return False
 # Path relative to tmpdir used as cwd for qemu below to avoid unix 
socket path length issues
 qmp_file = "." + next(tempfile._get_candidate_names())
-- 
2.40.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#182375): 
https://lists.openembedded.org/g/openembedded-core/message/182375
Mute This Topic: https://lists.openembedded.org/mt/99336456/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] Revert "libsdl2: disable SDL's own ccache"

2023-06-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

The reverted patch's purpose is to avoid libsdl2-native from
detecting ccache from host. Now that we have made cmake.bbclass
to not search the host paths, the original patch is no longer
needed.

This reverts commit 01472f512f45bdd319611871a21172216c74e29a.

Signed-off-by: Chen Qi 
---
 meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb
index f8319a8f29..3274475da1 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb
@@ -47,7 +47,6 @@ EXTRA_OECMAKE = "-DSDL_OSS=OFF -DSDL_ESD=OFF -DSDL_ARTS=OFF \
  -DSDL_X11_XRANDR=OFF \
  -DSDL_X11_XSCRNSAVER=OFF \
  -DSDL_X11_XSHAPE=OFF \
- -DSDL_CCACHE=OFF \
 "
 
 # opengl packageconfig factored out to make it easy for distros
-- 
2.40.0



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#182116): 
https://lists.openembedded.org/g/openembedded-core/message/182116
Mute This Topic: https://lists.openembedded.org/mt/99266305/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] cmake.bbclass: do not search host paths for find_program()

2023-06-01 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM[1] controls the search
behavior of find_program(). When this variable's value was
first used in OE, it was deliberately set to BOTH to allow
searching of host tools. This is to ensure the necessary tools
from host could be used. The downside is that the configure
behavior may differ on different host environments.

Later, this cmake.bbclass was added the ability to search tools
under the HOSTTOOLS_DIR. This means we no longer needs cmake to
search the host paths. So we remove the class-native setting of
BOTH.

[1] 
https://cmake.org/cmake/help/latest/variable/CMAKE_FIND_ROOT_PATH_MODE_PROGRAM.html

Signed-off-by: Chen Qi 
---
 meta/classes-recipe/cmake.bbclass | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/classes-recipe/cmake.bbclass 
b/meta/classes-recipe/cmake.bbclass
index 301367b515..0dda104a69 100644
--- a/meta/classes-recipe/cmake.bbclass
+++ b/meta/classes-recipe/cmake.bbclass
@@ -61,7 +61,6 @@ OECMAKE_PERLNATIVE_DIR ??= ""
 OECMAKE_EXTRA_ROOT_PATH ?= ""
 
 OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM = "ONLY"
-OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM:class-native = "BOTH"
 
 EXTRA_OECMAKE:append = " ${PACKAGECONFIG_CONFARGS}"
 
-- 
2.40.0



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#182115): 
https://lists.openembedded.org/g/openembedded-core/message/182115
Mute This Topic: https://lists.openembedded.org/mt/99266304/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] libsdl2: disable SDL's own ccache

2023-05-29 Thread Chen Qi via lists.openembedded.org
From: Chen Qi 

OE has its own ccache mechanism, disable libsdl2's own ccache
searching/enabling mechanism. Otherwise, if ccache is installed
on system, it will be used by default.

Signed-off-by: Chen Qi 
---
 meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb
index 3274475da1..f8319a8f29 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.26.5.bb
@@ -47,6 +47,7 @@ EXTRA_OECMAKE = "-DSDL_OSS=OFF -DSDL_ESD=OFF -DSDL_ARTS=OFF \
  -DSDL_X11_XRANDR=OFF \
  -DSDL_X11_XSCRNSAVER=OFF \
  -DSDL_X11_XSHAPE=OFF \
+ -DSDL_CCACHE=OFF \
 "
 
 # opengl packageconfig factored out to make it easy for distros
-- 
2.40.0


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



  1   2   3   4   5   6   7   8   9   10   >