Patchtest results for [oe-core][PATCHv3 1/2] vala: merge bb and inc files

2024-03-11 Thread Patchtest
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/PATCHv3-1-2-vala-merge-bb-and-inc-files.patch

FAIL: test commit message presence: Please include a commit message on your 
patch explaining the change (test_mbox.TestMbox.test_commit_message_presence)
FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed 
without "License-Update:" tag and description in commit message 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)

PASS: pretest src uri left files 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test Signed-off-by presence 
(test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
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)
PASS: test src uri left files 
(test_metadata.TestMetadata.test_src_uri_left_files)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
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 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 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 (#196971): 
https://lists.openembedded.org/g/openembedded-core/message/196971
Mute This Topic: https://lists.openembedded.org/mt/104879757/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe-core][PATCHv3 1/2] vala: merge bb and inc files

2024-03-11 Thread Markus Volk
Signed-off-by: Markus Volk 
---
 meta/recipes-devtools/vala/vala.inc| 71 -
 meta/recipes-devtools/vala/vala_0.56.15.bb | 72 +-
 2 files changed, 71 insertions(+), 72 deletions(-)
 delete mode 100644 meta/recipes-devtools/vala/vala.inc

diff --git a/meta/recipes-devtools/vala/vala.inc 
b/meta/recipes-devtools/vala/vala.inc
deleted file mode 100644
index 0177e86240..00
--- a/meta/recipes-devtools/vala/vala.inc
+++ /dev/null
@@ -1,71 +0,0 @@
-SUMMARY = "C#-like programming language for easing GObject programming"
-HOMEPAGE = "http://vala-project.org";
-DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject 
programming. \
-Vala compiles to plain C and has no runtime environment nor penalities 
whatsoever."
-SECTION = "devel"
-DEPENDS = "bison-native flex-native glib-2.0 gobject-introspection"
-
-# Appending libxslt-native to dependencies has an effect
-# of rebuilding the manual, which is very slow. Let's do this
-# only when api-documentation distro feature is enabled.
-DEPENDS:append:class-target = " ${@bb.utils.contains('DISTRO_FEATURES', 
'api-documentation', 'libxslt-native', '', d)}"
-
-# vala-native contains a native version of vapigen, which we use instead of 
the target one
-DEPENDS:append:class-target = " vala-native"
-BBCLASSEXTEND = "native"
-LICENSE = "LGPL-2.1-only"
-LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
-
-SHRT_VER = "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
-
-SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
-inherit autotools pkgconfig upstream-version-is-even
-
-FILES:${PN} += "${datadir}/${BPN}-${SHRT_VER}/vapi 
${libdir}/${BPN}-${SHRT_VER}/"
-FILES:${PN}-doc += "${datadir}/devhelp"
-
-# .gir files from gobject-introspection are installed to ${libdir} when 
multilib is enabled
-GIRDIR_OPT = "${@'--girdir=${STAGING_LIBDIR}/gir-1.0' if d.getVar('MULTILIBS') 
else ''}"
-
-do_configure:prepend:class-target() {
-# Write out a vapigen wrapper that will be provided by pkg-config file 
installed in target sysroot
-# The wrapper will call a native vapigen
-cat > ${B}/vapigen-wrapper << EOF
-#!/bin/sh
-vapigen-${SHRT_VER} ${GIRDIR_OPT} "\$@"
-EOF
-chmod +x ${B}/vapigen-wrapper
-}
-
-EXTRA_OECONF += " --disable-valadoc"
-
-# Vapigen wrapper needs to be available system-wide, because it will be used
-# to build vapi files from all other packages with vala support
-do_install:append:class-target() {
-install -d ${D}${bindir_crossscripts}/
-install ${B}/vapigen-wrapper ${D}${bindir_crossscripts}/
-}
-
-# Put vapigen wrapper into target sysroot so that it can be used when building
-# vapi files.
-SYSROOT_DIRS += "${bindir_crossscripts}"
-
-inherit multilib_script
-MULTILIB_SCRIPTS = "${PN}:${bindir}/vala-gen-introspect-0.56"
-
-SYSROOT_PREPROCESS_FUNCS:append:class-target = " vapigen_sysroot_preprocess"
-vapigen_sysroot_preprocess() {
-# Tweak the vapigen name in the vapigen pkgconfig file, so that it 
picks
-# up our wrapper.
-sed -i \
-   -e "s|vapigen=.*|vapigen=${bindir_crossscripts}/vapigen-wrapper|" \
-   ${SYSROOT_DESTDIR}${libdir}/pkgconfig/vapigen-${SHRT_VER}.pc
-}
-
-SSTATE_SCAN_FILES += "vapigen-wrapper"
-
-PACKAGE_PREPROCESS_FUNCS += "vala_package_preprocess"
-
-vala_package_preprocess () {
-   rm -rf ${PKGD}${bindir_crossscripts}
-}
diff --git a/meta/recipes-devtools/vala/vala_0.56.15.bb 
b/meta/recipes-devtools/vala/vala_0.56.15.bb
index dc483b12ba..a8fdd0a97a 100644
--- a/meta/recipes-devtools/vala/vala_0.56.15.bb
+++ b/meta/recipes-devtools/vala/vala_0.56.15.bb
@@ -1,3 +1,73 @@
-require ${BPN}.inc
+SUMMARY = "C#-like programming language for easing GObject programming"
+HOMEPAGE = "http://vala-project.org";
+DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject 
programming. \
+Vala compiles to plain C and has no runtime environment nor penalities 
whatsoever."
+SECTION = "devel"
+DEPENDS = "bison-native flex-native glib-2.0 gobject-introspection"
 
+# Appending libxslt-native to dependencies has an effect
+# of rebuilding the manual, which is very slow. Let's do this
+# only when api-documentation distro feature is enabled.
+DEPENDS:append:class-target = " ${@bb.utils.contains('DISTRO_FEATURES', 
'api-documentation', 'libxslt-native', '', d)}"
+
+# vala-native contains a native version of vapigen, which we use instead of 
the target one
+DEPENDS:append:class-target = " vala-native"
+BBCLASSEXTEND = "native"
+LICENSE = "LGPL-2.1-only"
+LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
+
+SHRT_VER = "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
+
+SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
 SRC_URI[sha256sum] = 
"535b6452ed310fd5fb5c7dd6794b6213dac3b48e645e5bff3173741ec2cb3f2b"
+
+inherit autotools pkgconfig upstream-version-is-even
+
+FI

[oe-core][PATCHv3 2/2] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Markus Volk
- add a backport patch to fix compatibility with older gtk4 versions

Signed-off-by: Markus Volk 
---
 ...tk4-Preserve-compatibility-with-4.14.patch | 39 +++
 meta/recipes-devtools/vala/vala_0.56.15.bb|  5 ++-
 2 files changed, 43 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch

diff --git 
a/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
new file mode 100644
index 00..161474086e
--- /dev/null
+++ 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
@@ -0,0 +1,39 @@
+From 17349020fb95454d06f827fd555b05248f10a370 Mon Sep 17 00:00:00 2001
+From: Rico Tzschichholz 
+Date: Thu, 7 Mar 2024 17:56:05 +0100
+Subject: [PATCH] gtk4: Preserve compatibility with < 4.14
+
+Don't prefer new accessor methods for Calendar.day/month/year
+
+Fixes https://gitlab.gnome.org/GNOME/vala/issues/1531
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/vala/-/commit/e0c4ea8c4a0bbf859b5341a7465b395892789d9e]
+
+Signed-off-by: Markus Volk 
+---
+ vapi/gtk4.vapi | 3 +++
+ vapi/metadata/Gtk-4.0.metadata | 5 +
+ 2 files changed, 8 insertions(+)
+
+diff --git a/vapi/gtk4.vapi b/vapi/gtk4.vapi
+index 49f8b2078..51ecea27d 100644
+--- a/vapi/gtk4.vapi
 b/vapi/gtk4.vapi
+@@ -7350,11 +7350,14 @@ namespace Gtk {
+   [Version (since = "4.14")]
+   public void set_year (int year);
+   public void unmark_day (uint day);
++  [NoAccessorMethod]
+   public int day { get; set; }
++  [NoAccessorMethod]
+   public int month { get; set; }
+   public bool show_day_names { get; set; }
+   public bool show_heading { get; set; }
+   public bool show_week_numbers { get; set; }
++  [NoAccessorMethod]
+   public int year { get; set; }
+   public signal void day_selected ();
+   public signal void next_month ();
+-- 
+2.44.0
+
diff --git a/meta/recipes-devtools/vala/vala_0.56.15.bb 
b/meta/recipes-devtools/vala/vala_0.56.15.bb
index a8fdd0a97a..915ddd8e4d 100644
--- a/meta/recipes-devtools/vala/vala_0.56.15.bb
+++ b/meta/recipes-devtools/vala/vala_0.56.15.bb
@@ -18,7 +18,10 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=fbc093901857fcd118f065f900982c24"
 
 SHRT_VER = "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
 
-SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
+SRC_URI = " \
+   http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz \
+   file://0001-gtk4-Preserve-compatibility-with-4.14.patch \
+"
 SRC_URI[sha256sum] = 
"535b6452ed310fd5fb5c7dd6794b6213dac3b48e645e5bff3173741ec2cb3f2b"
 
 inherit autotools pkgconfig upstream-version-is-even
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196970): 
https://lists.openembedded.org/g/openembedded-core/message/196970
Mute This Topic: https://lists.openembedded.org/mt/104879689/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] glibc: Fix conflict error when enbale multilib on aarch64.

2024-03-11 Thread leimaohui via lists.openembedded.org
Hi, 

Thank you very much. I'm sorry I didn't notice the same patch with me.

Best regards
Lei

> -Original Message-
> From: Alexandre Belloni 
> Sent: Tuesday, March 12, 2024 6:26 AM
> To: Lei, Maohui 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] glibc: Fix conflict error when enbale multilib 
> on
> aarch64.
> 
> https://lore.kernel.org/all/b023614f7765fc003a4aa854440c0b66d200d27b.cam
> e...@linuxfoundation.org/
> 
> On 07/03/2024 16:22:32-0800, leimaohui via lists.openembedded.org wrote:
> > Ping
> >
> >
> >
> > > -Original Message-
> > > From: openembedded-core@lists.openembedded.org
> > >  On Behalf Of Khem Raj
> > > Sent: Monday, February 26, 2024 2:19 PM
> > > To: Lei, Maohui 
> > > Cc: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] [PATCH] glibc: Fix conflict error when enbale
> > > multilib on aarch64.
> > >
> > > lgtm.
> > >
> > > On Sun, Feb 25, 2024 at 9:32 PM leimaohui via lists.openembedded.org
> > >  wrote:
> > > >
> > > > From: Lei Maohui 
> > > >
> > > > Error: Transaction test error:
> > > >   file /usr/include/finclude/math-vector-fortran.h from install of
> > > > lib32-libc6-dev-2.39+git0+312e159626-r0.armv7ahf_neon conflicts
> > > > with file from package libc6-dev-2.39+git0+312e159626-r0.aarch64
> > > >
> > > > The difference of math-vector-fortran.h between 32bit and 64bit is
> > > > as the following:
> > > >
> > > > ---
> > >
> tmp/work/aarch64-linux/glibc/2.39+git/image/usr/include/finclude/math-vecto
> > > r-fortran.h2024-02-26 03:41:59.56000 +
> > > > +++ tmp/work/armv7ahf-neon-xmllib32-linux-gnueabi/lib32-glibc/2.39
> > > > +++ +git /image/usr/include/finclude/math-vector-fortran.h
> > > > +++ 2024-02-26
> > > > +++ 02:22:28.59200 +
> > > > @@ -15,33 +15,5 @@
> > > >  !   You should have received a copy of the GNU Lesser General Public
> > > >  !   License along with the GNU C Library; if not, see
> > > >  !   .
> > > > -!GCC$ builtin (acos) attributes simd (notinbranch) -!GCC$ builtin
> > > > (acosf) attributes simd (notinbranch) -!GCC$ builtin (asin)
> > > > attributes simd (notinbranch) -!GCC$ builtin (asinf) attributes
> > > > simd
> > > > (notinbranch) -!GCC$ builtin (atan) attributes simd (notinbranch)
> > > > -!GCC$ builtin (atanf) attributes simd (notinbranch) -!GCC$
> > > > builtin
> > > > (atan2) attributes simd (notinbranch) -!GCC$ builtin (atan2f)
> > > > attributes simd (notinbranch) -!GCC$ builtin (cos) attributes simd
> > > > (notinbranch) -!GCC$ builtin (cosf) attributes simd (notinbranch)
> > > > -!GCC$ builtin (exp) attributes simd (notinbranch) -!GCC$ builtin
> > > > (expf) attributes simd (notinbranch) -!GCC$ builtin (exp10)
> > > > attributes simd (notinbranch) -!GCC$ builtin (exp10f) attributes
> > > > simd
> > > > (notinbranch) -!GCC$ builtin (exp2) attributes simd (notinbranch)
> > > > -!GCC$ builtin (exp2f) attributes simd (notinbranch) -!GCC$
> > > > builtin
> > > > (expm1) attributes simd (notinbranch) -!GCC$ builtin (expm1f)
> > > > attributes simd (notinbranch) -!GCC$ builtin (log) attributes simd
> > > > (notinbranch) -!GCC$ builtin (logf) attributes simd (notinbranch)
> > > > -!GCC$ builtin (log10) attributes simd (notinbranch) -!GCC$
> > > > builtin
> > > > (log10f) attributes simd (notinbranch) -!GCC$ builtin (log1p)
> > > > attributes simd (notinbranch) -!GCC$ builtin (log1pf) attributes
> > > > simd
> > > > (notinbranch) -!GCC$ builtin (log2) attributes simd (notinbranch)
> > > > -!GCC$ builtin (log2f) attributes simd (notinbranch) -!GCC$
> > > > builtin
> > > > (sin) attributes simd (notinbranch) -!GCC$ builtin (sinf)
> > > > attributes simd (notinbranch) -!GCC$ builtin (tan) attributes simd
> > > > (notinbranch) -!GCC$ builtin (tanf) attributes simd (notinbranch)
> > > > +
> > > > +! No SIMD math functions are available for this platform.
> > > >
> > > > Signed-off-by: Lei Maohui 
> > > > ---
> > > >  meta/recipes-core/glibc/glibc-package.inc | 1 +
> > > >  1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/meta/recipes-core/glibc/glibc-package.inc
> > > > b/meta/recipes-core/glibc/glibc-package.inc
> > > > index 1ef987be0a..19eb7afa81 100644
> > > > --- a/meta/recipes-core/glibc/glibc-package.inc
> > > > +++ b/meta/recipes-core/glibc/glibc-package.inc
> > > > @@ -167,6 +167,7 @@ do_install_armmultilib () {
> > > > oe_multilib_header fpu_control.h gnu/lib-names.h
> > > > gnu/stubs.h ieee754.h
> > > >
> > > > oe_multilib_header sys/elf.h sys/procfs.h sys/ptrace.h
> > > > sys/ucontext.h sys/user.h
> > > > +   oe_multilib_header finclude/math-vector-fortran.h
> > > >  }
> > > >
> > > >
> > > > --
> > > > 2.34.1
> > > >
> > > >
> > > >
> > > >
> 
> >
> > 
> >
> 
> 
> --
> Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel
> engineering https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196967): 
https://lists.o

Re: [OE-core] [PATCH] glibc: Fix conflict error when enbale multilib on aarch64.

2024-03-11 Thread Alexandre Belloni via lists.openembedded.org
https://lore.kernel.org/all/b023614f7765fc003a4aa854440c0b66d200d27b.ca...@linuxfoundation.org/

On 07/03/2024 16:22:32-0800, leimaohui via lists.openembedded.org wrote:
> Ping 
> 
> 
> 
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org
> >  On Behalf Of Khem Raj
> > Sent: Monday, February 26, 2024 2:19 PM
> > To: Lei, Maohui 
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH] glibc: Fix conflict error when enbale 
> > multilib on
> > aarch64.
> > 
> > lgtm.
> > 
> > On Sun, Feb 25, 2024 at 9:32 PM leimaohui via lists.openembedded.org
> >  wrote:
> > >
> > > From: Lei Maohui 
> > >
> > > Error: Transaction test error:
> > >   file /usr/include/finclude/math-vector-fortran.h from install of
> > > lib32-libc6-dev-2.39+git0+312e159626-r0.armv7ahf_neon conflicts with
> > > file from package libc6-dev-2.39+git0+312e159626-r0.aarch64
> > >
> > > The difference of math-vector-fortran.h between 32bit and 64bit is as
> > > the following:
> > >
> > > ---
> > tmp/work/aarch64-linux/glibc/2.39+git/image/usr/include/finclude/math-vecto
> > r-fortran.h2024-02-26 03:41:59.56000 +
> > > +++ tmp/work/armv7ahf-neon-xmllib32-linux-gnueabi/lib32-glibc/2.39+git
> > > +++ /image/usr/include/finclude/math-vector-fortran.h 2024-02-26
> > > +++ 02:22:28.59200 +
> > > @@ -15,33 +15,5 @@
> > >  !   You should have received a copy of the GNU Lesser General Public
> > >  !   License along with the GNU C Library; if not, see
> > >  !   .
> > > -!GCC$ builtin (acos) attributes simd (notinbranch) -!GCC$ builtin
> > > (acosf) attributes simd (notinbranch) -!GCC$ builtin (asin) attributes
> > > simd (notinbranch) -!GCC$ builtin (asinf) attributes simd
> > > (notinbranch) -!GCC$ builtin (atan) attributes simd (notinbranch)
> > > -!GCC$ builtin (atanf) attributes simd (notinbranch) -!GCC$ builtin
> > > (atan2) attributes simd (notinbranch) -!GCC$ builtin (atan2f)
> > > attributes simd (notinbranch) -!GCC$ builtin (cos) attributes simd
> > > (notinbranch) -!GCC$ builtin (cosf) attributes simd (notinbranch)
> > > -!GCC$ builtin (exp) attributes simd (notinbranch) -!GCC$ builtin
> > > (expf) attributes simd (notinbranch) -!GCC$ builtin (exp10) attributes
> > > simd (notinbranch) -!GCC$ builtin (exp10f) attributes simd
> > > (notinbranch) -!GCC$ builtin (exp2) attributes simd (notinbranch)
> > > -!GCC$ builtin (exp2f) attributes simd (notinbranch) -!GCC$ builtin
> > > (expm1) attributes simd (notinbranch) -!GCC$ builtin (expm1f)
> > > attributes simd (notinbranch) -!GCC$ builtin (log) attributes simd
> > > (notinbranch) -!GCC$ builtin (logf) attributes simd (notinbranch)
> > > -!GCC$ builtin (log10) attributes simd (notinbranch) -!GCC$ builtin
> > > (log10f) attributes simd (notinbranch) -!GCC$ builtin (log1p)
> > > attributes simd (notinbranch) -!GCC$ builtin (log1pf) attributes simd
> > > (notinbranch) -!GCC$ builtin (log2) attributes simd (notinbranch)
> > > -!GCC$ builtin (log2f) attributes simd (notinbranch) -!GCC$ builtin
> > > (sin) attributes simd (notinbranch) -!GCC$ builtin (sinf) attributes
> > > simd (notinbranch) -!GCC$ builtin (tan) attributes simd (notinbranch)
> > > -!GCC$ builtin (tanf) attributes simd (notinbranch)
> > > +
> > > +! No SIMD math functions are available for this platform.
> > >
> > > Signed-off-by: Lei Maohui 
> > > ---
> > >  meta/recipes-core/glibc/glibc-package.inc | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/meta/recipes-core/glibc/glibc-package.inc
> > > b/meta/recipes-core/glibc/glibc-package.inc
> > > index 1ef987be0a..19eb7afa81 100644
> > > --- a/meta/recipes-core/glibc/glibc-package.inc
> > > +++ b/meta/recipes-core/glibc/glibc-package.inc
> > > @@ -167,6 +167,7 @@ do_install_armmultilib () {
> > > oe_multilib_header fpu_control.h gnu/lib-names.h gnu/stubs.h
> > > ieee754.h
> > >
> > > oe_multilib_header sys/elf.h sys/procfs.h sys/ptrace.h
> > > sys/ucontext.h sys/user.h
> > > +   oe_multilib_header finclude/math-vector-fortran.h
> > >  }
> > >
> > >
> > > --
> > > 2.34.1
> > >
> > >
> > >
> > >

> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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



[OE-core] Patchtest results for [PATCH 1/7, v2] openssh: replace complete configuration files by patch

2024-03-11 Thread Patchtest
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/1-7-v2-openssh-replace-complete-configuration-files-by-patch.patch

FAIL: test Signed-off-by presence: A patch file has been added without a 
Signed-off-by tag: 'include-conf.patch' 
(test_patch.TestPatch.test_signed_off_by_presence)

PASS: pretest src uri left files 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
PASS: test Signed-off-by presence 
(test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test Upstream-Status presence 
(test_patch.TestPatch.test_upstream_status_presence_format)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence 
(test_mbox.TestMbox.test_commit_message_presence)
PASS: test lic files chksum modified not mentioned 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
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)
PASS: test src uri left files 
(test_metadata.TestMetadata.test_src_uri_left_files)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
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 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 (#196965): 
https://lists.openembedded.org/g/openembedded-core/message/196965
Mute This Topic: https://lists.openembedded.org/mt/104869678/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/7, v2] openssh: replace complete configuration files by patch

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Instead of shipping the whole configuration files for openssh, add
small patch includes configuration snippets from subdirectories.

This allows us to keep the original upstream configuration which is
mainly useful for documentation purposes.  It makes it more easy to
identify OE specific setup.

Signed-off-by: Enrico Scholz 
---
 .../openssh/openssh/include-conf.patch|  32 +
 .../openssh/openssh/ssh_config|  48 ---
 .../openssh/openssh/sshd_config   | 119 --
 .../openssh/openssh_9.6p1.bb  |   5 +-
 4 files changed, 33 insertions(+), 171 deletions(-)
 create mode 100644 meta/recipes-connectivity/openssh/openssh/include-conf.patch
 delete mode 100644 meta/recipes-connectivity/openssh/openssh/ssh_config
 delete mode 100644 meta/recipes-connectivity/openssh/openssh/sshd_config

diff --git a/meta/recipes-connectivity/openssh/openssh/include-conf.patch 
b/meta/recipes-connectivity/openssh/openssh/include-conf.patch
new file mode 100644
index ..3e0bd2957e25
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh/include-conf.patch
@@ -0,0 +1,32 @@
+Include configuration snippets from subdirectory.
+
+NOTE: first configuration option wins.
+
+Upstream-Status: Inappropriate [configuration]
+
+Index: openssh-9.5p1/ssh_config
+===
+--- openssh-9.5p1.orig/ssh_config
 openssh-9.5p1/ssh_config
+@@ -5,6 +5,8 @@
+ # users, and the values can be changed in per-user configuration files
+ # or on the command line.
+ 
++Include /etc/ssh/ssh_config.d/*.conf
++
+ # Configuration data is parsed as follows:
+ #  1. command line options
+ #  2. user-specific file
+Index: openssh-9.5p1/sshd_config
+===
+--- openssh-9.5p1.orig/sshd_config
 openssh-9.5p1/sshd_config
+@@ -10,6 +10,8 @@
+ # possible, but leave them commented.  Uncommented options override the
+ # default value.
+ 
++Include /etc/ssh/sshd_config.d/*.conf
++
+ #Port 22
+ #AddressFamily any
+ #ListenAddress 0.0.0.0
diff --git a/meta/recipes-connectivity/openssh/openssh/ssh_config 
b/meta/recipes-connectivity/openssh/openssh/ssh_config
deleted file mode 100644
index cb2774a163ed..
--- a/meta/recipes-connectivity/openssh/openssh/ssh_config
+++ /dev/null
@@ -1,48 +0,0 @@
-#  $OpenBSD: ssh_config,v 1.35 2020/07/17 03:43:42 dtucker Exp $
-
-# This is the ssh client system-wide configuration file.  See
-# ssh_config(5) for more information.  This file provides defaults for
-# users, and the values can be changed in per-user configuration files
-# or on the command line.
-
-# Configuration data is parsed as follows:
-#  1. command line options
-#  2. user-specific file
-#  3. system-wide file
-# Any configuration value is only changed the first time it is set.
-# Thus, host-specific definitions should be at the beginning of the
-# configuration file, and defaults at the end.
-
-# Site-wide defaults for some commonly used options.  For a comprehensive
-# list of available options, their meanings and defaults, please see the
-# ssh_config(5) man page.
-
-Include /etc/ssh/ssh_config.d/*.conf
-
-# Host *
-#   ForwardAgent no
-#   ForwardX11 no
-#   PasswordAuthentication yes
-#   HostbasedAuthentication no
-#   GSSAPIAuthentication no
-#   GSSAPIDelegateCredentials no
-#   BatchMode no
-#   CheckHostIP yes
-#   AddressFamily any
-#   ConnectTimeout 0
-#   StrictHostKeyChecking ask
-#   IdentityFile ~/.ssh/id_rsa
-#   IdentityFile ~/.ssh/id_dsa
-#   IdentityFile ~/.ssh/id_ecdsa
-#   IdentityFile ~/.ssh/id_ed25519
-#   Port 22
-#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc
-#   MACs hmac-md5,hmac-sha1,umac...@openssh.com
-#   EscapeChar ~
-#   Tunnel no
-#   TunnelDevice any:any
-#   PermitLocalCommand no
-#   VisualHostKey no
-#   ProxyCommand ssh -q -W %h:%p gateway.example.com
-#   RekeyLimit 1G 1h
-#   UserKnownHostsFile ~/.ssh/known_hosts.d/%k
diff --git a/meta/recipes-connectivity/openssh/openssh/sshd_config 
b/meta/recipes-connectivity/openssh/openssh/sshd_config
deleted file mode 100644
index e9eaf9315775..
--- a/meta/recipes-connectivity/openssh/openssh/sshd_config
+++ /dev/null
@@ -1,119 +0,0 @@
-#  $OpenBSD: sshd_config,v 1.104 2021/07/02 05:11:21 dtucker Exp $
-
-# This is the sshd server system-wide configuration file.  See
-# sshd_config(5) for more information.
-
-# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
-
-# The strategy used for options in the default sshd_config shipped with
-# OpenSSH is to specify options with their default value where
-# possible, but leave them commented.  Uncommented options override the
-# default value.
-
-Include /etc/ssh/sshd_config.d/*.conf
-
-#Port 22
-#AddressFamily any
-#ListenAddress 0.0.0.0
-#ListenAddress ::
-
-#HostKey /etc/ssh/ssh_host_rsa_key
-#HostKey /etc/ssh/ssh_host_ecdsa_key
-#HostKey /etc/ssh/ssh_host_ed

Re: [OE-core] Patchtest results for [PATCH 2/7] openssh-config: initial checkin

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
patcht...@automation.yoctoproject.org writes:

> FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed 
> without "License-Update:" tag and description in commit message 
> (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)

This failure seems to be bogus; patch creates a new recipe with a new
LIC_FILES_CHKSUM.  It does not change/update an existing tag.


Enrico

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



[OE-core] Patchtest results for [PATCH 2/7] openssh-config: initial checkin

2024-03-11 Thread Patchtest
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-7-openssh-config-initial-checkin.patch

FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed 
without "License-Update:" tag and description in commit message 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)

PASS: pretest src uri left files 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test Signed-off-by presence 
(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 lic files chksum presence 
(test_metadata.TestMetadata.test_lic_files_chksum_presence)
PASS: test license presence (test_metadata.TestMetadata.test_license_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)
PASS: test src uri left files 
(test_metadata.TestMetadata.test_src_uri_left_files)
PASS: test summary presence (test_metadata.TestMetadata.test_summary_presence)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
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 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 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 (#196962): 
https://lists.openembedded.org/g/openembedded-core/message/196962
Mute This Topic: https://lists.openembedded.org/mt/104868543/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[OE-core] Patchtest results for [PATCH 1/7] openssh: replace complete configuration files by patch

2024-03-11 Thread Patchtest
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/1-7-openssh-replace-complete-configuration-files-by-patch.patch

FAIL: test Signed-off-by presence: A patch file has been added without a 
Signed-off-by tag: 'include-conf.patch' 
(test_patch.TestPatch.test_signed_off_by_presence)
FAIL: test Upstream-Status presence: Upstream-Status is Inappropriate, but no 
reason was provided (test_patch.TestPatch.test_upstream_status_presence_format)

PASS: pretest src uri left files 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
PASS: test Signed-off-by presence 
(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 lic files chksum modified not mentioned 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
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)
PASS: test src uri left files 
(test_metadata.TestMetadata.test_src_uri_left_files)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
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 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 (#196961): 
https://lists.openembedded.org/g/openembedded-core/message/196961
Mute This Topic: https://lists.openembedded.org/mt/104868542/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 0/7] Replace sshd_config patching by snippets

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
To deal with system setups, sshd was configured in the following way:

 - sshd_config is shipped completely by OE and DISTRO_FEATURES (pam,
   x11) are patched in during do_install

   --> this is difficulty to maintain; e.g. sshd_config must be
   synchronized between OpenSSH releases and OE adaptations
   manually inserted

 - two different configuration files (sshd_config + sshd_config_readonly)
   are created; IMAGE_FEATURES decides which one is used and it is patched
   in a ROOTFS_COMMAND in the system

   --> this make it difficult for third party recipes to incorporate
   their changes (they have to go over both files)

   --> the readonly HostKey locations and algorithms are hardcoded
   which makes it difficult to place them e.g. on a persistent
   /opt partition and disable e.g. ecdsa

 - depending on IMAGE_FEATURES (empty passwords, root login), both
   files are patched by a ROOTFS_POSTCOMMAND

   --> these changes are lost when pkgmgmt is used for the image and
   openssh being updated


The patchset:

 - reduces changes to sshd_config to

   | Include /etc/ssh/sshd_config.d/*.conf

   --> This is already the done in current recipe and most mainline
   Linux distributions are doing it

 - moves configuration in new openssh-config recipe which is a weak
   dependency of openssh (and can be replaced by another IMAGE_INSTALL)

   Recipe ships configuration as small snippets which might contain
   dynamically created content (e.g. 'UsePAM yes')

 - IMAGE_FEATURE based setup is done by creating subpackages with
   the corresponding options.  These subpackages are added to
   FEATURE_PACKAGES_ssh-server-openssh

 - readonly rootfs setup has been enhanced by

   | RO_KEYDIR ??= "/var/run/ssh"
   | KEY_ALGORITHMS ??= "rsa ecdsa ed25519"

   parameters which can be overridden.


Enrico Scholz (7):
  openssh: replace complete configuration files by patch
  openssh-config: initial checkin
  openssh: move configuration tweaking in configuration recipe
  image: prepare openssh configuration
  openssh: replace 'allow-empty-password' rootfs scipt by configuration
  openssh: replace 'allow-root-login' rootfs scipt by configuration
  openssh: move read-only-rootfs setup in configuration snippet

 meta/classes-recipe/core-image.bbclass|  19 ++-
 .../rootfs-postcommands.bbclass   |  25 +---
 .../openssh/openssh-config.bb |  51 
 .../60-allow-empty-password.conf  |   1 +
 .../openssh-config/60-allow-root-login.conf   |   1 +
 .../openssh/openssh-config/80-oe.conf |   5 +
 .../openssh/openssh/include-conf.patch|  32 +
 .../openssh/openssh/ssh_config|  48 ---
 .../openssh/openssh/sshd_config   | 119 --
 .../openssh/openssh_9.6p1.bb  |  20 +--
 10 files changed, 112 insertions(+), 209 deletions(-)
 create mode 100644 meta/recipes-connectivity/openssh/openssh-config.bb
 create mode 100644 
meta/recipes-connectivity/openssh/openssh-config/60-allow-empty-password.conf
 create mode 100644 
meta/recipes-connectivity/openssh/openssh-config/60-allow-root-login.conf
 create mode 100644 meta/recipes-connectivity/openssh/openssh-config/80-oe.conf
 create mode 100644 meta/recipes-connectivity/openssh/openssh/include-conf.patch
 delete mode 100644 meta/recipes-connectivity/openssh/openssh/ssh_config
 delete mode 100644 meta/recipes-connectivity/openssh/openssh/sshd_config

-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196955): 
https://lists.openembedded.org/g/openembedded-core/message/196955
Mute This Topic: https://lists.openembedded.org/mt/104868003/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 7/7] openssh: move read-only-rootfs setup in configuration snippet

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

This patch replaces the duplicate 'sshd_config_readonly' configuration
file and logic behind by an extra packages which is installed when
corresponding IMAGE_FEATURES are set.

**NOTE**: this causes a regression when host keys are added manually
to the image.  Users have to do

| OPENSSH_FEATURE_CONFIGURATION:remove = "openssh-config-read-only-rootfs"

in this case, or create a .bbappend for openssh-config which sets
RO_KEYDIR.

Signed-off-by: Enrico Scholz 
---
 meta/classes-recipe/core-image.bbclass  | 12 
 meta/classes-recipe/rootfs-postcommands.bbclass | 13 +
 meta/recipes-connectivity/openssh/openssh-config.bb |  7 +++
 meta/recipes-connectivity/openssh/openssh_9.6p1.bb  |  7 +--
 4 files changed, 21 insertions(+), 18 deletions(-)

diff --git a/meta/classes-recipe/core-image.bbclass 
b/meta/classes-recipe/core-image.bbclass
index 10a2905d9a27..477b6ba47042 100644
--- a/meta/classes-recipe/core-image.bbclass
+++ b/meta/classes-recipe/core-image.bbclass
@@ -84,8 +84,20 @@ CORE_IMAGE_EXTRA_INSTALL ?= ""
 IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}"
 
 OPENSSH_FEATURE_CONFIGURATION = "\
+${@'openssh-config-read-only-rootfs' if etc_is_readonly(d) else ''} \
 ${@bb.utils.contains_any('IMAGE_FEATURES', [ 'debug-tweaks', 
'allow-empty-password' ], 'openssh-config-allow-empty-password', '',d)} \
 ${@bb.utils.contains_any('IMAGE_FEATURES', [ 'debug-tweaks', 
'allow-root-login' ], 'openssh-config-allow-root-login', '',d)} \
 "
 
+def etc_is_readonly(d):
+features = (d.getVar('IMAGE_FEATURES') or "").split()
+
+if 'read-only-rootfs' not in features:
+return False
+
+if 'stateless-rootfs' in features:
+return True
+
+return 'overlayfs-etc' not in features
+
 inherit image
diff --git a/meta/classes-recipe/rootfs-postcommands.bbclass 
b/meta/classes-recipe/rootfs-postcommands.bbclass
index 633f88de6ec8..ba6eb84e4055 100644
--- a/meta/classes-recipe/rootfs-postcommands.bbclass
+++ b/meta/classes-recipe/rootfs-postcommands.bbclass
@@ -188,21 +188,10 @@ read_only_rootfs_hook () {
fi
 
# If we're using openssh and the /etc/ssh directory has no 
pre-generated keys,
-   # we should configure openssh to use the configuration file 
/etc/ssh/sshd_config_readonly
-   # and the keys under /var/run/ssh.
+   # we should configure dropbear to use the keys under /var/lib/dropbear
# If overlayfs-etc is used this is not done as /etc is treated as 
writable
# If stateless-rootfs is enabled this is always done as we don't want 
to save keys then
if ${@ 'true' if not bb.utils.contains('IMAGE_FEATURES', 
'overlayfs-etc', True, False, d) or bb.utils.contains('IMAGE_FEATURES', 
'stateless-rootfs', True, False, d) else 'false'}; then
-   if [ -d ${IMAGE_ROOTFS}/etc/ssh ]; then
-   if [ -e ${IMAGE_ROOTFS}/etc/ssh/ssh_host_rsa_key ]; then
-   echo "SYSCONFDIR=\${SYSCONFDIR:-/etc/ssh}" >> 
${IMAGE_ROOTFS}/etc/default/ssh
-   echo "SSHD_OPTS=" >> 
${IMAGE_ROOTFS}/etc/default/ssh
-   else
-   echo "SYSCONFDIR=\${SYSCONFDIR:-/var/run/ssh}" 
>> ${IMAGE_ROOTFS}/etc/default/ssh
-   echo "SSHD_OPTS='-f 
/etc/ssh/sshd_config_readonly'" >> ${IMAGE_ROOTFS}/etc/default/ssh
-   fi
-   fi
-
# Also tweak the key location for dropbear in the same way.
if [ -d ${IMAGE_ROOTFS}/etc/dropbear ]; then
if [ ! -e 
${IMAGE_ROOTFS}/etc/dropbear/dropbear_rsa_host_key ]; then
diff --git a/meta/recipes-connectivity/openssh/openssh-config.bb 
b/meta/recipes-connectivity/openssh/openssh-config.bb
index d4ed661d8299..d2d0d9f4ad0d 100644
--- a/meta/recipes-connectivity/openssh/openssh-config.bb
+++ b/meta/recipes-connectivity/openssh/openssh-config.bb
@@ -9,6 +9,9 @@ SRC_URI = "\
 file://80-oe.conf \
 "
 
+RO_KEYDIR ??= "/var/run/ssh"
+KEY_ALGORITHMS ??= "rsa ecdsa ed25519"
+
 do_install() {
 d=${D}${sysconfdir}/ssh/sshd_config.d
 install -d "$d"
@@ -27,6 +30,10 @@ do_install() {
 if [ "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}" ]; then
 echo "X11Forwarding yes" >> "$f"
 fi
+
+for alg in ${KEY_ALGORITHMS}; do
+printf 'HostKey %s/ssh_host_%s_key\n' '${RO_KEYDIR}' "$alg"
+done > $d/60-read-only-rootfs.conf
 }
 
 python populate_packages:prepend() {
diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb 
b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
index e792b459d838..29bc132de8ef 100644
--- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
@@ -121,11 +121,6 @@ do_install:append () {
 
# Create config files for read-only rootfs
install -d ${D}${sysconfdir}/ssh
-   install -m 644 ${D}${sysconfdir}/ssh/sshd_config 
${D}${s

[OE-core] [PATCH 4/7] image: prepare openssh configuration

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Add an OPENSSH_FEATURE_CONFIGURATION variable which will hold openssh
configuration packages.

Signed-off-by: Enrico Scholz 
---
 meta/classes-recipe/core-image.bbclass | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/classes-recipe/core-image.bbclass 
b/meta/classes-recipe/core-image.bbclass
index 40fc15cb04f2..adf236e0693e 100644
--- a/meta/classes-recipe/core-image.bbclass
+++ b/meta/classes-recipe/core-image.bbclass
@@ -55,7 +55,7 @@ FEATURE_PACKAGES_tools-sdk = "packagegroup-core-sdk 
packagegroup-core-standalone
 FEATURE_PACKAGES_nfs-server = "packagegroup-core-nfs-server"
 FEATURE_PACKAGES_nfs-client = "packagegroup-core-nfs-client"
 FEATURE_PACKAGES_ssh-server-dropbear = "packagegroup-core-ssh-dropbear"
-FEATURE_PACKAGES_ssh-server-openssh = "packagegroup-core-ssh-openssh"
+FEATURE_PACKAGES_ssh-server-openssh = "packagegroup-core-ssh-openssh 
${OPENSSH_FEATURE_CONFIGURATION}"
 FEATURE_PACKAGES_hwcodecs = "${MACHINE_HWCODECS}"
 
 
@@ -83,4 +83,7 @@ CORE_IMAGE_EXTRA_INSTALL ?= ""
 
 IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}"
 
+OPENSSH_FEATURE_CONFIGURATION = "\
+"
+
 inherit image
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196959): 
https://lists.openembedded.org/g/openembedded-core/message/196959
Mute This Topic: https://lists.openembedded.org/mt/104868009/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/7] openssh: replace complete configuration files by patch

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Instead of shipping the whole configuration files for openssh, add
small patch includes configuration snippets from subdirectories.

This allows us to keep the original upstream configuration which is
mainly useful for documentation purposes.  It makes it more easy to
identify OE specific setup.

Signed-off-by: Enrico Scholz 
---
 .../openssh/openssh/include-conf.patch|  32 +
 .../openssh/openssh/ssh_config|  48 ---
 .../openssh/openssh/sshd_config   | 119 --
 .../openssh/openssh_9.6p1.bb  |   5 +-
 4 files changed, 33 insertions(+), 171 deletions(-)
 create mode 100644 meta/recipes-connectivity/openssh/openssh/include-conf.patch
 delete mode 100644 meta/recipes-connectivity/openssh/openssh/ssh_config
 delete mode 100644 meta/recipes-connectivity/openssh/openssh/sshd_config

diff --git a/meta/recipes-connectivity/openssh/openssh/include-conf.patch 
b/meta/recipes-connectivity/openssh/openssh/include-conf.patch
new file mode 100644
index ..3e0bd2957e25
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh/include-conf.patch
@@ -0,0 +1,32 @@
+Include configuration snippets from subdirectory.
+
+NOTE: first configuration option wins.
+
+Upstream-Status: Inappropriate
+
+Index: openssh-9.5p1/ssh_config
+===
+--- openssh-9.5p1.orig/ssh_config
 openssh-9.5p1/ssh_config
+@@ -5,6 +5,8 @@
+ # users, and the values can be changed in per-user configuration files
+ # or on the command line.
+ 
++Include /etc/ssh/ssh_config.d/*.conf
++
+ # Configuration data is parsed as follows:
+ #  1. command line options
+ #  2. user-specific file
+Index: openssh-9.5p1/sshd_config
+===
+--- openssh-9.5p1.orig/sshd_config
 openssh-9.5p1/sshd_config
+@@ -10,6 +10,8 @@
+ # possible, but leave them commented.  Uncommented options override the
+ # default value.
+ 
++Include /etc/ssh/sshd_config.d/*.conf
++
+ #Port 22
+ #AddressFamily any
+ #ListenAddress 0.0.0.0
diff --git a/meta/recipes-connectivity/openssh/openssh/ssh_config 
b/meta/recipes-connectivity/openssh/openssh/ssh_config
deleted file mode 100644
index cb2774a163ed..
--- a/meta/recipes-connectivity/openssh/openssh/ssh_config
+++ /dev/null
@@ -1,48 +0,0 @@
-#  $OpenBSD: ssh_config,v 1.35 2020/07/17 03:43:42 dtucker Exp $
-
-# This is the ssh client system-wide configuration file.  See
-# ssh_config(5) for more information.  This file provides defaults for
-# users, and the values can be changed in per-user configuration files
-# or on the command line.
-
-# Configuration data is parsed as follows:
-#  1. command line options
-#  2. user-specific file
-#  3. system-wide file
-# Any configuration value is only changed the first time it is set.
-# Thus, host-specific definitions should be at the beginning of the
-# configuration file, and defaults at the end.
-
-# Site-wide defaults for some commonly used options.  For a comprehensive
-# list of available options, their meanings and defaults, please see the
-# ssh_config(5) man page.
-
-Include /etc/ssh/ssh_config.d/*.conf
-
-# Host *
-#   ForwardAgent no
-#   ForwardX11 no
-#   PasswordAuthentication yes
-#   HostbasedAuthentication no
-#   GSSAPIAuthentication no
-#   GSSAPIDelegateCredentials no
-#   BatchMode no
-#   CheckHostIP yes
-#   AddressFamily any
-#   ConnectTimeout 0
-#   StrictHostKeyChecking ask
-#   IdentityFile ~/.ssh/id_rsa
-#   IdentityFile ~/.ssh/id_dsa
-#   IdentityFile ~/.ssh/id_ecdsa
-#   IdentityFile ~/.ssh/id_ed25519
-#   Port 22
-#   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc
-#   MACs hmac-md5,hmac-sha1,umac...@openssh.com
-#   EscapeChar ~
-#   Tunnel no
-#   TunnelDevice any:any
-#   PermitLocalCommand no
-#   VisualHostKey no
-#   ProxyCommand ssh -q -W %h:%p gateway.example.com
-#   RekeyLimit 1G 1h
-#   UserKnownHostsFile ~/.ssh/known_hosts.d/%k
diff --git a/meta/recipes-connectivity/openssh/openssh/sshd_config 
b/meta/recipes-connectivity/openssh/openssh/sshd_config
deleted file mode 100644
index e9eaf9315775..
--- a/meta/recipes-connectivity/openssh/openssh/sshd_config
+++ /dev/null
@@ -1,119 +0,0 @@
-#  $OpenBSD: sshd_config,v 1.104 2021/07/02 05:11:21 dtucker Exp $
-
-# This is the sshd server system-wide configuration file.  See
-# sshd_config(5) for more information.
-
-# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
-
-# The strategy used for options in the default sshd_config shipped with
-# OpenSSH is to specify options with their default value where
-# possible, but leave them commented.  Uncommented options override the
-# default value.
-
-Include /etc/ssh/sshd_config.d/*.conf
-
-#Port 22
-#AddressFamily any
-#ListenAddress 0.0.0.0
-#ListenAddress ::
-
-#HostKey /etc/ssh/ssh_host_rsa_key
-#HostKey /etc/ssh/ssh_host_ecdsa_key
-#HostKey /etc/ssh/ssh_host_ed25519_key
-
-# C

[OE-core] [PATCH 6/7] openssh: replace 'allow-root-login' rootfs scipt by configuration

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Install 'openssh-config-allow-root-login' when corresponding
IMAGE_FEATURES are active.

Signed-off-by: Enrico Scholz 
---
 meta/classes-recipe/core-image.bbclass  | 1 +
 meta/classes-recipe/rootfs-postcommands.bbclass | 6 --
 meta/recipes-connectivity/openssh/openssh-config.bb | 2 ++
 .../openssh/openssh-config/60-allow-root-login.conf | 1 +
 4 files changed, 4 insertions(+), 6 deletions(-)
 create mode 100644 
meta/recipes-connectivity/openssh/openssh-config/60-allow-root-login.conf

diff --git a/meta/classes-recipe/core-image.bbclass 
b/meta/classes-recipe/core-image.bbclass
index 63e0e99b2a56..10a2905d9a27 100644
--- a/meta/classes-recipe/core-image.bbclass
+++ b/meta/classes-recipe/core-image.bbclass
@@ -85,6 +85,7 @@ IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}"
 
 OPENSSH_FEATURE_CONFIGURATION = "\
 ${@bb.utils.contains_any('IMAGE_FEATURES', [ 'debug-tweaks', 
'allow-empty-password' ], 'openssh-config-allow-empty-password', '',d)} \
+${@bb.utils.contains_any('IMAGE_FEATURES', [ 'debug-tweaks', 
'allow-root-login' ], 'openssh-config-allow-root-login', '',d)} \
 "
 
 inherit image
diff --git a/meta/classes-recipe/rootfs-postcommands.bbclass 
b/meta/classes-recipe/rootfs-postcommands.bbclass
index 88f88505b5ed..633f88de6ec8 100644
--- a/meta/classes-recipe/rootfs-postcommands.bbclass
+++ b/meta/classes-recipe/rootfs-postcommands.bbclass
@@ -268,12 +268,6 @@ ssh_allow_empty_password () {
 # allow dropbear/openssh to accept root logins
 #
 ssh_allow_root_login () {
-   for config in sshd_config sshd_config_readonly; do
-   if [ -e ${IMAGE_ROOTFS}${sysconfdir}/ssh/$config ]; then
-   sed -i 
's/^[#[:space:]]*PermitRootLogin.*/PermitRootLogin yes/' 
${IMAGE_ROOTFS}${sysconfdir}/ssh/$config
-   fi
-   done
-
if [ -e ${IMAGE_ROOTFS}${sbindir}/dropbear ] ; then
if grep -q DROPBEAR_EXTRA_ARGS 
${IMAGE_ROOTFS}${sysconfdir}/default/dropbear 2>/dev/null ; then
sed -i '/^DROPBEAR_EXTRA_ARGS=/ s/-w//' 
${IMAGE_ROOTFS}${sysconfdir}/default/dropbear
diff --git a/meta/recipes-connectivity/openssh/openssh-config.bb 
b/meta/recipes-connectivity/openssh/openssh-config.bb
index 20dfe086f8ab..d4ed661d8299 100644
--- a/meta/recipes-connectivity/openssh/openssh-config.bb
+++ b/meta/recipes-connectivity/openssh/openssh-config.bb
@@ -5,6 +5,7 @@ LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384
 
 SRC_URI = "\
 file://60-allow-empty-password.conf \
+file://60-allow-root-login.conf \
 file://80-oe.conf \
 "
 
@@ -13,6 +14,7 @@ do_install() {
 install -d "$d"
 install -p -m 0644 \
 ${WORKDIR}/60-allow-empty-password.conf \
+${WORKDIR}/60-allow-root-login.conf \
 ${WORKDIR}/80-oe.conf \
 "$d"/
 
diff --git 
a/meta/recipes-connectivity/openssh/openssh-config/60-allow-root-login.conf 
b/meta/recipes-connectivity/openssh/openssh-config/60-allow-root-login.conf
new file mode 100644
index ..1073982f77c1
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh-config/60-allow-root-login.conf
@@ -0,0 +1 @@
+PermitRootLogin yes
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196958): 
https://lists.openembedded.org/g/openembedded-core/message/196958
Mute This Topic: https://lists.openembedded.org/mt/104868007/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/7] openssh: replace 'allow-empty-password' rootfs scipt by configuration

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Install 'openssh-config-allow-empty-password' when corresponding
IMAGE_FEATURES are active.

Signed-off-by: Enrico Scholz 
---
 meta/classes-recipe/core-image.bbclass  | 1 +
 meta/classes-recipe/rootfs-postcommands.bbclass | 6 --
 meta/recipes-connectivity/openssh/openssh-config.bb | 2 ++
 .../openssh/openssh-config/60-allow-empty-password.conf | 1 +
 4 files changed, 4 insertions(+), 6 deletions(-)
 create mode 100644 
meta/recipes-connectivity/openssh/openssh-config/60-allow-empty-password.conf

diff --git a/meta/classes-recipe/core-image.bbclass 
b/meta/classes-recipe/core-image.bbclass
index adf236e0693e..63e0e99b2a56 100644
--- a/meta/classes-recipe/core-image.bbclass
+++ b/meta/classes-recipe/core-image.bbclass
@@ -84,6 +84,7 @@ CORE_IMAGE_EXTRA_INSTALL ?= ""
 IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}"
 
 OPENSSH_FEATURE_CONFIGURATION = "\
+${@bb.utils.contains_any('IMAGE_FEATURES', [ 'debug-tweaks', 
'allow-empty-password' ], 'openssh-config-allow-empty-password', '',d)} \
 "
 
 inherit image
diff --git a/meta/classes-recipe/rootfs-postcommands.bbclass 
b/meta/classes-recipe/rootfs-postcommands.bbclass
index e81b69a239b5..88f88505b5ed 100644
--- a/meta/classes-recipe/rootfs-postcommands.bbclass
+++ b/meta/classes-recipe/rootfs-postcommands.bbclass
@@ -246,12 +246,6 @@ zap_empty_root_password () {
 # allow dropbear/openssh to accept logins from accounts with an empty password 
string
 #
 ssh_allow_empty_password () {
-   for config in sshd_config sshd_config_readonly; do
-   if [ -e ${IMAGE_ROOTFS}${sysconfdir}/ssh/$config ]; then
-   sed -i 
's/^[#[:space:]]*PermitEmptyPasswords.*/PermitEmptyPasswords yes/' 
${IMAGE_ROOTFS}${sysconfdir}/ssh/$config
-   fi
-   done
-
if [ -e ${IMAGE_ROOTFS}${sbindir}/dropbear ] ; then
if grep -q DROPBEAR_EXTRA_ARGS 
${IMAGE_ROOTFS}${sysconfdir}/default/dropbear 2>/dev/null ; then
if ! grep -q "DROPBEAR_EXTRA_ARGS=.*-B" 
${IMAGE_ROOTFS}${sysconfdir}/default/dropbear ; then
diff --git a/meta/recipes-connectivity/openssh/openssh-config.bb 
b/meta/recipes-connectivity/openssh/openssh-config.bb
index 312a1c903f63..20dfe086f8ab 100644
--- a/meta/recipes-connectivity/openssh/openssh-config.bb
+++ b/meta/recipes-connectivity/openssh/openssh-config.bb
@@ -4,6 +4,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 
 SRC_URI = "\
+file://60-allow-empty-password.conf \
 file://80-oe.conf \
 "
 
@@ -11,6 +12,7 @@ do_install() {
 d=${D}${sysconfdir}/ssh/sshd_config.d
 install -d "$d"
 install -p -m 0644 \
+${WORKDIR}/60-allow-empty-password.conf \
 ${WORKDIR}/80-oe.conf \
 "$d"/
 
diff --git 
a/meta/recipes-connectivity/openssh/openssh-config/60-allow-empty-password.conf 
b/meta/recipes-connectivity/openssh/openssh-config/60-allow-empty-password.conf
new file mode 100644
index ..04e75ab6cefa
--- /dev/null
+++ 
b/meta/recipes-connectivity/openssh/openssh-config/60-allow-empty-password.conf
@@ -0,0 +1 @@
+PermitEmptyPasswords yes
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196956): 
https://lists.openembedded.org/g/openembedded-core/message/196956
Mute This Topic: https://lists.openembedded.org/mt/104868004/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/7] openssh-config: initial checkin

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Place OE specific openssh setup (which was removed in a previous
patch) in a configuration snippet.

Signed-off-by: Enrico Scholz 
---
 .../openssh/openssh-config.bb | 30 +++
 .../openssh/openssh-config/80-oe.conf |  5 
 .../openssh/openssh_9.6p1.bb  |  2 ++
 3 files changed, 37 insertions(+)
 create mode 100644 meta/recipes-connectivity/openssh/openssh-config.bb
 create mode 100644 meta/recipes-connectivity/openssh/openssh-config/80-oe.conf

diff --git a/meta/recipes-connectivity/openssh/openssh-config.bb 
b/meta/recipes-connectivity/openssh/openssh-config.bb
new file mode 100644
index ..2ef6a770fcfe
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh-config.bb
@@ -0,0 +1,30 @@
+SUMMARY = "OE openssh configuration"
+DESCRIPTION = "Provides openssh configuration snippets which correspond to 
IMAGE_FEATURE"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+
+SRC_URI = "\
+file://80-oe.conf \
+"
+
+do_install() {
+d=${D}${sysconfdir}/ssh/sshd_config.d
+install -d "$d"
+install -p -m 0644 \
+${WORKDIR}/80-oe.conf \
+"$d"/
+}
+
+python populate_packages:prepend() {
+dir = d.expand('${sysconfdir}/ssh/sshd_config.d')
+
+do_split_packages(d, dir, '^60-(.*)\.conf',
+  output_pattern='${PN}-%s',
+  description="openssh config for '%s' feature",
+  extra_depends='',
+  prepend=True)
+}
+
+PACKAGES_DYNAMIC = "${PN}-*"
+
+FILES:${PN} = "${sysconfdir}/ssh/sshd_config.d/80-oe.conf"
diff --git a/meta/recipes-connectivity/openssh/openssh-config/80-oe.conf 
b/meta/recipes-connectivity/openssh/openssh-config/80-oe.conf
new file mode 100644
index ..9a92d3c8d197
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh-config/80-oe.conf
@@ -0,0 +1,5 @@
+KbdInteractiveAuthentication no
+
+Compression no
+ClientAliveInterval 15
+ClientAliveCountMax 4
diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb 
b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
index d500ca6019fe..406b349f8283 100644
--- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
@@ -191,6 +191,8 @@ RCONFLICTS:${PN}-sshd = "dropbear"
 CONFFILES:${PN}-sshd = "${sysconfdir}/ssh/sshd_config"
 CONFFILES:${PN}-ssh = "${sysconfdir}/ssh/ssh_config"
 
+RRECOMMENDS:${PN} += "openssh-config"
+
 ALTERNATIVE_PRIORITY = "90"
 ALTERNATIVE:${PN}-scp = "scp"
 ALTERNATIVE:${PN}-ssh = "ssh"
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196953): 
https://lists.openembedded.org/g/openembedded-core/message/196953
Mute This Topic: https://lists.openembedded.org/mt/104868001/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/7] openssh: move configuration tweaking in configuration recipe

2024-03-11 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz 

Instead of applying DISTRO_FEATURE based setup directly to
sshd_config, add it to our configuration snippet.

Signed-off-by: Enrico Scholz 
---
 meta/recipes-connectivity/openssh/openssh-config.bb | 10 ++
 meta/recipes-connectivity/openssh/openssh_9.6p1.bb  |  8 
 2 files changed, 10 insertions(+), 8 deletions(-)

diff --git a/meta/recipes-connectivity/openssh/openssh-config.bb 
b/meta/recipes-connectivity/openssh/openssh-config.bb
index 2ef6a770fcfe..312a1c903f63 100644
--- a/meta/recipes-connectivity/openssh/openssh-config.bb
+++ b/meta/recipes-connectivity/openssh/openssh-config.bb
@@ -13,6 +13,16 @@ do_install() {
 install -p -m 0644 \
 ${WORKDIR}/80-oe.conf \
 "$d"/
+
+f=$d/80-oe.conf
+
+if [ "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)}" ]; then
+echo "UsePAM yes" >> "$f"
+fi
+
+if [ "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}" ]; then
+echo "X11Forwarding yes" >> "$f"
+fi
 }
 
 python populate_packages:prepend() {
diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb 
b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
index 406b349f8283..e792b459d838 100644
--- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
@@ -109,11 +109,6 @@ do_compile_ptest() {
 do_install:append () {
if [ "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)}" ]; then
install -D -m 0644 ${WORKDIR}/sshd ${D}${sysconfdir}/pam.d/sshd
-   sed -i -e 's:#UsePAM no:UsePAM yes:' 
${D}${sysconfdir}/ssh/sshd_config
-   fi
-
-   if [ "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}" ]; then
-   sed -i -e 's:#X11Forwarding no:X11Forwarding yes:' 
${D}${sysconfdir}/ssh/sshd_config
fi
 
install -d ${D}${sysconfdir}/init.d
@@ -188,9 +183,6 @@ RPROVIDES:${PN}-sshd = "sshd"
 RCONFLICTS:${PN} = "dropbear"
 RCONFLICTS:${PN}-sshd = "dropbear"
 
-CONFFILES:${PN}-sshd = "${sysconfdir}/ssh/sshd_config"
-CONFFILES:${PN}-ssh = "${sysconfdir}/ssh/ssh_config"
-
 RRECOMMENDS:${PN} += "openssh-config"
 
 ALTERNATIVE_PRIORITY = "90"
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196954): 
https://lists.openembedded.org/g/openembedded-core/message/196954
Mute This Topic: https://lists.openembedded.org/mt/104868002/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 6/7][kirkstone] linux-yocto/5.15: fix partion scanning

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

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

1/1 [
Author: Christoph Hellwig
Email: h...@lst.de
Subject: block, loop: support partitions without scanning
Date: Fri, 27 May 2022 07:58:06 +0200

Historically we did distinguish between a flag that surpressed partition
scanning, and a combinations of the minors variable and another flag if
any partitions were supported.  This was generally confusing and doesn't
make much sense, but some corner case uses of the loop driver actually
do want to support manually added partitions on a device that does not
actively scan for partitions.  To make things worsee the loop driver
also wants to dynamically toggle the scanning for partitions on a live
gendisk, which makes the disk->flags updates non-atomic.

Introduce a new GD_SUPPRESS_PART_SCAN bit in disk->state that disables
just scanning for partitions, and toggle that instead of GENHD_FL_NO_PART
in the loop driver.

[bva: Notes for this backport:
   - drop return code in disk_scan_partitions for GD_SUPPRESS_PART_SCAN.
 The check doesn't strictly need ot be in this routine in 5.15, but
 this faciliates future changes in this area, since there are
 other checks in the same function.
   - GD_SUPPRESS_PART_SCAN could go to genh.c, but genhd.c includes
 blkdev.h, so we leave the new GD_SUPPRESS_PART_SCAN definition
 in the same places as where it was introduced upstream to keep
 the changes to a minimum
   - upstream commit e16e506ccd673 merges blkdev_reread_part into
 disk_scan_partitions. Backporting that change is more churn
 than we need, so we also add the check for GD_SUPPRESS_PART_SCAN
 into that routine to have the check hit in a 5.15 context.
]

Upstream-Status: Backport [commit b9684a71fca79]

Fixes: 1ebe2e5f9d68 ("block: remove GENHD_FL_EXT_DEVT")
Reported-by: Ming Lei 
Signed-off-by: Christoph Hellwig 
Reviewed-by: Ming Lei 
Link: https://lore.kernel.org/r/20220527055806.1972352-1-...@lst.de
Signed-off-by: Jens Axboe 
Signed-off-by: Bruce Ashfield 
]

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto-rt_5.15.bb  |  4 ++--
 .../linux/linux-yocto-tiny_5.15.bb|  4 ++--
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 22 +--
 3 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
index 7e80b6a3b2..00c03411b1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
@@ -11,8 +11,8 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "e856ac0473964a3f7b3b5544814decb8ae514c9a"
-SRCREV_meta ?= "7057b38eb882224cc002d13b7303e1a1767fa629"
+SRCREV_machine ?= "da32201bc41d994b0300c6b4738505f4875dc190"
+SRCREV_meta ?= "bef59dc5a78b4d101d1be23d4b36a73fd849241a"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
index 7253ab15f3..2051d1c0a1 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
@@ -14,8 +14,8 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "9dc9a9a07dba418b65e884e42e230c6c6e1a7f44"
-SRCREV_meta ?= "7057b38eb882224cc002d13b7303e1a1767fa629"
+SRCREV_machine ?= "540fc92dd7359025bb09962431565b5a9627536b"
+SRCREV_meta ?= "bef59dc5a78b4d101d1be23d4b36a73fd849241a"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
index 065091f25a..101aceb3dc 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
@@ -14,17 +14,17 @@ KBRANCH:qemux86  ?= "v5.15/standard/base"
 KBRANCH:qemux86-64 ?= "v5.15/standard/base"
 KBRANCH:qemumips64 ?= "v5.15/standard/mti-malta64"
 
-SRCREV_machine:qemuarm ?= "f99523c4bf2f8e48e9b2d2cd3cffee6c494b124e"
-SRCREV_machine:qemuarm64 ?= "8ee4ded018a7d795de4df15931c4a0a3a1b1d54d"
-SRCREV_machine:qemumips ?= "b8fbb69a10c4eea7ae580e8249a46056d1db24d1"
-SRCREV_machine:qemuppc ?= "533c5a1f7605c4f94161378a24a5d938b4b8c269"
-SRCREV_machine:qemuriscv64 ?= "68dd3d2718105c6a692c1333ae24c939297f8337"
-SRCREV_machine:qemuriscv32 ?= "68dd3d2718105c6a692c1333ae24c939297f8337"
-SRCREV_machine:qemux86 ?= "68dd3d2718105c6a692c1333ae24c939297f8337"
-SRCREV_machine:qemux86-64 ?= "68dd3d2718105c6a692c1333ae24c939297f8337"
-SRCREV_machine:qe

[OE-core] [PATCH 7/7][kirkstone] yocto-bsp: update to v5.15.150

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

Bumping the reference BSPs to match the version of the qemu*
BSPs in oe-core.

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto_5.15.bbappend  | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.15.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.15.bbappend
index 3ad175dc84..c6d145fdb9 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.15.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.15.bbappend
@@ -7,17 +7,17 @@ KMACHINE:genericx86 ?= "common-pc"
 KMACHINE:genericx86-64 ?= "common-pc-64"
 KMACHINE:beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine:genericx86 ?= "0b628306d1f9ea28c0e86369ce9bb87a47893c9c"
-SRCREV_machine:genericx86-64 ?= "0b628306d1f9ea28c0e86369ce9bb87a47893c9c"
-SRCREV_machine:edgerouter ?= "90f1ee6589264545f548d731c2480b08a007230f"
-SRCREV_machine:beaglebone-yocto ?= "9aabbaa89fcb21af7028e814c1f5b61171314d5a"
+SRCREV_machine:genericx86 ?= "7c82dac028864e8a608e70d3ac2dbc05b3cd1e14"
+SRCREV_machine:genericx86-64 ?= "7c82dac028864e8a608e70d3ac2dbc05b3cd1e14"
+SRCREV_machine:edgerouter ?= "23b867c1a618572a36b6283f55746a5162e08cc7"
+SRCREV_machine:beaglebone-yocto ?= "4fca0c437367cf4d4fe158d74e0ae880a3f99d3c"
 
 COMPATIBLE_MACHINE:genericx86 = "genericx86"
 COMPATIBLE_MACHINE:genericx86-64 = "genericx86-64"
 COMPATIBLE_MACHINE:edgerouter = "edgerouter"
 COMPATIBLE_MACHINE:beaglebone-yocto = "beaglebone-yocto"
 
-LINUX_VERSION:genericx86 = "5.15.72"
-LINUX_VERSION:genericx86-64 = "5.15.72"
-LINUX_VERSION:edgerouter = "5.15.54"
-LINUX_VERSION:beaglebone-yocto = "5.15.54"
+LINUX_VERSION:genericx86 = "5.15.150"
+LINUX_VERSION:genericx86-64 = "5.15.150"
+LINUX_VERSION:edgerouter = "5.15.150"
+LINUX_VERSION:beaglebone-yocto = "5.15.150"
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196952): 
https://lists.openembedded.org/g/openembedded-core/message/196952
Mute This Topic: https://lists.openembedded.org/mt/104867033/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/7][kirkstone] linux-yocto/5.15: update CVE exclusions (5.15.150)

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

Data pulled from: https://github.com/nluedtke/linux_kernel_cves

1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 25Feb24
Date: Sun, 25 Feb 2024 07:03:08 -0500

]

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/cve-exclusion_5.15.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/cve-exclusion_5.15.inc 
b/meta/recipes-kernel/linux/cve-exclusion_5.15.inc
index 2e30efe6be..922d7f457f 100644
--- a/meta/recipes-kernel/linux/cve-exclusion_5.15.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion_5.15.inc
@@ -1,9 +1,9 @@
 
 # Auto-generated CVE metadata, DO NOT EDIT BY HAND.
-# Generated at 2024-02-26 23:36:34.200936 for version 5.15.149
+# Generated at 2024-03-08 10:36:30.059302 for version 5.15.150
 
 python check_kernel_cve_status_version() {
-this_version = "5.15.149"
+this_version = "5.15.150"
 kernel_version = d.getVar("LINUX_VERSION")
 if kernel_version != this_version:
 bb.warn("Kernel CVE status needs updating: generated for %s but kernel 
is %s" % (this_version, kernel_version))
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196950): 
https://lists.openembedded.org/g/openembedded-core/message/196950
Mute This Topic: https://lists.openembedded.org/mt/104867031/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/7][kirkstone] linux-yocto/5.15: update to v5.15.150

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

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

80efc6265290 Linux 5.15.150
da6cabc1981e r8169: use new PM macros
b7f3fac6d301 netfilter: nf_tables: can't schedule in nft_chain_validate
a4efc62cd1ed ext4: avoid bb_free and bb_fragments inconsistency in 
mb_free_blocks()
c1317822e2de ext4: regenerate buddy after block freeing failed if under fc 
replay
d82ec7529c5f netfilter: nf_tables: fix scheduling-while-atomic splat
97eaa2955db4 arp: Prevent overflow in arp_req_get().
d7b6fa97ec89 fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via 
libaio
df31d05f0678 cifs: fix mid leak during reconnection after timeout threshold
aade859419ce i2c: imx: when being a target, mark the last read as processed
cb21407f0b39 i2c: imx: Add timer for handling the stop condition
33f649f1b1ce drm/amd/display: Fix memory leak in dm_sw_fini()
9a03126588e5 drm/syncobj: call drm_syncobj_fence_add_wait when 
WAIT_AVAILABLE flag is set
13b57b5cd591 netfilter: nft_flow_offload: release dst in case direct xmit 
path is used
4c167af9f6b5 netfilter: nft_flow_offload: reset dst in route object after 
setting up flow
7c71b831220e netfilter: flowtable: simplify route logic
664264a5c55b netfilter: nf_tables: set dormant flag on hook register failure
4338032aa90b tls: stop recv() if initial process_rx_list gave us non-DATA
ea845237a39d tls: rx: drop pointless else after goto
8b32e43a80a1 tls: rx: jump to a more appropriate label
39603a6d4e71 s390: use the correct count for __iowrite64_copy()
8cae520f21ad octeontx2-af: Consider the action set by PF
6dae096960bc drm/nouveau/instmem: fix uninitialized_var.cocci warning
4d3b2bd995ed net: dev: Convert sa_data to flexible array in struct sockaddr
d65ec3e48f70 packet: move from strlcpy with unused retval to strscpy
91b020aaa1e5 ipv6: sr: fix possible use-after-free and null-ptr-deref
e56662160fc2 afs: Increase buffer size in afs_update_volume_status()
5268bb02107b bpf: Fix racing between bpf_timer_cancel_and_free and 
bpf_timer_cancel
6800ad7417f3 ata: ahci_ceva: fix error handling for Xilinx GT PHY support
7fcc31a3a705 ata: libahci_platform: Introduce reset assertion/deassertion 
methods
ddac2e0e656e ata: libahci_platform: Convert to using devm bulk clocks API
302b92b37304 ipv6: properly combine dev_base_seq and ipv6.dev_addr_genid
a75b49547831 ipv4: properly combine dev_base_seq and ipv4.dev_addr_genid
2a7b878a7dad net: stmmac: Fix incorrect dereference in interrupt handlers
a41d9142d2dd nouveau: fix function cast warnings
1087c284fd11 scsi: jazz_esp: Only build if SCSI core is builtin
4e395fb89e7e bpf, scripts: Correct GPL license name
cd6070d9f5e7 RDMA/srpt: fix function pointer cast warnings
656bd1702fea arm64: dts: rockchip: set num-cs property for spi on px30
135e5465fefa RDMA/qedr: Fix qedr_create_user_qp error flow
989af2f29342 RDMA/srpt: Support specifying the srpt_service_guid parameter
b6e660e07622 RDMA/irdma: Add AE for too many RNRS
056ed95befd1 RDMA/irdma: Set the CQ read threshold for GEN 1
a95d4cf82775 RDMA/irdma: Validate max_send_wr and max_recv_wr
635d79aa477f RDMA/irdma: Fix KASAN issue with tasklet
aeb5ac1c9d10 RDMA/bnxt_re: Return error for SRQ resize
52de5805c147 IB/hfi1: Fix a memleak in init_credit_return
48c63a174489 cifs: add a warning when the in-flight count goes negative
6538b6d13ce3 xhci: track port suspend state correctly in unsuccessful 
resume cases
8839d5728baa xhci: decouple usb2 port resume and get_port_status request 
handling
8af9de2a5ba1 xhci: clear usb2 resume related variables in one place.
a99c8f1abef9 xhci: rename resume_done to resume_timestamp
63f0e79cf382 xhci: move port specific items such as state completions to 
port structure
ea6c19c7365d xhci: cleanup xhci_hub_control port references
95973afc870c ACPI: resource: Skip IRQ override on ASUS ExpertBook B1502CBA
4f080b6487bd ACPI: resource: Skip IRQ override on Asus Expertbook B2402CBA
c2a9376d507e ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks
1b64ff947a5a ACPI: resource: Skip IRQ override on Asus Vivobook S5602ZA
f3607954f2e6 ACPI: resource: Add ASUS model S5402ZA to quirks
27e99d785721 ACPI: video: Add backlight=native DMI quirk for Apple iMac12,1 
and iMac12,2
cb1003c07e74 ARM: dts: BCM53573: Describe on-SoC BCM53125 rev 4 switch
28e5e3e59b3b arm64: dts: rockchip: add SPDIF node for ROCK Pi 4
99c8b2e99783 arm64: dts: rockchip: add ES8316 codec for ROCK Pi 4
371036bf7666 arm64: dts: rockchip: fix regulator name on rk3399-rock-4
92dcd7d6c606 exfat: support dynamic allocate bh for exfat_entry_set_cache
b4dc693b29ef wifi: iwlwifi: mvm: avoid baid size integer overflow
fa92c463eba7 igb: Fix igb_down hung on surprise removal
16f653776caf wifi: wext-

[OE-core] [PATCH 3/7][kirkstone] linux-yocto/5.10: update to v5.10.210

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

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

aa6ca808a467 Linux 5.10.210
cf5a69e35591 PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq()
9f53d24852ff net: bcmgenet: Fix EEE implementation
9a865a11d689 netfilter: nf_tables: fix pointer math issue in 
nft_byteorder_eval()
67f386f75637 drm/msm/dsi: Enable runtime PM
21b38d85f6de PM: runtime: Have devm_pm_runtime_enable() handle 
pm_runtime_dont_use_autosuspend()
ede393e11819 PM: runtime: add devm_pm_runtime_enable helper
a891a0621e72 dm: limit the number of targets and parameter size area
c90746c03b3c nilfs2: replace WARN_ONs for invalid DAT metadata block 
requests
f3e4963566f5 nilfs2: fix potential bug in end_buffer_async_write
db896bbe4a9c sched/membarrier: reduce the ability to hammer on 
sys_membarrier
8f8f18564374 net: prevent mss overflow in skb_segment()
f7e0231eeaa3 Revert "arm64: Stash shadow stack pointer in the task struct 
on interrupt"
70ca0dbae4e9 hrtimer: Ignore slack time for RT tasks in 
schedule_hrtimeout_range()
c80ddc10927f netfilter: ipset: Missing gc cancellations fixed
a24d5f2ac8ef netfilter: ipset: fix performance regression in swap operation
583a6c76b949 scripts/decode_stacktrace.sh: optionally use LLVM utilities
0f906882eba5 scripts: decode_stacktrace: demangle Rust symbols
a3d71b6ae935 scripts/decode_stacktrace.sh: support old bash version
ae992f14b117 scripts/decode_stacktrace.sh: silence stderr messages from 
addr2line/nm
00f09825e14c serial: 8250_exar: Set missing rs485_supported flag
84bf7b87594d serial: 8250_exar: Fill in rs485_supported
dfd8b9d26b8b serial: Add rs485_supported to uart_port
0c3687822259 crypto: lib/mpi - Fix unexpected pointer access in mpi_ec_init
e0d2eeec88ae mips: Fix max_mapnr being uninitialized on early stages
41a4bd51d87c PCI: dwc: endpoint: Fix dw_pcie_ep_raise_msix_irq() alignment 
support
ff67f77fb0fc bus: moxtet: Add spi device table
88ec9bbcd33c Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"
6a42eb0d2170 tracing: Inform kmemleak of saved_cmdlines allocation
3a6e27dbe2fe pmdomain: core: Move the unused cleanup to a _sync initcall
978e50ef8c38 can: j1939: Fix UAF in j1939_sk_match_filter during 
setsockopt(SO_J1939_FILTER)
e4a6d3acaddb of: property: fix typo in io-channels
8180d0c27b93 ceph: prevent use-after-free in encode_cap_msg()
2e9506c9e0b9 s390/qeth: Fix potential loss of L3-IP@ in case of network 
issues
888679afbfc2 irqchip/gic-v3-its: Fix GICv4.1 VPE affinity update
2809645d8ae2 irqchip/irq-brcmstb-l2: Add write memory barrier before exit
45a3657c3fae wifi: mac80211: reload info pointer in ieee80211_tx_dequeue()
c7fa9590a9b2 nfp: flower: prevent re-adding mac index for bonded port
962091c40813 nfp: use correct macro for LengthSelect in BAR config
58054faf3bd2 crypto: ccp - Fix null pointer dereference in 
__sev_platform_shutdown_locked
98a4026b22ff nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()
364a66be2abd nilfs2: fix data corruption in dsync block recovery for small 
block sizes
a643d8d17947 ALSA: hda/conexant: Add quirk for SWS JS201D
ca0533fe6650 mmc: slot-gpio: Allow non-sleeping GPIO ro
bdc29f9ca3b1 x86/mm/ident_map: Use gbpages only where full GB page should 
be mapped.
09f21bee5b02 x86/Kconfig: Transmeta Crusoe is CPU family 5, not 6
1a8a72ee17e4 serial: max310x: improve crystal stable clock detection
6f248ee7aade serial: max310x: set default value when reading clock ready bit
92a0a5d61376 ring-buffer: Clean ring_buffer_poll_wait() error return
9ec807e7b6f5 hv_netvsc: Fix race condition between netvsc_probe and 
netvsc_remove
93d8109bf182 media: rc: bpf attach/detach requires write permission
a98ccbcddbb5 iio: accel: bma400: Fix a compilation problem
36a49290d7e6 iio: magnetometer: rm3100: add boundary check for the value 
read from RM3100_REG_TMRC
fa5884dd5bc2 staging: iio: ad5933: fix type mismatch regression
8a744f925de0 tracing: Fix wasted memory in saved_cmdlines logic
d033a555d9a1 ext4: fix double-free of blocks due to wrong extents moved_len
f86e12415b4e misc: fastrpc: Mark all sessions as invalid in cb_remove
a423042052ec binder: signal epoll threads of self-work
6d11240dd11b ALSA: hda/realtek: Enable headset mic on Vaio VJFE-ADL
cdaddb457d9e xen-netback: properly sync TX responses
0d8011a878fd net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame()
2f6d16f0520d nfc: nci: free rx_data_reassembly skb on NCI device cleanup
5abf3e8af2e3 kbuild: Fix changing ELF file type for output of gen_btf for 
big endian
6717c593c7cf firewire: core: correct documentation of fw_csr_string() 
kernel API
2dc1d93b2c77 lsm: fix the logic in security_inode_getsecctx()
7d4e19f7ff64 scsi: Revert "scsi: fcoe: Fix potential deadlock on

[OE-core] [PATCH 2/7][kirkstone] linux-yocto/5.15: update CVE exclusions

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

Data pulled from: https://github.com/nluedtke/linux_kernel_cves

1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 25Feb24
Date: Sun, 25 Feb 2024 07:03:08 -0500

]

Signed-off-by: Bruce Ashfield 
---
 .../linux/cve-exclusion_5.15.inc  | 197 +-
 1 file changed, 190 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-kernel/linux/cve-exclusion_5.15.inc 
b/meta/recipes-kernel/linux/cve-exclusion_5.15.inc
index d33f2b3c7f..2e30efe6be 100644
--- a/meta/recipes-kernel/linux/cve-exclusion_5.15.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion_5.15.inc
@@ -1,9 +1,9 @@
 
 # Auto-generated CVE metadata, DO NOT EDIT BY HAND.
-# Generated at 2024-02-06 21:02:11.546853 for version 5.15.148
+# Generated at 2024-02-26 23:36:34.200936 for version 5.15.149
 
 python check_kernel_cve_status_version() {
-this_version = "5.15.148"
+this_version = "5.15.149"
 kernel_version = d.getVar("LINUX_VERSION")
 if kernel_version != this_version:
 bb.warn("Kernel CVE status needs updating: generated for %s but kernel 
is %s" % (this_version, kernel_version))
@@ -7433,6 +7433,99 @@ CVE_CHECK_IGNORE += "CVE-2023-5197"
 # cpe-stable-backport: Backported in 5.15.147
 CVE_CHECK_IGNORE += "CVE-2023-52340"
 
+# cpe-stable-backport: Backported in 5.15.149
+CVE_CHECK_IGNORE += "CVE-2023-52429"
+
+# fixed-version: only affects 6.5rc6 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52433"
+
+# CVE-2023-52434 needs backporting (fixed from 6.7rc6)
+
+# cpe-stable-backport: Backported in 5.15.149
+CVE_CHECK_IGNORE += "CVE-2023-52435"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52436"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52438"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52439"
+
+# fixed-version: only affects 5.17rc4 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52440"
+
+# cpe-stable-backport: Backported in 5.15.145
+CVE_CHECK_IGNORE += "CVE-2023-52441"
+
+# cpe-stable-backport: Backported in 5.15.145
+CVE_CHECK_IGNORE += "CVE-2023-52442"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52443"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52444"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52445"
+
+# fixed-version: only affects 6.2rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52446"
+
+# CVE-2023-52447 needs backporting (fixed from 6.8rc1)
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52448"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52449"
+
+# fixed-version: only affects 6.2rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52450"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52451"
+
+# CVE-2023-52452 needs backporting (fixed from 6.8rc1)
+
+# fixed-version: only affects 6.2rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52453"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52454"
+
+# fixed-version: only affects 6.3rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52455"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52456"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52457"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52458"
+
+# fixed-version: only affects 6.6rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52459"
+
+# fixed-version: only affects 6.7rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52460"
+
+# fixed-version: only affects 6.7rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52461"
+
+# fixed-version: only affects 5.16rc1 onwards
+CVE_CHECK_IGNORE += "CVE-2023-52462"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52463"
+
+# cpe-stable-backport: Backported in 5.15.148
+CVE_CHECK_IGNORE += "CVE-2023-52464"
+
 # fixed-version: only affects 6.1rc1 onwards
 CVE_CHECK_IGNORE += "CVE-2023-5345"
 
@@ -7464,6 +7557,8 @@ CVE_CHECK_IGNORE += "CVE-2023-6200"
 
 # CVE-2023-6238 has no known resolution
 
+# CVE-2023-6240 has no known resolution
+
 # CVE-2023-6270 has no known resolution
 
 # CVE-2023-6356 has no known resolution
@@ -7511,7 +7606,8 @@ CVE_CHECK_IGNORE += "CVE-2023-7192"
 # fixed-version: only affects 6.5rc6 onwards
 CVE_CHECK_IGNORE += "CVE-2024-0193"
 
-# CVE-2024-0340 needs backporting (fixed from 6.4rc6)
+# cpe-stable-backport: Backported in 5.15.149
+CVE_CHECK_IGNORE += "CVE-2024-0340"
 
 # fixed-version: only affects 6.2rc1 onwards
 CVE_CHECK_IGNORE += "CVE-2024-0443"
@@ -7549,22 +7645,109 @@ CVE_CHECK_IGNORE += "CVE-2024-0775"
 # cpe-stable-backport: Backported in 5.15.148
 CVE_CHECK_IGNORE += "CVE-2024-1085"
 
-# CVE-2024-1086 needs backporting (fixed from 6.8rc2)
+# cpe-stable-backport: Backported in 5.15.149
+CVE_CHECK_IGNORE += "CVE-2024-1086

[OE-core] [PATCH 1/7][kirkstone] linux-yocto/5.15: update to v5.15.149

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

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

458ce51d0356 Linux 5.15.149
d72da18772ff usb: dwc3: gadget: Ignore End Transfer delay on teardown
acff71e58748 media: Revert "media: rkisp1: Drop IRQF_SHARED"
9ae312f7f3c2 usb: dwc3: gadget: Execute gadget stop after halting the 
controller
921acacb92b7 usb: dwc3: gadget: Don't delay End Transfer on delayed_status
4178bfa3fc9d staging: fbtft: core: set smem_len before fb_deferred_io_init 
call
9e25a0054090 smb3: Replace smb2pdu 1-element arrays with flex-arrays
0b49eac39c99 fs/ntfs3: Add null pointer checks
4c73597f68d7 net: bcmgenet: Fix EEE implementation
62900d358c48 Revert "selftests/bpf: Test tail call counting with bpf2bpf 
and data on stack"
75ac8dc02850 drm/msm/dsi: Enable runtime PM
c7a0fa3a6657 PM: runtime: Have devm_pm_runtime_enable() handle 
pm_runtime_dont_use_autosuspend()
1974b3c19a79 arm64: Subscribe Microsoft Azure Cobalt 100 to ARM Neoverse N2 
errata
888a0a46b80f dm: limit the number of targets and parameter size area
cf4da91e99f1 nilfs2: replace WARN_ONs for invalid DAT metadata block 
requests
8fa90634ec3e nilfs2: fix potential bug in end_buffer_async_write
50fb4e17df31 sched/membarrier: reduce the ability to hammer on 
sys_membarrier
b9aafef74407 netfilter: ipset: Missing gc cancellations fixed
6c53e8547687 net: prevent mss overflow in skb_segment()
95c0babebe6a hrtimer: Ignore slack time for RT tasks in 
schedule_hrtimeout_range()
c2dc077d8f72 netfilter: ipset: fix performance regression in swap operation
3b3e4d3560e3 scripts/decode_stacktrace.sh: optionally use LLVM utilities
473791d286a8 scripts: decode_stacktrace: demangle Rust symbols
1ce4ac55d96e scripts/decode_stacktrace.sh: support old bash version
2655757a3f10 fbdev: flush deferred IO before closing
15492bab7393 fbdev: Fix incorrect page mapping clearance at 
fb_deferred_io_release()
87b9802ca824 fbdev: Fix invalid page access after closing deferred I/O 
devices
9a95fc04261f fbdev: Rename pagelist to pagereflist for deferred I/O
186b89659c4c fbdev: Track deferred-I/O pages in pageref struct
e79b2b2aadef fbdev: defio: fix the pagelist corruption
0616b00a31d6 fbdev: Don't sort deferred-I/O pages by default
5d3aff76a316 fbdev/defio: Early-out if page is already enlisted
48a09969e43e serial: 8250_exar: Set missing rs485_supported flag
9ef7419bc20c serial: 8250_exar: Fill in rs485_supported
aded03eda2ba usb: dwc3: gadget: Queue PM runtime idle on disconnect event
21f0bff281b5 usb: dwc3: gadget: Handle EP0 request dequeuing properly
89353c886477 usb: dwc3: gadget: Refactor EP0 forced stall/restart into a 
separate API
915619257332 usb: dwc3: gadget: Stall and restart EP0 if host is 
unresponsive
352b38d15c6d usb: dwc3: gadget: Submit endxfer command if delayed during 
disconnect
9cccdcc95e33 usb: dwc3: gadget: Force sending delayed status during soft 
disconnect
1ea8a2a532e9 usb: dwc3: Fix ep0 handling when getting reset while doing 
control transfer
12c0a0804ade usb: dwc3: gadget: Delay issuing End Transfer
487341852fbc usb: dwc3: gadget: Only End Transfer for ep0 data phase
9273bd26b06d usb: dwc3: ep0: Don't prepare beyond Setup stage
92f7a10a2bfe usb: dwc3: gadget: Wait for ep0 xfers to complete during 
dequeue
2bb86817b33c crypto: lib/mpi - Fix unexpected pointer access in mpi_ec_init
44a8a2c92e5a bus: moxtet: Add spi device table
4e82b9c11d3c dma-buf: add dma_fence_timestamp helper
36f7371de977 af_unix: Fix task hung while purging oob_skb in GC.
ff2f35f5cda0 tracing: Inform kmemleak of saved_cmdlines allocation
579cb4ff1fc5 pmdomain: core: Move the unused cleanup to a _sync initcall
41ccb5bcbf03 can: j1939: Fix UAF in j1939_sk_match_filter during 
setsockopt(SO_J1939_FILTER)
03358aba9916 can: j1939: prevent deadlock by changing j1939_socks_lock to 
rwlock
6315697fc5bf of: property: fix typo in io-channels
310c7d9853ef mm: hugetlb pages should not be reserved by shmat() if 
SHM_NORESERVE
70e329b44076 ceph: prevent use-after-free in encode_cap_msg()
99fa6d451d98 net: ethernet: ti: cpsw_new: enable mac_managed_pm to fix mdio
ff42d99e50b9 s390/qeth: Fix potential loss of L3-IP@ in case of network 
issues
ddb4be0eb2ac net: ethernet: ti: cpsw: enable mac_managed_pm to fix mdio
86244ae70715 irqchip/gic-v3-its: Fix GICv4.1 VPE affinity update
27a2af914ff5 irqchip/irq-brcmstb-l2: Add write memory barrier before exit
b10c8883f845 wifi: mac80211: reload info pointer in ieee80211_tx_dequeue()
ef5b1041f756 nfp: flower: prevent re-adding mac index for bonded port
e58efe0f7af8 nfp: use correct macro for LengthSelect in BAR config
7535ec350a5f crypto: ccp - Fix null pointer dereference in 
__sev_platform_shutdown_locked
7e9b622bd074 nilfs2: fix hang in nilfs_loo

[OE-core] [PATCH 0/7][kirkstone]: linux-yocto: pull request

2024-03-11 Thread Bruce Ashfield
From: Bruce Ashfield 

Steve,

I've included the meta-yocto-bsp commit in this series, versus
sending it separately. It obviously doesn't go onto OEcore.

These are the updates I've been testing for the pratition scanning
issues.

We have a few -stable bumps, along with the backport of the upstream
change to fix the ptest issues.

Cheers,

Bruce

The following changes since commit d34002348374669528bb884c2d7be1b91938f471:

  kernel.bbclass: Set pkg-config variables for building modules (2024-03-07 
08:32:54 -1000)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel-kirkstone
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel-kirkstone

Bruce Ashfield (7):
  linux-yocto/5.15: update to v5.15.149
  linux-yocto/5.15: update CVE exclusions
  linux-yocto/5.10: update to v5.10.210
  linux-yocto/5.15: update to v5.15.150
  linux-yocto/5.15: update CVE exclusions (5.15.150)
  linux-yocto/5.15: fix partion scanning
  yocto-bsp: update to v5.15.150

 .../linux/linux-yocto_5.15.bbappend   |  16 +-
 .../linux/cve-exclusion_5.15.inc  | 197 +-
 .../linux/linux-yocto-rt_5.10.bb  |   4 +-
 .../linux/linux-yocto-rt_5.15.bb  |   6 +-
 .../linux/linux-yocto-tiny_5.10.bb|   6 +-
 .../linux/linux-yocto-tiny_5.15.bb|   6 +-
 meta/recipes-kernel/linux/linux-yocto_5.10.bb |  22 +-
 meta/recipes-kernel/linux/linux-yocto_5.15.bb |  26 +--
 8 files changed, 233 insertions(+), 50 deletions(-)

-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196945): 
https://lists.openembedded.org/g/openembedded-core/message/196945
Mute This Topic: https://lists.openembedded.org/mt/104867008/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] image_types_wic.bbclass: remove .env file in do_clean

2024-03-11 Thread Mauro

On 06/03/24 17:57, Richard Purdie wrote:

On Wed, 2024-03-06 at 08:37 -0800, Mauro wrote:

Before this commit, the .env file created in
tmp/sysroots//imgdata/.env was never cleaned,
but when the do_clean task is invoked on an image, the .env file
contains paths that are not valid anymore.
If another image wants to use the cleaned image fs to build a .wic,
the wic command fails because paths contained in .env are not found.
With this patch, the returned error is more clear:

   "File /.../tmp/sysroots//imgdata/.env doesn't
exist"

Signed-off-by: Mauro Salvini 
---
  meta/classes-recipe/image_types_wic.bbclass | 11 +++
  1 file changed, 11 insertions(+)

diff --git a/meta/classes-recipe/image_types_wic.bbclass
b/meta/classes-recipe/image_types_wic.bbclass
index cf3be909b3..b0b5691225 100644
--- a/meta/classes-recipe/image_types_wic.bbclass
+++ b/meta/classes-recipe/image_types_wic.bbclass
@@ -205,3 +205,14 @@ addtask do_flush_pseudodb after do_rootfs before
do_image do_image_qa
  addtask do_rootfs_wicenv after do_image before do_image_wic
  do_rootfs_wicenv[vardeps] += "${WICVARS}"
  do_rootfs_wicenv[prefuncs] = 'set_image_size'
+
+#
+# Clean also .env file created in
tmp/sysroots//imgdata/.env
+# when a clean is invoked
+#
+do_clean:append() {
+    stdir = d.getVar('STAGING_DIR')
+    outdir = os.path.join(stdir, d.getVar('MACHINE'), 'imgdata')
+    basename = d.getVar('IMAGE_BASENAME')
+    bb.utils.remove(os.path.join(outdir, basename) + '.env')
+}


This doesn't look right unfortunately.

Things should not be being placed into the sysroots (STAGING_DIR) that
aren't under the control of sstate. If things are, we need to fix that
at the source of the problem.

Cheers,

Richard




Hi Richard,

thank you.

What would be the correct directory where to put the .env files?
I don't know much about Yocto internals, but I can try do arrange a 
patch to solve the problem at the source.


Thanks, regards

--
Mauro

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



[OE-core] [PATCH v1] git: git-replacement-native: depend on ca-certificate

2024-03-11 Thread Max Krummenacher
From: Max Krummenacher 

git is delegating webacces for URLs using TLS to libcurl.
However our native libcurl build does not find a ca-certificate.crt
unless its curl-native work dir still exists and thus git will
fail.
If a recipe uses AUTOREV with a git repo using https as its protocol
parsing of that recipe will fail fetching the latest HEAD.

Fix that by depending on ca-certificate and give its location
to libcurl via git's envrironment variable GIT_SSL_CAINFO.

Signed-off-by: Max Krummenacher 
---
 meta/recipes-devtools/git/git_2.44.0.bb | 3 +++
 1 file changed, 3 insertions(+)

See also the ML discussion:
https://lore.kernel.org/all/20240309175750.2621579-1-max.oss...@gmail.com/

diff --git a/meta/recipes-devtools/git/git_2.44.0.bb 
b/meta/recipes-devtools/git/git_2.44.0.bb
index e6d1470873..90e555eba7 100644
--- a/meta/recipes-devtools/git/git_2.44.0.bb
+++ b/meta/recipes-devtools/git/git_2.44.0.bb
@@ -4,6 +4,7 @@ DESCRIPTION = "Git is a free and open source distributed 
version control system
 SECTION = "console/utils"
 LICENSE = "GPL-2.0-only & GPL-2.0-or-later & BSD-3-Clause & MIT & BSL-1.0 & 
LGPL-2.1-or-later"
 DEPENDS = "openssl zlib"
+DEPENDS:class-native += "ca-certificates"
 
 PROVIDES:append:class-native = " git-replacement-native"
 
@@ -95,6 +96,7 @@ perl_native_fixup () {
 
 REL_GIT_EXEC_PATH = "${@os.path.relpath(libexecdir, bindir)}/git-core"
 REL_GIT_TEMPLATE_DIR = "${@os.path.relpath(datadir, 
bindir)}/git-core/templates"
+REL_GIT_SSL_CAINFO = "${@os.path.relpath(sysconfdir, 
bindir)}/ssl/certs/ca-certificates.crt"
 
 do_install:append:class-target () {
perl_native_fixup
@@ -103,6 +105,7 @@ do_install:append:class-target () {
 do_install:append:class-native() {
create_wrapper ${D}${bindir}/git \
GIT_EXEC_PATH='`dirname $''realpath`'/${REL_GIT_EXEC_PATH} \
+   GIT_SSL_CAINFO='`dirname $''realpath`'/${REL_GIT_SSL_CAINFO} \
GIT_TEMPLATE_DIR='`dirname $''realpath`'/${REL_GIT_TEMPLATE_DIR}
 }
 
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196943): 
https://lists.openembedded.org/g/openembedded-core/message/196943
Mute This Topic: https://lists.openembedded.org/mt/104864192/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-yocto: enable fetching kernel metadata using file fetcher

2024-03-11 Thread Bruce Ashfield
On Mon, Mar 11, 2024 at 9:22 AM Taedcke, Christian
 wrote:
>
>
>
> On 11.03.2024 13:46, Bruce Ashfield via lists.openembedded.org wrote:
> > On Mon, Mar 11, 2024 at 5:15 AM Taedcke, Christian
> >  wrote:
> >>
> >> From: Christian Taedcke 
> >>
> >> The file fetcher does not support the destsuffix parameter. It does
> >> not rename the supplied folder during the fetch. Therefore the folder
> >> name (i.e. basepath) is added to the kernel-meta search directories.
> >>
> >
> > What's the benefit ? I need to understand what you are trying to
> > do that requires this.
>
> In a BSP layer for a custom machine we use the linux-yocto kernel.
> In the BSP layer the file /recipes-kernel/linux/linux-yocto_6.1.bbappend
> adds a local folder containing kernel metatdata to the SRC_URI:

Definitely a valid use-case!

>
> SRC_URI:append:my-machine = "file://my-meta;type=kmeta"
>
> The folder my-meta is a subfolder:
> /recipes-kernel/linux/linux-yocto/my-machine/my-meta
>
> Without this patch we would have to write:
> SRC_URI:append:my-machine = " file://my-meta;type=kmeta;destsuffix=my-meta"
>
> When using a file fetcher for kernel metatdata without this patch the
> destsuffix property would always have to be the same as the folder name
> itself. With this patch we do not need this duplication.

That's the (non-obvious) intentional part of the way that I ended
up implementing the identification of secondary / out of tree
meta-data files or directories that should be treated as feature
directories.

Initially I had more strictly enforced that the destsuffix and
folder name had to match. When it became not as strictly
required, it stayed around to avoid picking up invalid
meta data collections that were unfortunately named in the
SRC_URI. (I'm the one with the unfortunately named
meta-data that wasn't supposed to be pulled in as a kernel
meta directory :))

>
> >
> > Because my first thought is "absolutely not" to changing the way
> > this works.
> >
> > What I see below is possibly going to break out of tree BSP
> > definitions. The combination of kmeta and destsuffix really
> > isn't there to support the git fetcher, it is a keyword combination
> > that I used to indicate a meta-data repository that unfortunately
> > overlaps with the other fetcher parameters.
>
> Ok, that was not clear to me. The comment above the function
> find_kernel_feature_dirs() indicates that the returned value has
> something to do with how/where the fetcher stores the provided metadata:
>
> -> Return the name of the repository as it will be found in WORKDIR

The comments may be out of sync with how it currently works,
there was quite a bit of churn on this during the "early days".

You can see this was also covered recently on the docs mailing
list under: [docs] [PATCH] manuals: kernel-dev: Fix BSP in recipe space

>
> I think there are 2 ways forward:
> 1. Rewrite this patch so it does not affect out of tree BSPs (remove
> exception, still use destsuffix for other fetchers), or

Ideally it needs to still process destsuffix in file mode, but add
a new path that it can work without it being explicitly supplied.

> 2. Drop this patch completely
>
> >
> > The reality is that I won't be able to fully review and test
> > this until after the upcoming release is done, since I need to
> > also see about pulling together some regression tests and
> > submitting them at the same time.
>
> No problem, i am just in the process of upstreaming our in-house
> patches. This is not time-critical. We can continue the discussion after
> the release.

I'll pick this up in a couple of weeks (feel free to ping again), since
I really do need to run quite a few tests and then make them into
some sort of sanity suite .. since I can't really comment that this
might break something, without a way to actually test and show that
it is, or isn't the case.

Bruce

>
> Regards,
> Christian
>
> >
> > Bruce
> >
> >> Signed-off-by: Christian Taedcke 
> >> ---
> >>   meta/classes-recipe/kernel-yocto.bbclass | 21 ++---
> >>   1 file changed, 14 insertions(+), 7 deletions(-)
> >>
> >> diff --git a/meta/classes-recipe/kernel-yocto.bbclass 
> >> b/meta/classes-recipe/kernel-yocto.bbclass
> >> index 9a86616dad..3cbdf21df8 100644
> >> --- a/meta/classes-recipe/kernel-yocto.bbclass
> >> +++ b/meta/classes-recipe/kernel-yocto.bbclass
> >> @@ -62,8 +62,8 @@ def find_sccs(d):
> >>
> >>   return sources_list
> >>
> >> -# check the SRC_URI for "kmeta" type'd git repositories. Return the name 
> >> of
> >> -# the repository as it will be found in WORKDIR
> >> +# check the SRC_URI for "kmeta" type'd git repositories and directories. 
> >> Return
> >> +# the name of the repository or directory as it will be found in WORKDIR
> >>   def find_kernel_feature_dirs(d):
> >>   feature_dirs=[]
> >>   fetch = bb.fetch2.Fetch([], d)
> >> @@ -71,13 +71,20 @@ def find_kernel_feature_dirs(d):
> >>   urldata = fetch.ud[url]
> >>   parm = urldata.parm
> >>  

Re: [OE-core] [PATCH 1/3] linux-yocto: for-test-only: fix parted ptest

2024-03-11 Thread Steve Sakoman
On Mon, Mar 11, 2024 at 4:01 AM Bruce Ashfield  wrote:
>
> On Mon, Mar 11, 2024 at 9:51 AM Steve Sakoman  wrote:
> >
> > On Sun, Mar 10, 2024 at 4:25 PM Steve Sakoman via
> > lists.openembedded.org 
> > wrote:
> > >
> > > On Sun, Mar 10, 2024 at 4:10 PM Bruce Ashfield  
> > > wrote:
> > > >
> > > > On Fri, Mar 8, 2024 at 10:24 PM Bruce Ashfield via
> > > > lists.openembedded.org
> > > >  wrote:
> > > > >
> > > > > On Fri, Mar 8, 2024 at 6:44 PM Richard Purdie
> > > > >  wrote:
> > > > > >
> > > > > > On Fri, 2024-03-08 at 10:42 -0800, Steve Sakoman wrote:
> > > > > > > On Fri, Mar 8, 2024 at 5:10 AM Steve Sakoman via
> > > > > > > lists.openembedded.org 
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > I did fire up a test of Kevin's patch:
> > > > > > > >
> > > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6373
> > > > > > > >
> > > > > > > > Let's see what happens.
> > > > > > >
> > > > > > > I can confirm that this patch fixes the parted ptest issues and 
> > > > > > > does
> > > > > > > not trigger any other ptest issues.
> > > > > > >
> > > > > > > However since there is a kirkstone release build scheduled for 
> > > > > > > next
> > > > > > > Tuesday, the current plan of record is to revert the previous
> > > > > > > linux-yocto 5.15 version bump series for the release build.
> > > > > > >
> > > > > > > I will then wait for a patch from Bruce that fixes the problem 
> > > > > > > before
> > > > > > > reapplying it post release.
> > > > > >
> > > > > > If it takes a few more days it may be better to slip that release 
> > > > > > (when
> > > > > > QA are likely testing M3 anyway) in order to resolve this rather 
> > > > > > than
> > > > > > reverting a load of things we'll only then end up reapplying.
> > > > > >
> > > > >
> > > > > I'll be working on it over the weekend, along with some other kernel
> > > > > items that I didn't get to as I worked on this today and some 
> > > > > meta-virt
> > > > > things.
> > > >
> > > > Steve: Here's my latest queue:
> > > >
> > > > https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel-kirkstone
> > > >
> > > > It passed the parted and util-linux ptests locally.
> > >
> > > Thanks Bruce!
> > >
> > > I'll grab the patches and run an a-full on the autobuilder.
> >
> > The a-full results are here:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/
> >
> > The ptest runs came back all green, but there were failures in all of
> > the hw-ref tests that use older versions of 5.15 since the patch added
> > with SRC_URI +=  in your final commit doesn't apply to those older
> > kernel versions.
> >
>
> Yah, that's fine.
>
> We'd never merge the patch like I put it in the queue.
>
> I'll actually merge those changes into the linux-yocto tree and send
> SRCREV updates. I just wanted to make sure that they worked in
> your tests, like they worked in mine.
>
> I can also bump the reference BSPs to pick up the change.
>
> Really this is something that -stable should be fixing, but I'm not
> in a position to propose a fix (it is far from my area of expertise)
> so I kept the patches with as minor touches as possible so when
> (if) they fix the issue, I won't have much conflict.
>
> I can do those SRCREV bumps shortly and send the entire queue
> by patches if that works for you.

That would be perfect. Thanks for the quick response on this, I really
appreciate it!

Steve

> > For example, beaglebone:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/8751/steps/11/logs/errors
> >
> > Steve
> >
> > > > > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > > > > thee at its end
> > > > > - "Use the force Harry" - Gandalf, Star Trek II
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > > > thee at its end
> > > > - "Use the force Harry" - Gandalf, Star Trek II
> > > >
> > > >
> > > >
> > >
> > > 
> > >
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196941): 
https://lists.openembedded.org/g/openembedded-core/message/196941
Mute This Topic: https://lists.openembedded.org/mt/104794844/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] linux-yocto: for-test-only: fix parted ptest

2024-03-11 Thread Bruce Ashfield
On Mon, Mar 11, 2024 at 9:51 AM Steve Sakoman  wrote:
>
> On Sun, Mar 10, 2024 at 4:25 PM Steve Sakoman via
> lists.openembedded.org 
> wrote:
> >
> > On Sun, Mar 10, 2024 at 4:10 PM Bruce Ashfield  
> > wrote:
> > >
> > > On Fri, Mar 8, 2024 at 10:24 PM Bruce Ashfield via
> > > lists.openembedded.org
> > >  wrote:
> > > >
> > > > On Fri, Mar 8, 2024 at 6:44 PM Richard Purdie
> > > >  wrote:
> > > > >
> > > > > On Fri, 2024-03-08 at 10:42 -0800, Steve Sakoman wrote:
> > > > > > On Fri, Mar 8, 2024 at 5:10 AM Steve Sakoman via
> > > > > > lists.openembedded.org 
> > > > > > wrote:
> > > > > > >
> > > > > > > I did fire up a test of Kevin's patch:
> > > > > > >
> > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6373
> > > > > > >
> > > > > > > Let's see what happens.
> > > > > >
> > > > > > I can confirm that this patch fixes the parted ptest issues and does
> > > > > > not trigger any other ptest issues.
> > > > > >
> > > > > > However since there is a kirkstone release build scheduled for next
> > > > > > Tuesday, the current plan of record is to revert the previous
> > > > > > linux-yocto 5.15 version bump series for the release build.
> > > > > >
> > > > > > I will then wait for a patch from Bruce that fixes the problem 
> > > > > > before
> > > > > > reapplying it post release.
> > > > >
> > > > > If it takes a few more days it may be better to slip that release 
> > > > > (when
> > > > > QA are likely testing M3 anyway) in order to resolve this rather than
> > > > > reverting a load of things we'll only then end up reapplying.
> > > > >
> > > >
> > > > I'll be working on it over the weekend, along with some other kernel
> > > > items that I didn't get to as I worked on this today and some meta-virt
> > > > things.
> > >
> > > Steve: Here's my latest queue:
> > >
> > > https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel-kirkstone
> > >
> > > It passed the parted and util-linux ptests locally.
> >
> > Thanks Bruce!
> >
> > I'll grab the patches and run an a-full on the autobuilder.
>
> The a-full results are here:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/
>
> The ptest runs came back all green, but there were failures in all of
> the hw-ref tests that use older versions of 5.15 since the patch added
> with SRC_URI +=  in your final commit doesn't apply to those older
> kernel versions.
>

Yah, that's fine.

We'd never merge the patch like I put it in the queue.

I'll actually merge those changes into the linux-yocto tree and send
SRCREV updates. I just wanted to make sure that they worked in
your tests, like they worked in mine.

I can also bump the reference BSPs to pick up the change.

Really this is something that -stable should be fixing, but I'm not
in a position to propose a fix (it is far from my area of expertise)
so I kept the patches with as minor touches as possible so when
(if) they fix the issue, I won't have much conflict.

I can do those SRCREV bumps shortly and send the entire queue
by patches if that works for you.

Bruce

> For example, beaglebone:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/8751/steps/11/logs/errors
>
> Steve
>
> > > > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > > > thee at its end
> > > > - "Use the force Harry" - Gandalf, Star Trek II
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > > thee at its end
> > > - "Use the force Harry" - Gandalf, Star Trek II
> > >
> > >
> > >
> >
> > 
> >



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196940): 
https://lists.openembedded.org/g/openembedded-core/message/196940
Mute This Topic: https://lists.openembedded.org/mt/104794844/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] [REGRESSION] linux (git/curl-native) and autorev

2024-03-11 Thread Bruce Ashfield
On Mon, Mar 11, 2024 at 8:54 AM Max Krummenacher  wrote:
>
> On Sun, Mar 10, 2024 at 11:39:00PM +, Richard Purdie wrote:
> > On Sun, 2024-03-10 at 09:05 -0700, Bruce Ashfield wrote:
> > > On Sun, Mar 10, 2024 at 11:52 AM Richard Purdie
> > >  wrote:
> > > >
> > > > On Sun, 2024-03-10 at 06:20 -0700, Richard Purdie via
> > > > lists.openembedded.org wrote:
> > > > > On Sun, 2024-03-10 at 13:31 +0100, Max wrote:
> > > > > > Am Samstag, dem 09.03.2024 um 13:04 -0800 schrieb Bruce
> > > > > > Ashfield:
> > > > > > > On Sat, Mar 9, 2024 at 12:58 PM  wrote:
> > > > > > > >
> > > > > > > > From: Max Krummenacher 
> > > > > > > >
> > > > > > > > Hello
> > > > > > > >
> > > > > > > > If one builds a kernel using AUTOREV invoking bitbake only
> > > > > > > > works
> > > > > > > > once.
> > > > > > > > Any subsequent bitbake invocation fails parsing the meta
> > > > > > > > data.
> > > > > > > >
> > > > > > > > Reproducable with:
> > > > > > > > - latest poky, b5624ee564
> > > > > > > > - Kernel with SRCREV = "AUTOREV", e.g. in local.conf
> > > > > > > >   `SRCREV_machine:pn-linux-yocto:forcevariable =
> > > > > > > > "${AUTOREV}"`
> > > > > > > > - bitbake virtual/kernel; bitbake virtual/kernel
> > > > > > > >
> > > > > > > > On the second invocation parsing fails when the fetcher
> > > > > > > > tries
> > > > > > > > to
> > > > > > > > evaluate the latest SRCREV:
> > > > > > > >
> > > > > > > > > ERROR: ExpansionError during parsing meta/recipes-
> > > > > > > > > kernel/linux/linux-yocto_6.6.bb
> > > > > > > > > Traceback (most recent call last):
> > > > > > > > >   File "bitbake/lib/bb/fetch2/__init__.py", line 1245, in
> > > > > > > > > srcrev_internal_helper(ud= > > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > > 0x7f8e26195890>, name='machine'):
> > > > > > > > >  d.setVar("__BBAUTOREV_ACTED_UPON", True)
> > > > > > > > > >srcrev = ud.method.latest_revision(ud, d,
> > > > > > > > > name)
> > > > > > > > >
> > > > > > > > >   File "bitbake/lib/bb/fetch2/__init__.py", line 1667, in
> > > > > > > > > Git.latest_revision(ud= > > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > > 0x7f8e26195890>, name='machine'):
> > > > > > > > >  except KeyError:
> > > > > > > > > >revs[key] = rev =
> > > > > > > > > self._latest_revision(ud,
> > > > > > > > > d,
> > > > > > > > > name)
> > > > > > > > >  return rev
> > > > > > > > >   File "bitbake/lib/bb/fetch2/git.py", line 850, in
> > > > > > > > > Git._latest_revision(ud= > > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > > 0x7f8e26195890>, name='machine'):
> > > > > > > > >
> > > > > > > > > >output = self._lsremote(ud, d, "")
> > > > > > > > >  # Tags of the form ^{} may not work, need to
> > > > > > > > > fallback to other form
> > > > > > > > >   File "bitbake/lib/bb/fetch2/git.py", line 833, in
> > > > > > > > > Git._lsremote(ud= > > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > > 0x7f8e26195890>, search=''):
> > > > > > > > >  bb.fetch2.check_network_access(d,
> > > > > > > > > cmd,
> > > > > > > > > repourl)
> > > > > > > > > >output = runfetchcmd(cmd, d, True)
> > > > > > > > >  if not output:
> > > > > > > > >   File "bitbake/lib/bb/fetch2/__init__.py", line 957, in
> > > > > > > > > runfetchcmd(cmd='export PSEUDO_DISABLED=1; export
> > > > > > > > > DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1003/bus";
> > > > > > > > > export
> > > > > > > > > PATH="build/tmp/sysroots-uninative/x86_64-
> > > > > > > > > linux/usr/bin:scripts:build/tmp/work/qemux86_64-poky-
> > > > > > > > > linux/linux-yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > > native/usr/bin/x86_64-poky-
> > > > > > > > > linux:build/tmp/work/qemux86_64-
> > > > > > > > > poky-linux/linux-yocto/6.6.20+git/recipe-
> > > > > > > > > sysroot/usr/bin/crossscripts:build/tmp/work/qemux86_64-
> > > > > > > > > poky-
> > > > > > > > > linux/linux-yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > > native/usr/sbin:build/tmp/work/qemux86_64-poky-
> > > > > > > > > linux/linux-
> > > > > > > > > yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > > native/usr/bin:build/tmp/work/qemux86_64-poky-
> > > > > > > > > linux/linux-
> > > > > > > > > yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > > native/sbin:build/tmp/work/qemux86_64-poky-linux/linux-
> > > > > > > > > yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > > native/bin:bitbake/bin:build/tmp/hosttools"; export
> > > > > > > > > HOME="/home/krm"; git -c gc.autoDetach=false -c
> > > > > > > > > core.pager=cat
> > > > > > > > > -c safe.bareRepository=all ls-remote
> > > > > > > > > https://git.yoctoproject.org/linux-yocto.git ',
> > > > > > > > > d=,
> > > > > > > > > quiet=True, cleanup=[], log=None, workdir=None):
> > > > > > > > >
> > > > > > > > > >raise FetchError(error_message)
> > > > > > > > >
> > > > > > > > > bb.data_smart.ExpansionError: Failure expanding variable
> > > > > > > > > fetcher_hashes_dum

Re: [OE-core] [PATCH 1/3] linux-yocto: for-test-only: fix parted ptest

2024-03-11 Thread Steve Sakoman
On Sun, Mar 10, 2024 at 4:25 PM Steve Sakoman via
lists.openembedded.org 
wrote:
>
> On Sun, Mar 10, 2024 at 4:10 PM Bruce Ashfield  
> wrote:
> >
> > On Fri, Mar 8, 2024 at 10:24 PM Bruce Ashfield via
> > lists.openembedded.org
> >  wrote:
> > >
> > > On Fri, Mar 8, 2024 at 6:44 PM Richard Purdie
> > >  wrote:
> > > >
> > > > On Fri, 2024-03-08 at 10:42 -0800, Steve Sakoman wrote:
> > > > > On Fri, Mar 8, 2024 at 5:10 AM Steve Sakoman via
> > > > > lists.openembedded.org 
> > > > > wrote:
> > > > > >
> > > > > > I did fire up a test of Kevin's patch:
> > > > > >
> > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6373
> > > > > >
> > > > > > Let's see what happens.
> > > > >
> > > > > I can confirm that this patch fixes the parted ptest issues and does
> > > > > not trigger any other ptest issues.
> > > > >
> > > > > However since there is a kirkstone release build scheduled for next
> > > > > Tuesday, the current plan of record is to revert the previous
> > > > > linux-yocto 5.15 version bump series for the release build.
> > > > >
> > > > > I will then wait for a patch from Bruce that fixes the problem before
> > > > > reapplying it post release.
> > > >
> > > > If it takes a few more days it may be better to slip that release (when
> > > > QA are likely testing M3 anyway) in order to resolve this rather than
> > > > reverting a load of things we'll only then end up reapplying.
> > > >
> > >
> > > I'll be working on it over the weekend, along with some other kernel
> > > items that I didn't get to as I worked on this today and some meta-virt
> > > things.
> >
> > Steve: Here's my latest queue:
> >
> > https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel-kirkstone
> >
> > It passed the parted and util-linux ptests locally.
>
> Thanks Bruce!
>
> I'll grab the patches and run an a-full on the autobuilder.

The a-full results are here:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/

The ptest runs came back all green, but there were failures in all of
the hw-ref tests that use older versions of 5.15 since the patch added
with SRC_URI +=  in your final commit doesn't apply to those older
kernel versions.

For example, beaglebone:

https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/8751/steps/11/logs/errors

Steve

> > > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > > thee at its end
> > > - "Use the force Harry" - Gandalf, Star Trek II
> > >
> > >
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
> >
> >
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196938): 
https://lists.openembedded.org/g/openembedded-core/message/196938
Mute This Topic: https://lists.openembedded.org/mt/104794844/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-yocto: enable fetching kernel metadata using file fetcher

2024-03-11 Thread Taedcke, Christian



On 11.03.2024 13:46, Bruce Ashfield via lists.openembedded.org wrote:

On Mon, Mar 11, 2024 at 5:15 AM Taedcke, Christian
 wrote:


From: Christian Taedcke 

The file fetcher does not support the destsuffix parameter. It does
not rename the supplied folder during the fetch. Therefore the folder
name (i.e. basepath) is added to the kernel-meta search directories.



What's the benefit ? I need to understand what you are trying to
do that requires this.


In a BSP layer for a custom machine we use the linux-yocto kernel.
In the BSP layer the file /recipes-kernel/linux/linux-yocto_6.1.bbappend 
adds a local folder containing kernel metatdata to the SRC_URI:


SRC_URI:append:my-machine = "file://my-meta;type=kmeta"

The folder my-meta is a subfolder: 
/recipes-kernel/linux/linux-yocto/my-machine/my-meta


Without this patch we would have to write:
SRC_URI:append:my-machine = " file://my-meta;type=kmeta;destsuffix=my-meta"

When using a file fetcher for kernel metatdata without this patch the 
destsuffix property would always have to be the same as the folder name 
itself. With this patch we do not need this duplication.




Because my first thought is "absolutely not" to changing the way
this works.

What I see below is possibly going to break out of tree BSP
definitions. The combination of kmeta and destsuffix really
isn't there to support the git fetcher, it is a keyword combination
that I used to indicate a meta-data repository that unfortunately
overlaps with the other fetcher parameters.


Ok, that was not clear to me. The comment above the function 
find_kernel_feature_dirs() indicates that the returned value has 
something to do with how/where the fetcher stores the provided metadata:


-> Return the name of the repository as it will be found in WORKDIR

I think there are 2 ways forward:
1. Rewrite this patch so it does not affect out of tree BSPs (remove 
exception, still use destsuffix for other fetchers), or

2. Drop this patch completely



The reality is that I won't be able to fully review and test
this until after the upcoming release is done, since I need to
also see about pulling together some regression tests and
submitting them at the same time.


No problem, i am just in the process of upstreaming our in-house 
patches. This is not time-critical. We can continue the discussion after 
the release.


Regards,
Christian



Bruce


Signed-off-by: Christian Taedcke 
---
  meta/classes-recipe/kernel-yocto.bbclass | 21 ++---
  1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/meta/classes-recipe/kernel-yocto.bbclass 
b/meta/classes-recipe/kernel-yocto.bbclass
index 9a86616dad..3cbdf21df8 100644
--- a/meta/classes-recipe/kernel-yocto.bbclass
+++ b/meta/classes-recipe/kernel-yocto.bbclass
@@ -62,8 +62,8 @@ def find_sccs(d):

  return sources_list

-# check the SRC_URI for "kmeta" type'd git repositories. Return the name of
-# the repository as it will be found in WORKDIR
+# check the SRC_URI for "kmeta" type'd git repositories and directories. Return
+# the name of the repository or directory as it will be found in WORKDIR
  def find_kernel_feature_dirs(d):
  feature_dirs=[]
  fetch = bb.fetch2.Fetch([], d)
@@ -71,13 +71,20 @@ def find_kernel_feature_dirs(d):
  urldata = fetch.ud[url]
  parm = urldata.parm
  type=""
+destdir = ""
  if "type" in parm:
  type = parm["type"]
-if "destsuffix" in parm:
-destdir = parm["destsuffix"]
-if type == "kmeta":
-feature_dirs.append(destdir)
-
+if type == "kmeta":
+if urldata.type == "git":
+if "destsuffix" in parm:
+destdir = parm["destsuffix"]
+elif urldata.type == "file":
+destdir = urldata.basepath
+else:
+bb.fatal( "unsupported fetcher '%s' used for kernel-metadata" 
% (urldata.type) )
+if destdir:
+feature_dirs.append(destdir)
+
  return feature_dirs

  # find the master/machine source branch. In the same way that the fetcher 
proceses
--
2.34.1












-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196937): 
https://lists.openembedded.org/g/openembedded-core/message/196937
Mute This Topic: https://lists.openembedded.org/mt/104859707/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] [master][PATCH v2] librsvg: Fix do_package_qa error for librsvg

2024-03-11 Thread Alexander Kanavin
On Mon, 11 Mar 2024 at 13:15,  wrote:
> 1. Can we say, that oe-core will support Rust in future after Kirkstone  as a 
> standalone (without any external dependency )?

Yes. Rust is now part of the core, and will stay there.

> 2. We assume that kirkstone will stay with 1.59 and those who want later 
> versions (1.68+)can use meta-lts-mixins

That's right.

> 3. We have the following assumptions for meta-lts-mixins
>
>  a) We see kirkstone/rust-1.68, kirkstone/rust-1.70 branches.
>  A new branch will be created for a newer and stable rust version for 
> example kirkstone/rust-1.75 .

There's also kirkstone/rust which is not tied to a specific rust
version and aims to provide the 'latest'.

>  b)  If 1 is not correct then we assume meta-lts-mixins will cater to all 
> the LTS layers in future. That means we may see branches like 
> scarthgap/rust-***

That will not necessarily happen. It depends on somebody willing to do
the work. But this also means that you can make that contribution.
There are typically two steps:

1. Update master to the needed upstream rust release.
2. Backport those recipes into a branch in meta-lts-mixins.

Keep in mind that this is a community project, and no one owes you
these things. The good news is that you are welcome to handle them and
share with the community.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196936): 
https://lists.openembedded.org/g/openembedded-core/message/196936
Mute This Topic: https://lists.openembedded.org/mt/104803790/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] [REGRESSION] linux (git/curl-native) and autorev

2024-03-11 Thread Max Krummenacher
On Sun, Mar 10, 2024 at 11:39:00PM +, Richard Purdie wrote:
> On Sun, 2024-03-10 at 09:05 -0700, Bruce Ashfield wrote:
> > On Sun, Mar 10, 2024 at 11:52 AM Richard Purdie
> >  wrote:
> > > 
> > > On Sun, 2024-03-10 at 06:20 -0700, Richard Purdie via
> > > lists.openembedded.org wrote:
> > > > On Sun, 2024-03-10 at 13:31 +0100, Max wrote:
> > > > > Am Samstag, dem 09.03.2024 um 13:04 -0800 schrieb Bruce
> > > > > Ashfield:
> > > > > > On Sat, Mar 9, 2024 at 12:58 PM  wrote:
> > > > > > > 
> > > > > > > From: Max Krummenacher 
> > > > > > > 
> > > > > > > Hello
> > > > > > > 
> > > > > > > If one builds a kernel using AUTOREV invoking bitbake only
> > > > > > > works
> > > > > > > once.
> > > > > > > Any subsequent bitbake invocation fails parsing the meta
> > > > > > > data.
> > > > > > > 
> > > > > > > Reproducable with:
> > > > > > > - latest poky, b5624ee564
> > > > > > > - Kernel with SRCREV = "AUTOREV", e.g. in local.conf
> > > > > > >   `SRCREV_machine:pn-linux-yocto:forcevariable =
> > > > > > > "${AUTOREV}"`
> > > > > > > - bitbake virtual/kernel; bitbake virtual/kernel
> > > > > > > 
> > > > > > > On the second invocation parsing fails when the fetcher
> > > > > > > tries
> > > > > > > to
> > > > > > > evaluate the latest SRCREV:
> > > > > > > 
> > > > > > > > ERROR: ExpansionError during parsing meta/recipes-
> > > > > > > > kernel/linux/linux-yocto_6.6.bb
> > > > > > > > Traceback (most recent call last):
> > > > > > > >   File "bitbake/lib/bb/fetch2/__init__.py", line 1245, in
> > > > > > > > srcrev_internal_helper(ud= > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > 0x7f8e26195890>, name='machine'):
> > > > > > > >  d.setVar("__BBAUTOREV_ACTED_UPON", True)
> > > > > > > >     >    srcrev = ud.method.latest_revision(ud, d,
> > > > > > > > name)
> > > > > > > > 
> > > > > > > >   File "bitbake/lib/bb/fetch2/__init__.py", line 1667, in
> > > > > > > > Git.latest_revision(ud= > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > 0x7f8e26195890>, name='machine'):
> > > > > > > >  except KeyError:
> > > > > > > >     >    revs[key] = rev =
> > > > > > > > self._latest_revision(ud,
> > > > > > > > d,
> > > > > > > > name)
> > > > > > > >  return rev
> > > > > > > >   File "bitbake/lib/bb/fetch2/git.py", line 850, in
> > > > > > > > Git._latest_revision(ud= > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > 0x7f8e26195890>, name='machine'):
> > > > > > > > 
> > > > > > > >     >    output = self._lsremote(ud, d, "")
> > > > > > > >  # Tags of the form ^{} may not work, need to
> > > > > > > > fallback to other form
> > > > > > > >   File "bitbake/lib/bb/fetch2/git.py", line 833, in
> > > > > > > > Git._lsremote(ud= > > > > > > > 0x7f8e26f5f290>, d= > > > > > > > 0x7f8e26195890>, search=''):
> > > > > > > >  bb.fetch2.check_network_access(d,
> > > > > > > > cmd,
> > > > > > > > repourl)
> > > > > > > >     >    output = runfetchcmd(cmd, d, True)
> > > > > > > >  if not output:
> > > > > > > >   File "bitbake/lib/bb/fetch2/__init__.py", line 957, in
> > > > > > > > runfetchcmd(cmd='export PSEUDO_DISABLED=1; export
> > > > > > > > DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1003/bus";
> > > > > > > > export
> > > > > > > > PATH="build/tmp/sysroots-uninative/x86_64-
> > > > > > > > linux/usr/bin:scripts:build/tmp/work/qemux86_64-poky-
> > > > > > > > linux/linux-yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > native/usr/bin/x86_64-poky-
> > > > > > > > linux:build/tmp/work/qemux86_64-
> > > > > > > > poky-linux/linux-yocto/6.6.20+git/recipe-
> > > > > > > > sysroot/usr/bin/crossscripts:build/tmp/work/qemux86_64-
> > > > > > > > poky-
> > > > > > > > linux/linux-yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > native/usr/sbin:build/tmp/work/qemux86_64-poky-
> > > > > > > > linux/linux-
> > > > > > > > yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > native/usr/bin:build/tmp/work/qemux86_64-poky-
> > > > > > > > linux/linux-
> > > > > > > > yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > native/sbin:build/tmp/work/qemux86_64-poky-linux/linux-
> > > > > > > > yocto/6.6.20+git/recipe-sysroot-
> > > > > > > > native/bin:bitbake/bin:build/tmp/hosttools"; export
> > > > > > > > HOME="/home/krm"; git -c gc.autoDetach=false -c
> > > > > > > > core.pager=cat
> > > > > > > > -c safe.bareRepository=all ls-remote
> > > > > > > > https://git.yoctoproject.org/linux-yocto.git ',
> > > > > > > > d=,
> > > > > > > > quiet=True, cleanup=[], log=None, workdir=None):
> > > > > > > > 
> > > > > > > >     >    raise FetchError(error_message)
> > > > > > > > 
> > > > > > > > bb.data_smart.ExpansionError: Failure expanding variable
> > > > > > > > fetcher_hashes_dummyfunc[vardepvalue], expression was
> > > > > > > > ${@bb.fetch.get_hashvalue(d)} which triggered exception
> > > > > > > > FetchError: Fetcher failure: Fetch command export
> > > > > > > > PSEUDO_DISABLED=1; export
> > > > > > > > DBUS_SESSION_BUS_ADDRESS="

Re: [OE-core][PATCH] kernel-yocto: enable fetching kernel metadata using file fetcher

2024-03-11 Thread Bruce Ashfield
On Mon, Mar 11, 2024 at 5:15 AM Taedcke, Christian
 wrote:
>
> From: Christian Taedcke 
>
> The file fetcher does not support the destsuffix parameter. It does
> not rename the supplied folder during the fetch. Therefore the folder
> name (i.e. basepath) is added to the kernel-meta search directories.
>

What's the benefit ? I need to understand what you are trying to
do that requires this.

Because my first thought is "absolutely not" to changing the way
this works.

What I see below is possibly going to break out of tree BSP
definitions. The combination of kmeta and destsuffix really
isn't there to support the git fetcher, it is a keyword combination
that I used to indicate a meta-data repository that unfortunately
overlaps with the other fetcher parameters.

The reality is that I won't be able to fully review and test
this until after the upcoming release is done, since I need to
also see about pulling together some regression tests and
submitting them at the same time.

Bruce

> Signed-off-by: Christian Taedcke 
> ---
>  meta/classes-recipe/kernel-yocto.bbclass | 21 ++---
>  1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/meta/classes-recipe/kernel-yocto.bbclass 
> b/meta/classes-recipe/kernel-yocto.bbclass
> index 9a86616dad..3cbdf21df8 100644
> --- a/meta/classes-recipe/kernel-yocto.bbclass
> +++ b/meta/classes-recipe/kernel-yocto.bbclass
> @@ -62,8 +62,8 @@ def find_sccs(d):
>
>  return sources_list
>
> -# check the SRC_URI for "kmeta" type'd git repositories. Return the name of
> -# the repository as it will be found in WORKDIR
> +# check the SRC_URI for "kmeta" type'd git repositories and directories. 
> Return
> +# the name of the repository or directory as it will be found in WORKDIR
>  def find_kernel_feature_dirs(d):
>  feature_dirs=[]
>  fetch = bb.fetch2.Fetch([], d)
> @@ -71,13 +71,20 @@ def find_kernel_feature_dirs(d):
>  urldata = fetch.ud[url]
>  parm = urldata.parm
>  type=""
> +destdir = ""
>  if "type" in parm:
>  type = parm["type"]
> -if "destsuffix" in parm:
> -destdir = parm["destsuffix"]
> -if type == "kmeta":
> -feature_dirs.append(destdir)
> -
> +if type == "kmeta":
> +if urldata.type == "git":
> +if "destsuffix" in parm:
> +destdir = parm["destsuffix"]
> +elif urldata.type == "file":
> +destdir = urldata.basepath
> +else:
> +bb.fatal( "unsupported fetcher '%s' used for 
> kernel-metadata" % (urldata.type) )
> +if destdir:
> +feature_dirs.append(destdir)
> +
>  return feature_dirs
>
>  # find the master/machine source branch. In the same way that the fetcher 
> proceses
> --
> 2.34.1
>
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196934): 
https://lists.openembedded.org/g/openembedded-core/message/196934
Mute This Topic: https://lists.openembedded.org/mt/104859707/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] [master][PATCH v2] librsvg: Fix do_package_qa error for librsvg

2024-03-11 Thread Nisha . M . Parrakat
Thanks Alex for the reply.
So till now we are using meta-rust master along with the kirkstone yocto layers 
and are trying to understand if it makes sense to use it further.
We had a few questions for the maintainence of Rust.

1. Can we say, that oe-core will support Rust in future after Kirkstone  as a 
standalone (without any external dependency )?
2. We assume that kirkstone will stay with 1.59 and those who want later 
versions (1.68+)can use meta-lts-mixins
3. We have the following assumptions for meta-lts-mixins

a) We see kirkstone/rust-1.68, kirkstone/rust-1.70 branches.
A new branch will be created for a newer and stable rust version for example 
kirkstone/rust-1.75 .
b)  If *1* is not correct then we assume meta-lts-mixins will cater to all the 
LTS layers in future. That means we may see branches like scarthgap/rust-***

Thanks in advance for your reply !

regards,
Nisha Parrakat

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

2024-03-11 Thread Zoltan Boszormenyi

2024. 03. 11. 10:37 keltezéssel, Alexander Kanavin írta:

On Mon, 11 Mar 2024 at 10:30, Böszörményi Zoltán  wrote:


   If you manually edit the file on target, you might as well
manually resolve which version you want after the update as both are
available regardless of whether (noreplace) was used or not. Or
perhaps merge the manual edits into the new version.

The interesting use case here is that the configuration file
in question is generated on the machine using a GUI,
while a minimal stock version of the file is shipped by the package.

This can be handled by shipping the stock config under a different
file name (e.g. conf.sample or conf.template)?


Yes, I am aware. But why not use the package manager's
own features instead of adding a workaround?


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

2024-03-11 Thread Alexander Kanavin
On Mon, 11 Mar 2024 at 10:30, Böszörményi Zoltán  wrote:

> >   If you manually edit the file on target, you might as well
> > manually resolve which version you want after the update as both are
> > available regardless of whether (noreplace) was used or not. Or
> > perhaps merge the manual edits into the new version.
>
> The interesting use case here is that the configuration file
> in question is generated on the machine using a GUI,
> while a minimal stock version of the file is shipped by the package.

This can be handled by shipping the stock config under a different
file name (e.g. conf.sample or conf.template)?

Alex

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

2024-03-11 Thread Zoltan Boszormenyi

2024. 03. 09. 17:39 keltezéssel, Alexander Kanavin írta:

I think (noreplace) flag only matters when the file has been manually
edited after rpm installation and its checksum diverges from what is
registered in rpm database. Which is not a common scenario in
embedded.


So from Yocto's POV it's the same either way, right?


  If you manually edit the file on target, you might as well
manually resolve which version you want after the update as both are
available regardless of whether (noreplace) was used or not. Or
perhaps merge the manual edits into the new version.


The interesting use case here is that the configuration file
in question is generated on the machine using a GUI,
while a minimal stock version of the file is shipped by the package.



Alex

On Fri, 8 Mar 2024 at 12:20, Zoltan Boszormenyi  wrote:

Hi,

I just found out that if an updated package ships a modified
configuration file, then the Yocto package upgrade does this:

* rename the edited conffile to conffile.rpmsave
* install the new, modified one from the package

instead of:

* keep the edited conffile intact
* install the new, modified one from the package as conffile.rpmnew

I think this is what was asked in 2017 here:
https://docs.yoctoproject.org/pipermail/yocto/2017-May/036031.html

The answer was a little uninformed about saying that using
CONFFILES is the fix, because rpm can behave two ways, see above.

Yocto, to this day, uses "%config /path/to/conffile" instead of
"%config(noreplace) /path/to/conffile" in package_rpm.bbclass.
The latter would behave as "keep modified conffile + install conffile.rpmnew".

What's the official stance on this behaviour?
Is it a known issue?
Is this what the project would expect from a package upgrade?

FWIW, this one liner would change the behaviour:

diff --git a/meta/classes-global/package_rpm.bbclass 
b/meta/classes-global/package_rpm.bbclass
index 2e3e4e8c79..6610115849 100644
--- a/meta/classes-global/package_rpm.bbclass
+++ b/meta/classes-global/package_rpm.bbclass
@@ -256,7 +256,7 @@ python write_specfile () {
   attr = get_attr(file)
   p = path + '/' + file
   if conffiles.count(p):
-target.append(attr + '%config "' + escape_chars(p) + '"')
+target.append(attr + '%config(noreplace) "' + escape_chars(p) + 
'"')
   else:
   target.append(attr + '"' + escape_chars(p) + '"')


Maybe it's better to make it conditional on a different variable:

CONFFILES_MODE = "keepold"
vs
CONFFILES_MODE = "installnew"

and the patch would be something like this below (untested),
keeping the current behaviour as default:

diff --git a/meta/classes-global/package_rpm.bbclass 
b/meta/classes-global/package_rpm.bbclass
index 2e3e4e8c79..f0651d69ba 100644
--- a/meta/classes-global/package_rpm.bbclass
+++ b/meta/classes-global/package_rpm.bbclass
@@ -191,7 +191,7 @@ python write_specfile () {
   if not len(depends_dict[dep]):
   array.append("%s: %s" % (tag, dep))

-def walk_files(walkpath, target, conffiles, dirfiles):
+def walk_files(d, walkpath, target, conffiles, dirfiles):
   # We can race against the ipk/deb backends which create CONTROL or 
DEBIAN
directories
   # when packaging. We just ignore these files which are created in
   # packages-split/ and not package/
@@ -250,13 +250,19 @@ python write_specfile () {
   if (not files and not dirs) or path in dirfiles:
   target.append(attr + '%dir "' + escape_chars(path) + '"')

+conffiles_mode = d.getVar("CONFFILES_MODE") or "installnew"
+if conffiles_mode != "installnew" and conffiles_mode != "keepold":
+conffiles_mode = "installnew"
   for file in files:
   if file == "CONTROL" or file == "DEBIAN":
   continue
   attr = get_attr(file)
   p = path + '/' + file
   if conffiles.count(p):
-target.append(attr + '%config "' + escape_chars(p) + '"')
+if conffiles_mode == "keepold":
+target.append(attr + '%config(noreplace) "' + 
escape_chars(p) + '"')
+else:
+target.append(attr + '%config "' + escape_chars(p) + 
'"')
   else:
   target.append(attr + '"' + escape_chars(p) + '"')

@@ -430,7 +436,7 @@ python write_specfile () {
   srcrpostrm = splitrpostrm

   file_list = []
-walk_files(root, file_list, conffiles, dirfiles)
+walk_files(localdata, root, file_list, conffiles, dirfiles)
   if not file_list and localdata.getVar('ALLOW_EMPTY', False) != 
"1":
   bb.note("Not creating empty RPM package for %s" % splitname)
   else:
@@ -522,7 +528,7 @@ python write_specfile () {


[OE-core][PATCH] kernel-yocto: enable fetching kernel metadata using file fetcher

2024-03-11 Thread Taedcke, Christian
From: Christian Taedcke 

The file fetcher does not support the destsuffix parameter. It does
not rename the supplied folder during the fetch. Therefore the folder
name (i.e. basepath) is added to the kernel-meta search directories.

Signed-off-by: Christian Taedcke 
---
 meta/classes-recipe/kernel-yocto.bbclass | 21 ++---
 1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/meta/classes-recipe/kernel-yocto.bbclass 
b/meta/classes-recipe/kernel-yocto.bbclass
index 9a86616dad..3cbdf21df8 100644
--- a/meta/classes-recipe/kernel-yocto.bbclass
+++ b/meta/classes-recipe/kernel-yocto.bbclass
@@ -62,8 +62,8 @@ def find_sccs(d):
 
 return sources_list
 
-# check the SRC_URI for "kmeta" type'd git repositories. Return the name of
-# the repository as it will be found in WORKDIR
+# check the SRC_URI for "kmeta" type'd git repositories and directories. Return
+# the name of the repository or directory as it will be found in WORKDIR
 def find_kernel_feature_dirs(d):
 feature_dirs=[]
 fetch = bb.fetch2.Fetch([], d)
@@ -71,13 +71,20 @@ def find_kernel_feature_dirs(d):
 urldata = fetch.ud[url]
 parm = urldata.parm
 type=""
+destdir = ""
 if "type" in parm:
 type = parm["type"]
-if "destsuffix" in parm:
-destdir = parm["destsuffix"]
-if type == "kmeta":
-feature_dirs.append(destdir)
-   
+if type == "kmeta":
+if urldata.type == "git":
+if "destsuffix" in parm:
+destdir = parm["destsuffix"]
+elif urldata.type == "file":
+destdir = urldata.basepath
+else:
+bb.fatal( "unsupported fetcher '%s' used for kernel-metadata" 
% (urldata.type) )
+if destdir:
+feature_dirs.append(destdir)
+
 return feature_dirs
 
 # find the master/machine source branch. In the same way that the fetcher 
proceses
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196928): 
https://lists.openembedded.org/g/openembedded-core/message/196928
Mute This Topic: https://lists.openembedded.org/mt/104859707/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][PATCHv2] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Alexander Kanavin
Please split the .bb/.inc merge into a separate commit.


Alex

On Mon, 11 Mar 2024 at 08:21, Markus Volk  wrote:
>
> - add a backport patch to fix compatibility with older gtk4 versions
> - merge .bb and .inc
>
> Signed-off-by: Markus Volk 
> ---
>  meta/recipes-devtools/vala/vala.inc   | 71 -
>  ...tk4-Preserve-compatibility-with-4.14.patch | 39 ++
>  meta/recipes-devtools/vala/vala_0.56.15.bb| 76 ++-
>  3 files changed, 114 insertions(+), 72 deletions(-)
>  delete mode 100644 meta/recipes-devtools/vala/vala.inc
>  create mode 100644 
> meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
>
> diff --git a/meta/recipes-devtools/vala/vala.inc 
> b/meta/recipes-devtools/vala/vala.inc
> deleted file mode 100644
> index 0177e86240..00
> --- a/meta/recipes-devtools/vala/vala.inc
> +++ /dev/null
> @@ -1,71 +0,0 @@
> -SUMMARY = "C#-like programming language for easing GObject programming"
> -HOMEPAGE = "http://vala-project.org";
> -DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject 
> programming. \
> -Vala compiles to plain C and has no runtime environment nor penalities 
> whatsoever."
> -SECTION = "devel"
> -DEPENDS = "bison-native flex-native glib-2.0 gobject-introspection"
> -
> -# Appending libxslt-native to dependencies has an effect
> -# of rebuilding the manual, which is very slow. Let's do this
> -# only when api-documentation distro feature is enabled.
> -DEPENDS:append:class-target = " ${@bb.utils.contains('DISTRO_FEATURES', 
> 'api-documentation', 'libxslt-native', '', d)}"
> -
> -# vala-native contains a native version of vapigen, which we use instead of 
> the target one
> -DEPENDS:append:class-target = " vala-native"
> -BBCLASSEXTEND = "native"
> -LICENSE = "LGPL-2.1-only"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
> -
> -SHRT_VER = 
> "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
> -
> -SRC_URI = 
> "http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
> -inherit autotools pkgconfig upstream-version-is-even
> -
> -FILES:${PN} += "${datadir}/${BPN}-${SHRT_VER}/vapi 
> ${libdir}/${BPN}-${SHRT_VER}/"
> -FILES:${PN}-doc += "${datadir}/devhelp"
> -
> -# .gir files from gobject-introspection are installed to ${libdir} when 
> multilib is enabled
> -GIRDIR_OPT = "${@'--girdir=${STAGING_LIBDIR}/gir-1.0' if 
> d.getVar('MULTILIBS') else ''}"
> -
> -do_configure:prepend:class-target() {
> -# Write out a vapigen wrapper that will be provided by pkg-config 
> file installed in target sysroot
> -# The wrapper will call a native vapigen
> -cat > ${B}/vapigen-wrapper << EOF
> -#!/bin/sh
> -vapigen-${SHRT_VER} ${GIRDIR_OPT} "\$@"
> -EOF
> -chmod +x ${B}/vapigen-wrapper
> -}
> -
> -EXTRA_OECONF += " --disable-valadoc"
> -
> -# Vapigen wrapper needs to be available system-wide, because it will be used
> -# to build vapi files from all other packages with vala support
> -do_install:append:class-target() {
> -install -d ${D}${bindir_crossscripts}/
> -install ${B}/vapigen-wrapper ${D}${bindir_crossscripts}/
> -}
> -
> -# Put vapigen wrapper into target sysroot so that it can be used when 
> building
> -# vapi files.
> -SYSROOT_DIRS += "${bindir_crossscripts}"
> -
> -inherit multilib_script
> -MULTILIB_SCRIPTS = "${PN}:${bindir}/vala-gen-introspect-0.56"
> -
> -SYSROOT_PREPROCESS_FUNCS:append:class-target = " vapigen_sysroot_preprocess"
> -vapigen_sysroot_preprocess() {
> -# Tweak the vapigen name in the vapigen pkgconfig file, so that it 
> picks
> -# up our wrapper.
> -sed -i \
> -   -e "s|vapigen=.*|vapigen=${bindir_crossscripts}/vapigen-wrapper|" 
> \
> -   ${SYSROOT_DESTDIR}${libdir}/pkgconfig/vapigen-${SHRT_VER}.pc
> -}
> -
> -SSTATE_SCAN_FILES += "vapigen-wrapper"
> -
> -PACKAGE_PREPROCESS_FUNCS += "vala_package_preprocess"
> -
> -vala_package_preprocess () {
> -   rm -rf ${PKGD}${bindir_crossscripts}
> -}
> diff --git 
> a/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
>  
> b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
> new file mode 100644
> index 00..161474086e
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
> @@ -0,0 +1,39 @@
> +From 17349020fb95454d06f827fd555b05248f10a370 Mon Sep 17 00:00:00 2001
> +From: Rico Tzschichholz 
> +Date: Thu, 7 Mar 2024 17:56:05 +0100
> +Subject: [PATCH] gtk4: Preserve compatibility with < 4.14
> +
> +Don't prefer new accessor methods for Calendar.day/month/year
> +
> +Fixes https://gitlab.gnome.org/GNOME/vala/issues/1531
> +
> +Upstream-Status: Backport 
> [https://gitlab.gnome.org/GNOME/vala/-/commit/e0c4ea8c4a0bbf859b5341a7465b395892789d9e]
> +
> +Signed-off-by: Markus Volk 
> +---
> + vapi/gtk4.vapi | 3 +++
> + vapi/metadata/Gtk-4.0.metadata | 5 +

[OE-core] [nanbield][PATCH 7/7] gnutls: Upgrade 3.8.2 -> 3.8.3

2024-03-11 Thread Lee Chee Yang
From: Simone Weiß 

Upgrade version to adress recent CVE findings.

Changelog
=
** libgnutls: Fix more timing side-channel inside RSA-PSK key exchange
   [GNUTLS-SA-2024-01-14, CVSS: medium] [CVE-2024-0553]

** libgnutls: Fix assertion failure when verifying a certificate chain with a
   cycle of cross signatures
   [GNUTLS-SA-2024-01-09, CVSS: medium] [CVE-2024-0567]

** libgnutls: Fix regression in handling Ed25519 keys stored in PKCS#11 token
   certtool was unable to handle Ed25519 keys generated on PKCS#11
   with pkcs11-tool (OpenSC). This is a regression introduced in 3.8.2.

(cherry-pick from Oe-Core rev 705d2972b38efc9f331e3635c07ca92f8812b365)

Signed-off-by: Simone Weiß 
Signed-off-by: Alexandre Belloni 
Signed-off-by: Richard Purdie 
Signed-off-by: Lee Chee Yang 
---
 .../recipes-support/gnutls/{gnutls_3.8.2.bb => gnutls_3.8.3.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/gnutls/{gnutls_3.8.2.bb => gnutls_3.8.3.bb} (97%)

diff --git a/meta/recipes-support/gnutls/gnutls_3.8.2.bb 
b/meta/recipes-support/gnutls/gnutls_3.8.3.bb
similarity index 97%
rename from meta/recipes-support/gnutls/gnutls_3.8.2.bb
rename to meta/recipes-support/gnutls/gnutls_3.8.3.bb
index 43fb5c4c4e..27d6753be0 100644
--- a/meta/recipes-support/gnutls/gnutls_3.8.2.bb
+++ b/meta/recipes-support/gnutls/gnutls_3.8.3.bb
@@ -25,7 +25,7 @@ SRC_URI = 
"https://www.gnupg.org/ftp/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar
file://Add-ptest-support.patch \
"
 
-SRC_URI[sha256sum] = 
"e765e5016ffa9b9dd243e363a0460d57707ee2491267db2e96c9c2adef77"
+SRC_URI[sha256sum] = 
"f74fc5954b27d4ec6dfbb11dea987888b5b124289a3703afcada0ee520f4173e"
 
 inherit autotools texinfo pkgconfig gettext lib_package gtk-doc ptest
 
-- 
2.37.3


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



[OE-core] [nanbield][PATCH 6/7] gnutls: upgrade 3.8.1 -> 3.8.2

2024-03-11 Thread Lee Chee Yang
From: Wang Mingyu 

Changelog:

** libgnutls: Fix timing side-channel inside RSA-PSK key exchange.
** libgnutls: Add API functions to perform ECDH and DH key agreement
** libgnutls: Added support for AES-GCM-SIV ciphers
** libgnutls: transparent KTLS support is extended to FreeBSD kernel
** gnutls-cli: New option --starttls-name

(cherry-pick from Oe-Core rev 3c01bb0be8ddafa0aa1ad996ec524b51fd28f512)

Signed-off-by: Wang Mingyu 
Signed-off-by: Alexandre Belloni 
Signed-off-by: Lee Chee Yang 
---
 .../recipes-support/gnutls/{gnutls_3.8.1.bb => gnutls_3.8.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/gnutls/{gnutls_3.8.1.bb => gnutls_3.8.2.bb} (97%)

diff --git a/meta/recipes-support/gnutls/gnutls_3.8.1.bb 
b/meta/recipes-support/gnutls/gnutls_3.8.2.bb
similarity index 97%
rename from meta/recipes-support/gnutls/gnutls_3.8.1.bb
rename to meta/recipes-support/gnutls/gnutls_3.8.2.bb
index 455031dd47..43fb5c4c4e 100644
--- a/meta/recipes-support/gnutls/gnutls_3.8.1.bb
+++ b/meta/recipes-support/gnutls/gnutls_3.8.2.bb
@@ -25,7 +25,7 @@ SRC_URI = 
"https://www.gnupg.org/ftp/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar
file://Add-ptest-support.patch \
"
 
-SRC_URI[sha256sum] = 
"ba8b9e15ae20aba88f44661978f5b5863494316fe7e722ede9d069fe6294829c"
+SRC_URI[sha256sum] = 
"e765e5016ffa9b9dd243e363a0460d57707ee2491267db2e96c9c2adef77"
 
 inherit autotools texinfo pkgconfig gettext lib_package gtk-doc ptest
 
-- 
2.37.3


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



[OE-core] [nanbield][PATCH 5/7] bind: Upgrade 9.18.21 -> 9.18.24

2024-03-11 Thread Lee Chee Yang
From: Soumya Sambu 

Changelog:
=
9.18.24:
- Fix case insensitive setting for isc_ht hashtable.
[GL #4568]

9.18.23:
- Specific DNS answers could cause a denial-of-service
condition due to DNS validation taking a long time.
(CVE-2023-50387) [GL #4424]
- Change 6315 inadvertently introduced regressions that
could cause named to crash. [GL #4234]
- Under some circumstances, the DoT code in client
mode could process more than one message at a time when
that was not expected. That has been fixed. [GL #4487]

9.18.22:
- Limit isc_task_send() overhead for RBTDB tree pruning.
[GL #4383]
- Restore DNS64 state when handling a serve-stale timeout.
(CVE-2023-5679) [GL #4334]
- Specific queries could trigger an assertion check with
nxdomain-redirect enabled. (CVE-2023-5517) [GL #4281]
- Speed up parsing of DNS messages with many different
names. (CVE-2023-4408) [GL #4234]
- Address race conditions in dns_tsigkey_find().
[GL #4182]
- Conversion from NSEC3 signed to NSEC signed could
temporarily put the zone into a state where it was
treated as unsigned until the NSEC chain was built.
Additionally conversion from one set of NSEC3 parameters
to another could also temporarily put the zone into a
state where it was treated as unsigned until the new
NSEC3 chain was built. [GL #1794] [GL #4495]
- Memory leak in zone.c:sign_zone. When named signed a
zone it could leak dst_keys due to a misplaced
'continue'. [GL #4488]
- Log more details about the cause of "not exact" errors.
[GL #4500]
- The wrong time was being used to determine what RRSIGs
where to be generated when dnssec-policy was in use.
[GL #4494]
- The "trust-anchor-telemetry" statement is no longer
marked as experimental. This silences a relevant log
message that was emitted even when the feature was
explicitly disabled. [GL #4497]
- Fix statistics export to use full 64 bit signed numbers
instead of truncating values to unsigned 32 bits.
[GL #4467]
- NetBSD has added 'hmac' to libc which collides with our
use of 'hmac'. [GL #4478]

(cherry-pick from Oe-Core rev d7f31aba343948dbaadafc8c0c66f78e6ffb46e3)

Signed-off-by: Soumya Sambu 
Signed-off-by: Richard Purdie 
Signed-off-by: Lee Chee Yang 
---
 .../bind/{bind_9.18.21.bb => bind_9.18.24.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-connectivity/bind/{bind_9.18.21.bb => bind_9.18.24.bb} 
(97%)

diff --git a/meta/recipes-connectivity/bind/bind_9.18.21.bb 
b/meta/recipes-connectivity/bind/bind_9.18.24.bb
similarity index 97%
rename from meta/recipes-connectivity/bind/bind_9.18.21.bb
rename to meta/recipes-connectivity/bind/bind_9.18.24.bb
index f5fb4bd1e5..2874990320 100644
--- a/meta/recipes-connectivity/bind/bind_9.18.21.bb
+++ b/meta/recipes-connectivity/bind/bind_9.18.24.bb
@@ -20,7 +20,7 @@ SRC_URI = 
"https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \
file://0001-avoid-start-failure-with-bind-user.patch \
"
 
-SRC_URI[sha256sum] = 
"a556be22505d9ea4f9c6717aee9c549739c68498aff3ca69035787ecc648fec5"
+SRC_URI[sha256sum] = 
"709d73023c9115ddad3bab65b6c8c79a590196d0d114f5d0ca2533dbd52ddf66"
 
 UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/";
 # follow the ESV versions divisible by 2
-- 
2.37.3


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



[OE-core] [nanbield][PATCH 4/7] bind: upgrade 9.18.20 -> 9.18.21

2024-03-11 Thread Lee Chee Yang
From: Wang Mingyu 

bind-ensure-searching-for-json-headers-searches-sysr.patch
refreshed for 9.18.21

Changelog:
==
-Improve LRU cleaning behaviour.
-The "resolver-nonbackoff-tries" and "resolver-retry-interval" options are
 deprecated; a warning will be logged if they are used.
-BIND might sometimes crash after startup or re-configuration when one 'tls'
 entry is used multiple times to connect to remote servers due to initialisation
 attempts from contexts of multiple threads. That has been fixed.
-Dig +yaml will now report "no servers could be reached" also for UDP setup
 failure when no other servers or tries are left.
-Recognize escapes when reading the public key from file.
-Dig +yaml will now report "no servers could be reached" on TCP connection
 failure as well as for UDP timeouts.
-Deprecate AES-based DNS cookies.

(cherry-pick from Oe-core rev b750d54622a0fa0a35d83ddc59f07661e903360b)

Signed-off-by: Wang Mingyu 
Signed-off-by: Alexandre Belloni 
Signed-off-by: Richard Purdie 
Signed-off-by: Lee Chee Yang 
---
 ...nd-ensure-searching-for-json-headers-searches-sysr.patch | 6 +++---
 .../bind/{bind_9.18.20.bb => bind_9.18.21.bb}   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
 rename meta/recipes-connectivity/bind/{bind_9.18.20.bb => bind_9.18.21.bb} 
(97%)

diff --git 
a/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
 
b/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
index f1abd179e8..38d07cae39 100644
--- 
a/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
+++ 
b/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
@@ -1,4 +1,4 @@
-From 246087f89e9434b726c7884e4c0964f71084f091 Mon Sep 17 00:00:00 2001
+From 5ae30329f168c1e8d2e0c3831988a4f3e9096e39 Mon Sep 17 00:00:00 2001
 From: Paul Gortmaker 
 Date: Tue, 9 Jun 2015 11:22:00 -0400
 Subject: [PATCH] bind: ensure searching for json headers searches sysroot
@@ -33,10 +33,10 @@ Signed-off-by: Paul Gortmaker 
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/configure.ac b/configure.ac
-index 10e8bf6..bf20690 100644
+index 2ab8ddd..92fe983 100644
 --- a/configure.ac
 +++ b/configure.ac
-@@ -814,7 +814,7 @@ AS_CASE([$with_lmdb],
+@@ -761,7 +761,7 @@ AS_CASE([$with_lmdb],
[no],[],
[auto|yes], [PKG_CHECK_MODULES([LMDB], [lmdb],
   [ac_lib_lmdb_found=yes],
diff --git a/meta/recipes-connectivity/bind/bind_9.18.20.bb 
b/meta/recipes-connectivity/bind/bind_9.18.21.bb
similarity index 97%
rename from meta/recipes-connectivity/bind/bind_9.18.20.bb
rename to meta/recipes-connectivity/bind/bind_9.18.21.bb
index 187685eef5..f5fb4bd1e5 100644
--- a/meta/recipes-connectivity/bind/bind_9.18.20.bb
+++ b/meta/recipes-connectivity/bind/bind_9.18.21.bb
@@ -20,7 +20,7 @@ SRC_URI = 
"https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \
file://0001-avoid-start-failure-with-bind-user.patch \
"
 
-SRC_URI[sha256sum] = 
"4b891ebf58d3f2a7ac3dd2682990f528a3448eaa1c992ddc5c141b8587a98ec5"
+SRC_URI[sha256sum] = 
"a556be22505d9ea4f9c6717aee9c549739c68498aff3ca69035787ecc648fec5"
 
 UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/";
 # follow the ESV versions divisible by 2
-- 
2.37.3


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



[OE-core] [nanbield][PATCH 2/7] openssl: upgrade to 3.1.5

2024-03-11 Thread Lee Chee Yang
From: Lee Chee Yang 

Changes between 3.1.4 and 3.1.5 [30 Jan 2024]
 * A file in PKCS12 format can contain certificates and keys and may
come from
   an untrusted source. The PKCS12 specification allows certain fields
to be
   NULL, but OpenSSL did not correctly check for this case. A fix has
been
   applied to prevent a NULL pointer dereference that results in OpenSSL
   crashing. If an application processes PKCS12 files from an untrusted
source
   using the OpenSSL APIs then that application will be vulnerable to
this
   issue prior to this fix.

   OpenSSL APIs that were vulnerable to this are: PKCS12_parse(),
   PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(),
PKCS12_unpack_authsafes()
   and PKCS12_newpass().

   We have also fixed a similar issue in SMIME_write_PKCS7(). However
since this
   function is related to writing data we do not consider it security
   significant.

   ([CVE-2024-0727])
https://www.openssl.org/news/cl31.txt

drop fix_random_labels.patch as fixed in
https://github.com/openssl/openssl/commit/99630a1b08fd6464d95052dee4a3500afeb95867

Signed-off-by: Lee Chee Yang 
---
 .../openssl/openssl/fix_random_labels.patch   | 22 ---
 .../{openssl_3.1.4.bb => openssl_3.1.5.bb}|  3 +--
 2 files changed, 1 insertion(+), 24 deletions(-)
 delete mode 100644 
meta/recipes-connectivity/openssl/openssl/fix_random_labels.patch
 rename meta/recipes-connectivity/openssl/{openssl_3.1.4.bb => 
openssl_3.1.5.bb} (98%)

diff --git a/meta/recipes-connectivity/openssl/openssl/fix_random_labels.patch 
b/meta/recipes-connectivity/openssl/openssl/fix_random_labels.patch
deleted file mode 100644
index 78dcd81685..00
--- a/meta/recipes-connectivity/openssl/openssl/fix_random_labels.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-The perl script adds random suffixes to the local function names to ensure
-it doesn't clash with other parts of openssl. Set the random number seed
-to something predictable so the assembler files are generated consistently
-and our own reproducible builds tests pass.
-
-Upstream-Status: Pending
-Signed-off-by: Richard Purdie 
-
-Index: openssl-3.1.0/crypto/modes/asm/aes-gcm-avx512.pl
-===
 openssl-3.1.0.orig/crypto/modes/asm/aes-gcm-avx512.pl
-+++ openssl-3.1.0/crypto/modes/asm/aes-gcm-avx512.pl
-@@ -191,6 +191,9 @@ my $CTX_OFFSET_HTable= (16 * 6);
- # ;;; Helper functions
- # ;
- 
-+# Ensure the local labels are reproduicble
-+srand(1);
-+
- # ; Generates "random" local labels
- sub random_string() {
-   my @chars  = ('a' .. 'z', 'A' .. 'Z', '0' .. '9', '_');
diff --git a/meta/recipes-connectivity/openssl/openssl_3.1.4.bb 
b/meta/recipes-connectivity/openssl/openssl_3.1.5.bb
similarity index 98%
rename from meta/recipes-connectivity/openssl/openssl_3.1.4.bb
rename to meta/recipes-connectivity/openssl/openssl_3.1.5.bb
index 0fe4e76808..9c1d4e31be 100644
--- a/meta/recipes-connectivity/openssl/openssl_3.1.4.bb
+++ b/meta/recipes-connectivity/openssl/openssl_3.1.5.bb
@@ -11,7 +11,6 @@ SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz 
\
file://run-ptest \

file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-co.patch \
file://0001-Configure-do-not-tweak-mips-cflags.patch \
-   file://fix_random_labels.patch \
file://0001-Added-handshake-history-reporting-when-test-fails.patch 
\
"
 
@@ -19,7 +18,7 @@ SRC_URI:append:class-nativesdk = " \
file://environment.d-openssl.sh \
"
 
-SRC_URI[sha256sum] = 
"840af5366ab9b522bde525826be3ef0fb0af81c6a9ebd84caa600fea1731eee3"
+SRC_URI[sha256sum] = 
"6ae015467dabf0469b139ada93319327be24b98251ffaeceda0221848dc09262"
 
 inherit lib_package multilib_header multilib_script ptest perlnative manpages
 MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
-- 
2.37.3


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



[OE-core] [nanbield][PATCH 3/7] python3-jinja2: upgrade 3.1.2 -> 3.1.3

2024-03-11 Thread Lee Chee Yang
From: Wang Mingyu 

Changelog:
==
-Fix compiler error when checking if required blocks in parent templates are 
empty.
-xmlattr filter does not allow keys with spaces.
-Make error messages stemming from invalid nesting of {% trans %} blocks more 
helpful

upgrade include fix for CVE-2024-22195.
(cherry-pick from Oe-Core rev 8a0524464583d69df7746253f5020c2c125a8e1f)

Signed-off-by: Wang Mingyu 
Signed-off-by: Alexandre Belloni 
Signed-off-by: Richard Purdie 
Signed-off-by: Lee Chee Yang 
---
 .../python/{python3-jinja2_3.1.2.bb => python3-jinja2_3.1.3.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-jinja2_3.1.2.bb => 
python3-jinja2_3.1.3.bb} (92%)

diff --git a/meta/recipes-devtools/python/python3-jinja2_3.1.2.bb 
b/meta/recipes-devtools/python/python3-jinja2_3.1.3.bb
similarity index 92%
rename from meta/recipes-devtools/python/python3-jinja2_3.1.2.bb
rename to meta/recipes-devtools/python/python3-jinja2_3.1.3.bb
index fa6d930a9c..18057809c8 100644
--- a/meta/recipes-devtools/python/python3-jinja2_3.1.2.bb
+++ b/meta/recipes-devtools/python/python3-jinja2_3.1.3.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "https://pypi.org/project/Jinja2/";
 LICENSE = "BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=5dc88300786f1c214c1e9827a5229462"
 
-SRC_URI[sha256sum] = 
"31351a702a408a9e7595a8fc6150fc3f43bb6bf7e319770cbc0db9df9437e852"
+SRC_URI[sha256sum] = 
"ac8bd6544d4bb2c9792bf3a159e80bba8fda7f07e81bc3aed565432d5925ba90"
 
 PYPI_PACKAGE = "Jinja2"
 
-- 
2.37.3


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



[OE-core] [nanbield][PATCH 1/7] libxml2: upgrade to 2.11.7

2024-03-11 Thread Lee Chee Yang
From: Lee Chee Yang 

libxml2 2.11.7
Security
[CVE-2024-25062] xmlreader: Don't expand XIncludes when backtracking

libxml2 2.11.6
Regressions
threads: Fix --with-thread-alloc
xinclude: Fix 'last' pointer in xmlXIncludeCopyNode

Bug fixes
parser: Fix potential use-after-free in xmlParseCharDataInternal

Signed-off-by: Lee Chee Yang 
---
 .../libxml/{libxml2_2.11.5.bb => libxml2_2.11.7.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-core/libxml/{libxml2_2.11.5.bb => libxml2_2.11.7.bb} (97%)

diff --git a/meta/recipes-core/libxml/libxml2_2.11.5.bb 
b/meta/recipes-core/libxml/libxml2_2.11.7.bb
similarity index 97%
rename from meta/recipes-core/libxml/libxml2_2.11.5.bb
rename to meta/recipes-core/libxml/libxml2_2.11.7.bb
index fc82912df2..482ce9042d 100644
--- a/meta/recipes-core/libxml/libxml2_2.11.5.bb
+++ b/meta/recipes-core/libxml/libxml2_2.11.7.bb
@@ -18,7 +18,7 @@ SRC_URI += 
"http://www.w3.org/XML/Test/xmlts20130923.tar;subdir=${BP};name=testt
file://install-tests.patch \
"
 
-SRC_URI[archive.sha256sum] = 
"3727b078c360ec69fa869de14bd6f75d7ee8d36987b071e6928d4720a28df3a6"
+SRC_URI[archive.sha256sum] = 
"fb27720e25eaf457f94fd3d7189bcf2626c6dccf4201553bc8874d50e3560162"
 SRC_URI[testtar.sha256sum] = 
"c6b2d42ee50b8b236e711a97d68e6c4b5c8d83e69a2be4722379f08702ea7273"
 
 # Disputed as a security issue, but fixed in d39f780
-- 
2.37.3


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



Patchtest results for [oe-core][PATCHv2] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Patchtest
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/PATCHv2-vala-fix-for-gtk4-prior-to-4.14.patch

FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed 
without "License-Update:" tag and description in commit message 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)

PASS: pretest src uri left files 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
PASS: test Signed-off-by presence 
(test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test Signed-off-by presence 
(test_patch.TestPatch.test_signed_off_by_presence)
PASS: test Upstream-Status presence 
(test_patch.TestPatch.test_upstream_status_presence_format)
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)
PASS: test src uri left files 
(test_metadata.TestMetadata.test_src_uri_left_files)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
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 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 (#196919): 
https://lists.openembedded.org/g/openembedded-core/message/196919
Mute This Topic: https://lists.openembedded.org/mt/104858933/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Patchtest results for [oe-core][PATCH] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Patchtest
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/vala-fix-for-gtk4-prior-to-4.14.patch

FAIL: test Signed-off-by presence: A patch file has been added without a 
Signed-off-by tag: '0001-gtk4-Preserve-compatibility-with-4.14.patch' 
(test_patch.TestPatch.test_signed_off_by_presence)
FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed 
without "License-Update:" tag and description in commit message 
(test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)

PASS: pretest src uri left files 
(test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
PASS: test Signed-off-by presence 
(test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test Upstream-Status presence 
(test_patch.TestPatch.test_upstream_status_presence_format)
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)
PASS: test src uri left files 
(test_metadata.TestMetadata.test_src_uri_left_files)

SKIP: pretest pylint: No python related patches, skipping test 
(test_python_pylint.PyLint.pretest_pylint)
SKIP: test bugzilla entry format: No bug ID found 
(test_mbox.TestMbox.test_bugzilla_entry_format)
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 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 (#196917): 
https://lists.openembedded.org/g/openembedded-core/message/196917
Mute This Topic: https://lists.openembedded.org/mt/104858856/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe-core][PATCHv2] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Markus Volk
- add a backport patch to fix compatibility with older gtk4 versions
- merge .bb and .inc

Signed-off-by: Markus Volk 
---
 meta/recipes-devtools/vala/vala.inc   | 71 -
 ...tk4-Preserve-compatibility-with-4.14.patch | 39 ++
 meta/recipes-devtools/vala/vala_0.56.15.bb| 76 ++-
 3 files changed, 114 insertions(+), 72 deletions(-)
 delete mode 100644 meta/recipes-devtools/vala/vala.inc
 create mode 100644 
meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch

diff --git a/meta/recipes-devtools/vala/vala.inc 
b/meta/recipes-devtools/vala/vala.inc
deleted file mode 100644
index 0177e86240..00
--- a/meta/recipes-devtools/vala/vala.inc
+++ /dev/null
@@ -1,71 +0,0 @@
-SUMMARY = "C#-like programming language for easing GObject programming"
-HOMEPAGE = "http://vala-project.org";
-DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject 
programming. \
-Vala compiles to plain C and has no runtime environment nor penalities 
whatsoever."
-SECTION = "devel"
-DEPENDS = "bison-native flex-native glib-2.0 gobject-introspection"
-
-# Appending libxslt-native to dependencies has an effect
-# of rebuilding the manual, which is very slow. Let's do this
-# only when api-documentation distro feature is enabled.
-DEPENDS:append:class-target = " ${@bb.utils.contains('DISTRO_FEATURES', 
'api-documentation', 'libxslt-native', '', d)}"
-
-# vala-native contains a native version of vapigen, which we use instead of 
the target one
-DEPENDS:append:class-target = " vala-native"
-BBCLASSEXTEND = "native"
-LICENSE = "LGPL-2.1-only"
-LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
-
-SHRT_VER = "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
-
-SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
-inherit autotools pkgconfig upstream-version-is-even
-
-FILES:${PN} += "${datadir}/${BPN}-${SHRT_VER}/vapi 
${libdir}/${BPN}-${SHRT_VER}/"
-FILES:${PN}-doc += "${datadir}/devhelp"
-
-# .gir files from gobject-introspection are installed to ${libdir} when 
multilib is enabled
-GIRDIR_OPT = "${@'--girdir=${STAGING_LIBDIR}/gir-1.0' if d.getVar('MULTILIBS') 
else ''}"
-
-do_configure:prepend:class-target() {
-# Write out a vapigen wrapper that will be provided by pkg-config file 
installed in target sysroot
-# The wrapper will call a native vapigen
-cat > ${B}/vapigen-wrapper << EOF
-#!/bin/sh
-vapigen-${SHRT_VER} ${GIRDIR_OPT} "\$@"
-EOF
-chmod +x ${B}/vapigen-wrapper
-}
-
-EXTRA_OECONF += " --disable-valadoc"
-
-# Vapigen wrapper needs to be available system-wide, because it will be used
-# to build vapi files from all other packages with vala support
-do_install:append:class-target() {
-install -d ${D}${bindir_crossscripts}/
-install ${B}/vapigen-wrapper ${D}${bindir_crossscripts}/
-}
-
-# Put vapigen wrapper into target sysroot so that it can be used when building
-# vapi files.
-SYSROOT_DIRS += "${bindir_crossscripts}"
-
-inherit multilib_script
-MULTILIB_SCRIPTS = "${PN}:${bindir}/vala-gen-introspect-0.56"
-
-SYSROOT_PREPROCESS_FUNCS:append:class-target = " vapigen_sysroot_preprocess"
-vapigen_sysroot_preprocess() {
-# Tweak the vapigen name in the vapigen pkgconfig file, so that it 
picks
-# up our wrapper.
-sed -i \
-   -e "s|vapigen=.*|vapigen=${bindir_crossscripts}/vapigen-wrapper|" \
-   ${SYSROOT_DESTDIR}${libdir}/pkgconfig/vapigen-${SHRT_VER}.pc
-}
-
-SSTATE_SCAN_FILES += "vapigen-wrapper"
-
-PACKAGE_PREPROCESS_FUNCS += "vala_package_preprocess"
-
-vala_package_preprocess () {
-   rm -rf ${PKGD}${bindir_crossscripts}
-}
diff --git 
a/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
new file mode 100644
index 00..161474086e
--- /dev/null
+++ 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
@@ -0,0 +1,39 @@
+From 17349020fb95454d06f827fd555b05248f10a370 Mon Sep 17 00:00:00 2001
+From: Rico Tzschichholz 
+Date: Thu, 7 Mar 2024 17:56:05 +0100
+Subject: [PATCH] gtk4: Preserve compatibility with < 4.14
+
+Don't prefer new accessor methods for Calendar.day/month/year
+
+Fixes https://gitlab.gnome.org/GNOME/vala/issues/1531
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/vala/-/commit/e0c4ea8c4a0bbf859b5341a7465b395892789d9e]
+
+Signed-off-by: Markus Volk 
+---
+ vapi/gtk4.vapi | 3 +++
+ vapi/metadata/Gtk-4.0.metadata | 5 +
+ 2 files changed, 8 insertions(+)
+
+diff --git a/vapi/gtk4.vapi b/vapi/gtk4.vapi
+index 49f8b2078..51ecea27d 100644
+--- a/vapi/gtk4.vapi
 b/vapi/gtk4.vapi
+@@ -7350,11 +7350,14 @@ namespace Gtk {
+   [Version (since = "4.14")]
+   public void set_year (int year);
+   public void unmark_day (uint day);
++  [NoAccessorMet

Re: [oe-core][PATCH] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Markus Volk
I simply dropped the part that patched gtk-4.0.metadata. The problem is 
fixed without it
and I dont really have an idea what this file is used for. So I dislike 
adding it


On Mon, Mar 11 2024 at 12:10:36 AM -07:00:00, Markus Volk 
 wrote:

- add a backport patch to fix compatibility with older gtk4 versions
- merge .bb and .inc

Signed-off-by: Markus Volk >

---
 meta/recipes-devtools/vala/vala.inc   | 71 -
 ...tk4-Preserve-compatibility-with-4.14.patch | 37 +
 meta/recipes-devtools/vala/vala_0.56.15.bb| 76 
++-

 3 files changed, 112 insertions(+), 72 deletions(-)
 delete mode 100644 meta/recipes-devtools/vala/vala.inc
 create mode 100644 
meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch


diff --git a/meta/recipes-devtools/vala/vala.inc 
b/meta/recipes-devtools/vala/vala.inc

deleted file mode 100644
index 0177e86240..00
--- a/meta/recipes-devtools/vala/vala.inc
+++ /dev/null
@@ -1,71 +0,0 @@
-SUMMARY = "C#-like programming language for easing GObject 
programming"

-HOMEPAGE = "http://vala-project.org "
-DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject 
programming. \
-Vala compiles to plain C and has no runtime environment nor 
penalities whatsoever."

-SECTION = "devel"
-DEPENDS = "bison-native flex-native glib-2.0 gobject-introspection"
-
-# Appending libxslt-native to dependencies has an effect
-# of rebuilding the manual, which is very slow. Let's do this
-# only when api-documentation distro feature is enabled.
-DEPENDS:append:class-target = " ${@bb.utils.contains 
('DISTRO_FEATURES', 'api-documentation', 
'libxslt-native', '', d)}"

-
-# vala-native contains a native version of vapigen, which we use 
instead of the target one

-DEPENDS:append:class-target = " vala-native"
-BBCLASSEXTEND = "native"
-LICENSE = "LGPL-2.1-only"
-LIC_FILES_CHKSUM = 
"file://COPYING;md5=fbc093901857fcd118f065f900982c24" 


-
-SHRT_VER = "${@d.getVar 
('PV').split('.')[0]}.${@d.getVar 
('PV').split('.')[1]}"

-
-SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz 
"

-inherit autotools pkgconfig upstream-version-is-even
-
-FILES:${PN} += "${datadir}/${BPN}-${SHRT_VER}/vapi 
${libdir}/${BPN}-${SHRT_VER}/"

-FILES:${PN}-doc += "${datadir}/devhelp"
-
-# .gir files from gobject-introspection are installed to ${libdir} 
when multilib is enabled
-GIRDIR_OPT = "${@'--girdir=${STAGING_LIBDIR}/gir-1.0' if 
d.getVar('MULTILIBS') else ''}"

-
-do_configure:prepend:class-target() {
-# Write out a vapigen wrapper that will be provided by 
pkg-config file installed in target sysroot

-# The wrapper will call a native vapigen
-cat > ${B}/vapigen-wrapper << EOF
-#!/bin/sh
-vapigen-${SHRT_VER} ${GIRDIR_OPT} "\$@"
-EOF
-chmod +x ${B}/vapigen-wrapper
-}
-
-EXTRA_OECONF += " --disable-valadoc"
-
-# Vapigen wrapper needs to be available system-wide, because it will 
be used

-# to build vapi files from all other packages with vala support
-do_install:append:class-target() {
-install -d ${D}${bindir_crossscripts}/
-install ${B}/vapigen-wrapper ${D}${bindir_crossscripts}/
-}
-
-# Put vapigen wrapper into target sysroot so that it can be used 
when building

-# vapi files.
-SYSROOT_DIRS += "${bindir_crossscripts}"
-
-inherit multilib_script
-MULTILIB_SCRIPTS = "${PN}:${bindir}/vala-gen-introspect-0.56"
-
-SYSROOT_PREPROCESS_FUNCS:append:class-target = " 
vapigen_sysroot_preprocess"

-vapigen_sysroot_preprocess() {
-# Tweak the vapigen name in the vapigen pkgconfig file, so 
that it picks

-# up our wrapper.
-sed -i \
-   -e 
"s|vapigen=.*|vapigen=${bindir_crossscripts}/vapigen-wrapper|" \
-   
${SYSROOT_DESTDIR}${libdir}/pkgconfig/vapigen-${SHRT_VER}.pc

-}
-
-SSTATE_SCAN_FILES += "vapigen-wrapper"
-
-PACKAGE_PREPROCESS_FUNCS += "vala_package_preprocess"
-
-vala_package_preprocess () {
-   rm -rf ${PKGD}${bindir_crossscripts}
-}
diff --git 
a/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch

new file mode 100644
index 00..e33b0bb36b
--- /dev/null
+++ 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch

@@ -0,0 +1,37 @@
+From 17349020fb95454d06f827fd555b05248f10a370 Mon Sep 17 00:00:00 
2001
+From: Rico Tzschichholz >

+Date: Thu, 7 Mar 2024 17:56:05 +0100
+Subject: [PATCH] gtk4: Preserve compatibility with < 4.14
+
+Don't prefer new accessor methods for Calendar.day/month/year
+
+Fixes 
+
+Upstream-Status: Backport 
[

[oe-core][PATCH] vala: fix for gtk4 prior to 4.14

2024-03-11 Thread Markus Volk
- add a backport patch to fix compatibility with older gtk4 versions
- merge .bb and .inc

Signed-off-by: Markus Volk 
---
 meta/recipes-devtools/vala/vala.inc   | 71 -
 ...tk4-Preserve-compatibility-with-4.14.patch | 37 +
 meta/recipes-devtools/vala/vala_0.56.15.bb| 76 ++-
 3 files changed, 112 insertions(+), 72 deletions(-)
 delete mode 100644 meta/recipes-devtools/vala/vala.inc
 create mode 100644 
meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch

diff --git a/meta/recipes-devtools/vala/vala.inc 
b/meta/recipes-devtools/vala/vala.inc
deleted file mode 100644
index 0177e86240..00
--- a/meta/recipes-devtools/vala/vala.inc
+++ /dev/null
@@ -1,71 +0,0 @@
-SUMMARY = "C#-like programming language for easing GObject programming"
-HOMEPAGE = "http://vala-project.org";
-DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject 
programming. \
-Vala compiles to plain C and has no runtime environment nor penalities 
whatsoever."
-SECTION = "devel"
-DEPENDS = "bison-native flex-native glib-2.0 gobject-introspection"
-
-# Appending libxslt-native to dependencies has an effect
-# of rebuilding the manual, which is very slow. Let's do this
-# only when api-documentation distro feature is enabled.
-DEPENDS:append:class-target = " ${@bb.utils.contains('DISTRO_FEATURES', 
'api-documentation', 'libxslt-native', '', d)}"
-
-# vala-native contains a native version of vapigen, which we use instead of 
the target one
-DEPENDS:append:class-target = " vala-native"
-BBCLASSEXTEND = "native"
-LICENSE = "LGPL-2.1-only"
-LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
-
-SHRT_VER = "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
-
-SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
-inherit autotools pkgconfig upstream-version-is-even
-
-FILES:${PN} += "${datadir}/${BPN}-${SHRT_VER}/vapi 
${libdir}/${BPN}-${SHRT_VER}/"
-FILES:${PN}-doc += "${datadir}/devhelp"
-
-# .gir files from gobject-introspection are installed to ${libdir} when 
multilib is enabled
-GIRDIR_OPT = "${@'--girdir=${STAGING_LIBDIR}/gir-1.0' if d.getVar('MULTILIBS') 
else ''}"
-
-do_configure:prepend:class-target() {
-# Write out a vapigen wrapper that will be provided by pkg-config file 
installed in target sysroot
-# The wrapper will call a native vapigen
-cat > ${B}/vapigen-wrapper << EOF
-#!/bin/sh
-vapigen-${SHRT_VER} ${GIRDIR_OPT} "\$@"
-EOF
-chmod +x ${B}/vapigen-wrapper
-}
-
-EXTRA_OECONF += " --disable-valadoc"
-
-# Vapigen wrapper needs to be available system-wide, because it will be used
-# to build vapi files from all other packages with vala support
-do_install:append:class-target() {
-install -d ${D}${bindir_crossscripts}/
-install ${B}/vapigen-wrapper ${D}${bindir_crossscripts}/
-}
-
-# Put vapigen wrapper into target sysroot so that it can be used when building
-# vapi files.
-SYSROOT_DIRS += "${bindir_crossscripts}"
-
-inherit multilib_script
-MULTILIB_SCRIPTS = "${PN}:${bindir}/vala-gen-introspect-0.56"
-
-SYSROOT_PREPROCESS_FUNCS:append:class-target = " vapigen_sysroot_preprocess"
-vapigen_sysroot_preprocess() {
-# Tweak the vapigen name in the vapigen pkgconfig file, so that it 
picks
-# up our wrapper.
-sed -i \
-   -e "s|vapigen=.*|vapigen=${bindir_crossscripts}/vapigen-wrapper|" \
-   ${SYSROOT_DESTDIR}${libdir}/pkgconfig/vapigen-${SHRT_VER}.pc
-}
-
-SSTATE_SCAN_FILES += "vapigen-wrapper"
-
-PACKAGE_PREPROCESS_FUNCS += "vala_package_preprocess"
-
-vala_package_preprocess () {
-   rm -rf ${PKGD}${bindir_crossscripts}
-}
diff --git 
a/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
new file mode 100644
index 00..e33b0bb36b
--- /dev/null
+++ 
b/meta/recipes-devtools/vala/vala/0001-gtk4-Preserve-compatibility-with-4.14.patch
@@ -0,0 +1,37 @@
+From 17349020fb95454d06f827fd555b05248f10a370 Mon Sep 17 00:00:00 2001
+From: Rico Tzschichholz 
+Date: Thu, 7 Mar 2024 17:56:05 +0100
+Subject: [PATCH] gtk4: Preserve compatibility with < 4.14
+
+Don't prefer new accessor methods for Calendar.day/month/year
+
+Fixes https://gitlab.gnome.org/GNOME/vala/issues/1531
+
+Upstream-Status: Backport 
[https://gitlab.gnome.org/GNOME/vala/-/commit/e0c4ea8c4a0bbf859b5341a7465b395892789d9e]
+---
+ vapi/gtk4.vapi | 3 +++
+ vapi/metadata/Gtk-4.0.metadata | 5 +
+ 2 files changed, 8 insertions(+)
+
+diff --git a/vapi/gtk4.vapi b/vapi/gtk4.vapi
+index 49f8b2078..51ecea27d 100644
+--- a/vapi/gtk4.vapi
 b/vapi/gtk4.vapi
+@@ -7350,11 +7350,14 @@ namespace Gtk {
+   [Version (since = "4.14")]
+   public void set_year (int year);
+   public void unmark_day (uint day);
++  [NoAccessorMethod]
+   public int