Re: [OE-core] Yocto reproducibilty issue :: rust-llvm binary differences

2023-02-21 Thread Sundeep KOKKONDA
Additional object files link (if needed) -> https://we.tl/t-RvgWukdcFB

poky/build-llvm-A/tmp/work/x86_64-linux/rust-native/ -> rust-native-A-obj.tar
poky/build-llvm-B/tmp/work/x86_64-linux/rust-native/ -> rust-native-B-obj.tar
poky/build-llvm-A/tmp/work/x86_64-linux/rust-llvm-native/ -> 
rust-llvm-native-A-obj.tar
poky/build-llvm-B/tmp/work/x86_64-linux/rust-llvm-native/ -> 
rust-llvm-native-B-obj.tar

> 
> $ diff -ur rust-llvm-native-A-obj rust-llvm-native-B-obj
> Binary files rust-llvm-native-A-obj/llvm-config.cpp.o and
> rust-llvm-native-B-obj/llvm-config.cpp.o differ
> Binary files rust-llvm-native-A-obj/python.o and
> rust-llvm-native-B-obj/python.o differ
> 
> $ diff -ur rust-native-A-obj rust-native-B-obj
> Binary files rust-native-A-obj/1mg8n9voykv9ib2d.o and
> rust-native-B-obj/1mg8n9voykv9ib2d.o differ
> Binary files rust-native-A-obj/538dmycheh7dlbck.o and
> rust-native-B-obj/538dmycheh7dlbck.o differ
> Binary files rust-native-A-obj/python.o and rust-native-B-obj/python.o
> differ
>

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



Re: [OE-core][kirkstone][PATCH 1/1] apr-util: fix for CVE-2022-25147

2023-02-21 Thread Narpat Mali
Sure, Tim.

I think there is no need to send the patch again to upgrade apr-util to 1.6.3 
since, Steve Sakoman has already sent review request for some set of patches 
for kirkstone and these also include the patch for apr-util: update 1.6.1 -> 
1.6.3 version. These patches are currently available at “stable/kirkstone-nut” 
branch.

http://cgit.openembedded.org/openembedded-core-contrib/commit/?h=stable/kirkstone-nut=e24b38a14b3520648ec418783fb74fcf61df7ff2

Please let me know if my above understanding is correct or not.

Best Regards,
Narpat


From: Tim Orling
Sent: 22 February 2023 07:37
To: Mali, Narpat
Cc: Polampalli, Archana; G Pillai, 
Hari; 
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][kirkstone][PATCH 1/1] apr-util: fix for CVE-2022-25147

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


On Tue, Feb 21, 2023 at 5:20 AM Narpat Mali 
mailto:narpat.m...@windriver.com>> wrote:
Integer Overflow or Wraparound vulnerability in apr_base64 functions
of Apache Portable Runtime Utility (APR-util) allows an attacker to
write beyond bounds of a buffer. This issue affects Apache Portable
Runtime Utility (APR-util) 1.6.1 and prior versions.

Reference:
https://nvd.nist.gov/vuln/detail/CVE-2022-25147

It might make more sense to upgrade to 1.6.3, as it appears to include some 
additional fixes and no new features.

https://downloads.apache.org/apr/CHANGES-APR-UTIL-1.6


Signed-off-by: Narpat Mali 
mailto:narpat.m...@windriver.com>>
---
 .../apr/apr-util/CVE-2022-25147.patch | 180 ++
 
meta/recipes-support/apr/apr-util_1.6.1.bb
|   3 +-
 2 files changed, 182 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-support/apr/apr-util/CVE-2022-25147.patch

diff --git a/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch 
b/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
new file mode 100644
index 00..e85785aca0
--- /dev/null
+++ b/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
@@ -0,0 +1,180 @@
+From 3f5257075c7eb601aed6333e9bb5d9eb0e11254b Mon Sep 17 00:00:00 2001
+From: Yann Ylavic mailto:yla...@apache.org>>
+Date: Thu, 20 Oct 2022 09:38:34 +
+Subject: [PATCH] apr_base64: Make sure encoding/decoding lengths fit in an int
+ >= 0.
+
+The (old) API of apr_base64 functions has always used int for representing
+lengths and it does not return errors. Make sure to abort() if the provided
+data don't fit.
+
+* encoding/apr_base64.c():
+  #define APR_BASE64_ENCODE_MAX and APR_BASE64_DECODE_MAX as the hard length
+  limits for encoding and decoding respectively.
+
+* encoding/apr_base64.c(apr_base64_encode_len, apr_base64_encode,
+apr_base64_encode_binary, apr_pbase64_encode):
+  abort() if the given length is above APR_BASE64_ENCODE_MAX.
+
+* encoding/apr_base64.c(apr_base64_decode_len, apr_base64_decode,
+apr_base64_decode_binary, apr_pbase64_decode):
+  abort() if the given plain buffer length is above APR_BASE64_DECODE_MAX.
+
+
+apr_base64: Follow up to r1902206: Cap to APR_BASE64_ENCODE_MAX in 
apr_pbase64_encode().
+
+
+Merges r1902206[, r1904666] from trunk.
+Merges r1904727 from 1.7.x.
+
+
+git-svn-id: 
https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x@1904728
 13f79535-47bb-0310-9956-ffa450edef68
+
+CVE: CVE-2022-25147
+
+Upstream-Status: Backport 
[https://github.com/apache/apr-util/commit/3f5257075c7eb601aed6333e9bb5d9eb0e11254b]
+
+Signed-off-by: Narpat Mali 
mailto:narpat.m...@windriver.com>>
+---
+ encoding/apr_base64.c | 41 +
+ 1 file changed, 25 insertions(+), 16 deletions(-)
+
+diff --git a/encoding/apr_base64.c b/encoding/apr_base64.c
+index e9b75e3d..ac9f2816 100644
+--- a/encoding/apr_base64.c
 

Re: [OE-core] Yocto reproducibilty issue :: rust-llvm binary differences

2023-02-21 Thread Sundeep KOKKONDA
Hello Alex,

files are here... https://we.tl/t-ijJJZnBvKh

Thanks,
Sundeep K.

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



[OE-core] [PATCH v2] gdb: Upgrade to 13.1

2023-02-21 Thread Khem Raj
Pass -Wno-enum-constexpr-conversion with clang

GDB 13.1 includes the following changes and enhancements:

* Support for the following new targets has been added in both
  GDB and GDBserver:

  ** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*

  ** GNU/Linux/CSKY (gdbserver) csky*-*linux*

* The Windows native target now supports target async.

* FreeBSD:

  ** Arm and AArch64: Support for Thread Local Storage (TLS) variables

  ** Hardware watchpoint support on AArch64 FreeBSD

* Floating-point support has now been added on LoongArch GNU/Linux.

* New commands:

 ** set print nibbles [on|off]
show print nibbles

This controls whether the 'print/t' command will display binary values
in groups of four bits, known as "nibbles".  The default is 'off'.

 ** Various styling-related commands. See the gdb/NEWS file for more
details (see link at the bottom).

 ** Various maintenance commands.  These are normally aimed at GDB
experts or developers. See the gdb/NEWS file for more details
(see link at the bottom).

* Python API improvements:

 ** New Python API for instruction disassembly.
The new attribute 'locations' of gdb.Breakpoint returns a list of
gdb.BreakpointLocation objects specifying the locations where the
breakpoint is inserted into the debuggee.

 ** New Python type gdb.BreakpointLocation.

 ** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
that formats ADDRESS as 'address '

 ** New function gdb.current_language that returns the name of the
current language.  Unlike gdb.parameter('language'), this will
never return 'auto'.

 ** New function gdb.print_options that returns a dictionary of the
prevailing print options, in the form accepted by gdb.Value.format_string.

 ** New method gdb.Frame.language that returns the name of the
frame's language.

 ** gdb.Value.format_string now uses the format provided by 'print',
if it is called during a 'print' or other similar operation.

 ** gdb.Value.format_string now accepts the 'summary' keyword.  This
can be used to request a shorter representation of a value, the
way that 'set print frame-arguments scalars' does.

 ** The gdb.register_window_type method now restricts the set of
acceptable window names.  The first character of a window's name
must start with a character in the set [a-zA-Z], every subsequent
character of a window's name must be in the set [-_.a-zA-Z0-9].

* GDB/MI changes:

  ** MI version 1 is deprecated, and will be removed in GDB 14.

  ** The async record stating the stopped reason 'breakpoint-hit' now
 contains an optional field locno.

* Miscellaneous improvements:

  ** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.

  ** New convenience variable $_inferior_thread_count contains the number
 of live threads in the current inferior.

  ** New convenience variables $_hit_bpnum and $_hit_locno, set to
 the breakpoint number and the breakpoint location number of
 the breakpoint last hit.

  ** The "info breakpoints" now displays enabled breakpoint locations
 of disabled breakpoints as in the "y-" state.

  ** The format of 'disassemble /r' and 'record instruction-history /r'
 has changed to match the layout of GNU objdump when disassembling.

 A new format "/b" has been introduce to provide the old behavior
 of "/r".

  ** The TUI no longer styles the source and assembly code highlighted
 by the current position indicator by default. You can however
 re-enable styling using the new "set style tui-current-position"
 command.

  ** It is now possible to use the "document" command to document
 user-defined commands.

  ** Support for memory tag data for AArch64 MTE.

* Support Removal notices:

  ** DBX mode has been removed.

  ** Support for building against Python version 2 has been removed.
 It is now only possible to build GDB against Python 3.

  ** Support for the following commands has been removed:

 set debug aix-solib on|off
 show debug aix-solib
 set debug solib-frv on|off
 show debug solib-frv

 Use the "set/show debug solib" commands instead.

For a complete list and more details on each item, please see the gdb/NEWS
file, available at [1]:

[1] 
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-13.1-release

Signed-off-by: Khem Raj 
---
v2: Rebase on master

 meta/conf/distro/include/tcmode-default.inc   |  2 +-
 ...ian_12.1.bb => gdb-cross-canadian_13.1.bb} |  0
 .../{gdb-cross_12.1.bb => gdb-cross_13.1.bb}  |  0
 meta/recipes-devtools/gdb/gdb.inc | 19 -
 ...make-man-install-relative-to-DESTDIR.patch | 28 -
 ...x-nat-Define-_ABIO32-if-not-defined.patch} |  9 ++---
 ...-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch} | 11 ++---
 ...eadline.a-when-using-disable-static.patch} | 13 +++---
 ...s.h.patch => 0004-use-asm-sgidefs.h.patch} |  9 ++---
 ...atch => 

[OE-core] [PATCH] gdb: Upgrade to 13.1

2023-02-21 Thread Khem Raj
GDB 13.1 includes the following changes and enhancements:

* Support for the following new targets has been added in both
  GDB and GDBserver:

  ** GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*

  ** GNU/Linux/CSKY (gdbserver) csky*-*linux*

* The Windows native target now supports target async.

* FreeBSD:

  ** Arm and AArch64: Support for Thread Local Storage (TLS) variables

  ** Hardware watchpoint support on AArch64 FreeBSD

* Floating-point support has now been added on LoongArch GNU/Linux.

* New commands:

 ** set print nibbles [on|off]
show print nibbles

This controls whether the 'print/t' command will display binary values
in groups of four bits, known as "nibbles".  The default is 'off'.

 ** Various styling-related commands. See the gdb/NEWS file for more
details (see link at the bottom).

 ** Various maintenance commands.  These are normally aimed at GDB
experts or developers. See the gdb/NEWS file for more details
(see link at the bottom).

* Python API improvements:

 ** New Python API for instruction disassembly.
The new attribute 'locations' of gdb.Breakpoint returns a list of
gdb.BreakpointLocation objects specifying the locations where the
breakpoint is inserted into the debuggee.

 ** New Python type gdb.BreakpointLocation.

 ** New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE)
that formats ADDRESS as 'address '

 ** New function gdb.current_language that returns the name of the
current language.  Unlike gdb.parameter('language'), this will
never return 'auto'.

 ** New function gdb.print_options that returns a dictionary of the
prevailing print options, in the form accepted by gdb.Value.format_string.

 ** New method gdb.Frame.language that returns the name of the
frame's language.

 ** gdb.Value.format_string now uses the format provided by 'print',
if it is called during a 'print' or other similar operation.

 ** gdb.Value.format_string now accepts the 'summary' keyword.  This
can be used to request a shorter representation of a value, the
way that 'set print frame-arguments scalars' does.

 ** The gdb.register_window_type method now restricts the set of
acceptable window names.  The first character of a window's name
must start with a character in the set [a-zA-Z], every subsequent
character of a window's name must be in the set [-_.a-zA-Z0-9].

* GDB/MI changes:

  ** MI version 1 is deprecated, and will be removed in GDB 14.

  ** The async record stating the stopped reason 'breakpoint-hit' now
 contains an optional field locno.

* Miscellaneous improvements:

  ** gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.

  ** New convenience variable $_inferior_thread_count contains the number
 of live threads in the current inferior.

  ** New convenience variables $_hit_bpnum and $_hit_locno, set to
 the breakpoint number and the breakpoint location number of
 the breakpoint last hit.

  ** The "info breakpoints" now displays enabled breakpoint locations
 of disabled breakpoints as in the "y-" state.

  ** The format of 'disassemble /r' and 'record instruction-history /r'
 has changed to match the layout of GNU objdump when disassembling.

 A new format "/b" has been introduce to provide the old behavior
 of "/r".

  ** The TUI no longer styles the source and assembly code highlighted
 by the current position indicator by default. You can however
 re-enable styling using the new "set style tui-current-position"
 command.

  ** It is now possible to use the "document" command to document
 user-defined commands.

  ** Support for memory tag data for AArch64 MTE.

* Support Removal notices:

  ** DBX mode has been removed.

  ** Support for building against Python version 2 has been removed.
 It is now only possible to build GDB against Python 3.

  ** Support for the following commands has been removed:

 set debug aix-solib on|off
 show debug aix-solib
 set debug solib-frv on|off
 show debug solib-frv

 Use the "set/show debug solib" commands instead.

For a complete list and more details on each item, please see the gdb/NEWS
file, available at [1]:

[1] 
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-13.1-release

Signed-off-by: Khem Raj 
---
 meta/conf/distro/include/tcmode-default.inc   |  2 +-
 ...ian_12.1.bb => gdb-cross-canadian_13.1.bb} |  0
 .../{gdb-cross_12.1.bb => gdb-cross_13.1.bb}  |  0
 meta/recipes-devtools/gdb/gdb.inc | 19 -
 ...make-man-install-relative-to-DESTDIR.patch | 28 -
 ...x-nat-Define-_ABIO32-if-not-defined.patch} |  9 ++---
 ...-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch} | 11 ++---
 ...eadline.a-when-using-disable-static.patch} | 13 +++---
 ...s.h.patch => 0004-use-asm-sgidefs.h.patch} |  9 ++---
 ...atch => 0005-Change-order-of-CFLAGS.patch} |  9 ++---
 

Re: [OE-core] [PATCH 08/11] build-appliance-image: use a real /tmp

2023-02-21 Thread Trevor Woerner
On Tue 2023-02-21 @ 03:44:42 PM, Trevor Woerner via lists.openembedded.org 
wrote:
> Make /tmp a real directory in the root filesystem and not a link to an
> in-memory tmpfs. Otherwise bitbake will run out of inodes on /tmp very quickly
> and stop any build.
> 
> Signed-off-by: Trevor Woerner 
> ---
>  meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 ++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
> b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> index 3a84de0a2b43..1f7b96a9fcf4 100644
> --- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> +++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> @@ -113,6 +113,12 @@ fakeroot do_tweak_image () {
>   # add a /lib64 symlink
>   # this is needed for building rust-native on a 64-bit build appliance
>   ln -rs ${IMAGE_ROOTFS}/lib ${IMAGE_ROOTFS}/lib64
> +
> + # make /tmp a real directory and not a link to an in-memory tmpfs
> + # otherwise /tmp will run out of inodes very quickly when bitbaking
> + sed -i -e 's#l root root 1777 /tmp /var/tmp#d root root 1777 /tmp 
> none#' ${IMAGE_ROOTFS}/etc/default/volatiles/00_core
> + mkdir -p ${IMAGE_ROOTFS}/tmp
> + chmod 1777 ${IMAGE_ROOTFS}/tmp
>  }

Richard, this feels rather "hacky" to me. I can't help wonder if it would be
better to implement a VOLATILE_TMP_DIR mechanism (along the same lines as
VOLATILE_LOG_DIR)?

https://docs.yoctoproject.org/dev/ref-manual/variables.html?highlight=volatile_log_dir#term-VOLATILE_LOG_DIR
https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/initscripts/initscripts_1.0.bb#n107

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177556): 
https://lists.openembedded.org/g/openembedded-core/message/177556
Mute This Topic: https://lists.openembedded.org/mt/97151865/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 09/11] build-appliance-image: QB_MEM: allow user config

2023-02-21 Thread Khem Raj
On Tue, Feb 21, 2023 at 12:45 PM Trevor Woerner  wrote:
>
> Allow the user to specify a QB_MEM value of their choosing, otherwise set it
> to a default value.
>
> Signed-off-by: Trevor Woerner 
> ---
>  meta/recipes-core/images/build-appliance-image_15.0.0.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
> b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> index 1f7b96a9fcf4..aa1e87763d57 100644
> --- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> +++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> @@ -11,7 +11,7 @@ IMAGE_INSTALL = "packagegroup-core-boot 
> packagegroup-core-ssh-openssh packagegro
>
>  IMAGE_FEATURES += "x11-base package-management splash"
>
> -QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m 512", "-m 
> 256", d)}'
> +QB_MEM ?= '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m 512", "-m 
> 256", d)}'
>

it would be good to see if we can say something like minimum memory
needed so it should be a fallback
if user sets higher value then it should use that. So for that matter
it looks its fine unless someone sets
QB_MEM < minmem then it will get some trouble.

>  # Ensure there's enough space to do a core-image-sato build, with rm_work 
> enabled
>  IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
> --
> 2.36.0.rc2.17.g4027e30c53
>
>
> 
>

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



Re: [OE-core][kirkstone][PATCH 1/1] apr-util: fix for CVE-2022-25147

2023-02-21 Thread Tim Orling
On Tue, Feb 21, 2023 at 5:20 AM Narpat Mali 
wrote:

> Integer Overflow or Wraparound vulnerability in apr_base64 functions
> of Apache Portable Runtime Utility (APR-util) allows an attacker to
> write beyond bounds of a buffer. This issue affects Apache Portable
> Runtime Utility (APR-util) 1.6.1 and prior versions.
>
> Reference:
> https://nvd.nist.gov/vuln/detail/CVE-2022-25147
>

It might make more sense to upgrade to 1.6.3, as it appears to include some
additional fixes and no new features.

https://downloads.apache.org/apr/CHANGES-APR-UTIL-1.6


> Signed-off-by: Narpat Mali 
> ---
>  .../apr/apr-util/CVE-2022-25147.patch | 180 ++
>  meta/recipes-support/apr/apr-util_1.6.1.bb|   3 +-
>  2 files changed, 182 insertions(+), 1 deletion(-)
>  create mode 100644 meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
>
> diff --git a/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
> b/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
> new file mode 100644
> index 00..e85785aca0
> --- /dev/null
> +++ b/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
> @@ -0,0 +1,180 @@
> +From 3f5257075c7eb601aed6333e9bb5d9eb0e11254b Mon Sep 17 00:00:00 2001
> +From: Yann Ylavic 
> +Date: Thu, 20 Oct 2022 09:38:34 +
> +Subject: [PATCH] apr_base64: Make sure encoding/decoding lengths fit in
> an int
> + >= 0.
> +
> +The (old) API of apr_base64 functions has always used int for representing
> +lengths and it does not return errors. Make sure to abort() if the
> provided
> +data don't fit.
> +
> +* encoding/apr_base64.c():
> +  #define APR_BASE64_ENCODE_MAX and APR_BASE64_DECODE_MAX as the hard
> length
> +  limits for encoding and decoding respectively.
> +
> +* encoding/apr_base64.c(apr_base64_encode_len, apr_base64_encode,
> +apr_base64_encode_binary, apr_pbase64_encode):
> +  abort() if the given length is above APR_BASE64_ENCODE_MAX.
> +
> +* encoding/apr_base64.c(apr_base64_decode_len, apr_base64_decode,
> +apr_base64_decode_binary, apr_pbase64_decode):
> +  abort() if the given plain buffer length is above APR_BASE64_DECODE_MAX.
> +
> +
> +apr_base64: Follow up to r1902206: Cap to APR_BASE64_ENCODE_MAX in
> apr_pbase64_encode().
> +
> +
> +Merges r1902206[, r1904666] from trunk.
> +Merges r1904727 from 1.7.x.
> +
> +
> +git-svn-id:
> https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x@1904728
> 13f79535-47bb-0310-9956-ffa450edef68
> +
> +CVE: CVE-2022-25147
> +
> +Upstream-Status: Backport [
> https://github.com/apache/apr-util/commit/3f5257075c7eb601aed6333e9bb5d9eb0e11254b
> ]
> +
> +Signed-off-by: Narpat Mali 
> +---
> + encoding/apr_base64.c | 41 +
> + 1 file changed, 25 insertions(+), 16 deletions(-)
> +
> +diff --git a/encoding/apr_base64.c b/encoding/apr_base64.c
> +index e9b75e3d..ac9f2816 100644
> +--- a/encoding/apr_base64.c
>  b/encoding/apr_base64.c
> +@@ -20,11 +20,20 @@
> +  * ugly 'len' functions, which is quite a nasty cost.
> +  */
> +
> ++#undef NDEBUG /* always abort() on assert()ion failure */
> ++#include 
> ++
> + #include "apr_base64.h"
> + #if APR_CHARSET_EBCDIC
> + #include "apr_xlate.h"
> + #endif/* APR_CHARSET_EBCDIC */
> +
> ++/* Above APR_BASE64_ENCODE_MAX length the encoding can't fit in an int
> >= 0 */
> ++#define APR_BASE64_ENCODE_MAX 1610612733
> ++
> ++/* Above APR_BASE64_DECODE_MAX length the decoding can't fit in an int
> >= 0 */
> ++#define APR_BASE64_DECODE_MAX 2863311524u
> ++
> + /* ck but it's fast and const should make it shared text page. */
> + static const unsigned char pr2six[256] =
> + {
> +@@ -109,24 +118,22 @@ APU_DECLARE(apr_status_t)
> apr_base64init_ebcdic(apr_xlate_t *to_ascii,
> +
> + APU_DECLARE(int) apr_base64_decode_len(const char *bufcoded)
> + {
> +-int nbytesdecoded;
> + register const unsigned char *bufin;
> + register apr_size_t nprbytes;
> +
> + bufin = (const unsigned char *) bufcoded;
> + while (pr2six[*(bufin++)] <= 63);
> +-
> + nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> +-nbytesdecoded = (((int)nprbytes + 3) / 4) * 3;
> ++assert(nprbytes <= APR_BASE64_DECODE_MAX);
> +
> +-return nbytesdecoded + 1;
> ++return (int)(((nprbytes + 3u) / 4u) * 3u + 1u);
> + }
> +
> + APU_DECLARE(int) apr_base64_decode(char *bufplain, const char *bufcoded)
> + {
> + #if APR_CHARSET_EBCDIC
> + apr_size_t inbytes_left, outbytes_left;
> +-#endif/* APR_CHARSET_EBCDIC */
> ++#endif /* APR_CHARSET_EBCDIC */
> + int len;
> +
> + len = apr_base64_decode_binary((unsigned char *) bufplain, bufcoded);
> +@@ -143,7 +150,7 @@ APU_DECLARE(int) apr_base64_decode(char *bufplain,
> const char *bufcoded)
> +  * the conversion of the output to ebcdic is left out.
> +  */
> + APU_DECLARE(int) apr_base64_decode_binary(unsigned char *bufplain,
> +- const char *bufcoded)
> 

Re: [OE-core] [PATCH] gdb: Upgrade to 12.1

2023-02-21 Thread Khem Raj
On Tue, Feb 21, 2023 at 5:27 PM Randy MacLeod 
wrote:

> On 2022-05-12 15:28, Khem Raj wrote:
>
> Release Announcement [1] and Notes [2]
>
> [1] https://lists.gnu.org/archive/html/info-gnu/2022-05/msg0.html
> [2] 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-12.1-release
>
> I just noticed that gdb-13.1 was released 2 days ago (Feb 19, 2023) .
>
> It seems like a good candidate to be included in the 4.2 release.
>
> $ git diff gdb-12-branch  gdb-13-branch gdb | diffstat | tail -1
>  6222 files changed, 142614 insertions(+), 63875 deletions(-)
>
> and  notes linked below.
>
> Khem,
>
> Are you working on that or should someone else start on it?
>

I have branch for 13.x already so will send patches tonight

../Randy
>
>
> https://www.sourceware.org/gdb/download/ANNOUNCEMENT
>
> https://www.sourceware.org/gdb/
>
>
> Signed-off-by: Khem Raj  
> ---
>  meta/conf/distro/include/tcmode-default.inc|  2 +-
>  ...canadian_11.2.bb => gdb-cross-canadian_12.1.bb} |  0
>  .../gdb/{gdb-cross_11.2.bb => gdb-cross_12.1.bb}   |  0
>  meta/recipes-devtools/gdb/gdb.inc  | 14 +++---
>  ...0001-make-man-install-relative-to-DESTDIR.patch | 10 +-
>  ...s-linux-nat-Define-_ABIO32-if-not-defined.patch |  8 
>  ...Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 11 +--
>  ...-libreadline.a-when-using-disable-static.patch} | 14 +++---
>  ...gidefs.h.patch => 0005-use-asm-sgidefs.h.patch} |  8 
>  ...AGS.patch => 0006-Change-order-of-CFLAGS.patch} | 10 +-
>  ...> 0007-resolve-restrict-keyword-conflict.patch} |  6 +++---
>  ...tch => 0008-Fix-invalid-sigprocmask-call.patch} |  8 
>  patch => 0009-gdbserver-ctrl-c-handling.patch} | 10 +-
>  .../gdb/{gdb_11.2.bb => gdb_12.1.bb}   |  0
>  14 files changed, 50 insertions(+), 51 deletions(-)
>  rename meta/recipes-devtools/gdb/{gdb-cross-canadian_11.2.bb => 
> gdb-cross-canadian_12.1.bb} (100%)
>  rename meta/recipes-devtools/gdb/{gdb-cross_11.2.bb => gdb-cross_12.1.bb} 
> (100%)
>  rename 
> meta/recipes-devtools/gdb/gdb/{0005-Dont-disable-libreadline.a-when-using-disable-static.patch
>  => 0004-Dont-disable-libreadline.a-when-using-disable-static.patch} (80%)
>  rename meta/recipes-devtools/gdb/gdb/{0006-use-asm-sgidefs.h.patch => 
> 0005-use-asm-sgidefs.h.patch} (84%)
>  rename meta/recipes-devtools/gdb/gdb/{0007-Change-order-of-CFLAGS.patch => 
> 0006-Change-order-of-CFLAGS.patch} (80%)
>  rename 
> meta/recipes-devtools/gdb/gdb/{0008-resolve-restrict-keyword-conflict.patch 
> => 0007-resolve-restrict-keyword-conflict.patch} (93%)
>  rename 
> meta/recipes-devtools/gdb/gdb/{0009-Fix-invalid-sigprocmask-call.patch => 
> 0008-Fix-invalid-sigprocmask-call.patch} (90%)
>  rename meta/recipes-devtools/gdb/gdb/{0010-gdbserver-ctrl-c-handling.patch 
> => 0009-gdbserver-ctrl-c-handling.patch} (82%)
>  rename meta/recipes-devtools/gdb/{gdb_11.2.bb => gdb_12.1.bb} (100%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc 
> b/meta/conf/distro/include/tcmode-default.inc
> index 9660f2804a7..1179ba172ff 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -19,7 +19,7 @@ PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
>  GCCVERSION ?= "12.%"
>  SDKGCCVERSION ?= "${GCCVERSION}"
>  BINUVERSION ?= "2.38%"
> -GDBVERSION ?= "11.%"
> +GDBVERSION ?= "12.%"
>  GLIBCVERSION ?= "2.35"
>  LINUXLIBCVERSION ?= "5.16%"
>  QEMUVERSION ?= "7.0%"
> diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian_11.2.bb 
> b/meta/recipes-devtools/gdb/gdb-cross-canadian_12.1.bb
> similarity index 100%
> rename from meta/recipes-devtools/gdb/gdb-cross-canadian_11.2.bb
> rename to meta/recipes-devtools/gdb/gdb-cross-canadian_12.1.bb
> diff --git a/meta/recipes-devtools/gdb/gdb-cross_11.2.bb 
> b/meta/recipes-devtools/gdb/gdb-cross_12.1.bb
> similarity index 100%
> rename from meta/recipes-devtools/gdb/gdb-cross_11.2.bb
> rename to meta/recipes-devtools/gdb/gdb-cross_12.1.bb
> diff --git a/meta/recipes-devtools/gdb/gdb.inc 
> b/meta/recipes-devtools/gdb/gdb.inc
> index 649ee287276..3b569fd40e7 100644
> --- a/meta/recipes-devtools/gdb/gdb.inc
> +++ b/meta/recipes-devtools/gdb/gdb.inc
> @@ -8,11 +8,11 @@ SRC_URI = "${GNU_MIRROR}/gdb/gdb-${PV}.tar.xz \
> file://0001-make-man-install-relative-to-DESTDIR.patch \
> file://0002-mips-linux-nat-Define-_ABIO32-if-not-defined.patch \
> 
> file://0003-ppc-ptrace-Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch \
> -   
> file://0005-Dont-disable-libreadline.a-when-using-disable-static.patch \
> -   file://0006-use-asm-sgidefs.h.patch \
> -   file://0007-Change-order-of-CFLAGS.patch \
> -   file://0008-resolve-restrict-keyword-conflict.patch \
> -   file://0009-Fix-invalid-sigprocmask-call.patch \
> -   file://0010-gdbserver-ctrl-c-handling.patch \
> +   
> 

Re: [OE-core] [PATCH] gdb: Upgrade to 12.1

2023-02-21 Thread Randy MacLeod

On 2022-05-12 15:28, Khem Raj wrote:

Release Announcement [1] and Notes [2]

[1]https://lists.gnu.org/archive/html/info-gnu/2022-05/msg0.html
[2]https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-12.1-release


I just noticed that gdb-13.1 was released 2 days ago (Feb 19, 2023) .

It seems like a good candidate to be included in the 4.2 release.

$ git diff gdb-12-branch  gdb-13-branch gdb | diffstat | tail -1
 6222 files changed, 142614 insertions(+), 63875 deletions(-)

and  notes linked below.

Khem,

Are you working on that or should someone else start on it?

../Randy


https://www.sourceware.org/gdb/download/ANNOUNCEMENT

https://www.sourceware.org/gdb/



Signed-off-by: Khem Raj
---
  meta/conf/distro/include/tcmode-default.inc|  2 +-
  ...canadian_11.2.bb => gdb-cross-canadian_12.1.bb} |  0
  .../gdb/{gdb-cross_11.2.bb => gdb-cross_12.1.bb}   |  0
  meta/recipes-devtools/gdb/gdb.inc  | 14 +++---
  ...0001-make-man-install-relative-to-DESTDIR.patch | 10 +-
  ...s-linux-nat-Define-_ABIO32-if-not-defined.patch |  8 
  ...Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 11 +--
  ...-libreadline.a-when-using-disable-static.patch} | 14 +++---
  ...gidefs.h.patch => 0005-use-asm-sgidefs.h.patch} |  8 
  ...AGS.patch => 0006-Change-order-of-CFLAGS.patch} | 10 +-
  ...> 0007-resolve-restrict-keyword-conflict.patch} |  6 +++---
  ...tch => 0008-Fix-invalid-sigprocmask-call.patch} |  8 
  patch => 0009-gdbserver-ctrl-c-handling.patch} | 10 +-
  .../gdb/{gdb_11.2.bb => gdb_12.1.bb}   |  0
  14 files changed, 50 insertions(+), 51 deletions(-)
  rename meta/recipes-devtools/gdb/{gdb-cross-canadian_11.2.bb => 
gdb-cross-canadian_12.1.bb} (100%)
  rename meta/recipes-devtools/gdb/{gdb-cross_11.2.bb => gdb-cross_12.1.bb} 
(100%)
  rename 
meta/recipes-devtools/gdb/gdb/{0005-Dont-disable-libreadline.a-when-using-disable-static.patch
 => 0004-Dont-disable-libreadline.a-when-using-disable-static.patch} (80%)
  rename meta/recipes-devtools/gdb/gdb/{0006-use-asm-sgidefs.h.patch => 
0005-use-asm-sgidefs.h.patch} (84%)
  rename meta/recipes-devtools/gdb/gdb/{0007-Change-order-of-CFLAGS.patch => 
0006-Change-order-of-CFLAGS.patch} (80%)
  rename 
meta/recipes-devtools/gdb/gdb/{0008-resolve-restrict-keyword-conflict.patch => 
0007-resolve-restrict-keyword-conflict.patch} (93%)
  rename meta/recipes-devtools/gdb/gdb/{0009-Fix-invalid-sigprocmask-call.patch 
=> 0008-Fix-invalid-sigprocmask-call.patch} (90%)
  rename meta/recipes-devtools/gdb/gdb/{0010-gdbserver-ctrl-c-handling.patch => 
0009-gdbserver-ctrl-c-handling.patch} (82%)
  rename meta/recipes-devtools/gdb/{gdb_11.2.bb => gdb_12.1.bb} (100%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 9660f2804a7..1179ba172ff 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -19,7 +19,7 @@ PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
  GCCVERSION ?= "12.%"
  SDKGCCVERSION ?= "${GCCVERSION}"
  BINUVERSION ?= "2.38%"
-GDBVERSION ?= "11.%"
+GDBVERSION ?= "12.%"
  GLIBCVERSION ?= "2.35"
  LINUXLIBCVERSION ?= "5.16%"
  QEMUVERSION ?= "7.0%"
diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian_11.2.bb 
b/meta/recipes-devtools/gdb/gdb-cross-canadian_12.1.bb
similarity index 100%
rename from meta/recipes-devtools/gdb/gdb-cross-canadian_11.2.bb
rename to meta/recipes-devtools/gdb/gdb-cross-canadian_12.1.bb
diff --git a/meta/recipes-devtools/gdb/gdb-cross_11.2.bb 
b/meta/recipes-devtools/gdb/gdb-cross_12.1.bb
similarity index 100%
rename from meta/recipes-devtools/gdb/gdb-cross_11.2.bb
rename to meta/recipes-devtools/gdb/gdb-cross_12.1.bb
diff --git a/meta/recipes-devtools/gdb/gdb.inc 
b/meta/recipes-devtools/gdb/gdb.inc
index 649ee287276..3b569fd40e7 100644
--- a/meta/recipes-devtools/gdb/gdb.inc
+++ b/meta/recipes-devtools/gdb/gdb.inc
@@ -8,11 +8,11 @@ SRC_URI = "${GNU_MIRROR}/gdb/gdb-${PV}.tar.xz \
 file://0001-make-man-install-relative-to-DESTDIR.patch  \
 file://0002-mips-linux-nat-Define-_ABIO32-if-not-defined.patch  \
 
file://0003-ppc-ptrace-Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch  \
-file://0005-Dont-disable-libreadline.a-when-using-disable-static.patch  \
-file://0006-use-asm-sgidefs.h.patch  \
-file://0007-Change-order-of-CFLAGS.patch  \
-file://0008-resolve-restrict-keyword-conflict.patch  \
-file://0009-Fix-invalid-sigprocmask-call.patch  \
-file://0010-gdbserver-ctrl-c-handling.patch  \
+file://0004-Dont-disable-libreadline.a-when-using-disable-static.patch  \
+file://0005-use-asm-sgidefs.h.patch  \
+file://0006-Change-order-of-CFLAGS.patch  \
+file://0007-resolve-restrict-keyword-conflict.patch  \
+file://0008-Fix-invalid-sigprocmask-call.patch  \
+file://0009-gdbserver-ctrl-c-handling.patch  \
 "
-SRC_URI[sha256sum] = 

Re: [OE-core] [PATCH 3/3] glibc: backport the fix for CVE-2023-25139

2023-02-21 Thread Randy MacLeod

On 2023-02-20 11:35, Alexander Kanavin via lists.openembedded.org wrote:

But then the cve should be marked as resolved?


Yash is new to this game.

Yash,

Please submit an update along the lines of:
https://git.openembedded.org/openembedded-core/commit/?id=ebb0220bf211ec1318a0a7f6a9ab80cf7775a848

and next time you bump glibc/gcc/... indicate that the CVE is fixed by 
setting CVE_CHECK_IGNORE.


../Randy



Alex

On Mon 20. Feb 2023 at 17.34, Ross Burton  wrote:

Ignore this, "glibc: stable 2.37 branch updates” incorporates it.

Ross

> On 20 Feb 2023, at 16:28, Ross Burton via lists.openembedded.org

 wrote:
>
> Signed-off-by: Ross Burton 
> ---
> ...r-grouping-in-printf-width-bug-30068.patch | 84
+++
> meta/recipes-core/glibc/glibc_2.37.bb     
   |  1 +
> 2 files changed, 85 insertions(+)
> create mode 100644

meta/recipes-core/glibc/glibc/0001-Account-for-grouping-in-printf-width-bug-30068.patch
>
> diff --git

a/meta/recipes-core/glibc/glibc/0001-Account-for-grouping-in-printf-width-bug-30068.patch

b/meta/recipes-core/glibc/glibc/0001-Account-for-grouping-in-printf-width-bug-30068.patch
> new file mode 100644
> index 000..9efd39a9eb4
> --- /dev/null
> +++

b/meta/recipes-core/glibc/glibc/0001-Account-for-grouping-in-printf-width-bug-30068.patch
> @@ -0,0 +1,84 @@
> +CVE: CVE-2023-25139
> +Upstream-Status: Backport
> +Signed-off-by: Ross Burton 
> +
> +From 07b9521fc6369d000216b96562ff7c0ed32a16c4 Mon Sep 17
00:00:00 2001
> +From: Carlos O'Donell 
> +Date: Thu, 19 Jan 2023 12:50:20 +0100
> +Subject: [PATCH] Account for grouping in printf width (bug 30068)
> +
> +This is a partial fix for mishandling of grouping when formatting
> +integers.  It properly computes the width in the presence of
grouping
> +characters when the width is larger than the number of significant
> +digits. The precision related issue is documented in bug 23432.
> +
> +Co-authored-by: Andreas Schwab 
> +(cherry picked from commit
c980549cc6a1c03c23cc2fe3e7b0fe626a0364b0)
> +---
> + stdio-common/Makefile               |  2 ++
> + stdio-common/tst-grouping3.c        | 54
+
> + stdio-common/vfprintf-process-arg.c | 22 +---
> + 3 files changed, 73 insertions(+), 5 deletions(-)
> + create mode 100644 stdio-common/tst-grouping3.c
> +
> +diff --git a/stdio-common/vfprintf-process-arg.c
b/stdio-common/vfprintf-process-arg.c
> +index 24c9125f9f..8c0fcbcf78 100644
> +--- a/stdio-common/vfprintf-process-arg.c
>  b/stdio-common/vfprintf-process-arg.c
> +@@ -186,11 +186,17 @@ LABEL (unsigned_number):      /* Unsigned
number of base BASE.  */
> +   bool octal_marker = (prec <= number_length && number.word != 0
> +                        && alt && base == 8);
> +
> +-  prec = MAX (0, prec - (workend - string));
> ++  /* At this point prec_inc is the additional bytes required
for the
> ++     specificed precision.  It is 0 if the precision would not
have
> ++     required additional bytes i.e. the number of input digits
is more
> ++     than the precision.  It is greater than zero if the
precision is
> ++     more than the number of digits without grouping
(precision only
> ++     considers digits).  */
> ++  unsigned int prec_inc = MAX (0, prec - (workend - string));
> +
> +   if (!left)
> +     {
> +-      width -= number_length + prec;
> ++      width -= number_length + prec_inc;
> +
> +       if (number.word != 0 && alt && (base == 16 || base == 2))
> +         /* Account for 0X, 0x, 0B or 0b hex or binary marker.  */
> +@@ -221,7 +227,7 @@ LABEL (unsigned_number):      /* Unsigned
number of base BASE.  */
> +           Xprintf_buffer_putc (buf, spec);
> +         }
> +
> +-      width += prec;
> ++      width += prec_inc;
> +       Xprintf_buffer_pad (buf, L_('0'), width);
> +
> +       if (octal_marker)
> +@@ -237,6 +243,8 @@ LABEL (unsigned_number):      /* Unsigned
number of base BASE.  */
> +     }
> +   else
> +     {
> ++      /* Perform left justification adjustments.  */
> ++
> +       if (is_negative)
> +         {
> +           Xprintf_buffer_putc (buf, L_('-'));
> +@@ -263,9 +271,13 @@ LABEL (unsigned_number):      /* Unsigned
number of base BASE.  */
> +       if (octal_marker)
> + --width;
> +
> +-      width -= workend - string + prec;
> ++      /* Adjust the width by subtracting the number of bytes
> ++         required to represent the number with grouping characters
> ++ (NUMBER_LENGTH) and any additional bytes required for
> ++ precision.  */
> ++      width 

[OE-core] [PATCH 11/11] build-appliance-image: check for xattr feature

2023-02-21 Thread Trevor Woerner
The xattr DISTRO_FEATURE is required otherwise a bitbake build will fail due
to a failure with the 'cp' utility:

Subprocess output:
cp: cannot preserve extended attributes, cp is built without xattr 
support

ERROR: Logfile of failure stored in: 
/home/builder/poky/build/tmp/work/qemux86_64-poky-linux/packagegroup-base/1.0-r83/temp/log.do_populate_lic.1001
ERROR: Task 
(/home/builder/poky/meta/recipes-core/packagegroups/packagegroup-base.bb:do_populate_lic)
 failed with exit code '1'

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index aa1e87763d57..2321d3a51a24 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -22,7 +22,9 @@ APPEND += "rootfstype=ext4 quiet"
 DEPENDS = "zip-native python3-pip-native"
 IMAGE_FSTYPES = "ext4 wic.vmdk wic.vhd wic.vhdx"
 
-inherit core-image setuptools3
+inherit core-image setuptools3 features_check
+
+REQUIRED_DISTRO_FEATURES += "xattr"
 
 SRCREV ?= "a5507f383cdab99806df131bf4aef191799c5153"
 SRC_URI = "git://git.yoctoproject.org/poky;branch=master \
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177549): 
https://lists.openembedded.org/g/openembedded-core/message/177549
Mute This Topic: https://lists.openembedded.org/mt/97118456/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 10/11] QB_SMP: allow user modification

2023-02-21 Thread Trevor Woerner
Allow a user to override the QM_SMP value giving them the opportunity to
select for themselves the number of CPUs to use in qemu.

Signed-off-by: Trevor Woerner 
---
 meta/conf/machine/include/riscv/qemuriscv.inc  | 2 +-
 meta/conf/machine/include/x86/qemuboot-x86.inc | 2 +-
 meta/conf/machine/qemuarm.conf | 2 +-
 meta/conf/machine/qemuarm64.conf   | 2 +-
 meta/conf/machine/qemuppc64.conf   | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/machine/include/riscv/qemuriscv.inc 
b/meta/conf/machine/include/riscv/qemuriscv.inc
index 1d32b4a58209..c977a266ca21 100644
--- a/meta/conf/machine/include/riscv/qemuriscv.inc
+++ b/meta/conf/machine/include/riscv/qemuriscv.inc
@@ -26,7 +26,7 @@ UBOOT_ENTRYPOINT:riscv32 = "0x8040"
 UBOOT_ENTRYPOINT:riscv64 = "0x8020"
 
 # qemuboot options
-QB_SMP = "-smp 4"
+QB_SMP ?= "-smp 4"
 QB_KERNEL_CMDLINE_APPEND = "earlycon=sbi"
 QB_MACHINE = "-machine virt"
 QB_DEFAULT_BIOS = "fw_jump.elf"
diff --git a/meta/conf/machine/include/x86/qemuboot-x86.inc 
b/meta/conf/machine/include/x86/qemuboot-x86.inc
index 3953679366d9..dd7e7c938413 100644
--- a/meta/conf/machine/include/x86/qemuboot-x86.inc
+++ b/meta/conf/machine/include/x86/qemuboot-x86.inc
@@ -1,6 +1,6 @@
 # For runqemu
 IMAGE_CLASSES += "qemuboot"
-QB_SMP = "-smp 4"
+QB_SMP ?= "-smp 4"
 QB_CPU:x86 = "-cpu IvyBridge -machine q35,i8042=off"
 QB_CPU_KVM:x86 = "-cpu IvyBridge -machine q35,i8042=off"
 
diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
index 1bd4e3e154fc..c5234231e2e5 100644
--- a/meta/conf/machine/qemuarm.conf
+++ b/meta/conf/machine/qemuarm.conf
@@ -16,7 +16,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 QB_SYSTEM_NAME = "qemu-system-arm"
 QB_MACHINE = "-machine virt,highmem=off"
 QB_CPU = "-cpu cortex-a15"
-QB_SMP = "-smp 4"
+QB_SMP ?= "-smp 4"
 # Standard Serial console
 QB_KERNEL_CMDLINE_APPEND = "vmalloc=256"
 # For graphics to work we need to define the VGA device as well as the 
necessary USB devices
diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf
index ffc51c803fa7..2f0f0e4f842f 100644
--- a/meta/conf/machine/qemuarm64.conf
+++ b/meta/conf/machine/qemuarm64.conf
@@ -16,7 +16,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 QB_SYSTEM_NAME = "qemu-system-aarch64"
 QB_MACHINE = "-machine virt"
 QB_CPU = "-cpu cortex-a57"
-QB_SMP = "-smp 4"
+QB_SMP ?= "-smp 4"
 QB_CPU_KVM = "-cpu host -machine gic-version=3"
 # For graphics to work we need to define the VGA device as well as the 
necessary USB devices
 QB_GRAPHICS = "-device virtio-gpu-pci"
diff --git a/meta/conf/machine/qemuppc64.conf b/meta/conf/machine/qemuppc64.conf
index 770933931324..2fbd26a6f997 100644
--- a/meta/conf/machine/qemuppc64.conf
+++ b/meta/conf/machine/qemuppc64.conf
@@ -13,7 +13,7 @@ SERIAL_CONSOLES ?= "115200;hvc0"
 QB_SYSTEM_NAME = "qemu-system-ppc64"
 QB_MACHINE = "-machine pseries"
 QB_CPU = "-cpu POWER9"
-QB_SMP = "-smp 2"
+QB_SMP ?= "-smp 2"
 
 QB_NFSROOTFS_EXTRA_OPT = "wsize=524288,rsize=524288"
 QB_KERNEL_CMDLINE_APPEND = "console=hvc0 nohugevmalloc"
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177548): 
https://lists.openembedded.org/g/openembedded-core/message/177548
Mute This Topic: https://lists.openembedded.org/mt/97118455/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 09/11] build-appliance-image: QB_MEM: allow user config

2023-02-21 Thread Trevor Woerner
Allow the user to specify a QB_MEM value of their choosing, otherwise set it
to a default value.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index 1f7b96a9fcf4..aa1e87763d57 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -11,7 +11,7 @@ IMAGE_INSTALL = "packagegroup-core-boot 
packagegroup-core-ssh-openssh packagegro
 
 IMAGE_FEATURES += "x11-base package-management splash"
 
-QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m 512", "-m 
256", d)}'
+QB_MEM ?= '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m 512", "-m 
256", d)}'
 
 # Ensure there's enough space to do a core-image-sato build, with rm_work 
enabled
 IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177547): 
https://lists.openembedded.org/g/openembedded-core/message/177547
Mute This Topic: https://lists.openembedded.org/mt/97118452/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 08/11] build-appliance-image: use a real /tmp

2023-02-21 Thread Trevor Woerner
Make /tmp a real directory in the root filesystem and not a link to an
in-memory tmpfs. Otherwise bitbake will run out of inodes on /tmp very quickly
and stop any build.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index 3a84de0a2b43..1f7b96a9fcf4 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -113,6 +113,12 @@ fakeroot do_tweak_image () {
# add a /lib64 symlink
# this is needed for building rust-native on a 64-bit build appliance
ln -rs ${IMAGE_ROOTFS}/lib ${IMAGE_ROOTFS}/lib64
+
+   # make /tmp a real directory and not a link to an in-memory tmpfs
+   # otherwise /tmp will run out of inodes very quickly when bitbaking
+   sed -i -e 's#l root root 1777 /tmp /var/tmp#d root root 1777 /tmp 
none#' ${IMAGE_ROOTFS}/etc/default/volatiles/00_core
+   mkdir -p ${IMAGE_ROOTFS}/tmp
+   chmod 1777 ${IMAGE_ROOTFS}/tmp
 }
 
 IMAGE_PREPROCESS_COMMAND += "do_populate_poky_src; do_tweak_image; "
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177546): 
https://lists.openembedded.org/g/openembedded-core/message/177546
Mute This Topic: https://lists.openembedded.org/mt/97118451/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 07/11] build-appliance-image: add /lib64 symlink

2023-02-21 Thread Trevor Woerner
Add a /lib64 -> /lib symlink in case the build appliance is 64-bit.

Building rust-native requires cargo to be run. The native cargo is linked to
look for /lib64/ld-linux-x86-64.so.2 and can't be run without it. The build
produces the following error, even though that file does exist:

FileNotFoundError: [Errno 2] No such file or directory: 
'/home/builder/poky/build/tmp/work/x86_64-linux/rust-native/1.66.1-r0/rust-snapshot/bin/cargo'

Trying to run this binary on its own gives:

qemux86-64:~/poky/build$ 
tmp/work/x86_64-linux/rust-native/1.66.1-r0/rust-snapshot/bin/cargo
-sh: 
tmp/work/x86_64-linux/rust-native/1.66.1-r0/rust-snapshot/bin/cargo: cannot 
execute: required file not found

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index ad5ea92b3eda..3a84de0a2b43 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -109,7 +109,13 @@ fakeroot do_populate_poky_src () {
chown -R builder:builder ${IMAGE_ROOTFS}/home/builder/.cache
 }
 
-IMAGE_PREPROCESS_COMMAND += "do_populate_poky_src; "
+fakeroot do_tweak_image () {
+   # add a /lib64 symlink
+   # this is needed for building rust-native on a 64-bit build appliance
+   ln -rs ${IMAGE_ROOTFS}/lib ${IMAGE_ROOTFS}/lib64
+}
+
+IMAGE_PREPROCESS_COMMAND += "do_populate_poky_src; do_tweak_image; "
 # For pip usage above
 do_image[network] = "1"
 
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177545): 
https://lists.openembedded.org/g/openembedded-core/message/177545
Mute This Topic: https://lists.openembedded.org/mt/97118450/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 06/11] build-appliance-image: fix HOMEPAGE

2023-02-21 Thread Trevor Woerner
Update the HOMEPAGE metadata.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index b000ea0c4d70..ad5ea92b3eda 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -1,6 +1,6 @@
 SUMMARY = "An image containing the build system itself"
 DESCRIPTION = "An image containing the build system that you can boot and run 
using any of qemu, VirtualBox, VMware Player or VMware Workstation."
-HOMEPAGE = "http://www.yoctoproject.org/documentation/build-appliance;
+HOMEPAGE = 
"https://docs.yoctoproject.org/overview-manual/yp-intro.html#archived-components;
 
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177544): 
https://lists.openembedded.org/g/openembedded-core/message/177544
Mute This Topic: https://lists.openembedded.org/mt/97118447/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 05/11] build-appliance-image kernel: linux-yocto: qemuall: add taskstats

2023-02-21 Thread Trevor Woerner
Add the taskstats configuration to any kernel built for qemuall for bitbake's
benefit:

WARNING: The Linux kernel on your build host was not configured to 
provide process I/O statistics. (CONFIG_TASK_IO_ACCOUNTING is not set)

Signed-off-by: Trevor Woerner 
---
 meta/recipes-kernel/linux/linux-yocto.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto.inc 
b/meta/recipes-kernel/linux/linux-yocto.inc
index 091003ed8299..93eef9e94684 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -31,7 +31,7 @@ DEPENDS:append:arc = " libgcc"
 KERNEL_CC:append:arc = " ${TOOLCHAIN_OPTIONS}"
 KERNEL_LD:append:arc = " ${TOOLCHAIN_OPTIONS}"
 
-KERNEL_FEATURES:append:qemuall=" features/debug/printk.scc"
+KERNEL_FEATURES:append:qemuall=" features/debug/printk.scc 
features/taskstats/taskstats.scc"
 
 KERNEL_FEATURES:append = " ${@bb.utils.contains('MACHINE_FEATURES', 'efi', 
'cfg/efi.scc', '', d)}"
 KERNEL_FEATURES:append = " ${@bb.utils.contains('MACHINE_FEATURES', 'numa', 
'features/numa/numa.scc', '', d)}"
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177543): 
https://lists.openembedded.org/g/openembedded-core/message/177543
Mute This Topic: https://lists.openembedded.org/mt/97118444/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 03/11] build-appliance-image: add support for qemu

2023-02-21 Thread Trevor Woerner
Add ext4 explicitly to the list of IMAGE_FSTYPES so the build appliance can be
run with runqemu.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index 064e7a1ed82f..e28096758b9b 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -1,5 +1,5 @@
 SUMMARY = "An image containing the build system itself"
-DESCRIPTION = "An image containing the build system that you can boot and run 
using either VirtualBox, VMware Player or VMware Workstation."
+DESCRIPTION = "An image containing the build system that you can boot and run 
using any of qemu, VirtualBox, VMware Player or VMware Workstation."
 HOMEPAGE = "http://www.yoctoproject.org/documentation/build-appliance;
 
 LICENSE = "MIT"
@@ -20,7 +20,7 @@ IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
 APPEND += "rootfstype=ext4 quiet"
 
 DEPENDS = "zip-native python3-pip-native"
-IMAGE_FSTYPES = "wic.vmdk wic.vhd wic.vhdx"
+IMAGE_FSTYPES = "ext4 wic.vmdk wic.vhd wic.vhdx"
 
 inherit core-image setuptools3
 
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177541): 
https://lists.openembedded.org/g/openembedded-core/message/177541
Mute This Topic: https://lists.openembedded.org/mt/97118441/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 04/11] build-appliance-image: set TERM

2023-02-21 Thread Trevor Woerner
Choose a nicer terminal for the build appliance so that build warnings and
errors show up in colour instead of:

$<50>Setscene tasks: 2844 of 2844
$<50>WARNING: mesa-2_22.3.3-r0 do_fetch: Failed to fetch URL 
https://mesa.freedesktop.org/archive/mesa-22.3.3.tar.xz, attempting MIRRORS if 
available
$<50>WARNING: glslang-native-1_1.3.236.0-r0 do_fetch: Failed to fetch 
URL git://github.com/KhronosGroup/glslang.git;protocol=https;branch=master, 
attempting MIRRORS if available

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index e28096758b9b..b000ea0c4d70 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -63,6 +63,7 @@ fakeroot do_populate_poky_src () {
 
echo "INHERIT += \"rm_work\"" >> 
${IMAGE_ROOTFS}/home/builder/poky/build/conf/auto.conf
echo "export LC_ALL=en_US.utf8" >> ${IMAGE_ROOTFS}/home/builder/.bashrc
+   echo "export TERM=xterm-color" >> ${IMAGE_ROOTFS}/home/builder/.bashrc
 
# Also save (for reference only) the actual SRCREV used to create this 
image
echo "export BA_SRCREV=${SRCREV}" >> 
${IMAGE_ROOTFS}/home/builder/.bashrc
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177542): 
https://lists.openembedded.org/g/openembedded-core/message/177542
Mute This Topic: https://lists.openembedded.org/mt/97118442/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 01/11] packagegroup-self-hosted: alphabetize

2023-02-21 Thread Trevor Woerner
Several of the lists of packages are alphabetized, but the alphabetization
was lost in a couple areas.

Signed-off-by: Trevor Woerner 
---
 .../packagegroups/packagegroup-self-hosted.bb  | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb 
b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
index a1b0ee288362..529d4c5c5c6b 100644
--- a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
@@ -127,7 +127,6 @@ RDEPENDS:packagegroup-self-hosted-extended = "\
 grep \
 groff \
 gzip \
-settings-daemon \
 libaio \
 libusb1 \
 libxml2 \
@@ -160,6 +159,7 @@ RDEPENDS:packagegroup-self-hosted-extended = "\
 readline \
 rpm \
 setserial \
+settings-daemon \
 socat \
 subversion \
 sudo \
@@ -173,22 +173,22 @@ RDEPENDS:packagegroup-self-hosted-extended = "\
 wget \
 which \
 xinetd \
+xz \
 zip \
 zlib \
-xz \
 "
 
 
 RDEPENDS:packagegroup-self-hosted-graphics = "\
+adwaita-icon-theme \
 builder \
+l3afpad \
 libgl \
 libgl-dev \
 libglu \
 libglu-dev \
 libx11-dev \
-adwaita-icon-theme \
-xdg-utils \
-l3afpad \
 pcmanfm \
 vte \
+xdg-utils \
 "
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177539): 
https://lists.openembedded.org/g/openembedded-core/message/177539
Mute This Topic: https://lists.openembedded.org/mt/97118439/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 02/11] packagegroup-self-hosted: add zstd

2023-02-21 Thread Trevor Woerner
Add missing tools necessary on the host for a build.

Signed-off-by: Trevor Woerner 
---
 meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb 
b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
index 529d4c5c5c6b..dd000fda49d1 100644
--- a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
@@ -176,6 +176,7 @@ RDEPENDS:packagegroup-self-hosted-extended = "\
 xz \
 zip \
 zlib \
+zstd \
 "
 
 
-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177540): 
https://lists.openembedded.org/g/openembedded-core/message/177540
Mute This Topic: https://lists.openembedded.org/mt/97118440/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 00/11] build-appliance-image revival

2023-02-21 Thread Trevor Woerner
Revive the build-appliance.

The build-appliance-image produces an image that contains all the necessary
pieces in order to perform a bitbake build. This patch series contains a
number of small tweaks that were needed in order for the build of the
appliance to succeed, and then for a build within the appliance to succeed as
well.

Trevor Woerner (11):
  packagegroup-self-hosted: alphabetize
  packagegroup-self-hosted: add zstd
  build-appliance-image: add support for qemu
  build-appliance-image: set TERM
  build-appliance-image kernel: linux-yocto: qemuall: add taskstats
  build-appliance-image: fix HOMEPAGE
  build-appliance-image: add /lib64 symlink
  build-appliance-image: use a real /tmp
  build-appliance-image: QB_MEM: allow user config
  QB_SMP: allow user modification
  build-appliance-image: check for xattr feature

 meta/conf/machine/include/riscv/qemuriscv.inc |  2 +-
 .../conf/machine/include/x86/qemuboot-x86.inc |  2 +-
 meta/conf/machine/qemuarm.conf|  2 +-
 meta/conf/machine/qemuarm64.conf  |  2 +-
 meta/conf/machine/qemuppc64.conf  |  2 +-
 .../images/build-appliance-image_15.0.0.bb| 27 ++-
 .../packagegroups/packagegroup-self-hosted.bb | 11 
 meta/recipes-kernel/linux/linux-yocto.inc |  2 +-
 8 files changed, 33 insertions(+), 17 deletions(-)

-- 
2.36.0.rc2.17.g4027e30c53


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177538): 
https://lists.openembedded.org/g/openembedded-core/message/177538
Mute This Topic: https://lists.openembedded.org/mt/97118438/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] vte: update 0.70.2 -> 0.70.3

2023-02-21 Thread Markus Volk
v2 enables vala only, if gobject-introspection-data is in 
DISTRO_FEATURES to unblock platforms that don't provide it


Am Di, 21. Feb 2023 um 19:52:31 +0100 schrieb Markus Volk 
:

- Allow to build the gtk4 widget and vapi
  This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe and remove unneeded patch

Signed-off-by: Markus Volk >

---
 ...EXITCODE-macro-for-non-glibc-systems.patch | 42 
---

 .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 22 +-
 2 files changed, 10 insertions(+), 54 deletions(-)
 delete mode 100644 
meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} 
(69%)


diff --git 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch 
b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch

deleted file mode 100644
index b4100fc381..00
--- 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch

+++ /dev/null
@@ -1,42 +0,0 @@
-From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 
2001
-From: Danilo Spinella >

-Date: Thu, 21 Mar 2019 14:19:26 +0100
-Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Upstream-Status: Submitted [1]
-
-Signed-off-by: Andreas Müller >

-
-[1] 
-

- src/missing.hh | 4 
- src/widget.cc  | 1 +
- 2 files changed, 5 insertions(+)
-
 a/src/missing.hh
-+++ b/src/missing.hh
-@@ -24,6 +24,10 @@
- #define NSIG (8 * sizeof(sigset_t))
- #endif
-
-+#ifndef W_EXITCODE
-+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
-+#endif
-+
- #ifndef HAVE_FDWALK
- int fdwalk(int (*cb)(void* data, int fd),
-void* data);
 a/src/widget.cc
-+++ b/src/widget.cc
-@@ -21,6 +21,7 @@
- #include "widget.hh"
-
- #include  // for W_EXITCODE
-+#include "missing.hh" // for W_EXITCODE on non-glibc systems
-
- #include 
- #include 
diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.3.bb

similarity index 69%
rename from meta/recipes-support/vte/vte_0.70.2.bb
rename to meta/recipes-support/vte/vte_0.70.3.bb
index ec2fb1f522..a39598216b 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.3.bb
@@ -11,30 +11,28 @@ LIC_FILES_CHKSUM = " \
 file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 
 \

 "

-DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
+DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native 
gperf-native icu pango zlib"


 GNOMEBASEBUILDCLASS = "meson"
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"

-inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection
+inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection vala


-# vapigen.m4 is required when vala is not present (but the one from 
vala should be used normally)
-SRC_URI += 
"file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch" 

-SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
+SRC_URI[archive.sha256sum] = 
"9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"


 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"

-# Help g-ir-scanner find the .so for linking
-do_compile:prepend() {
-export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
-}
-
 # Package additional files
 FILES:${PN}-dev += "${datadir}/vala/vapi/*"

-PACKAGECONFIG ??= "gnutls"
-PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
+PACKAGECONFIG ??= " \
+gnutls \
+${@bb.utils.contains 
('DISTRO_FEATURES', 
'gobject-introspection-data', 'vala', '', d)} \
+${@bb.utils.contains 
('DISTRO_FEATURES', 'opengl', 'gtk4', 
'', d)} \

+"
+PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
+PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
 PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
 PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
 # vala requires gir
--
2.34.1




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177536): 
https://lists.openembedded.org/g/openembedded-core/message/177536
Mute This Topic: https://lists.openembedded.org/mt/97115916/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] vte: update 0.70.2 -> 0.70.3

2023-02-21 Thread Markus Volk
- Allow to build the gtk4 widget and vapi
  This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe and remove unneeded patch

Signed-off-by: Markus Volk 
---
 ...EXITCODE-macro-for-non-glibc-systems.patch | 42 ---
 .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 22 +-
 2 files changed, 10 insertions(+), 54 deletions(-)
 delete mode 100644 
meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (69%)

diff --git 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 
b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
deleted file mode 100644
index b4100fc381..00
--- 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 2001
-From: Danilo Spinella 
-Date: Thu, 21 Mar 2019 14:19:26 +0100
-Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Upstream-Status: Submitted [1]
-
-Signed-off-by: Andreas Müller 
-
-[1] https://gitlab.gnome.org/GNOME/vte/issues/72
-

- src/missing.hh | 4 
- src/widget.cc  | 1 +
- 2 files changed, 5 insertions(+)
-
 a/src/missing.hh
-+++ b/src/missing.hh
-@@ -24,6 +24,10 @@
- #define NSIG (8 * sizeof(sigset_t))
- #endif
- 
-+#ifndef W_EXITCODE
-+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
-+#endif
-+
- #ifndef HAVE_FDWALK
- int fdwalk(int (*cb)(void* data, int fd),
-void* data);
 a/src/widget.cc
-+++ b/src/widget.cc
-@@ -21,6 +21,7 @@
- #include "widget.hh"
- 
- #include  // for W_EXITCODE
-+#include "missing.hh" // for W_EXITCODE on non-glibc systems
- 
- #include 
- #include 
diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.3.bb
similarity index 69%
rename from meta/recipes-support/vte/vte_0.70.2.bb
rename to meta/recipes-support/vte/vte_0.70.3.bb
index ec2fb1f522..a39598216b 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.3.bb
@@ -11,30 +11,28 @@ LIC_FILES_CHKSUM = " \
 file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 \
 "
 
-DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
+DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu 
pango zlib"
 
 GNOMEBASEBUILDCLASS = "meson"
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"
 
-inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection
+inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection vala
 
-# vapigen.m4 is required when vala is not present (but the one from vala 
should be used normally)
-SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
+SRC_URI[archive.sha256sum] = 
"9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 
-# Help g-ir-scanner find the .so for linking
-do_compile:prepend() {
-export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
-}
-
 # Package additional files
 FILES:${PN}-dev += "${datadir}/vala/vapi/*"
 
-PACKAGECONFIG ??= "gnutls"
-PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
+PACKAGECONFIG ??= " \
+gnutls \
+${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', 
'vala', '', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'gtk4', '', d)} \
+"
+PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
+PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
 PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
 PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
 # vala requires gir
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177535): 
https://lists.openembedded.org/g/openembedded-core/message/177535
Mute This Topic: https://lists.openembedded.org/mt/97115916/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] vte: update 0.70.2 -> 0.70.3

2023-02-21 Thread Markus Volk
- Allow to build the gtk4 widget and vapi
  This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe and remove unneeded patch

Signed-off-by: Markus Volk 
---
 ...EXITCODE-macro-for-non-glibc-systems.patch | 42 ---
 .../vte/{vte_0.70.2.bb => vte_0.70.3.bb}  | 18 +++-
 2 files changed, 6 insertions(+), 54 deletions(-)
 delete mode 100644 
meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 rename meta/recipes-support/vte/{vte_0.70.2.bb => vte_0.70.3.bb} (69%)

diff --git 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
 
b/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
deleted file mode 100644
index b4100fc381..00
--- 
a/meta/recipes-support/vte/vte/0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From de9639baac792327c701e509258b8a13f6959e82 Mon Sep 17 00:00:00 2001
-From: Danilo Spinella 
-Date: Thu, 21 Mar 2019 14:19:26 +0100
-Subject: [PATCH] Add W_EXITCODE macro for non-glibc systems
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Upstream-Status: Submitted [1]
-
-Signed-off-by: Andreas Müller 
-
-[1] https://gitlab.gnome.org/GNOME/vte/issues/72
-

- src/missing.hh | 4 
- src/widget.cc  | 1 +
- 2 files changed, 5 insertions(+)
-
 a/src/missing.hh
-+++ b/src/missing.hh
-@@ -24,6 +24,10 @@
- #define NSIG (8 * sizeof(sigset_t))
- #endif
- 
-+#ifndef W_EXITCODE
-+#define W_EXITCODE(ret, sig) ((ret) << 8 | (sig))
-+#endif
-+
- #ifndef HAVE_FDWALK
- int fdwalk(int (*cb)(void* data, int fd),
-void* data);
 a/src/widget.cc
-+++ b/src/widget.cc
-@@ -21,6 +21,7 @@
- #include "widget.hh"
- 
- #include  // for W_EXITCODE
-+#include "missing.hh" // for W_EXITCODE on non-glibc systems
- 
- #include 
- #include 
diff --git a/meta/recipes-support/vte/vte_0.70.2.bb 
b/meta/recipes-support/vte/vte_0.70.3.bb
similarity index 69%
rename from meta/recipes-support/vte/vte_0.70.2.bb
rename to meta/recipes-support/vte/vte_0.70.3.bb
index ec2fb1f522..970d7ea64a 100644
--- a/meta/recipes-support/vte/vte_0.70.2.bb
+++ b/meta/recipes-support/vte/vte_0.70.3.bb
@@ -11,30 +11,24 @@ LIC_FILES_CHKSUM = " \
 file://COPYING.XTERM;md5=d7fc3a23c16c039afafe2e042030f057 \
 "
 
-DEPENDS = "glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu"
+DEPENDS = "fribidi glib-2.0 gtk+3 libpcre2 libxml2-native gperf-native icu 
pango zlib"
 
 GNOMEBASEBUILDCLASS = "meson"
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"
 
-inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection
+inherit gnomebase gi-docgen features_check upstream-version-is-even 
gobject-introspection vala
 
-# vapigen.m4 is required when vala is not present (but the one from vala 
should be used normally)
-SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = 
"4d15b4380de3f564d57eabd006389c407c705df5b0c70030fdcc24971a334d80"
+SRC_URI[archive.sha256sum] = 
"9457134a02f3157fca04f7e0d39bdb0f3099be0a3ce82b7139d0c98a80748f23"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 
-# Help g-ir-scanner find the .so for linking
-do_compile:prepend() {
-export GIR_EXTRA_LIBS_PATH="${B}/src/.libs"
-}
-
 # Package additional files
 FILES:${PN}-dev += "${datadir}/vala/vapi/*"
 
-PACKAGECONFIG ??= "gnutls"
-PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false,vala-native vala"
+PACKAGECONFIG ??= "gnutls vala ${@bb.utils.contains('DISTRO_FEATURES', 
'opengl', 'gtk4', '', d)}"
+PACKAGECONFIG[gtk4] = "-Dgtk4=true,-Dgtk4=false,gtk4"
+PACKAGECONFIG[vala] = "-Dvapi=true,-Dvapi=false"
 PACKAGECONFIG[gnutls] = "-Dgnutls=true,-Dgnutls=false,gnutls"
 PACKAGECONFIG[systemd] = "-D_systemd=true,-D_systemd=false,systemd"
 # vala requires gir
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177534): 
https://lists.openembedded.org/g/openembedded-core/message/177534
Mute This Topic: https://lists.openembedded.org/mt/97115769/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] weston: Add kiosk shell

2023-02-21 Thread Joshua Watt
Adds support for the kiosk shell to weston. The Kiosk shell is designed
to run a fullscreen application in a "kiosk" mode, but unlike the
fullscreen shell the kiosk mode still provides traditional desktop
protocols.

Signed-off-by: Joshua Watt 
---
 meta/recipes-graphics/wayland/weston_11.0.1.bb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/wayland/weston_11.0.1.bb 
b/meta/recipes-graphics/wayland/weston_11.0.1.bb
index b943842bc4..2daecc9856 100644
--- a/meta/recipes-graphics/wayland/weston_11.0.1.bb
+++ b/meta/recipes-graphics/wayland/weston_11.0.1.bb
@@ -42,7 +42,9 @@ PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 
'wayland', 'kms wayla
screenshare \
shell-desktop \
shell-fullscreen \
-   shell-ivi"
+   shell-ivi \
+   shell-kiosk \
+   "
 
 # Can be 'damage', 'im', 'egl', 'shm', 'touch', 'dmabuf-feedback', 
'dmabuf-v4l', 'dmabuf-egl' or 'all'
 SIMPLECLIENTS ?= "all"
@@ -86,6 +88,8 @@ PACKAGECONFIG[shell-desktop] = 
"-Dshell-desktop=true,-Dshell-desktop=false"
 PACKAGECONFIG[shell-fullscreen] = 
"-Dshell-fullscreen=true,-Dshell-fullscreen=false"
 # In-Vehicle Infotainment (IVI) shell
 PACKAGECONFIG[shell-ivi] = "-Dshell-ivi=true,-Dshell-ivi=false"
+# Kiosk shell
+PACKAGECONFIG[shell-kiosk] = "-Dshell-kiosk=true,-Dshell-kiosk=false"
 # JPEG image loading support
 PACKAGECONFIG[image-jpeg] = "-Dimage-jpeg=true,-Dimage-jpeg=false, jpeg"
 # support libseat based launch
-- 
2.33.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177533): 
https://lists.openembedded.org/g/openembedded-core/message/177533
Mute This Topic: https://lists.openembedded.org/mt/97115121/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 reproducibilty issue :: rust-llvm binary differences

2023-02-21 Thread Alexander Kanavin
Are the two different sets of object files available somewhere for
download and inspection? I could take a look and see if I can spot the
difference, but I need the files.

Alex

On Tue, 21 Feb 2023 at 17:47, Sundeep KOKKONDA
 wrote:
>
> Hello,
>
> The rust builds are not reproducible when the build path is changed. The 
> issue details are in https://bugzilla.yoctoproject.org/show_bug.cgi?id=14875.
>
> After debugging several ways, we tried to find at what build stage the Yocto 
> build artifacts are deviating with rust sources generated artifacts.
>
> I took the identical rust tarball sources (rustc-1.67.0-src.tar.xz) as Yocto 
> rust sources and built in two different paths (buildA & buildB directories). 
> In the rust sources the generated binaries are identical between 2 different 
> builds.
>
> But, In Yocto we found that the binaries 
> '../tmp/work/x86_64-linux/rust-native/1.67.0-r0/recipe-sysroot-native/usr/lib/llvm-rust/lib/libLTO.so
>  & libRemarks.so' are differed between 2 builds. See the differences in the 
> attached 'libLTO-diff.png'.
>
> And these objects are passed to compile all rust crates in later build stages 
> (with option '-L 
> native=/ala-lpggp31/skokkonda/875/poky/buildC/tmp/work/x86_64-linux/rust-native/1.67.0-r0/recipe-sysroot-native/usr/lib/llvm-rust/lib').
>
> So, we suspect this could be the reason for this reproducibility issue in 
> Yocto. I tried to find the reason for difference in these binaries but the 
> '-vv' build log doesn't give enough info by linking which objects this 
> libLTO.so is generated. I tried the disassembly of object files generated in 
> ../x86_64-linux/rust-native/ but that didn't showup these binary differences.
>
> Anyone who has expertise with rust-llvm can guide me here on how these *.so 
> are generating and how to understand/fix these differences.
>
>
>
> Thanks,
> Sundeep K.
>
> 
>

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



[OE-core] [meta-oe][dunfell][PATCH 2/2] zeromq: upgrade 4.3.3 -> 4.3.4

2023-02-21 Thread Hugo Simeliere via lists.openembedded.org
Signed-off-by: Zheng Ruoqin 
Signed-off-by: Khem Raj 
(cherry picked from commit 8ced89f62f152e2b233c532ce03408bf46bde55b)
Signed-off-by: Hugo SIMELIERE 
---
.../zeromq/{zeromq_4.3.3.bb => zeromq_4.3.4.bb}   | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-oe/recipes-connectivity/zeromq/{zeromq_4.3.3.bb => zeromq_4.3.4.bb} 
(87%)

diff --git a/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.3.bb 
b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.4.bb
similarity index 87%
rename from meta-oe/recipes-connectivity/zeromq/zeromq_4.3.3.bb
rename to meta-oe/recipes-connectivity/zeromq/zeromq_4.3.4.bb
index a10500475..4381f2d6d 100644
--- a/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.3.bb
+++ b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.4.bb
@@ -10,8 +10,8 @@ SRC_URI = 
"http://github.com/zeromq/libzmq/releases/download/v${PV}/zeromq-${PV}
 file://0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch \
 file://run-ptest \
"
-SRC_URI[md5sum] = "78acc277d95e10812d71b2b3c3c3c9a9"
-SRC_URI[sha256sum] = 
"9d9285db37ae942ed0780c016da87060497877af45094ff9e1a1ca736e3875a2"
+SRC_URI[md5sum] = "c897d4005a3f0b8276b00b7921412379"
+SRC_URI[sha256sum] = 
"c593001a89f5a85dd2ddf564805deb860e02471171b3f204944857336295c3e5"
 UPSTREAM_CHECK_URI = "https://github.com/${BPN}/libzmq/releases;
--
2.25.1


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



[OE-core] [meta-oe][dunfell][PATCH 1/2] zeromq: upgrade 4.3.2 -> 4.3.3

2023-02-21 Thread Hugo Simeliere via lists.openembedded.org
Refresh the following patch:
0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch

Signed-off-by: Zang Ruochen 
Signed-off-by: Khem Raj 
(cherry picked from commit 117b3f95507b464aafe6a1948cf4a79f26194acb)
Signed-off-by: Hugo SIMELIERE 
---
...void-host-specific-path-to-libsodium.patch | 19 +--
.../{zeromq_4.3.2.bb => zeromq_4.3.3.bb}  |  4 ++--
2 files changed, 15 insertions(+), 8 deletions(-)
rename meta-oe/recipes-connectivity/zeromq/{zeromq_4.3.2.bb => zeromq_4.3.3.bb} 
(87%)

diff --git 
a/meta-oe/recipes-connectivity/zeromq/files/0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch
 
b/meta-oe/recipes-connectivity/zeromq/files/0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch
index eb3dee4d3..3b0300c8a 100644
--- 
a/meta-oe/recipes-connectivity/zeromq/files/0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch
+++ 
b/meta-oe/recipes-connectivity/zeromq/files/0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch
@@ -1,6 +1,7 @@
+From 24ad50286a87833329213dc0b0e68c21a95f Mon Sep 17 00:00:00 2001
From: Niko Mauno 
-Date: Wed Apr 22 09:00:00 2020 +0300
-Subject: CMakeLists.txt: Avoid host-specific path to libsodium
+Date: Wed, 22 Apr 2020 09:00:00 +0300
+Subject: [PATCH] CMakeLists.txt: Avoid host-specific path to libsodium
 Avoid propagating full build host specific path to generated
ZeroMQTargets.cmake when building with libsodium, which changes the
@@ -17,10 +18,16 @@ Upstream-Status: Pending
 Signed-off-by: Niko Mauno 
+---
+ CMakeLists.txt | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index e92141d..d0775c1 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
-@@ -1210,7 +1210,7 @@
-   target_link_libraries(libzmq ${OPTIONAL_LIBRARIES} 
${CMAKE_THREAD_LIBS_INIT})
+@@ -1428,7 +1428,7 @@ if(BUILD_SHARED)
+   endif()

if(SODIUM_FOUND)
-target_link_libraries(libzmq ${SODIUM_LIBRARIES})
@@ -28,8 +35,8 @@ Signed-off-by: Niko Mauno 
  # On Solaris, libsodium depends on libssp
  if(${CMAKE_SYSTEM_NAME} MATCHES "SunOS")
target_link_libraries(libzmq ssp)
-@@ -1240,7 +1240,7 @@
-   target_link_libraries(libzmq-static ${OPTIONAL_LIBRARIES} 
${CMAKE_THREAD_LIBS_INIT})
+@@ -1473,7 +1473,7 @@ if(BUILD_STATIC)
+   endif()

if(SODIUM_FOUND)
-target_link_libraries(libzmq-static ${SODIUM_LIBRARIES})
diff --git a/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.2.bb 
b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.3.bb
similarity index 87%
rename from meta-oe/recipes-connectivity/zeromq/zeromq_4.3.2.bb
rename to meta-oe/recipes-connectivity/zeromq/zeromq_4.3.3.bb
index 02a4c04fd..a10500475 100644
--- a/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.2.bb
+++ b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.3.bb
@@ -10,8 +10,8 @@ SRC_URI = 
"http://github.com/zeromq/libzmq/releases/download/v${PV}/zeromq-${PV}
 file://0001-CMakeLists-txt-Avoid-host-specific-path-to-libsodium.patch \
 file://run-ptest \
"
-SRC_URI[md5sum] = "2047e917c2cc93505e2579bcba67a573"
-SRC_URI[sha256sum] = 
"ebd7b5c830d6428956b67a0454a7f8cbed1de74b3b01e5c33c5378e22740f763"
+SRC_URI[md5sum] = "78acc277d95e10812d71b2b3c3c3c9a9"
+SRC_URI[sha256sum] = 
"9d9285db37ae942ed0780c016da87060497877af45094ff9e1a1ca736e3875a2"
 UPSTREAM_CHECK_URI = "https://github.com/${BPN}/libzmq/releases;
--
2.25.1


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



[OE-core][dunfell][PATCH] bluez5: Exclude CVE-2022-39177 from cve-check

2023-02-21 Thread Hugo Simeliere via lists.openembedded.org
CVE already fixed in CVE-2022-39176.patch

Signed-off-by: Hugo SIMELIERE 
---
meta/recipes-connectivity/bluez5/bluez5_5.55.bb | 7 +++
1 file changed, 7 insertions(+)

diff --git a/meta/recipes-connectivity/bluez5/bluez5_5.55.bb 
b/meta/recipes-connectivity/bluez5/bluez5_5.55.bb
index e5353bd815..be74a35e0a 100644
--- a/meta/recipes-connectivity/bluez5/bluez5_5.55.bb
+++ b/meta/recipes-connectivity/bluez5/bluez5_5.55.bb
@@ -6,6 +6,13 @@ SRC_URI[sha256sum] = 
"8863717113c4897e2ad3271fc808ea245319e6fd95eed2e934fae8e089
# These issues have kernel fixes rather than bluez fixes so exclude here
CVE_CHECK_WHITELIST += "CVE-2020-12352 CVE-2020-24490"
+# Commit 7a80d2096f1b7125085e21448112aa02f49f5e9a, 
e2b0f0d8d63e1223bb714a9efb37e2257818268b
+# and 0388794dc5fdb73a4ea88bcf148de0a12b4364d4 to fix CVE-2022-39177
+# already backport in CVE-2022-39176.patch
+# https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968
+
+CVE_CHECK_WHITELIST += "CVE-2022-39177"
+
# noinst programs in Makefile.tools that are conditional on READLINE
# support
NOINST_TOOLS_READLINE ?= " \
--
2.25.1

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



[OE-core] Yocto reproducibilty issue :: rust-llvm binary differences

2023-02-21 Thread Sundeep KOKKONDA
Hello,

The rust builds are not reproducible when the build path is changed. The issue 
details are in https://bugzilla.yoctoproject.org/show_bug.cgi?id=14875.

After debugging several ways, we tried to find at what build stage the Yocto 
build artifacts are deviating with rust sources generated artifacts.

I took the identical rust tarball sources (rustc-1.67.0-src.tar.xz) as Yocto 
rust sources and built in two different paths (buildA & buildB directories). In 
the rust sources the generated binaries are identical between 2 different 
builds.

But, In Yocto we found that the binaries 
'../tmp/work/x86_64-linux/rust-native/1.67.0-r0/recipe-sysroot-native/usr/lib/llvm-rust/lib/libLTO.so
 & libRemarks.so' are differed between 2 builds. See the differences in the 
attached 'libLTO-diff.png'.

And these objects are passed to compile all rust crates in later build stages 
(with option '-L 
native=/ala-lpggp31/skokkonda/875/poky/buildC/tmp/work/x86_64-linux/rust-native/1.67.0-r0/recipe-sysroot-native/usr/lib/llvm-rust/lib').

So, we suspect this could be the reason for this reproducibility issue in 
Yocto. I tried to find the reason for difference in these binaries but the 
'-vv' build log doesn't give enough info by linking which objects this 
libLTO.so is generated. I tried the disassembly of object files generated in 
../x86_64-linux/rust-native/ but that didn't showup these binary differences.

Anyone who has expertise with rust-llvm can guide me here on how these *.so are 
generating and how to understand/fix these differences.



Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177528): 
https://lists.openembedded.org/g/openembedded-core/message/177528
Mute This Topic: https://lists.openembedded.org/mt/97113152/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/1] lib/oe/reproducible: Use git log without gpg signature

2023-02-21 Thread Benoît Mauduit via lists . openembedded . org

Hello,

Any update on my patch ?

Thanks,

BR,

On 1/12/23 14:23, Benoît Mauduit via lists.openembedded.org wrote:

Previously, if "showSignature" is present in user gitconfig, parsing
of the timestamp will fail.

Ideally we should replace this command with a git plumbing command.

Signed-off-by: Benoît Mauduit 
---
  meta/lib/oe/reproducible.py | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oe/reproducible.py b/meta/lib/oe/reproducible.py
index 04a1810d4f2..9ac75c02e38 100644
--- a/meta/lib/oe/reproducible.py
+++ b/meta/lib/oe/reproducible.py
@@ -115,7 +115,8 @@ def get_source_date_epoch_from_git(d, sourcedir):
  return None
  
  bb.debug(1, "git repository: %s" % gitpath)

-p = subprocess.run(['git', '--git-dir', gitpath, 'log', '-1', 
'--pretty=%ct'], check=True, stdout=subprocess.PIPE)
+p = subprocess.run(['git', '-c', 'log.showSignature=false', '--git-dir', 
gitpath, 'log', '-1', '--pretty=%ct'],
+   check=True, stdout=subprocess.PIPE)
  return int(p.stdout.decode('utf-8'))
  
  def get_source_date_epoch_from_youngest_file(d, sourcedir):








--
Benoît Mauduit



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



[OE-core] elfutils 0.189 release next week (~Feb 28)

2023-02-21 Thread Randy MacLeod
I don't see anything Uber critical in this update but should we take 0.189
for the 4.2 release in a week? The maintainers seem to be open to releasing
a little earlier if prompted.

Randy


-- Forwarded message -
From: Mark Wielaard 
Date: Tue., Feb. 21, 2023, 08:33
Subject: elfutils 0.189 release next week
To: 


Hi,

We accumulated a lot of patches since 0.188 (59 commits by 13 authors)
with some nice new features and some important bug fixes. So it would
be good to push a new release out.

I cleaned up the patchwork list and will go over the following 25
pending patches to see what can be incorporated:
https://patchwork.sourceware.org/project/elfutils/list/ [*]
If your patch is not on that list please ping.

I propose to do the 0.189 release on Tuesday February 28, but it can be
earlier or later if that is more convenient.

Cheers,

Mark

[*] That is this list of patches:
git pw patch list --format simple --state New --state RFC --state
Under-Review --state Changes-Requested --column Name

[2/2] libdw: Use elf_rawdata when checking .debug section
[1/2] libelf: memmove any extra bytes left by elf_cvt_gnuhash convers...
A scenario where Perf cannot unwind the user stack by dwarf with libd...
PR28873 - Implement eu-readelf -D
[v2,16/16] lib: Use HAVE_LIBINTL_H to guard #include 
[v2,15/16] libelf: F_GETFD may not predefined with msvc/mingw, guard ...
[v2,14/16] Add function sys_get_page_size to replace platform depende...
[v2,12/16] libasm/debuginfod: fchmod doesn't present on win32
[v2,11/16] libebl/libdwelf: define ssize_t and pid_t for MSVC within ...
[v2,10/16] libasm: stdio_ext.h are not present on win32
[v2,09/16] libelf: uid_t, gid_t and mode_t are not comes with msvcrt,...
[v2,08/16] lib: Implement error properly even when not HAVE_ERR_H
[v2,07/16] libdw: Fixes compile of dwarf_whatattr.c and dwarf_whatfor...
[v2,05/16] libcpu: Remove the need of NMNES by using enum
[v2,04/16] Fixes usage of basename about prototype differences
[v2,03/16] Use configure to detect HAVE_DECL_MMAP and use it for syst...
[v2,02/16] move platform depended include into system.h of libebl
PATCH: Bug debuginfod/29472 followup
[RFC] backends: Add RISC-V object attribute printing
[Bug,libdw/29434] Memory leak in `dwarf_getscopes`
[PATCHv2] strip: keep .ctf section in stripped file
[4/4] libdwfl, eu-stack, aarch64: Add API for setting AARCH64 PAC mas...
[3/4] libdwfl, aarch64: Demangle return addresses using a PAC mask
[2/4] libdw, aarch64: Implement DW_CFA_AARCH64_negate_ra_state CFI in...
[1/4] aarch64: Create definitions for AARCH64_RA_SIGN_STATE register

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



[OE-core][dunfell][PATCH] openssl: upgrade 1.1.1s to 1.1.1t

2023-02-21 Thread Hugo Simeliere via lists.openembedded.org
Major changes between OpenSSL 1.1.1s and OpenSSL 1.1.1t [7 Feb 2023]
* Fixed X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)
* Fixed Use-after-free following BIO_new_NDEF (CVE-2023-0215)
* Fixed Double free after calling PEM_read_bio_ex (CVE-2022-4450)
* Fixed Timing Oracle in RSA Decryption (CVE-2022-4304)

Signed-off-by: Hugo SIMELIERE 
---
.../openssl/{openssl_1.1.1s.bb => openssl_1.1.1t.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/openssl/{openssl_1.1.1s.bb => 
openssl_1.1.1t.bb} (98%)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1s.bb 
b/meta/recipes-connectivity/openssl/openssl_1.1.1t.bb
similarity index 98%
rename from meta/recipes-connectivity/openssl/openssl_1.1.1s.bb
rename to meta/recipes-connectivity/openssl/openssl_1.1.1t.bb
index 6c8f285996..a1956ad8c2 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1s.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1t.bb
@@ -24,7 +24,7 @@ SRC_URI_append_class-nativesdk = " \
file://environment.d-openssl.sh \
"
-SRC_URI[sha256sum] = 
"c5ac01e760ee6ff0dab61d6b2bbd30146724d063eb322180c6f18a6f74e4b6aa"
+SRC_URI[sha256sum] = 
"8dee9b24bdb1dcbf0c3d1e9b02fb8f6bf22165e807f45adeb7c9677536859d3b"
 inherit lib_package multilib_header multilib_script ptest
MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
--
2.25.1


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



[OE-core] Yocto Project Status 21 February 2023 (WW08)

2023-02-21 Thread Stephen Jolley
Current Dev Position: YP 4.2 M3 Feature Freeze

Next Deadline: 20th February 2023 YP 4.2 M3 Build

 

Next Team Meetings:

*   Bug Triage meeting Thursday February 23rd 7:30 am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Weekly Project Engineering Sync Tuesday February 21st at 8 am PDT (

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

 

Key Status/Updates:

*   YP 3.1.23 is due to be released.
*   We are due to build M3 and are at feature freeze for YP 4.2.
*   We saw further version upgrades this week and a number of bitbake
hang fixes or fixes for exits with no output. There are a few remaining
issues to conclude then we should be in a good position to build M3.
*   CVE levels in master are reducing. The remaining concern is the
large number of linux-yocto CVEs which have shown up since we last updated
the exclusion lists. The full list can be seen here:

https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.
txt

Help in resolving these so we can remove the exclusion on linux-yocto on all
reports would be appreciated.

*   We have a growing number of bugs in bugzilla, any help with them is
appreciated.

 

Ways to contribute:

*   As people are likely aware, the project has a number of components
which are either unmaintained, or have people with little to no time trying
to keep them alive. These components include: patchtest, layerindex,
devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more.
Many have open bugs. Help is welcome in trying to better look after these
components!
*   There are bugs identified as possible for newcomers to the project:

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

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

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.
*   Help is very much welcome in trying to resolve our autobuilder
intermittent issues. You can see the list of failures we're continuing to
see by searching for the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
*   Help us resolve CVE issues:
 CVE metrics 

 

YP 4.2 Milestone Dates:

*   YP 4.2 M3 build date 2023/02/20
*   YP 4.2 M3 Release date 2023/03/03
*   YP 4.2 M4 build date 2023/04/03
*   YP 4.2 M4 Release date 2023/04/28

 

Upcoming dot releases:

*   YP 3.1.23 is ready for release
*   YP 4.0.8 build date 2023/02/27
*   YP 4.0.8 Release date 2023/03/10
*   YP 4.1.3 build date 2023/03/06
*   YP 4.1.3 Release date 2023/03/17
*   YP 3.1.24 build date 2023/03/20
*   YP 3.1.24 Release date 2023/03/31
*   YP 4.0.9 build date 2023/04/10
*   YP 4.0.9 Release date 2023/04/21
*   YP 4.1.4 build date 2023/05/01
*   YP 4.1.4 Release date 2023/05/13
*   YP 3.1.25 build date 2023/05/08
*   YP 3.1.25 Release date 2023/05/19
*   YP 4.0.10 build date 2023/05/15
*   YP 4.0.10 Release date 2023/05/26

 

Tracking Metrics:

*   WDD 2402 (last week 2407) (

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

*   Total patches found: 1186 (last week 1187)
*   Patches in the Pending State: 277 (23%) [last week 277 (23%)]

*
https://autobuilder.yocto.io/pub/non-release/patchmetrics/

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status 

[OE-core][kirkstone 21/23] oeqa qemurunner.py: add timeout to QMP calls

2023-02-21 Thread Steve Sakoman
From: Mikko Rapeli 

When a qemu machine hangs, the QMP calls can hang for ever
too, and when this happens any failing test commands from ssh
runner may be followed by dump_monitor() calls which
then also hang. Hangs followed by hangs.

Use runqemutime at setup and run_monitor() specific timeout
for later calls.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit 3a07bdf77dc6ecbf4c620b051dd032abaaf1e4ff)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/utils/qemurunner.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index fedabb189a..aa9e530f1b 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -342,6 +342,8 @@ class QemuRunner:
 return False
 
 try:
+# set timeout value for all QMP calls
+self.qmp.settimeout(self.runqemutime)
 self.qmp.connect()
 connect_time = time.time()
 self.logger.info("QMP connected to QEMU at %s and took %s 
seconds" %
@@ -617,6 +619,7 @@ class QemuRunner:
 
 def run_monitor(self, command, args=None, timeout=60):
 if hasattr(self, 'qmp') and self.qmp:
+self.qmp.settimeout(timeout)
 if args is not None:
 return self.qmp.cmd(command, args)
 else:
-- 
2.34.1


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



[OE-core][kirkstone 04/23] apr: update 1.7.0 -> 1.7.2

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

Changes for APR 1.7.2

  *) Correct a packaging issue in 1.7.1. The contents of the release were
 correct, but the top level directory was misnamed.

Changes for APR 1.7.1

  *) SECURITY: CVE-2022-24963 (cve.mitre.org)
 Integer Overflow or Wraparound vulnerability in apr_encode functions of
 Apache Portable Runtime (APR) allows an attacker to write beyond bounds
 of a buffer.

  *) SECURITY: CVE-2022-28331 (cve.mitre.org)
 On Windows, Apache Portable Runtime 1.7.0 and earlier may write beyond
 the end of a stack based buffer in apr_socket_sendv(). This is a result
 of integer overflow.

  *) SECURITY: CVE-2021-35940 (cve.mitre.org)
 Restore fix for out-of-bounds array dereference in apr_time_exp*() 
functions.
 (This issue was addressed as CVE-2017-12613 in APR 1.6.3 and
 later 1.6.x releases, but was missing in 1.7.0.)  [Stefan Sperling]

  *) configure: Fix various build issues for compilers enforcing
 strict C99 compliance.  PR 66396, 66408, 66426.
 [Florian Weimer , Sam James ]

  *) apr_atomic_read64(): Fix non-atomic read on 32-bit Windows [Ivan Zhakov]

  *) configure: Prefer posix name-based shared memory over SysV IPC.
 [Jim Jagielski]

  *) configure: Add --disable-sctp argument to forcibly disable SCTP
 support, or --enable-sctp which fails if SCTP support is not
 detected.  [Lubos Uhliarik , Joe Orton]

  *) Fix handle leak in the Win32 apr_uid_current implementation.
 PR 61165. [Ivan Zhakov]

  *) Add error handling for lseek() failures in apr_file_write() and
 apr_file_writev().  [Joe Orton]

  *) Don't silently set APR_FOPEN_NOCLEANUP for apr_file_mktemp() created file
 to avoid a fd and inode leak when/if later passed to apr_file_setaside().
 [Yann Ylavic]

  *) APR's configure script uses AC_TRY_RUN to detect whether the return type
 of strerror_r is int. When cross-compiling this defaults to no.

 This commit adds an AC_CACHE_CHECK so users who cross-compile APR may
 influence the outcome with a configure variable. [Sebastian Kemper
 ]

  *) Add a cache check with which users who cross-compile APR
 can influence the outcome of the /dev/zero test by setting the variable
 ac_cv_mmap__dev_zero=yes [Sebastian Kemper ]

  *) Trick autoconf into printing the correct default prefix in the help.
 [Stefan Fritsch]

  *) Don't try to use PROC_PTHREAD by default when cross compiling.
 [Yann Ylavic]

  *) Add the ability to cross compile APR. [Graham Leggett]

  *) While cross-compiling, the tools/gen_test_char could not
 be executed at build time, use AX_PROG_CC_FOR_BUILD to
 build native tools/gen_test_char

 Support explicit libtool by variable assigning before buildcheck.sh,
 it is helpful for cross-compiling (such as libtool=aarch64-linux-libtool)
 [Hongxu Jia ]

  *) Avoid an overflow on 32 bit platforms. [René Hjortskov Nielsen
 ]

  *) Use AC_CHECK_SIZEOF, so as to support cross compiling. PR 56053.
 [Mike Frysinger ]

  *) Add --tag=CC to libtool invocations. PR 62640. [Michael Osipov]

  *) apr_pools: Fix pool debugging output so that creation events are
 always emitted before allocation events and subpool destruction
 events are emitted on pool clear/destroy for proper accounting.
 [Brane Čibej]

  *) apr_socket_listen: Allow larger listen backlog values on Windows 8+.
 [Evgeny Kotkov ]

  *) Fixed: apr_get_oslevel() was returning APR_WIN_XP on Windows 10

  *) Fix attempt to free invalid memory on exit when apr_app is used
 on Windows. [Ivan Zhakov]

  *) Fix double free on exit when apr_app is used on Windows. [Ivan Zhakov]

  *) Fix a regression in apr_stat() for root path on Windows. [Ivan Zhakov]

Dropped patches have all been merged, addressed separately or are backports.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit 3ffae93f24bb1e3954b232099153fd059cfd7daf)
Signed-off-by: Steve Sakoman 
(cherry picked from commit e5326ea0ac7e55b2d671a27c1e035c43b8bbc70d)
Signed-off-by: Steve Sakoman 
---
 ...ion-to-disable-timed-dependant-tests.patch | 20 ++---
 ...CHE_CHECK-for-strerror_r-return-type.patch | 52 -
 ...-runtime-test-for-mmap-that-can-map-.patch | 26 +++
 ...ir-path-references-from-installed-ap.patch | 25 +++---
 ...configure.in-support-cross-compiling.patch | 63 ---
 ...ze-doesn-t-match-in-glibc-when-cross.patch | 76 ---
 .../apr/apr/CVE-2021-35940.patch  | 58 --
 .../recipes-support/apr/apr/autoconf270.patch | 22 --
 .../apr/apr/libtoolize_check.patch| 21 +++--
 .../apr/{apr_1.7.0.bb => apr_1.7.2.bb}|  8 +-
 10 files changed, 51 insertions(+), 320 deletions(-)
 delete mode 100644 
meta/recipes-support/apr/apr/0001-add-AC_CACHE_CHECK-for-strerror_r-return-type.patch
 delete mode 100644 

[OE-core][kirkstone 07/23] libjpeg-turbo: upgrade 2.1.4 -> 2.1.5

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

Significant changes relative to 2.1.4

Fixed issues in the build system whereby, when using the Ninja Multi-Config 
CMake generator, a static build of libjpeg-turbo (a build in which 
ENABLE_SHARED is 0) could not be installed, a Windows installer could not be 
built, and the Java regression tests failed.

Fixed a regression introduced by 2.0 beta1[15] that caused a buffer overrun in 
the progressive Huffman encoder when attempting to transform a 
specially-crafted malformed 12-bit-per-component JPEG image into a progressive 
12-bit-per-component JPEG image using a 12-bit-per-component build of 
libjpeg-turbo (-DWITH_12BIT=1.) Given that the buffer overrun was fully 
contained within the progressive Huffman encoder structure and did not cause a 
segfault or other user-visible errant behavior, given that the lossless 
transformer (unlike the decompressor) is not generally exposed to arbitrary 
data exploits, and given that 12-bit-per-component builds of libjpeg-turbo are 
uncommon, this issue did not likely pose a security risk.

Fixed an issue whereby, when using a 12-bit-per-component build of 
libjpeg-turbo (-DWITH_12BIT=1), passing samples with values greater than 4095 
or less than 0 to jpeg_write_scanlines() caused a buffer overrun or underrun in 
the RGB-to-YCbCr color converter.

Fixed a floating point exception that occurred when attempting to use the 
jpegtran -drop and -trim options to losslessly transform a specially-crafted 
malformed JPEG image.

Fixed an issue in tjBufSizeYUV2() whereby it returned a bogus result, rather 
than throwing an error, if the align parameter was not a power of 2. Fixed a 
similar issue in tjCompressFromYUV() whereby it generated a corrupt JPEG image 
in certain cases, rather than throwing an error, if the align parameter was not 
a power of 2.

Fixed an issue whereby tjDecompressToYUV2(), which is a wrapper for 
tjDecompressToYUVPlanes(), used the desired YUV image dimensions rather than 
the actual scaled image dimensions when computing the plane pointers and 
strides to pass to tjDecompressToYUVPlanes(). This caused a buffer overrun and 
subsequent segfault if the desired image dimensions exceeded the scaled image 
dimensions.

Fixed an issue whereby, when decompressing a 12-bit-per-component JPEG image 
(-DWITH_12BIT=1) using an alpha-enabled output color space such as 
JCS_EXT_RGBA, the alpha channel was set to 255 rather than 4095.

Fixed an issue whereby the Java version of TJBench did not accept a range of 
quality values.

Fixed an issue whereby, when -progressive was passed to TJBench, the JPEG input 
image was not transformed into a progressive JPEG image prior to decompression.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit f779689c2c766b609be31222d71110c1a15145a8)
Signed-off-by: Steve Sakoman 
(cherry picked from commit a5d15ae9f4671790d3c5fb3606ec0861c17ed6dd)
Signed-off-by: Steve Sakoman 
---
 .../jpeg/{libjpeg-turbo_2.1.4.bb => libjpeg-turbo_2.1.5.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/jpeg/{libjpeg-turbo_2.1.4.bb => 
libjpeg-turbo_2.1.5.bb} (97%)

diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.4.bb 
b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.5.bb
similarity index 97%
rename from meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.4.bb
rename to meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.5.bb
index 1708fa97f0..4d21ca1e1d 100644
--- a/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.4.bb
+++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_2.1.5.bb
@@ -14,7 +14,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz \
file://0001-libjpeg-turbo-fix-package_qa-error.patch \
"
 
-SRC_URI[sha256sum] = 
"d3ed26a1131a13686dfca4935e520eb7c90ae76fbc45d98bb50a8dc86230342b"
+SRC_URI[sha256sum] = 
"bc12bc9dce55300c6bf4342bc233bcc26bd38bf289eedf147360d731c668ddaf"
 UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/libjpeg-turbo/files/;
 UPSTREAM_CHECK_REGEX = "/libjpeg-turbo/files/(?P(\d+[\.\-_]*)+)/"
 
-- 
2.34.1


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



[OE-core][kirkstone 23/23] oeqa/selftest/bbtests: Update message lookup for test_git_unpack_nonetwork_fail

2023-02-21 Thread Steve Sakoman
From: Alexandre Belloni 

bitbake's output changed, update the test

Signed-off-by: Alexandre Belloni 
Signed-off-by: Richard Purdie 
(cherry picked from commit 7e64b63f96dd1d71e263e7bbbe6591e51e98395a)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/selftest/cases/bbtests.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/bbtests.py 
b/meta/lib/oeqa/selftest/cases/bbtests.py
index cfac7afcf4..b42bbb651d 100644
--- a/meta/lib/oeqa/selftest/cases/bbtests.py
+++ b/meta/lib/oeqa/selftest/cases/bbtests.py
@@ -350,4 +350,4 @@ INHERIT:remove = \"report-error\"
 self.write_config("DISTROOVERRIDES .= \":gitunpack-enable-recipe\"")
 
 result = bitbake('gitunpackoffline-fail -c fetch', ignore_status=True)
-self.assertTrue("Recipe uses a floating tag/branch without a fixed 
SRCREV" in result.output, msg = "Recipe without PV set to SRCPV should have 
failed: %s" % result.output)
+self.assertTrue(re.search("Recipe uses a floating tag/branch .* for 
repo .* without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev()", 
result.output), msg = "Recipe without PV set to SRCPV should have failed: %s" % 
result.output)
-- 
2.34.1


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



[OE-core][kirkstone 01/23] tar: CVE-2022-48303

2023-02-21 Thread Steve Sakoman
From: Rodolfo Quesada Zumbado 

Fixes CVE-2022-48303 by checking Base-256 encoding is at least
2 bytes long. GNU Tar through 1.34 has a one-byte out-of-bounds
read that results in use of uninitialized memory for a conditional
jump. Exploitation to change the flow of control has not been
demonstrated. The issue occurs in from_header in list.c via a
V7 archive in which mtime has approximately 11 whitespace characters.

Reference:
https://nvd.nist.gov/vuln/detail/CVE-2022-48303

Upstream patch:
https://savannah.gnu.org/bugs/?62387
https://git.savannah.gnu.org/cgit/tar.git/patch/src/list.c?id=3da78400eafcccb97e2f2fd4b227ea40d794ede8

Signed-off-by: Rodolfo Quesada Zumbado 
Signed-off-by: Joe Slater 
Signed-off-by: Steve Sakoman 
---
 .../tar/tar/CVE-2022-48303.patch  | 43 +++
 meta/recipes-extended/tar/tar_1.34.bb |  4 +-
 2 files changed, 46 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-extended/tar/tar/CVE-2022-48303.patch

diff --git a/meta/recipes-extended/tar/tar/CVE-2022-48303.patch 
b/meta/recipes-extended/tar/tar/CVE-2022-48303.patch
new file mode 100644
index 00..b2f40f3e64
--- /dev/null
+++ b/meta/recipes-extended/tar/tar/CVE-2022-48303.patch
@@ -0,0 +1,43 @@
+From 3da78400eafcccb97e2f2fd4b227ea40d794ede8 Mon Sep 17 00:00:00 2001
+From: Sergey Poznyakoff 
+Date: Sat, 11 Feb 2023 11:57:39 +0200
+Subject: Fix boundary checking in base-256 decoder
+
+* src/list.c (from_header): Base-256 encoding is at least 2 bytes
+long.
+
+Upstream-Status: Backport [see reference below]
+CVE: CVE-2022-48303
+
+Reference to upstream patch:
+https://savannah.gnu.org/bugs/?62387
+https://git.savannah.gnu.org/cgit/tar.git/patch/src/list.c?id=3da78400eafcccb97e2f2fd4b227ea40d794ede8
+
+Signed-off-by: Rodolfo Quesada Zumbado 
+Signed-off-by: Joe Slater 
+---
+ src/list.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)Signed-off-by: Rodolfo Quesada 
Zumbado 
+
+
+(limited to 'src/list.c')
+
+diff --git a/src/list.c b/src/list.c
+index 9fafc42..86bcfdd 100644
+--- a/src/list.c
 b/src/list.c
+@@ -881,8 +881,9 @@ from_header (char const *where0, size_t digs, char const 
*type,
+ where++;
+   }
+ }
+-  else if (*where == '\200' /* positive base-256 */
+- || *where == '\377' /* negative base-256 */)
++  else if (where <= lim - 2
++ && (*where == '\200' /* positive base-256 */
++ || *where == '\377' /* negative base-256 */))
+ {
+   /* Parse base-256 output.  A nonnegative number N is
+represented as (256**DIGS)/2 + N; a negative number -N is
+-- 
+cgit v1.1
+
diff --git a/meta/recipes-extended/tar/tar_1.34.bb 
b/meta/recipes-extended/tar/tar_1.34.bb
index 7307cd57a2..1ef5fe221e 100644
--- a/meta/recipes-extended/tar/tar_1.34.bb
+++ b/meta/recipes-extended/tar/tar_1.34.bb
@@ -6,7 +6,9 @@ SECTION = "base"
 LICENSE = "GPL-3.0-only"
 LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
 
-SRC_URI = "${GNU_MIRROR}/tar/tar-${PV}.tar.bz2"
+SRC_URI = "${GNU_MIRROR}/tar/tar-${PV}.tar.bz2 \
+   file://CVE-2022-48303.patch \
+"
 
 SRC_URI[sha256sum] = 
"b44cc67f8a1f6b0250b7c860e952b37e8ed932a90bd9b1862a511079255646ff"
 
-- 
2.34.1


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



[OE-core][kirkstone 22/23] oeqa qemurunner.py: try to avoid reading one character at a time

2023-02-21 Thread Steve Sakoman
From: Mikko Rapeli 

Read from serial console with a small delay to bundle data to e.g.
full lines. Reading one character at a time is not needed and causes
busy looping.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit 0049f6757f6f956fb4cc77b3df6a672c20b53cf4)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/utils/qemurunner.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index aa9e530f1b..925d05a339 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -647,6 +647,8 @@ class QemuRunner:
 except InterruptedError:
 continue
 if sread:
+# try to avoid reading single character at a time
+time.sleep(0.1)
 answer = self.server_socket.recv(1024)
 if answer:
 data += answer.decode('utf-8')
-- 
2.34.1


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



[OE-core][kirkstone 20/23] oeqa qemurunner: read more data at a time from serial

2023-02-21 Thread Steve Sakoman
From: Mikko Rapeli 

Use a short sleep to bundle serial console reads so that
we are not reading one character at a time which reduces busy
looping.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit cafe65d8cf7544edbd387f7f5f6d77c64c6b18fa)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/utils/qemurunner.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 9a99859388..fedabb189a 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -195,7 +195,7 @@ class QemuRunner:
 qmp_file = "." + next(tempfile._get_candidate_names())
 qmp_param = ' -S -qmp unix:./%s,server,wait' % (qmp_file)
 qmp_port = self.tmpdir + "/" + qmp_file
-# Create a second socket connection for debugging use, 
+# Create a second socket connection for debugging use,
 # note this will NOT cause qemu to block waiting for the connection
 qmp_file2 = "." + next(tempfile._get_candidate_names())
 qmp_param += ' -qmp unix:./%s,server,nowait' % (qmp_file2)
@@ -459,6 +459,8 @@ class QemuRunner:
 socklist.remove(self.server_socket)
 self.logger.debug("Connection from %s:%s" % addr)
 else:
+# try to avoid reading only a single character at a time
+time.sleep(0.1)
 data = data + sock.recv(1024)
 if data:
 bootlog += data
-- 
2.34.1


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



[OE-core][kirkstone 19/23] oeqa dump.py: add error counter and stop after 5 failures

2023-02-21 Thread Steve Sakoman
From: Mikko Rapeli 

If test target qemu machine hangs completely, dump_target() calls
over serial console are taking a long time to time out, possibly
for every failing ssh command execution and a lot of test cases,
and same with dump_monitor().

Instead of trying for ever, count errors and after 5 stop trying
to dump_target() and dump_monitor() completely.

These help to end testing earlier when a test target is completely
deadlocked and all ssh, serial and QMP communication with it are
failing.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit d9ad0a055abba983c6cee1dca4d2f0a8a3c48782)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/utils/dump.py | 23 +--
 1 file changed, 21 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/dump.py b/meta/lib/oeqa/utils/dump.py
index 95a79a571c..6fd5832051 100644
--- a/meta/lib/oeqa/utils/dump.py
+++ b/meta/lib/oeqa/utils/dump.py
@@ -91,37 +91,55 @@ class HostDumper(BaseDumper):
 self._write_dump(cmd.split()[0], result.output)
 
 class TargetDumper(BaseDumper):
-""" Class to get dumps from target, it only works with QemuRunner """
+""" Class to get dumps from target, it only works with QemuRunner.
+Will give up permanently after 5 errors from running commands over
+serial console. This helps to end testing when target is really dead, 
hanging
+or unresponsive.
+"""
 
 def __init__(self, cmds, parent_dir, runner):
 super(TargetDumper, self).__init__(cmds, parent_dir)
 self.runner = runner
+self.errors = 0
 
 def dump_target(self, dump_dir=""):
+if self.errors >= 5:
+print("Too many errors when dumping data from target, assuming 
it is dead! Will not dump data anymore!")
+return
 if dump_dir:
 self.dump_dir = dump_dir
 for cmd in self.cmds:
 # We can continue with the testing if serial commands fail
 try:
 (status, output) = self.runner.run_serial(cmd)
+if status == 0:
+self.errors = self.errors + 1
 self._write_dump(cmd.split()[0], output)
 except:
+self.errors = self.errors + 1
 print("Tried to dump info from target but "
 "serial console failed")
 print("Failed CMD: %s" % (cmd))
 
 class MonitorDumper(BaseDumper):
-""" Class to get dumps via the Qemu Monitor, it only works with QemuRunner 
"""
+""" Class to get dumps via the Qemu Monitor, it only works with QemuRunner
+Will stop completely if there are more than 5 errors when dumping 
monitor data.
+This helps to end testing when target is really dead, hanging or 
unresponsive.
+"""
 
 def __init__(self, cmds, parent_dir, runner):
 super(MonitorDumper, self).__init__(cmds, parent_dir)
 self.runner = runner
+self.errors = 0
 
 def dump_monitor(self, dump_dir=""):
 if self.runner is None:
 return
 if dump_dir:
 self.dump_dir = dump_dir
+if self.errors >= 5:
+print("Too many errors when dumping data from qemu monitor, 
assuming it is dead! Will not dump data anymore!")
+return
 for cmd in self.cmds:
 cmd_name = cmd.split()[0]
 try:
@@ -135,4 +153,5 @@ class MonitorDumper(BaseDumper):
 output = self.runner.run_monitor(cmd_name)
 self._write_dump(cmd_name, output)
 except Exception as e:
+self.errors = self.errors + 1
 print("Failed to dump QMP CMD: %s with\nException: %s" % 
(cmd_name, e))
-- 
2.34.1


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



[OE-core][kirkstone 18/23] oeqa ssh.py: add connection keep alive options to ssh client

2023-02-21 Thread Steve Sakoman
From: Mikko Rapeli 

Configure ssh client to test that connection with server is up.
If the server does not respond within a minute then the connection,
target machine or sshd daemon are stuck and it's better to exit
the command execution with errors.

Some tests can execute a long time without returning stdout/stderror
data and it's difficult to adjust timers for those cases if
connection to target machine or the target machine itself hangs
and output is not expected in minutes or even hours.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit ba68ff04c5786eca7cd8dd44056705867dea8ac4)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/core/target/ssh.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib/oeqa/core/target/ssh.py
index f1b9090bbf..48a463861d 100644
--- a/meta/lib/oeqa/core/target/ssh.py
+++ b/meta/lib/oeqa/core/target/ssh.py
@@ -34,6 +34,8 @@ class OESSHTarget(OETarget):
 self.timeout = timeout
 self.user = user
 ssh_options = [
+'-o', 'ServerAliveCountMax=2',
+'-o', 'ServerAliveInterval=30',
 '-o', 'UserKnownHostsFile=/dev/null',
 '-o', 'StrictHostKeyChecking=no',
 '-o', 'LogLevel=ERROR'
-- 
2.34.1


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



[OE-core][kirkstone 17/23] oeqa ssh.py: move output prints to new line

2023-02-21 Thread Steve Sakoman
From: Mikko Rapeli 

The output from is garbled otherwise and it's not
easy to remove debug output form real command output on target.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit 917a70cbc43ac1c70c477b220c4115735457ef04)
Signed-off-by: Steve Sakoman 
---
 meta/lib/oeqa/core/target/ssh.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib/oeqa/core/target/ssh.py
index f956a7744f..f1b9090bbf 100644
--- a/meta/lib/oeqa/core/target/ssh.py
+++ b/meta/lib/oeqa/core/target/ssh.py
@@ -240,7 +240,7 @@ def SSHCall(command, logger, timeout=None, **opts):
 eof = True
 else:
 output += data
-logger.debug('Partial data from SSH call: %s' % 
data)
+logger.debug('Partial data from SSH call:\n%s' % 
data)
 endtime = time.time() + timeout
 except InterruptedError:
 continue
@@ -256,12 +256,12 @@ def SSHCall(command, logger, timeout=None, **opts):
 endtime = time.time() - starttime
 lastline = ("\nProcess killed - no output for %d seconds. 
Total"
 " running time: %d seconds." % (timeout, endtime))
-logger.debug('Received data from SSH call %s ' % lastline)
+logger.debug('Received data from SSH call:\n%s ' % lastline)
 output += lastline
 
 else:
 output = process.communicate()[0].decode('utf-8', errors='ignore')
-logger.debug('Data from SSH call: %s' % output.rstrip())
+logger.debug('Data from SSH call:\n%s' % output.rstrip())
 
 options = {
 "stdout": subprocess.PIPE,
-- 
2.34.1


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



[OE-core][kirkstone 16/23] devshell: Do not add scripts/git-intercept to PATH

2023-02-21 Thread Steve Sakoman
From: Peter Kjellerstedt 

The use of scripts/git-intercept was introduced in commit 3266c327df
(install/devshell: Introduce git intercept script due to fakeroot
issues) and later reverted in commit af27c81eaf (scripts: Make git
intercept global).

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Luca Ceresoli 
(cherry picked from commit f6c260c8e2a33e282a35afc99de4ef8cc1791b08)
Signed-off-by: Steve Sakoman 
---
 meta/classes/devshell.bbclass | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/classes/devshell.bbclass b/meta/classes/devshell.bbclass
index 247d04478c..26c01c080a 100644
--- a/meta/classes/devshell.bbclass
+++ b/meta/classes/devshell.bbclass
@@ -2,8 +2,6 @@ inherit terminal
 
 DEVSHELL = "${SHELL}"
 
-PATH:prepend:task-devshell = "${COREBASE}/scripts/git-intercept:"
-
 python do_devshell () {
 if d.getVarFlag("do_devshell", "manualfakeroot"):
d.prependVar("DEVSHELL", "pseudo ")
-- 
2.34.1


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



[OE-core][kirkstone 15/23] image.bbclass: print all QA functions exceptions

2023-02-21 Thread Steve Sakoman
From: Mauro Queiros 

For the QA checks in `image.bbclass`, all exceptions
other than `oe.utils.ImageQAFailed` always print the
following generic message:
"Image QA function func_name failed"

This can be very misleading, as it may hide
python syntax errors and other kind of issues that are
hard to detect without more explicit error messages.

This change makes sure that the error message of all
exceptions are displayed.

Before this change:
 "Image QA function func_name failed"

After this change:
 "Image QA function func_name failed: f-string: empty expression not allowed 
(, line 13)"

Signed-off-by: Mauro Queiros 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit 3d85b30d8704d38b86f5b006748cebc74bd2a4fa)
Signed-off-by: Steve Sakoman 
---
 meta/classes/image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index aa14ea2316..00413d56d1 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -313,7 +313,7 @@ fakeroot python do_image_qa () {
 except oe.utils.ImageQAFailed as e:
 qamsg = qamsg + '\tImage QA function %s failed: %s\n' % (e.name, 
e.description)
 except Exception as e:
-qamsg = qamsg + '\tImage QA function %s failed\n' % cmd
+qamsg = qamsg + '\tImage QA function %s failed: %s\n' % (cmd, e)
 
 if qamsg:
 imgname = d.getVar('IMAGE_NAME')
-- 
2.34.1


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



[OE-core][kirkstone 14/23] update-alternatives: fix typos

2023-02-21 Thread Steve Sakoman
From: Ulrich Ölmann 

Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit d3ca05b072c152b76a86edaaddebabdef312ea95)
Signed-off-by: Steve Sakoman 
---
 meta/classes/update-alternatives.bbclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/classes/update-alternatives.bbclass 
b/meta/classes/update-alternatives.bbclass
index fc1ffd828c..7581a70439 100644
--- a/meta/classes/update-alternatives.bbclass
+++ b/meta/classes/update-alternatives.bbclass
@@ -1,5 +1,5 @@
 # This class is used to help the alternatives system which is useful when
-# multiple sources provide same command. You can use update-alternatives
+# multiple sources provide the same command. You can use update-alternatives
 # command directly in your recipe, but in most cases this class simplifies
 # that job.
 #
@@ -29,7 +29,7 @@
 # A non-default link to create for a target
 # ALTERNATIVE_TARGET[name] = "target"
 #
-#   This is the name of the binary as it's been install by do_install
+#   This is the name of the binary as it's been installed by do_install
 #   i.e. ALTERNATIVE_TARGET[sh] = "/bin/bash"
 #
 # A package specific link for a target
@@ -62,7 +62,7 @@ ALTERNATIVE_PRIORITY = "10"
 
 # We need special processing for vardeps because it can not work on
 # modified flag values.  So we aggregate the flags into a new variable
-# and include that vairable in the set.
+# and include that variable in the set.
 UPDALTVARS  = "ALTERNATIVE ALTERNATIVE_LINK_NAME ALTERNATIVE_TARGET 
ALTERNATIVE_PRIORITY"
 
 PACKAGE_WRITE_DEPS += "virtual/update-alternatives-native"
-- 
2.34.1


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



[OE-core][kirkstone 13/23] qemu: fix compile error

2023-02-21 Thread Steve Sakoman
From: Kai Kang 

Backport 2 patches and rebase
0001-hw-display-qxl-Pass-requested-buffer-size-to-qxl_phy.patch to fix
compile error:

../qemu-6.2.0/hw/display/qxl.c: In function 'qxl_phys2virt':
../qemu-6.2.0/hw/display/qxl.c:1477:67: error: 'size' undeclared (first use in 
this function); did you mean 'gsize'?
 1477 | if (!qxl_get_check_slot_offset(qxl, pqxl, , , 
size)) {
  |   ^~~~
  |   gsize
../qemu-6.2.0/hw/display/qxl.c:1477:67: note: each undeclared identifier is 
reported only once for each function it appears in

Signed-off-by: Kai Kang 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/qemu/qemu.inc   |   2 +
 ...ave-qxl_log_command-Return-early-if-.patch |  57 +
 ...ass-requested-buffer-size-to-qxl_phy.patch | 217 ++
 3 files changed, 276 insertions(+)
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Have-qxl_log_command-Return-early-if-.patch
 create mode 100644 
meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Pass-requested-buffer-size-to-qxl_phy.patch

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index b68be447f1..5430718f75 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -93,6 +93,8 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://0021-target-ppc-implement-xs-n-maddqp-o-xs-n-msubqp-o.patch \
file://CVE-2022-3165.patch \
file://CVE-2022-4144.patch \
+   
file://0001-hw-display-qxl-Have-qxl_log_command-Return-early-if-.patch \
+   
file://0001-hw-display-qxl-Pass-requested-buffer-size-to-qxl_phy.patch \
"
 UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
 
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Have-qxl_log_command-Return-early-if-.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Have-qxl_log_command-Return-early-if-.patch
new file mode 100644
index 00..cd846222c9
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Have-qxl_log_command-Return-early-if-.patch
@@ -0,0 +1,57 @@
+Upstream-Status: Backport [https://github.com/qemu/qemu/commit/61c34fc]
+
+Signed-off-by: Kai Kang 
+
+From 61c34fc194b776ecadc39fb26b061331107e5599 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Philippe=20Mathieu-Daud=C3=A9?= 
+Date: Mon, 28 Nov 2022 21:27:37 +0100
+Subject: [PATCH] hw/display/qxl: Have qxl_log_command Return early if no
+ log_cmd handler
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Only 3 command types are logged: no need to call qxl_phys2virt()
+for the other types. Using different cases will help to pass
+different structure sizes to qxl_phys2virt() in a pair of commits.
+
+Reviewed-by: Marc-André Lureau 
+Signed-off-by: Philippe Mathieu-Daudé 
+Signed-off-by: Stefan Hajnoczi 
+Message-Id: <20221128202741.4945-2-phi...@linaro.org>
+---
+ hw/display/qxl-logger.c | 11 +++
+ 1 file changed, 11 insertions(+)
+
+diff --git a/hw/display/qxl-logger.c b/hw/display/qxl-logger.c
+index 68bfa47568..1bcf803db6 100644
+--- a/hw/display/qxl-logger.c
 b/hw/display/qxl-logger.c
+@@ -247,6 +247,16 @@ int qxl_log_command(PCIQXLDevice *qxl, const char *ring, 
QXLCommandExt *ext)
+ qxl_name(qxl_type, ext->cmd.type),
+ compat ? "(compat)" : "");
+ 
++switch (ext->cmd.type) {
++case QXL_CMD_DRAW:
++break;
++case QXL_CMD_SURFACE:
++break;
++case QXL_CMD_CURSOR:
++break;
++default:
++goto out;
++}
+ data = qxl_phys2virt(qxl, ext->cmd.data, ext->group_id);
+ if (!data) {
+ return 1;
+@@ -269,6 +279,7 @@ int qxl_log_command(PCIQXLDevice *qxl, const char *ring, 
QXLCommandExt *ext)
+ qxl_log_cmd_cursor(qxl, data, ext->group_id);
+ break;
+ }
++out:
+ fprintf(stderr, "\n");
+ return 0;
+ }
+-- 
+2.34.1
+
diff --git 
a/meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Pass-requested-buffer-size-to-qxl_phy.patch
 
b/meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Pass-requested-buffer-size-to-qxl_phy.patch
new file mode 100644
index 00..ac51cf567a
--- /dev/null
+++ 
b/meta/recipes-devtools/qemu/qemu/0001-hw-display-qxl-Pass-requested-buffer-size-to-qxl_phy.patch
@@ -0,0 +1,217 @@
+Upstream-Status: Backport [https://github.com/qemu/qemu/commit/8efec0e]
+
+Backport and rebase patch to fix compile error which imported by 
CVE-2022-4144.patch:
+
+../qemu-6.2.0/hw/display/qxl.c: In function 'qxl_phys2virt':
+../qemu-6.2.0/hw/display/qxl.c:1477:67: error: 'size' undeclared (first use in 
this function); did you mean 'gsize'?
+   1477 | if (!qxl_get_check_slot_offset(qxl, pqxl, , 
, size)) {
+   |   
^~~~
+

[OE-core][kirkstone 12/23] libgit2: upgrade 1.4.4 -> 1.4.5

2023-02-21 Thread Steve Sakoman
Fixes:

libgit2, when compiled using the optional, included libssh2 backend, fails to 
verify SSH keys by default.

Description
When using an SSH remote with the optional, included libssh2 backend, libgit2 
does not perform certificate checking by default. Prior versions of libgit2 
require the caller to set the certificate_check field of libgit2's 
git_remote_callbacks structure - if a certificate check callback is not set, 
libgit2 does not perform any certificate checking. This means that by default - 
without configuring a certificate check callback, clients will not perform 
validation on the server SSH keys and may be subject to a man-in-the-middle 
attack.

Beginning in libgit2 v1.4.5 and v1.5.1, libgit2 will now perform host key 
checking by default. Users can still override the default behavior using the 
certificate_check function.

The libgit2 security team would like to thank the Julia and Rust security teams 
for responsibly disclosing this vulnerability and assisting with fixing the 
vulnerability.

Signed-off-by: Steve Sakoman 
---
 .../libgit2/{libgit2_1.4.4.bb => libgit2_1.4.5.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/libgit2/{libgit2_1.4.4.bb => libgit2_1.4.5.bb} 
(91%)

diff --git a/meta/recipes-support/libgit2/libgit2_1.4.4.bb 
b/meta/recipes-support/libgit2/libgit2_1.4.5.bb
similarity index 91%
rename from meta/recipes-support/libgit2/libgit2_1.4.4.bb
rename to meta/recipes-support/libgit2/libgit2_1.4.5.bb
index a6f4d8d7f2..aadfe4ad02 100644
--- a/meta/recipes-support/libgit2/libgit2_1.4.4.bb
+++ b/meta/recipes-support/libgit2/libgit2_1.4.5.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=e5a9227de4cb6afb5d35ed7b0fdf480d"
 DEPENDS = "curl openssl zlib libssh2 libgcrypt libpcre2"
 
 SRC_URI = 
"git://github.com/libgit2/libgit2.git;branch=maint/v1.4;protocol=https"
-SRCREV = "3b7d756ccfaf9ec2922d2db22e6cc98f8ab6580c"
+SRCREV = "cd6f679af401eda1f172402006ef8265f8bd58ea"
 
 S = "${WORKDIR}/git"
 
-- 
2.34.1


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



[OE-core][kirkstone 11/23] libgit2: uprade 1.4.3 -> 1.4.4

2023-02-21 Thread Steve Sakoman
This is a security release with multiple changes.

This provides compatibility with git's changes to address CVE 2022-29187. As a 
follow up to CVE 2022-24765, now not only is the working directory of a 
non-bare repository examined for its ownership, but the .git directory and the 
.git file (if present) are also examined for their ownership.

A fix for compatibility with git's (new) behavior for CVE 2022-24765 allows 
users on POSIX systems to access a git repository that is owned by them when 
they are running in sudo.

A fix for further compatibility with git's (existing) behavior for CVE 
2022-24765 allows users on Windows to access a git repository that is owned by 
the Administrator when running with escalated privileges (using runas 
Administrator).

The bundled zlib is updated to v1.2.12, as prior versions had memory corruption 
bugs. It is not known that there is a security vulnerability in libgit2 based 
on these bugs, but we are updating to be cautious.

Signed-off-by: Steve Sakoman 
---
 .../libgit2/{libgit2_1.4.3.bb => libgit2_1.4.4.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/libgit2/{libgit2_1.4.3.bb => libgit2_1.4.4.bb} 
(91%)

diff --git a/meta/recipes-support/libgit2/libgit2_1.4.3.bb 
b/meta/recipes-support/libgit2/libgit2_1.4.4.bb
similarity index 91%
rename from meta/recipes-support/libgit2/libgit2_1.4.3.bb
rename to meta/recipes-support/libgit2/libgit2_1.4.4.bb
index 7e27b5b018..a6f4d8d7f2 100644
--- a/meta/recipes-support/libgit2/libgit2_1.4.3.bb
+++ b/meta/recipes-support/libgit2/libgit2_1.4.4.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=e5a9227de4cb6afb5d35ed7b0fdf480d"
 DEPENDS = "curl openssl zlib libssh2 libgcrypt libpcre2"
 
 SRC_URI = 
"git://github.com/libgit2/libgit2.git;branch=maint/v1.4;protocol=https"
-SRCREV = "465bbf88ea939a965fbcbade72870c61f815e457"
+SRCREV = "3b7d756ccfaf9ec2922d2db22e6cc98f8ab6580c"
 
 S = "${WORKDIR}/git"
 
-- 
2.34.1


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



[OE-core][kirkstone 10/23] sudo: upgrade 1.9.12p1 -> 1.9.12p2

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

Changes:

Fixed a compilation error on Linux/aarch64. GitHub issue #197.

Fixed a potential crash introduced in the fix GitHub issue #134. If a user’s 
sudoers entry did not have any RunAs user’s set, running sudo -U otheruser -l 
would dereference a NULL pointer.

Fixed a bug introduced in sudo 1.9.12 that could prevent sudo from creating a 
I/O files when the iolog_file sudoers setting contains six or more Xs.

Fixed a compilation issue on AIX with the native compiler. GitHub issue #231.

Fixed CVE-2023-22809, a flaw in sudo’s -e option (aka sudoedit) that could 
allow a malicious user with sudoedit privileges to edit arbitrary files

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit 5a3f5f4f607f5e06af772287109b68579154fb2f)
Signed-off-by: Steve Sakoman 
(cherry picked from commit cd1b6167242003c79b39d8761ea0f36db41f0671)
Signed-off-by: Steve Sakoman 
---
 .../sudo/{sudo_1.9.12p1.bb => sudo_1.9.12p2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/sudo/{sudo_1.9.12p1.bb => sudo_1.9.12p2.bb} (96%)

diff --git a/meta/recipes-extended/sudo/sudo_1.9.12p1.bb 
b/meta/recipes-extended/sudo/sudo_1.9.12p2.bb
similarity index 96%
rename from meta/recipes-extended/sudo/sudo_1.9.12p1.bb
rename to meta/recipes-extended/sudo/sudo_1.9.12p2.bb
index 1495b67b8b..ae7207c081 100644
--- a/meta/recipes-extended/sudo/sudo_1.9.12p1.bb
+++ b/meta/recipes-extended/sudo/sudo_1.9.12p2.bb
@@ -8,7 +8,7 @@ SRC_URI = "https://www.sudo.ws/dist/sudo-${PV}.tar.gz \
 
 PAM_SRC_URI = "file://sudo.pam"
 
-SRC_URI[sha256sum] = 
"475a18a8eb3da8b2917ceab063a6baf51ea09128c3c47e3e0e33ab7497bab7d8"
+SRC_URI[sha256sum] = 
"b9a0b1ae0f1ddd9be7f3eafe70be05ee81f572f6f536632c44cd4101bb2a8539"
 
 DEPENDS += " virtual/crypt ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 
'libpam', '', d)}"
 RDEPENDS:${PN} += " ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 
'pam-plugin-limits pam-plugin-keyinit', '', d)}"
-- 
2.34.1


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



[OE-core][kirkstone 09/23] git: upgrade 2.35.6 -> 2.35.7

2023-02-21 Thread Steve Sakoman
From: Sakib Sajal 

Upgrade git to latest 2.37.x release to address
security issues CVE-2022-23521 and CVE-2022-41903.

Signed-off-by: Sakib Sajal 
Signed-off-by: Steve Sakoman 
---
 meta/recipes-devtools/git/{git_2.35.6.bb => git_2.35.7.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/git/{git_2.35.6.bb => git_2.35.7.bb} (98%)

diff --git a/meta/recipes-devtools/git/git_2.35.6.bb 
b/meta/recipes-devtools/git/git_2.35.7.bb
similarity index 98%
rename from meta/recipes-devtools/git/git_2.35.6.bb
rename to meta/recipes-devtools/git/git_2.35.7.bb
index 0bb4a6a021..7cc8e5722b 100644
--- a/meta/recipes-devtools/git/git_2.35.6.bb
+++ b/meta/recipes-devtools/git/git_2.35.7.bb
@@ -167,4 +167,4 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
  "
 EXTRA_OEMAKE += "NO_GETTEXT=1"
 
-SRC_URI[tarball.sha256sum] = 
"6bd51e0487028543ba40fe3d5b33bd124526a7f7109824aa7f022e79edf93bd1"
+SRC_URI[tarball.sha256sum] = 
"fc849272a95cc7457091221a645fcd753b3b1984767ee3323fb6a0aa944bbcb4"
-- 
2.34.1


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



[OE-core][kirkstone 08/23] linux-firmware: upgrade 20221214 -> 20230117

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

License-Update: additional firmwares, copyright years

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit fdb8c12fc71b4a985372f5d02ce59a1402c14c4a)
Signed-off-by: Steve Sakoman 
---
 ...inux-firmware_20221214.bb => linux-firmware_20230117.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-kernel/linux-firmware/{linux-firmware_20221214.bb => 
linux-firmware_20230117.bb} (99%)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20221214.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_20230117.bb
similarity index 99%
rename from meta/recipes-kernel/linux-firmware/linux-firmware_20221214.bb
rename to meta/recipes-kernel/linux-firmware/linux-firmware_20230117.bb
index c2354e627f..1dce06c8f5 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20221214.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20230117.bb
@@ -70,7 +70,7 @@ LICENSE = "\
 LIC_FILES_CHKSUM = "file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc 
\
 
file://LICENCE.adsp_sst;md5=615c45b91a5a4a9fe046d6ab9a2df728 \
 file://LICENCE.agere;md5=af0133de6b4a9b2522defd5f188afd31 \
-file://LICENSE.amdgpu;md5=44c1166d052226cb2d6c8d7400090203 
\
+file://LICENSE.amdgpu;md5=a2589a05ea5b6bd2b7f4f623c7e7a649 
\
 
file://LICENSE.amd-ucode;md5=6ca90c57f7b248de1e25c7f68ffc4698 \
 
file://LICENSE.amlogic_vdec;md5=dc44f59bf64a81643e500ad3f39a468a \
 
file://LICENCE.atheros_firmware;md5=30a14c7823beedac9fa39c64fdd01a13 \
@@ -132,7 +132,7 @@ LIC_FILES_CHKSUM = 
"file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc \
 "
 # WHENCE checksum is defined separately to ease overriding it if
 # class-devupstream is selected.
-WHENCE_CHKSUM  = "bf7c716d16e48fe118c6209f99b13253"
+WHENCE_CHKSUM  = "05f1d941972cedadbf667c05f6010378"
 
 # These are not common licenses, set NO_GENERIC_LICENSE for them
 # so that the license files will be copied from fetched source
@@ -209,7 +209,7 @@ SRC_URI:class-devupstream = 
"git://git.kernel.org/pub/scm/linux/kernel/git/firmw
 # Pin this to the 20220509 release, override this in local.conf
 SRCREV:class-devupstream ?= "b19cbdca78ab2adfd210c91be15a22568e8b8cae"
 
-SRC_URI[sha256sum] = 
"e793783e92acbde549965521462d1d1327827360664cf242dbda08f075654331"
+SRC_URI[sha256sum] = 
"df11e25ba2fb4d5343473757e17a3b4cef599250a26b1f7e0f038850f0cb3d64"
 
 inherit allarch
 
-- 
2.34.1


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



[OE-core][kirkstone 05/23] apr-util: update 1.6.1 -> 1.6.3

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

Changes with APR-util 1.6.3

  *) Correct a packaging issue in 1.6.2. The contents of the release were
 correct, but the top level directory was misnamed.

Changes with APR-util 1.6.2

  *) SECURITY: CVE-2022-25147 (cve.mitre.org)
 Integer Overflow or Wraparound vulnerability in apr_base64 functions
 of Apache Portable Runtime Utility (APR-util) allows an attacker to
 write beyond bounds of a buffer.

  *) Teach configure how to find and build against MariaDB 10.2. PR 61517
 [Kris Karas ]

  *) apr_crypto_commoncrypto: Remove stray reference to -lcrypto that
 prevented commoncrypto being enabled. [Graham Leggett]

  *) Add --tag=CC to libtool invocations. PR 62640. [Michael Osipov]

  *) apr_dbm_gdbm: Fix handling of error codes. This makes gdbm 1.14 work.
 apr_dbm_gdbm will now also return error codes starting with
 APR_OS_START_USEERR, as apr_dbm_berkleydb does, instead of always
 returning APR_EGENERAL. [Stefan Fritsch]

Drop backport.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit dca707f9fecc805503e17f6db3e4c88069ac0125)
Signed-off-by: Steve Sakoman 
(cherry picked from commit 43cd36b178ebb602edd5919c26f8b8642736a3a8)
Signed-off-by: Steve Sakoman 
---
 .../0001-Fix-error-handling-in-gdbm.patch | 134 --
 .../{apr-util_1.6.1.bb => apr-util_1.6.3.bb}  |   6 +-
 2 files changed, 2 insertions(+), 138 deletions(-)
 delete mode 100644 
meta/recipes-support/apr/apr-util/0001-Fix-error-handling-in-gdbm.patch
 rename meta/recipes-support/apr/{apr-util_1.6.1.bb => apr-util_1.6.3.bb} (94%)

diff --git 
a/meta/recipes-support/apr/apr-util/0001-Fix-error-handling-in-gdbm.patch 
b/meta/recipes-support/apr/apr-util/0001-Fix-error-handling-in-gdbm.patch
deleted file mode 100644
index 6f27876a7f..00
--- a/meta/recipes-support/apr/apr-util/0001-Fix-error-handling-in-gdbm.patch
+++ /dev/null
@@ -1,134 +0,0 @@
-From 6b638fa9afbeb54dfa19378e391465a5284ce1ad Mon Sep 17 00:00:00 2001
-From: Changqing Li 
-Date: Wed, 12 Sep 2018 17:16:36 +0800
-Subject: [PATCH] Fix error handling in gdbm
-
-Only check for gdbm_errno if the return value of the called gdbm_*
-function says so. This fixes apr-util with gdbm 1.14, which does not
-seem to always reset gdbm_errno.
-
-Also make the gdbm driver return error codes starting with
-APR_OS_START_USEERR instead of always returning APR_EGENERAL. This is
-what the berkleydb driver already does.
-
-Also ensure that dsize is 0 if dptr == NULL.
-
-Upstream-Status: Backport 
[https://svn.apache.org/viewvc?view=revisionrevision=1825311]
-
-Signed-off-by: Changqing Li 

- dbm/apr_dbm_gdbm.c | 47 +--
- 1 file changed, 29 insertions(+), 18 deletions(-)
-
-diff --git a/dbm/apr_dbm_gdbm.c b/dbm/apr_dbm_gdbm.c
-index 749447a..1c86327 100644
 a/dbm/apr_dbm_gdbm.c
-+++ b/dbm/apr_dbm_gdbm.c
-@@ -36,13 +36,25 @@
- static apr_status_t g2s(int gerr)
- {
- if (gerr == -1) {
--/* ### need to fix this */
--return APR_EGENERAL;
-+if (gdbm_errno == GDBM_NO_ERROR)
-+   return APR_SUCCESS;
-+return APR_OS_START_USEERR + gdbm_errno;
- }
- 
- return APR_SUCCESS;
- }
- 
-+static apr_status_t gdat2s(datum d)
-+{
-+if (d.dptr == NULL) {
-+if (gdbm_errno == GDBM_NO_ERROR || gdbm_errno == GDBM_ITEM_NOT_FOUND)
-+   return APR_SUCCESS;
-+return APR_OS_START_USEERR + gdbm_errno;
-+   }
-+
-+return APR_SUCCESS;
-+}
-+
- static apr_status_t datum_cleanup(void *dptr)
- {
- if (dptr)
-@@ -53,22 +65,15 @@ static apr_status_t datum_cleanup(void *dptr)
- 
- static apr_status_t set_error(apr_dbm_t *dbm, apr_status_t dbm_said)
- {
--apr_status_t rv = APR_SUCCESS;
- 
--/* ### ignore whatever the DBM said (dbm_said); ask it explicitly */
-+dbm->errcode = dbm_said;  
- 
--if ((dbm->errcode = gdbm_errno) == GDBM_NO_ERROR) {
-+if (dbm_said == APR_SUCCESS)
- dbm->errmsg = NULL;
--}
--else {
--dbm->errmsg = gdbm_strerror(gdbm_errno);
--rv = APR_EGENERAL;/* ### need something better */
--}
--
--/* captured it. clear it now. */
--gdbm_errno = GDBM_NO_ERROR;
-+else
-+dbm->errmsg = gdbm_strerror(dbm_said - APR_OS_START_USEERR);
- 
--return rv;
-+return dbm_said;
- }
- 
- /* --
-@@ -107,7 +112,7 @@ static apr_status_t vt_gdbm_open(apr_dbm_t **pdb, const 
char *pathname,
-  NULL);
- 
- if (file == NULL)
--return APR_EGENERAL;  /* ### need a better error */
-+return APR_OS_START_USEERR + gdbm_errno;   /* ### need a better error 
*/
- 
- /* we have an open database... return it */
- *pdb = apr_pcalloc(pool, sizeof(**pdb));
-@@ -141,10 +146,12 @@ static apr_status_t vt_gdbm_fetch(apr_dbm_t *dbm, 
apr_datum_t key,
- if (pvalue->dptr)

[OE-core][kirkstone 06/23] bind: upgrade 9.18.10 -> 9.18.11

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

Stable branch update

License-update: copyright years

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit 63e8a8952c3d1b3b5c481be6bba52a3f4d65648e)
Signed-off-by: Steve Sakoman 
(cherry picked from commit 54e2de8a589766c9a305c9bd0782afb5353fd109)
Signed-off-by: Steve Sakoman 
---
 .../0001-avoid-start-failure-with-bind-user.patch | 0
 ...0001-named-lwresd-V-and-start-log-hide-build-options.patch | 0
 ...bind-ensure-searching-for-json-headers-searches-sysr.patch | 0
 .../bind/{bind-9.18.10 => bind-9.18.11}/bind9 | 0
 .../bind/{bind-9.18.10 => bind-9.18.11}/conf.patch| 0
 .../bind/{bind-9.18.10 => bind-9.18.11}/generate-rndc-key.sh  | 0
 .../init.d-add-support-for-read-only-rootfs.patch | 0
 .../make-etc-initd-bind-stop-work.patch   | 0
 .../bind/{bind-9.18.10 => bind-9.18.11}/named.service | 0
 .../bind/{bind_9.18.10.bb => bind_9.18.11.bb} | 4 ++--
 10 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-avoid-start-failure-with-bind-user.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => bind-9.18.11}/bind9 
(100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/generate-rndc-key.sh (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/init.d-add-support-for-read-only-rootfs.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/make-etc-initd-bind-stop-work.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/named.service (100%)
 rename meta/recipes-connectivity/bind/{bind_9.18.10.bb => bind_9.18.11.bb} 
(96%)

diff --git 
a/meta/recipes-connectivity/bind/bind-9.18.10/0001-avoid-start-failure-with-bind-user.patch
 
b/meta/recipes-connectivity/bind/bind-9.18.11/0001-avoid-start-failure-with-bind-user.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.18.10/0001-avoid-start-failure-with-bind-user.patch
rename to 
meta/recipes-connectivity/bind/bind-9.18.11/0001-avoid-start-failure-with-bind-user.patch
diff --git 
a/meta/recipes-connectivity/bind/bind-9.18.10/0001-named-lwresd-V-and-start-log-hide-build-options.patch
 
b/meta/recipes-connectivity/bind/bind-9.18.11/0001-named-lwresd-V-and-start-log-hide-build-options.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.18.10/0001-named-lwresd-V-and-start-log-hide-build-options.patch
rename to 
meta/recipes-connectivity/bind/bind-9.18.11/0001-named-lwresd-V-and-start-log-hide-build-options.patch
diff --git 
a/meta/recipes-connectivity/bind/bind-9.18.10/bind-ensure-searching-for-json-headers-searches-sysr.patch
 
b/meta/recipes-connectivity/bind/bind-9.18.11/bind-ensure-searching-for-json-headers-searches-sysr.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.18.10/bind-ensure-searching-for-json-headers-searches-sysr.patch
rename to 
meta/recipes-connectivity/bind/bind-9.18.11/bind-ensure-searching-for-json-headers-searches-sysr.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.18.10/bind9 
b/meta/recipes-connectivity/bind/bind-9.18.11/bind9
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.18.10/bind9
rename to meta/recipes-connectivity/bind/bind-9.18.11/bind9
diff --git a/meta/recipes-connectivity/bind/bind-9.18.10/conf.patch 
b/meta/recipes-connectivity/bind/bind-9.18.11/conf.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.18.10/conf.patch
rename to meta/recipes-connectivity/bind/bind-9.18.11/conf.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.18.10/generate-rndc-key.sh 
b/meta/recipes-connectivity/bind/bind-9.18.11/generate-rndc-key.sh
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.18.10/generate-rndc-key.sh
rename to meta/recipes-connectivity/bind/bind-9.18.11/generate-rndc-key.sh
diff --git 
a/meta/recipes-connectivity/bind/bind-9.18.10/init.d-add-support-for-read-only-rootfs.patch
 
b/meta/recipes-connectivity/bind/bind-9.18.11/init.d-add-support-for-read-only-rootfs.patch
similarity index 100%
rename from 
meta/recipes-connectivity/bind/bind-9.18.10/init.d-add-support-for-read-only-rootfs.patch
rename to 
meta/recipes-connectivity/bind/bind-9.18.11/init.d-add-support-for-read-only-rootfs.patch
diff --git 
a/meta/recipes-connectivity/bind/bind-9.18.10/make-etc-initd-bind-stop-work.patch
 

[OE-core][kirkstone 03/23] lttng-tools: update 2.13.8 -> 2.13.9

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

2023-01-13 (National Sticker Day) LTTng modules 2.13.8
* fix: jbd2: use the correct print format
* Fix: in_x32_syscall was introduced in v4.7.0
* Explicitly skip tracing x32 system calls
* fix: kallsyms wrapper on ppc64el
* fix: Adjust ranges for RHEL 8.6 kernels
* fix: kvm-x86 requires CONFIG_KALLSYMS_ALL
* fix: mm/slab_common: drop kmem_alloc & avoid dereferencing fields 
when not using (v6.1)

Drop determinism.patch as issue resolved upstream via linked ticket.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit cd9e72a390efb778a6278e2e6c9604ab29d6feb9)
Signed-off-by: Steve Sakoman 
(cherry picked from commit 812fb8f02b25bfd30f6d9640cf3b50131d68e0b1)
Signed-off-by: Steve Sakoman 
---
 .../lttng/lttng-tools/determinism.patch   | 64 ---
 ...-tools_2.13.8.bb => lttng-tools_2.13.9.bb} |  3 +-
 2 files changed, 1 insertion(+), 66 deletions(-)
 delete mode 100644 meta/recipes-kernel/lttng/lttng-tools/determinism.patch
 rename meta/recipes-kernel/lttng/{lttng-tools_2.13.8.bb => 
lttng-tools_2.13.9.bb} (98%)

diff --git a/meta/recipes-kernel/lttng/lttng-tools/determinism.patch 
b/meta/recipes-kernel/lttng/lttng-tools/determinism.patch
deleted file mode 100644
index 0a897a8e13..00
--- a/meta/recipes-kernel/lttng/lttng-tools/determinism.patch
+++ /dev/null
@@ -1,64 +0,0 @@
-This is a bit ugly. Specifing abs_builddir as an RPATH is plain wrong when
-cross compiling. Sadly, removing the rpath makes libtool/automake do
-weird things and breaks the build as shared libs are no longer generated.
-
-We already try and delete the RPATH at do_install with chrpath however
-that does leave the path in the string table so it doesn't help us
-with reproducibility.
-
-Instead, hack in a bogus but harmless path, then delete it later in
-our do_install. Ultimately we may want to pass a specific path to use
-to configure if we really do need to set an RPATH at all. It is unclear
-to me whether the tests need that or not.
-
-Fixes reproducibility issues for lttng-tools.
-
-Upstream-Status: Submitted [https://bugs.lttng.org/issues/1361 - needs 
discussion with upstream about the correct solution]
-RP 2021/3/1
-
-Index: lttng-tools-2.12.2/tests/regression/ust/ust-dl/Makefile.am
-===
 lttng-tools-2.12.2.orig/tests/regression/ust/ust-dl/Makefile.am
-+++ lttng-tools-2.12.2/tests/regression/ust/ust-dl/Makefile.am
-@@ -27,16 +27,16 @@ noinst_LTLIBRARIES = libzzz.la libbar.la
- 
- libzzz_la_SOURCES = libzzz.c libzzz.h
- libzzz_la_LDFLAGS = -module -shared -avoid-version \
--  -rpath $(abs_builddir)
-+  -rpath /usr/lib
- 
- libbar_la_SOURCES = libbar.c libbar.h
- libbar_la_LDFLAGS = -module -shared -avoid-version \
--  -rpath $(abs_builddir)
-+  -rpath /usr/lib
- libbar_la_LIBADD = libzzz.la
- 
- libfoo_la_SOURCES = libfoo.c libfoo.h
- libfoo_la_LDFLAGS = -module -shared -avoid-version \
--  -rpath $(abs_builddir)
-+  -rpath /usr/lib
- libfoo_la_LIBADD = libbar.la
- 
- CLEANFILES = libfoo.so libfoo.so.debug libbar.so libbar.so.debug \
-@@ -44,7 +44,7 @@ CLEANFILES = libfoo.so libfoo.so.debug l
- 
- libtp_la_SOURCES = libbar-tp.h libbar-tp.c libfoo-tp.h libfoo-tp.c \
-   libzzz-tp.h libzzz-tp.c
--libtp_la_LDFLAGS = -module -shared -rpath $(abs_builddir)
-+libtp_la_LDFLAGS = -module -shared -rpath /usr/lib
- 
- # Extract debug symbols
- libfoo.so.debug: libfoo.la
-Index: 
lttng-tools-2.12.2/tests/utils/testapp/userspace-probe-elf-binary/Makefile.am
-===
 
lttng-tools-2.12.2.orig/tests/utils/testapp/userspace-probe-elf-binary/Makefile.am
-+++ 
lttng-tools-2.12.2/tests/utils/testapp/userspace-probe-elf-binary/Makefile.am
-@@ -5,7 +5,7 @@ AM_CFLAGS += -O0
- noinst_LTLIBRARIES = libfoo.la
- 
- libfoo_la_SOURCES = foo.c foo.h
--libfoo_la_LDFLAGS = -shared -module -avoid-version -rpath 
$(abs_builddir)/.libs/
-+libfoo_la_LDFLAGS = -shared -module -avoid-version -rpath /usr/lib
- 
- noinst_PROGRAMS = userspace-probe-elf-binary
- userspace_probe_elf_binary_SOURCES = userspace-probe-elf-binary.c
diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb 
b/meta/recipes-kernel/lttng/lttng-tools_2.13.9.bb
similarity index 98%
rename from meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
rename to meta/recipes-kernel/lttng/lttng-tools_2.13.9.bb
index a814eb79f9..1f6929e307 100644
--- a/meta/recipes-kernel/lttng/lttng-tools_2.13.8.bb
+++ b/meta/recipes-kernel/lttng/lttng-tools_2.13.9.bb
@@ -35,11 +35,10 @@ SRC_URI = 
"https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \
file://0001-tests-do-not-strip-a-helper-library.patch \
file://run-ptest \
file://lttng-sessiond.service \
-   file://determinism.patch \
 

[OE-core][kirkstone 02/23] diffutils: update 3.8 -> 3.9

2023-02-21 Thread Steve Sakoman
From: Alexander Kanavin 

NEWS

* Noteworthy changes in release 3.9 (2023-01-15) [stable]

** Bug fixes

  diff -c and -u no longer output incorrect timezones in headers
  on platforms like Solaris where struct tm lacks tm_gmtoff.
  [bug#51228 introduced in 3.4]

Drop patch as issue fixed upstream.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Luca Ceresoli 
Signed-off-by: Richard Purdie 
(cherry picked from commit e5ec5de7217de28bccf3243496df6b41ca8a1d0b)
Signed-off-by: Steve Sakoman 
(cherry picked from commit 6bf52987a82370a1353399a480271a76237e7619)
Signed-off-by: Steve Sakoman 
---
 ...001-Skip-strip-trailing-cr-test-case.patch | 11 +++
 ...a-standard-layout-so-glibc-and-musl-.patch | 33 ---
 .../{diffutils_3.8.bb => diffutils_3.9.bb}|  3 +-
 3 files changed, 6 insertions(+), 41 deletions(-)
 delete mode 100644 
meta/recipes-extended/diffutils/diffutils/0001-mcontext-is-not-a-standard-layout-so-glibc-and-musl-.patch
 rename meta/recipes-extended/diffutils/{diffutils_3.8.bb => diffutils_3.9.bb} 
(88%)

diff --git 
a/meta/recipes-extended/diffutils/diffutils/0001-Skip-strip-trailing-cr-test-case.patch
 
b/meta/recipes-extended/diffutils/diffutils/0001-Skip-strip-trailing-cr-test-case.patch
index aac1c43465..8b88c308f2 100644
--- 
a/meta/recipes-extended/diffutils/diffutils/0001-Skip-strip-trailing-cr-test-case.patch
+++ 
b/meta/recipes-extended/diffutils/diffutils/0001-Skip-strip-trailing-cr-test-case.patch
@@ -1,4 +1,4 @@
-From bd7fb8be2ae2d75347cf7733302d5093046ffa85 Mon Sep 17 00:00:00 2001
+From 027229d25392b22d7280c0abbc3efde4f467d167 Mon Sep 17 00:00:00 2001
 From: Peiran Hong 
 Date: Thu, 5 Sep 2019 15:42:22 -0400
 Subject: [PATCH] Skip strip-trailing-cr test case
@@ -10,19 +10,21 @@ package.
 Upstream-Status: Inappropriate [embedded specific]
 
 Signed-off-by: Peiran Hong 
+
 ---
  tests/Makefile.am | 4 +++-
  1 file changed, 3 insertions(+), 1 deletion(-)
 
 diff --git a/tests/Makefile.am b/tests/Makefile.am
-index 83a7c9d..04d51b5 100644
+index d98df82..757ea52 100644
 --- a/tests/Makefile.am
 +++ b/tests/Makefile.am
-@@ -21,8 +21,10 @@ TESTS = \
+@@ -21,9 +21,11 @@ TESTS = \
stdin \
strcoll-0-names \
filename-quoting \
 -  strip-trailing-cr \
+   timezone \
colors
 +# Skipping this test since it requires valgrind
 +# and thus is too heavy for diffutils package
@@ -30,6 +32,3 @@ index 83a7c9d..04d51b5 100644
  
  XFAIL_TESTS = large-subopt
  
--- 
-2.21.0
-
diff --git 
a/meta/recipes-extended/diffutils/diffutils/0001-mcontext-is-not-a-standard-layout-so-glibc-and-musl-.patch
 
b/meta/recipes-extended/diffutils/diffutils/0001-mcontext-is-not-a-standard-layout-so-glibc-and-musl-.patch
deleted file mode 100644
index 4928e1eaff..00
--- 
a/meta/recipes-extended/diffutils/diffutils/0001-mcontext-is-not-a-standard-layout-so-glibc-and-musl-.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From f385ad6639380eb6dfa8b8eb4a5ba65dd12db744 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 25 Mar 2022 13:43:19 -0700
-Subject: [PATCH] mcontext is not a standard layout so glibc and musl differ
-
-This is already applied to libsigsegv upstream, hopefully next version
-of grep will update its internal copy and we can drop this patch
-
-Upstream-Status: Backport 
[https://git.savannah.gnu.org/gitweb/?p=libsigsegv.git;a=commitdiff;h=a6ff69873110c0a8ba6f7fd90532dbc11224828c]
-
-Signed-off-by: Khem Raj 

- lib/sigsegv.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/lib/sigsegv.c b/lib/sigsegv.c
-index 998c827..b6f4841 100644
 a/lib/sigsegv.c
-+++ b/lib/sigsegv.c
-@@ -219,8 +219,8 @@ int libsigsegv_version = LIBSIGSEGV_VERSION;
- #   define SIGSEGV_FAULT_STACKPOINTER  ((ucontext_t *) 
ucp)->uc_mcontext.gp_regs[1]
- #  else /* 32-bit */
- /* both should be equivalent */
--#   if 0
--#define SIGSEGV_FAULT_STACKPOINTER  ((ucontext_t *) 
ucp)->uc_mcontext.regs->gpr[1]
-+#   if ! defined __GLIBC__
-+#define SIGSEGV_FAULT_STACKPOINTER  ((ucontext_t *) 
ucp)->uc_regs->gregs[1]
- #   else
- #define SIGSEGV_FAULT_STACKPOINTER  ((ucontext_t *) 
ucp)->uc_mcontext.uc_regs->gregs[1]
- #   endif
--- 
-2.35.1
-
diff --git a/meta/recipes-extended/diffutils/diffutils_3.8.bb 
b/meta/recipes-extended/diffutils/diffutils_3.9.bb
similarity index 88%
rename from meta/recipes-extended/diffutils/diffutils_3.8.bb
rename to meta/recipes-extended/diffutils/diffutils_3.9.bb
index 8889c83ee2..2bb9e6f32d 100644
--- a/meta/recipes-extended/diffutils/diffutils_3.8.bb
+++ b/meta/recipes-extended/diffutils/diffutils_3.9.bb
@@ -6,10 +6,9 @@ require diffutils.inc
 SRC_URI = "${GNU_MIRROR}/diffutils/diffutils-${PV}.tar.xz \
file://run-ptest \
file://0001-Skip-strip-trailing-cr-test-case.patch \
-   
file://0001-mcontext-is-not-a-standard-layout-so-glibc-and-musl-.patch \
"
 
-SRC_URI[sha256sum] = 
"a6bdd7d1b31266d11c4f4de6c1b748d4607ab0231af5188fc2533d0ae2438fec"
+SRC_URI[sha256sum] = 

[OE-core][kirkstone 00/23] Patch review

2023-02-21 Thread Steve Sakoman
Please review this set of patches for kirkstone and have comments back by
end of day Thursday.

Passed a-full on autobuilder:

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

The following changes since commit 54c30e509074073b99a7a8890482ba1af2abbab9:

  oeqa context.py: fix --target-ip comment to include ssh port number 
(2023-02-11 04:06:51 -1000)

are available in the Git repository at:

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

Alexander Kanavin (8):
  diffutils: update 3.8 -> 3.9
  lttng-tools: update 2.13.8 -> 2.13.9
  apr: update 1.7.0 -> 1.7.2
  apr-util: update 1.6.1 -> 1.6.3
  bind: upgrade 9.18.10 -> 9.18.11
  libjpeg-turbo: upgrade 2.1.4 -> 2.1.5
  linux-firmware: upgrade 20221214 -> 20230117
  sudo: upgrade 1.9.12p1 -> 1.9.12p2

Alexandre Belloni (1):
  oeqa/selftest/bbtests: Update message lookup for
test_git_unpack_nonetwork_fail

Kai Kang (1):
  qemu: fix compile error

Mauro Queiros (1):
  image.bbclass: print all QA functions exceptions

Mikko Rapeli (6):
  oeqa ssh.py: move output prints to new line
  oeqa ssh.py: add connection keep alive options to ssh client
  oeqa dump.py: add error counter and stop after 5 failures
  oeqa qemurunner: read more data at a time from serial
  oeqa qemurunner.py: add timeout to QMP calls
  oeqa qemurunner.py: try to avoid reading one character at a time

Peter Kjellerstedt (1):
  devshell: Do not add scripts/git-intercept to PATH

Rodolfo Quesada Zumbado (1):
  tar: CVE-2022-48303

Sakib Sajal (1):
  git: upgrade 2.35.6 -> 2.35.7

Steve Sakoman (2):
  libgit2: uprade 1.4.3 -> 1.4.4
  libgit2: upgrade 1.4.4 -> 1.4.5

Ulrich Ölmann (1):
  update-alternatives: fix typos

 meta/classes/devshell.bbclass |   2 -
 meta/classes/image.bbclass|   2 +-
 meta/classes/update-alternatives.bbclass  |   6 +-
 meta/lib/oeqa/core/target/ssh.py  |   8 +-
 meta/lib/oeqa/selftest/cases/bbtests.py   |   2 +-
 meta/lib/oeqa/utils/dump.py   |  23 +-
 meta/lib/oeqa/utils/qemurunner.py |   9 +-
 ...1-avoid-start-failure-with-bind-user.patch |   0
 ...d-V-and-start-log-hide-build-options.patch |   0
 ...ching-for-json-headers-searches-sysr.patch |   0
 .../bind/{bind-9.18.10 => bind-9.18.11}/bind9 |   0
 .../{bind-9.18.10 => bind-9.18.11}/conf.patch |   0
 .../generate-rndc-key.sh  |   0
 ...t.d-add-support-for-read-only-rootfs.patch |   0
 .../make-etc-initd-bind-stop-work.patch   |   0
 .../named.service |   0
 .../bind/{bind_9.18.10.bb => bind_9.18.11.bb} |   4 +-
 .../git/{git_2.35.6.bb => git_2.35.7.bb}  |   2 +-
 meta/recipes-devtools/qemu/qemu.inc   |   2 +
 ...ave-qxl_log_command-Return-early-if-.patch |  57 +
 ...ass-requested-buffer-size-to-qxl_phy.patch | 217 ++
 ...001-Skip-strip-trailing-cr-test-case.patch |  11 +-
 ...a-standard-layout-so-glibc-and-musl-.patch |  33 ---
 .../{diffutils_3.8.bb => diffutils_3.9.bb}|   3 +-
 .../{sudo_1.9.12p1.bb => sudo_1.9.12p2.bb}|   2 +-
 .../tar/tar/CVE-2022-48303.patch  |  43 
 meta/recipes-extended/tar/tar_1.34.bb |   4 +-
 ...-turbo_2.1.4.bb => libjpeg-turbo_2.1.5.bb} |   2 +-
 ...20221214.bb => linux-firmware_20230117.bb} |   6 +-
 .../lttng/lttng-tools/determinism.patch   |  64 --
 ...-tools_2.13.8.bb => lttng-tools_2.13.9.bb} |   3 +-
 .../0001-Fix-error-handling-in-gdbm.patch | 134 ---
 .../{apr-util_1.6.1.bb => apr-util_1.6.3.bb}  |   6 +-
 ...ion-to-disable-timed-dependant-tests.patch |  20 +-
 ...CHE_CHECK-for-strerror_r-return-type.patch |  52 -
 ...-runtime-test-for-mmap-that-can-map-.patch |  26 +--
 ...ir-path-references-from-installed-ap.patch |  25 +-
 ...configure.in-support-cross-compiling.patch |  63 -
 ...ze-doesn-t-match-in-glibc-when-cross.patch |  76 --
 .../apr/apr/CVE-2021-35940.patch  |  58 -
 .../recipes-support/apr/apr/autoconf270.patch |  22 --
 .../apr/apr/libtoolize_check.patch|  21 +-
 .../apr/{apr_1.7.0.bb => apr_1.7.2.bb}|   8 +-
 .../{libgit2_1.4.3.bb => libgit2_1.4.5.bb}|   2 +-
 44 files changed, 430 insertions(+), 588 deletions(-)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-avoid-start-failure-with-bind-user.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => bind-9.18.11}/bind9 
(100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 
bind-9.18.11}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.18.10 => 

Re: [OE-core] [PATCH 2/2] [YOCTO #13270] docbook-xml-dtd: refactor for style, add version check regex

2023-02-21 Thread Richard Elberger
Hello Ross,

It wasn't entirely clear to me that the patch would be required if taken 
from docbook, but I see that my "test scope" was not appropriate and you 
have surfaced why patching is required. Now that I have a test target 
this helps but in future I probably should build world but... just tried 
that and got a gtk4 dependency error.

rpcme@proteus:~/elinux/oe-core/meta/recipes-devtools/docbook-xml$ 
bitbake world
Loading cache: 100% 
|#|
 
Time: 0:00:00
Loaded 1692 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'gtk4' (but 
/home/rpcme/elinux/oe-core/meta/recipes-gnome/libportal/libportal_0.6.bb 
DEPENDS on or otherwise requires it)
gtk4 was skipped: missing required distro feature 'opengl' (not in 
DISTRO_FEATURES)
ERROR: Required build target 'meta-world-pkgdata' has no buildable 
providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 
'libportal', 'gtk4']

Given oe-core is distroless (this is my first time not using a distro 
conf), how best to ensure I'm checking everything I need to check 
(beyond getting the patch right to make this buildable).

Will do it this evening after normal working hours ... the workday is 
now in full swing and cannot work on it right now...

On 2/21/23 08:45, Ross Burton wrote:
> Sorry, but this doesn’t work:
>
> If you build xmlto-native:
>
>   validity error : Could not load the external subset 
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
>   Document 
> /yocto/ross/build/tmp/work/aarch64-linux/xmlto-native/0.0.28+0.0.29+gitAUTOINC+6fa6a0e076-r0/build/../git/doc/xmlif.xml
>  does not validate
>
>   
> /yocto/ross/build/tmp/work/aarch64-linux/xmlto-native/0.0.28+0.0.29+gitAUTOINC+6fa6a0e076-r0/build/../git/doc/xmlif.xml:4:
>  warning: failed to load external entity 
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
>  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd”>
>
> Ross


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177499): 
https://lists.openembedded.org/g/openembedded-core/message/177499
Mute This Topic: https://lists.openembedded.org/mt/97074293/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] Cve fetcher update

2023-02-21 Thread Ross Burton
Hi Marta,

> On 21 Feb 2023, at 13:20, Marta Rybczynska  wrote:
> I'm finishing the new fetcher for cve check using the 2.0 NVD API. Will need 
> testers to check as many configurations as possible before we switch the 
> format.
> 
> The current estimate is this week, hoping that the real life doesn't 
> interfere.
> 
> Good news for all users is that nothing changes for you. Results should be 
> compatible. The one noticeable thing is that the complete fetch is longer 
> than before.

Awesome, thanks Marta.  I’ll happily review and test the code.

How long is a complete fetch now?  My very rough testing when I first looked at 
the new API suggested 30 minutes for a full sync.

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



Re: [OE-core] [PATCH 2/2] [YOCTO #13270] docbook-xml-dtd: refactor for style, add version check regex

2023-02-21 Thread Ross Burton
Sorry, but this doesn’t work:

If you build xmlto-native:

 validity error : Could not load the external subset 
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
 Document 
/yocto/ross/build/tmp/work/aarch64-linux/xmlto-native/0.0.28+0.0.29+gitAUTOINC+6fa6a0e076-r0/build/../git/doc/xmlif.xml
 does not validate

 
/yocto/ross/build/tmp/work/aarch64-linux/xmlto-native/0.0.28+0.0.29+gitAUTOINC+6fa6a0e076-r0/build/../git/doc/xmlif.xml:4:
 warning: failed to load external entity 
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd”>

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



[OE-core][kirkstone][PATCH 1/1] apr-util: fix for CVE-2022-25147

2023-02-21 Thread Narpat Mali
Integer Overflow or Wraparound vulnerability in apr_base64 functions
of Apache Portable Runtime Utility (APR-util) allows an attacker to
write beyond bounds of a buffer. This issue affects Apache Portable
Runtime Utility (APR-util) 1.6.1 and prior versions.

Reference:
https://nvd.nist.gov/vuln/detail/CVE-2022-25147

Signed-off-by: Narpat Mali 
---
 .../apr/apr-util/CVE-2022-25147.patch | 180 ++
 meta/recipes-support/apr/apr-util_1.6.1.bb|   3 +-
 2 files changed, 182 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-support/apr/apr-util/CVE-2022-25147.patch

diff --git a/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch 
b/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
new file mode 100644
index 00..e85785aca0
--- /dev/null
+++ b/meta/recipes-support/apr/apr-util/CVE-2022-25147.patch
@@ -0,0 +1,180 @@
+From 3f5257075c7eb601aed6333e9bb5d9eb0e11254b Mon Sep 17 00:00:00 2001
+From: Yann Ylavic 
+Date: Thu, 20 Oct 2022 09:38:34 +
+Subject: [PATCH] apr_base64: Make sure encoding/decoding lengths fit in an int
+ >= 0.
+
+The (old) API of apr_base64 functions has always used int for representing
+lengths and it does not return errors. Make sure to abort() if the provided
+data don't fit.
+
+* encoding/apr_base64.c():
+  #define APR_BASE64_ENCODE_MAX and APR_BASE64_DECODE_MAX as the hard length
+  limits for encoding and decoding respectively.
+
+* encoding/apr_base64.c(apr_base64_encode_len, apr_base64_encode,
+apr_base64_encode_binary, apr_pbase64_encode):
+  abort() if the given length is above APR_BASE64_ENCODE_MAX.
+
+* encoding/apr_base64.c(apr_base64_decode_len, apr_base64_decode,
+apr_base64_decode_binary, apr_pbase64_decode):
+  abort() if the given plain buffer length is above APR_BASE64_DECODE_MAX.
+
+
+apr_base64: Follow up to r1902206: Cap to APR_BASE64_ENCODE_MAX in 
apr_pbase64_encode().
+
+
+Merges r1902206[, r1904666] from trunk.
+Merges r1904727 from 1.7.x.
+
+
+git-svn-id: 
https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x@1904728 
13f79535-47bb-0310-9956-ffa450edef68
+
+CVE: CVE-2022-25147
+
+Upstream-Status: Backport 
[https://github.com/apache/apr-util/commit/3f5257075c7eb601aed6333e9bb5d9eb0e11254b]
+
+Signed-off-by: Narpat Mali 
+---
+ encoding/apr_base64.c | 41 +
+ 1 file changed, 25 insertions(+), 16 deletions(-)
+
+diff --git a/encoding/apr_base64.c b/encoding/apr_base64.c
+index e9b75e3d..ac9f2816 100644
+--- a/encoding/apr_base64.c
 b/encoding/apr_base64.c
+@@ -20,11 +20,20 @@
+  * ugly 'len' functions, which is quite a nasty cost.
+  */
+ 
++#undef NDEBUG /* always abort() on assert()ion failure */
++#include 
++
+ #include "apr_base64.h"
+ #if APR_CHARSET_EBCDIC
+ #include "apr_xlate.h"
+ #endif/* APR_CHARSET_EBCDIC */
+ 
++/* Above APR_BASE64_ENCODE_MAX length the encoding can't fit in an int >= 0 */
++#define APR_BASE64_ENCODE_MAX 1610612733
++
++/* Above APR_BASE64_DECODE_MAX length the decoding can't fit in an int >= 0 */
++#define APR_BASE64_DECODE_MAX 2863311524u
++
+ /* ck but it's fast and const should make it shared text page. */
+ static const unsigned char pr2six[256] =
+ {
+@@ -109,24 +118,22 @@ APU_DECLARE(apr_status_t) 
apr_base64init_ebcdic(apr_xlate_t *to_ascii,
+ 
+ APU_DECLARE(int) apr_base64_decode_len(const char *bufcoded)
+ {
+-int nbytesdecoded;
+ register const unsigned char *bufin;
+ register apr_size_t nprbytes;
+ 
+ bufin = (const unsigned char *) bufcoded;
+ while (pr2six[*(bufin++)] <= 63);
+-
+ nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
+-nbytesdecoded = (((int)nprbytes + 3) / 4) * 3;
++assert(nprbytes <= APR_BASE64_DECODE_MAX);
+ 
+-return nbytesdecoded + 1;
++return (int)(((nprbytes + 3u) / 4u) * 3u + 1u);
+ }
+ 
+ APU_DECLARE(int) apr_base64_decode(char *bufplain, const char *bufcoded)
+ {
+ #if APR_CHARSET_EBCDIC
+ apr_size_t inbytes_left, outbytes_left;
+-#endif/* APR_CHARSET_EBCDIC */
++#endif /* APR_CHARSET_EBCDIC */
+ int len;
+ 
+ len = apr_base64_decode_binary((unsigned char *) bufplain, bufcoded);
+@@ -143,7 +150,7 @@ APU_DECLARE(int) apr_base64_decode(char *bufplain, const 
char *bufcoded)
+  * the conversion of the output to ebcdic is left out.
+  */
+ APU_DECLARE(int) apr_base64_decode_binary(unsigned char *bufplain,
+- const char *bufcoded)
++  const char *bufcoded)
+ {
+ int nbytesdecoded;
+ register const unsigned char *bufin;
+@@ -153,12 +160,13 @@ APU_DECLARE(int) apr_base64_decode_binary(unsigned char 
*bufplain,
+ bufin = (const unsigned char *) bufcoded;
+ while (pr2six[*(bufin++)] <= 63);
+ nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
+-nbytesdecoded = (((int)nprbytes + 3) / 4) * 3;
++assert(nprbytes <= 

[OE-core] Cve fetcher update

2023-02-21 Thread Marta Rybczynska
Hello all,
I'm finishing the new fetcher for cve check using the 2.0 NVD API. Will
need testers to check as many configurations as possible before we switch
the format.

The current estimate is this week, hoping that the real life doesn't
interfere.

Good news for all users is that nothing changes for you. Results should be
compatible. The one noticeable thing is that the complete fetch is longer
than before.

Kind regards,
Marta

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177495): 
https://lists.openembedded.org/g/openembedded-core/message/177495
Mute This Topic: https://lists.openembedded.org/mt/97108178/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] create.py: add command arg to add layer to bblayers.conf

2023-02-21 Thread Pedro Baptista
From: Pedro Baptista 

Add command arg `--add-layer` which enables the create
and add layer in a single step.

Signed-off-by: Pedro Baptista 
---
 meta/lib/bblayers/create.py | 11 ++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/meta/lib/bblayers/create.py b/meta/lib/bblayers/create.py
index c8f3f1b370..517554c587 100644
--- a/meta/lib/bblayers/create.py
+++ b/meta/lib/bblayers/create.py
@@ -12,6 +12,7 @@ import shutil
 import bb.utils
 
 from bblayers.common import LayerPlugin
+from bblayers.action import ActionPlugin
 
 logger = logging.getLogger('bitbake-layers')
 
@@ -69,11 +70,19 @@ class CreatePlugin(LayerPlugin):
 with open(os.path.join(example, args.examplerecipe + '_%s.bb') % 
args.version, 'w') as fd:
 fd.write(example_template)
 
-logger.plain('Add your new layer with \'bitbake-layers add-layer %s\'' 
% args.layerdir)
+if args.add_layer:
+# Add the layer to bblayers.conf
+args.layerdir = [layerdir]
+ActionPlugin.do_add_layer(self, args)
+logger.plain('Layer added %s' % args.layerdir)
+
+else:
+logger.plain('Add your new layer with \'bitbake-layers add-layer 
%s\'' % args.layerdir)
 
 def register_commands(self, sp):
 parser_create_layer = self.add_command(sp, 'create-layer', 
self.do_create_layer, parserecipes=False)
 parser_create_layer.add_argument('layerdir', help='Layer directory to 
create')
+parser_create_layer.add_argument('--add-layer', '-a', 
action='store_true', help='Add the layer to bblayers.conf after creation')
 parser_create_layer.add_argument('--layerid', '-i', help='Layer id to 
use if different from layername')
 parser_create_layer.add_argument('--priority', '-p', default=6, 
help='Priority of recipes in layer')
 parser_create_layer.add_argument('--example-recipe-name', '-e', 
dest='examplerecipe', default='example', help='Filename of the example recipe')
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177494): 
https://lists.openembedded.org/g/openembedded-core/message/177494
Mute This Topic: https://lists.openembedded.org/mt/97106914/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] docbook-xml: Switch from debian packages to upstream docbook sources

2023-02-21 Thread Richard Elberger
The process in the last few days has very helpful because it forces me 
to organize practices better on my end. Thank you.

On 2/21/23 05:33, Alexander Kanavin wrote:
> Thanks, I do not have any further comments. The next step is taking
> this through the automated test matrix.
>
> Alex
>
> On Tue, 21 Feb 2023 at 11:29, Richard Elberger  wrote:
>> This patch changes the docbook-xml distribution package source from
>> debian to docbook which aligns the recipe with the source
>> originator. Other changes made to the recipe include:
>>
>> This patch resolves [YOCTO #13270].
>>
>> - removal of version 4.0 given docbook no longer distributes version
>>4.0
>> - simplification of the header description.
>> - inline comments to communicate the rationale behind gathering
>>multiple versions and LICENSE file handling.
>> - minor ordering changes to align with styling conventions and better
>>context to better communicate use - i.e. the inherit statements and
>>related operations.
>>
>> Signed-off-by: Richard Elberger 
>> ---
>>   .../docbook-xml/docbook-xml-dtd4_4.5.bb   | 60 ---
>>   1 file changed, 39 insertions(+), 21 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb 
>> b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
>> index 2bec1442af..dd6159b2f3 100644
>> --- a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
>> +++ b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
>> @@ -1,28 +1,46 @@
>>   SUMMARY = "Document type definitions for verification of XML data files"
>>   DESCRIPTION = "Document type definitions for verification of XML data \
>> -files against the DocBook rule set, it ships with the latest DocBook 4.5 \
>> -XML DTD, as well as a selected set of legacy DTDs for use with older \
>> -documents, including 4.0, 4.1.2, 4.2, 4.3 and 4.4"
>> -HOMEPAGE = "http://www.docbook.org/xml/;
>> +files against the DocBook rule set."
>> +HOMEPAGE = "https://docbook.org;
>> +
>> +# The upstream sources are not distributed with a license file.
>> +# LICENSE-OASIS is included as a "patch" to workaround this. When
>> +# upgrading this recipe, please verify whether this is still needed.
>>
>>   LICENSE = "OASIS"
>>   LIC_FILES_CHKSUM = 
>> "file://${WORKDIR}/LICENSE-OASIS;md5=c608985dd5f7f215e669e7639a0b1d2e"
>>
>> -# Note: the upstream sources are not distributed with a license file.
>> -# LICENSE-OASIS is included as a "patch" to workaround this. When
>> -# upgrading this recipe, please verify whether this is still needed.
>> -SRC_URI = 
>> "http://snapshot.debian.org/archive/debian/20160728T043443Z/pool/main/d/docbook-xml/docbook-xml_${PV}.orig.tar.gz
>>  \
>> -   file://LICENSE-OASIS \
>> -   file://docbook-xml-update-catalog.xml.patch \
>> -"
>> +# To support apps with xml schema backward compatibility, we must
>> +# install a set of schemas. Install the latest based on PV and then
>> +# name any specific versions as required. TODO: Figure out a mechanism
>> +# to filter exactly which versions are necessary, if that's even
>> +# possible.
>> +#
>> +# DocBook.org lists available release packages at https://docbook.org/xml/.
>> +#
>> +# The release packages relate docbook source at
>> +# https://github.com/docbook/docbook but building them requires the
>> +# Gradle build system. In future, it might be safer to use the source
>> +# tree which would also enable proper SBOM generation through the
>> +# bitbake build system.
>> +#
>>
>> -SRC_URI[md5sum] = "487b4d44e15cffb1f4048af23f98208e"
>> -SRC_URI[sha256sum] = 
>> "b0f8edcf697f5318e63dd98c9a931f3fee167af0805ba441db372e0f17b2a44f"
>> +SRC_URI = 
>> "https://docbook.org/xml/4.1.2/docbkx412.zip;name=payload412;subdir=docbook-xml-4.1.2
>>  \
>> +   
>> https://docbook.org/xml/4.2/docbook-xml-4.2.zip;name=payload42;subdir=docbook-xml-4.2
>>  \
>> +   
>> https://docbook.org/xml/4.3/docbook-xml-4.3.zip;name=payload43;subdir=docbook-xml-4.3
>>  \
>> +   
>> https://docbook.org/xml/4.4/docbook-xml-4.4.zip;name=payload44;subdir=docbook-xml-4.4
>>  \
>> +   
>> https://docbook.org/xml/${PV}/docbook-xml-${PV}.zip;name=payloadPV;subdir=docbook-xml-${PV}
>>  \
>> +   file://LICENSE-OASIS"
>>
>> -UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/d/docbook-xml/"
>> +SRC_URI[payload412.sha256sum] = 
>> "30f0644064e0ea71751438251940b1431f46acada814a062870f486c772e7772"
>> +SRC_URI[payload42.sha256sum] = 
>> "acc4601e4f97a196076b7e64b368d9248b07c7abf26b34a02cca40eeebe60fa2"
>> +SRC_URI[payload43.sha256sum] = 
>> "23068a94ea6fd484b004c5a73ec36a66aa47ea8f0d6b62cc1695931f5c143464"
>> +SRC_URI[payload44.sha256sum] = 
>> "02f159eb88c4254d95e831c51c144b1863b216d909b5ff45743a1ce6f5273090"
>> +SRC_URI[payloadPV.sha256sum] = 
>> "4e4e037a2b83c98c6c94818390d4bdd3f6e10f6ec62dd79188594e26190dc7b4"
>>
>> -S = "${WORKDIR}/docbook-xml-4.5.c31424"
>> +UPSTREAM_CHECK_REGEX = "docbook-xml-(?P4(\.\d+)).zip"
>>
>> +S = "${WORKDIR}"
>>   inherit 

Re: [OE-core] [PATCH] docbook-xml: Switch from debian packages to upstream docbook sources

2023-02-21 Thread Alexander Kanavin
Thanks, I do not have any further comments. The next step is taking
this through the automated test matrix.

Alex

On Tue, 21 Feb 2023 at 11:29, Richard Elberger  wrote:
>
> This patch changes the docbook-xml distribution package source from
> debian to docbook which aligns the recipe with the source
> originator. Other changes made to the recipe include:
>
> This patch resolves [YOCTO #13270].
>
> - removal of version 4.0 given docbook no longer distributes version
>   4.0
> - simplification of the header description.
> - inline comments to communicate the rationale behind gathering
>   multiple versions and LICENSE file handling.
> - minor ordering changes to align with styling conventions and better
>   context to better communicate use - i.e. the inherit statements and
>   related operations.
>
> Signed-off-by: Richard Elberger 
> ---
>  .../docbook-xml/docbook-xml-dtd4_4.5.bb   | 60 ---
>  1 file changed, 39 insertions(+), 21 deletions(-)
>
> diff --git a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb 
> b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
> index 2bec1442af..dd6159b2f3 100644
> --- a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
> +++ b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
> @@ -1,28 +1,46 @@
>  SUMMARY = "Document type definitions for verification of XML data files"
>  DESCRIPTION = "Document type definitions for verification of XML data \
> -files against the DocBook rule set, it ships with the latest DocBook 4.5 \
> -XML DTD, as well as a selected set of legacy DTDs for use with older \
> -documents, including 4.0, 4.1.2, 4.2, 4.3 and 4.4"
> -HOMEPAGE = "http://www.docbook.org/xml/;
> +files against the DocBook rule set."
> +HOMEPAGE = "https://docbook.org;
> +
> +# The upstream sources are not distributed with a license file.
> +# LICENSE-OASIS is included as a "patch" to workaround this. When
> +# upgrading this recipe, please verify whether this is still needed.
>
>  LICENSE = "OASIS"
>  LIC_FILES_CHKSUM = 
> "file://${WORKDIR}/LICENSE-OASIS;md5=c608985dd5f7f215e669e7639a0b1d2e"
>
> -# Note: the upstream sources are not distributed with a license file.
> -# LICENSE-OASIS is included as a "patch" to workaround this. When
> -# upgrading this recipe, please verify whether this is still needed.
> -SRC_URI = 
> "http://snapshot.debian.org/archive/debian/20160728T043443Z/pool/main/d/docbook-xml/docbook-xml_${PV}.orig.tar.gz
>  \
> -   file://LICENSE-OASIS \
> -   file://docbook-xml-update-catalog.xml.patch \
> -"
> +# To support apps with xml schema backward compatibility, we must
> +# install a set of schemas. Install the latest based on PV and then
> +# name any specific versions as required. TODO: Figure out a mechanism
> +# to filter exactly which versions are necessary, if that's even
> +# possible.
> +#
> +# DocBook.org lists available release packages at https://docbook.org/xml/.
> +#
> +# The release packages relate docbook source at
> +# https://github.com/docbook/docbook but building them requires the
> +# Gradle build system. In future, it might be safer to use the source
> +# tree which would also enable proper SBOM generation through the
> +# bitbake build system.
> +#
>
> -SRC_URI[md5sum] = "487b4d44e15cffb1f4048af23f98208e"
> -SRC_URI[sha256sum] = 
> "b0f8edcf697f5318e63dd98c9a931f3fee167af0805ba441db372e0f17b2a44f"
> +SRC_URI = 
> "https://docbook.org/xml/4.1.2/docbkx412.zip;name=payload412;subdir=docbook-xml-4.1.2
>  \
> +   
> https://docbook.org/xml/4.2/docbook-xml-4.2.zip;name=payload42;subdir=docbook-xml-4.2
>  \
> +   
> https://docbook.org/xml/4.3/docbook-xml-4.3.zip;name=payload43;subdir=docbook-xml-4.3
>  \
> +   
> https://docbook.org/xml/4.4/docbook-xml-4.4.zip;name=payload44;subdir=docbook-xml-4.4
>  \
> +   
> https://docbook.org/xml/${PV}/docbook-xml-${PV}.zip;name=payloadPV;subdir=docbook-xml-${PV}
>  \
> +   file://LICENSE-OASIS"
>
> -UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/d/docbook-xml/"
> +SRC_URI[payload412.sha256sum] = 
> "30f0644064e0ea71751438251940b1431f46acada814a062870f486c772e7772"
> +SRC_URI[payload42.sha256sum] = 
> "acc4601e4f97a196076b7e64b368d9248b07c7abf26b34a02cca40eeebe60fa2"
> +SRC_URI[payload43.sha256sum] = 
> "23068a94ea6fd484b004c5a73ec36a66aa47ea8f0d6b62cc1695931f5c143464"
> +SRC_URI[payload44.sha256sum] = 
> "02f159eb88c4254d95e831c51c144b1863b216d909b5ff45743a1ce6f5273090"
> +SRC_URI[payloadPV.sha256sum] = 
> "4e4e037a2b83c98c6c94818390d4bdd3f6e10f6ec62dd79188594e26190dc7b4"
>
> -S = "${WORKDIR}/docbook-xml-4.5.c31424"
> +UPSTREAM_CHECK_REGEX = "docbook-xml-(?P4(\.\d+)).zip"
>
> +S = "${WORKDIR}"
>  inherit allarch
>  BBCLASSEXTEND = "native"
>
> @@ -34,19 +52,19 @@ do_compile (){
>  :
>  }
>
> +inherit xmlcatalog
> +
>  do_install () {
>  install -d ${D}${sysconfdir}/xml/
>  xmlcatalog --create --noout ${D}${sysconfdir}/xml/docbook-xml.xml
>
> -for DTDVERSION in 4.0 4.1.2 4.2 4.3 

Re: [OE-core] [PATCH] ref-manual: Fix invalid feature name

2023-02-21 Thread Niko Mauno via lists.openembedded.org

On 20.2.2023 19.45, Michael Opdenacker wrote:


Thanks for the patch!
You also have an issue with the way your e-mails are received here. Here 
is a workaround:

https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Fixing_your_From_identity

I fixed the commit manually, but doing this will help for next time.


Thanks for pointing the issue Michael, I've now applied the mitigation.
BR, Niko

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177491): 
https://lists.openembedded.org/g/openembedded-core/message/177491
Mute This Topic: https://lists.openembedded.org/mt/97066768/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] docbook-xml: Switch from debian packages to upstream docbook sources

2023-02-21 Thread Richard Elberger
This patch changes the docbook-xml distribution package source from
debian to docbook which aligns the recipe with the source
originator. Other changes made to the recipe include:

This patch resolves [YOCTO #13270].

- removal of version 4.0 given docbook no longer distributes version
  4.0
- simplification of the header description.
- inline comments to communicate the rationale behind gathering
  multiple versions and LICENSE file handling.
- minor ordering changes to align with styling conventions and better
  context to better communicate use - i.e. the inherit statements and
  related operations.

Signed-off-by: Richard Elberger 
---
 .../docbook-xml/docbook-xml-dtd4_4.5.bb   | 60 ---
 1 file changed, 39 insertions(+), 21 deletions(-)

diff --git a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb 
b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
index 2bec1442af..dd6159b2f3 100644
--- a/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
+++ b/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
@@ -1,28 +1,46 @@
 SUMMARY = "Document type definitions for verification of XML data files"
 DESCRIPTION = "Document type definitions for verification of XML data \
-files against the DocBook rule set, it ships with the latest DocBook 4.5 \
-XML DTD, as well as a selected set of legacy DTDs for use with older \
-documents, including 4.0, 4.1.2, 4.2, 4.3 and 4.4"
-HOMEPAGE = "http://www.docbook.org/xml/;
+files against the DocBook rule set."
+HOMEPAGE = "https://docbook.org;
+
+# The upstream sources are not distributed with a license file.
+# LICENSE-OASIS is included as a "patch" to workaround this. When
+# upgrading this recipe, please verify whether this is still needed.
 
 LICENSE = "OASIS"
 LIC_FILES_CHKSUM = 
"file://${WORKDIR}/LICENSE-OASIS;md5=c608985dd5f7f215e669e7639a0b1d2e"
 
-# Note: the upstream sources are not distributed with a license file.
-# LICENSE-OASIS is included as a "patch" to workaround this. When
-# upgrading this recipe, please verify whether this is still needed.
-SRC_URI = 
"http://snapshot.debian.org/archive/debian/20160728T043443Z/pool/main/d/docbook-xml/docbook-xml_${PV}.orig.tar.gz
 \
-   file://LICENSE-OASIS \
-   file://docbook-xml-update-catalog.xml.patch \
-"
+# To support apps with xml schema backward compatibility, we must
+# install a set of schemas. Install the latest based on PV and then
+# name any specific versions as required. TODO: Figure out a mechanism
+# to filter exactly which versions are necessary, if that's even
+# possible.
+#
+# DocBook.org lists available release packages at https://docbook.org/xml/.
+#
+# The release packages relate docbook source at
+# https://github.com/docbook/docbook but building them requires the
+# Gradle build system. In future, it might be safer to use the source
+# tree which would also enable proper SBOM generation through the
+# bitbake build system.
+#
 
-SRC_URI[md5sum] = "487b4d44e15cffb1f4048af23f98208e"
-SRC_URI[sha256sum] = 
"b0f8edcf697f5318e63dd98c9a931f3fee167af0805ba441db372e0f17b2a44f"
+SRC_URI = 
"https://docbook.org/xml/4.1.2/docbkx412.zip;name=payload412;subdir=docbook-xml-4.1.2
 \
+   
https://docbook.org/xml/4.2/docbook-xml-4.2.zip;name=payload42;subdir=docbook-xml-4.2
 \
+   
https://docbook.org/xml/4.3/docbook-xml-4.3.zip;name=payload43;subdir=docbook-xml-4.3
 \
+   
https://docbook.org/xml/4.4/docbook-xml-4.4.zip;name=payload44;subdir=docbook-xml-4.4
 \
+   
https://docbook.org/xml/${PV}/docbook-xml-${PV}.zip;name=payloadPV;subdir=docbook-xml-${PV}
 \
+   file://LICENSE-OASIS"
 
-UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/d/docbook-xml/"
+SRC_URI[payload412.sha256sum] = 
"30f0644064e0ea71751438251940b1431f46acada814a062870f486c772e7772"
+SRC_URI[payload42.sha256sum] = 
"acc4601e4f97a196076b7e64b368d9248b07c7abf26b34a02cca40eeebe60fa2"
+SRC_URI[payload43.sha256sum] = 
"23068a94ea6fd484b004c5a73ec36a66aa47ea8f0d6b62cc1695931f5c143464"
+SRC_URI[payload44.sha256sum] = 
"02f159eb88c4254d95e831c51c144b1863b216d909b5ff45743a1ce6f5273090"
+SRC_URI[payloadPV.sha256sum] = 
"4e4e037a2b83c98c6c94818390d4bdd3f6e10f6ec62dd79188594e26190dc7b4"
 
-S = "${WORKDIR}/docbook-xml-4.5.c31424"
+UPSTREAM_CHECK_REGEX = "docbook-xml-(?P4(\.\d+)).zip"
 
+S = "${WORKDIR}"
 inherit allarch
 BBCLASSEXTEND = "native"
 
@@ -34,19 +52,19 @@ do_compile (){
 :
 }
 
+inherit xmlcatalog
+
 do_install () {
 install -d ${D}${sysconfdir}/xml/
 xmlcatalog --create --noout ${D}${sysconfdir}/xml/docbook-xml.xml
 
-for DTDVERSION in 4.0 4.1.2 4.2 4.3 4.4 4.5; do
+for DTDVERSION in 4.1.2 4.2 4.3 4.4 4.5; do
 DEST=${datadir}/xml/docbook/schema/dtd/$DTDVERSION
 install -d -m 755 ${D}$DEST
-cp -v -R docbook-$DTDVERSION/* ${D}$DEST
-xmlcatalog --verbose --noout --add nextCatalog unused 
file://$DEST/catalog.xml ${D}${sysconfdir}/xml/docbook-xml.xml
+cp -v -R docbook-xml-$DTDVERSION/* 

[OE-core] [PATCH] python3-setuptools: upgrade 67.3.1 -> 67.3.3

2023-02-21 Thread wangmy
From: Wang Mingyu 

Changelog:
==
#3820: Restore quoted #include argument to has_function.
#3827: Improve deprecation warning message on pkg_resources.declare_namespace
to display package name.

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

diff --git a/meta/recipes-devtools/python/python3-setuptools_67.3.1.bb 
b/meta/recipes-devtools/python/python3-setuptools_67.3.3.bb
similarity index 95%
rename from meta/recipes-devtools/python/python3-setuptools_67.3.1.bb
rename to meta/recipes-devtools/python/python3-setuptools_67.3.3.bb
index ef759c8bef..053b671e2a 100644
--- a/meta/recipes-devtools/python/python3-setuptools_67.3.1.bb
+++ b/meta/recipes-devtools/python/python3-setuptools_67.3.3.bb
@@ -11,7 +11,7 @@ SRC_URI:append:class-native = " 
file://0001-conditionally-do-not-fetch-code-by-e
 SRC_URI += " \
 
file://0001-_distutils-sysconfig.py-make-it-possible-to-substite.patch"
 
-SRC_URI[sha256sum] = 
"daec07fd848d80676694d6bf69c009d28910aeece68a38dbe88b7e1bb6dba12e"
+SRC_URI[sha256sum] = 
"ed4e75fafe103c79b692f217158ba87edf38d31004b9dbc1913debb48793c828"
 
 DEPENDS += "${PYTHON_PN}"
 
-- 
2.34.1


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



[OE-core] [PATCH] python3-zipp: upgrade 3.13.0 -> 3.14.0

2023-02-21 Thread wangmy
From: Wang Mingyu 

Changelog:
Minor cleanup in tests, including #93.

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

diff --git a/meta/recipes-devtools/python/python3-zipp_3.13.0.bb 
b/meta/recipes-devtools/python/python3-zipp_3.14.0.bb
similarity index 85%
rename from meta/recipes-devtools/python/python3-zipp_3.13.0.bb
rename to meta/recipes-devtools/python/python3-zipp_3.14.0.bb
index 8df5d4637b..dc5091f6c7 100644
--- a/meta/recipes-devtools/python/python3-zipp_3.13.0.bb
+++ b/meta/recipes-devtools/python/python3-zipp_3.14.0.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/jaraco/zipp;
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=7a7126e068206290f3fe9f8d6c713ea6"
 
-SRC_URI[sha256sum] = 
"23f70e964bc11a34cef175bc90ba2914e1e4545ea1e3e2f67c079671883f9cb6"
+SRC_URI[sha256sum] = 
"9e5421e176ef5ab4c0ad896624e87a7b2f07aca746c9b2aa305952800cb8eecb"
 
 DEPENDS += "${PYTHON_PN}-setuptools-scm-native"
 
-- 
2.34.1


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



[OE-core] [PATCH] python3-pytest-subtests: upgrade 0.9.0 -> 0.10.0

2023-02-21 Thread wangmy
From: Wang Mingyu 

Changelog:
=
Added experimental support for suppressing subtest output dots in non-verbose
mode with --no-subtests-shortletter -- this allows the native pytest column
calculations to not be disrupted and minimizes unneeded output for large CI 
systems.

Signed-off-by: Wang Mingyu 
---
 ...test-subtests_0.9.0.bb => python3-pytest-subtests_0.10.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-pytest-subtests_0.9.0.bb => 
python3-pytest-subtests_0.10.0.bb} (86%)

diff --git a/meta/recipes-devtools/python/python3-pytest-subtests_0.9.0.bb 
b/meta/recipes-devtools/python/python3-pytest-subtests_0.10.0.bb
similarity index 86%
rename from meta/recipes-devtools/python/python3-pytest-subtests_0.9.0.bb
rename to meta/recipes-devtools/python/python3-pytest-subtests_0.10.0.bb
index bfaff39077..e1f2a49d31 100644
--- a/meta/recipes-devtools/python/python3-pytest-subtests_0.9.0.bb
+++ b/meta/recipes-devtools/python/python3-pytest-subtests_0.10.0.bb
@@ -7,7 +7,7 @@ BUGTRACKER = 
"https://github.com/pytest-dev/pytest-subtests/issues;
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=242b4e17fa287dcf7aef372f6bc3dcb1"
 
-SRC_URI[sha256sum] = 
"c0317cd5f6a5eb3e957e89dbe4fc3322a9afddba2db8414355ed2a2cb91a844e"
+SRC_URI[sha256sum] = 
"d9961a67c1791e8c1e32dce7a70ed1e54f3b1e641087f2094f2d37087ab7fb17"
 
 inherit pypi setuptools3
 
-- 
2.34.1


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



[OE-core] [PATCH] python3-poetry-core: upgrade 1.5.0 -> 1.5.1

2023-02-21 Thread wangmy
From: Wang Mingyu 

Changelog:
Improve performance by caching parsed markers, constraints and versions (#556).

Signed-off-by: Wang Mingyu 
---
 ...ython3-poetry-core_1.5.0.bb => python3-poetry-core_1.5.1.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-poetry-core_1.5.0.bb => 
python3-poetry-core_1.5.1.bb} (95%)

diff --git a/meta/recipes-devtools/python/python3-poetry-core_1.5.0.bb 
b/meta/recipes-devtools/python/python3-poetry-core_1.5.1.bb
similarity index 95%
rename from meta/recipes-devtools/python/python3-poetry-core_1.5.0.bb
rename to meta/recipes-devtools/python/python3-poetry-core_1.5.1.bb
index 03db426b39..952ffef99d 100644
--- a/meta/recipes-devtools/python/python3-poetry-core_1.5.0.bb
+++ b/meta/recipes-devtools/python/python3-poetry-core_1.5.1.bb
@@ -19,7 +19,7 @@ LIC_FILES_CHKSUM = "\
 
file://src/poetry/core/_vendor/typing_extensions.LICENSE;md5=f16b323917992e0f8a6f0071bc9913e2
 \
 "
 
-SRC_URI[sha256sum] = 
"253521bb7104e1df81f64d7b49ea1825057c91fa156d7d0bd752fefdad6f8c7a"
+SRC_URI[sha256sum] = 
"41887261358863f25831fa0ad1fe7e451fc32d1c81fcf7710ba5174cc0047c6d"
 
 inherit python_poetry_core pypi
 PYPI_ARCHIVE_NAME = "poetry_core-${PV}.${PYPI_PACKAGE_EXT}"
-- 
2.34.1


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



[OE-core] [PATCH] python3-pip: update 23.0 -> 23.0.1

2023-02-21 Thread wangmy
From: Wang Mingyu 

Changelog:

Features

- Ignore PIP_REQUIRE_VIRTUALENV for "pip index"
- Implement "--break-system-packages" to permit installing packages into
  "EXTERNALLY-MANAGED" Python installations.

Bug Fixes
-
- Improve handling of isolated build environments on platforms that
  customize the Python's installation schemes, such as Debian and
  Homebrew.
- Do not crash in presence of misformatted hash field in "direct_url.json".

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

diff --git a/meta/recipes-devtools/python/python3-pip_23.0.bb 
b/meta/recipes-devtools/python/python3-pip_23.0.1.bb
similarity index 97%
rename from meta/recipes-devtools/python/python3-pip_23.0.bb
rename to meta/recipes-devtools/python/python3-pip_23.0.1.bb
index 8b956932c3..d9b9906ff9 100644
--- a/meta/recipes-devtools/python/python3-pip_23.0.bb
+++ b/meta/recipes-devtools/python/python3-pip_23.0.1.bb
@@ -33,7 +33,7 @@ inherit pypi python_setuptools_build_meta
 
 SRC_URI += "file://no_shebang_mangling.patch"
 
-SRC_URI[sha256sum] = 
"aee438284e82c8def684b0bcc50b1f6ed5e941af97fa940e83e2e8ef1a59da9b"
+SRC_URI[sha256sum] = 
"cd015ea1bfb0fcef59d8a286c1f8bebcb983f6317719d415dc5351efb7cd7024"
 
 do_install:append() {
 rm -f ${D}/${bindir}/pip
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177485): 
https://lists.openembedded.org/g/openembedded-core/message/177485
Mute This Topic: https://lists.openembedded.org/mt/97105964/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] libx11-compose-data: 1.8.3 -> 1.8.4

2023-02-21 Thread wangmy
From: Wang Mingyu 

Signed-off-by: Wang Mingyu 
---
 ...ibx11-compose-data_1.8.3.bb => libx11-compose-data_1.8.4.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/xorg-lib/{libx11-compose-data_1.8.3.bb => 
libx11-compose-data_1.8.4.bb} (90%)

diff --git a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.3.bb 
b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.4.bb
similarity index 90%
rename from meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.3.bb
rename to meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.4.bb
index e734a215fd..2131f46213 100644
--- a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.3.bb
+++ b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.8.4.bb
@@ -16,7 +16,7 @@ XORG_PN = "libX11"
 SRC_URI += "file://0001-Drop-x11-dependencies.patch \
"
 
-SRC_URI[sha256sum] = 
"e31565c84006b6b8e01dc9399c806085739710bc2db2e0930f1511ed9d6585bd"
+SRC_URI[sha256sum] = 
"c9a287a5aefa9804ce3cfafcf516fe96ed3f7e8e45c0e2ee59e84c86757df518"
 
 REQUIRED_DISTRO_FEATURES = ""
 
-- 
2.34.1


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

2023-02-21 Thread wangmy
From: Wang Mingyu 

Signed-off-by: Wang Mingyu 
---
 .../harfbuzz/{harfbuzz_7.0.0.bb => harfbuzz_7.0.1.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/harfbuzz/{harfbuzz_7.0.0.bb => harfbuzz_7.0.1.bb} 
(95%)

diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_7.0.0.bb 
b/meta/recipes-graphics/harfbuzz/harfbuzz_7.0.1.bb
similarity index 95%
rename from meta/recipes-graphics/harfbuzz/harfbuzz_7.0.0.bb
rename to meta/recipes-graphics/harfbuzz/harfbuzz_7.0.1.bb
index a85c4ca1ce..55421ebcbe 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_7.0.0.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_7.0.1.bb
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b98429b8e8e3c2a67cfef01e99e4893d \
 "
 
 SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz"
-SRC_URI[sha256sum] = 
"7b4685b7066c5c6b8dc6cd7b02f63c554fb8cc1c4ddcfc44bc284efa3c20cf28"
+SRC_URI[sha256sum] = 
"2cf4d3d8f225007511990a36a34195f0d6562ca56df0a8b0885b382837948199"
 
 inherit meson pkgconfig lib_package gtk-doc gobject-introspection 
github-releases
 
-- 
2.34.1


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

2023-02-21 Thread wangmy
From: Wang Mingyu 

Signed-off-by: Wang Mingyu 
---
 meta/recipes-support/curl/{curl_7.88.0.bb => curl_7.88.1.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/curl/{curl_7.88.0.bb => curl_7.88.1.bb} (98%)

diff --git a/meta/recipes-support/curl/curl_7.88.0.bb 
b/meta/recipes-support/curl/curl_7.88.1.bb
similarity index 98%
rename from meta/recipes-support/curl/curl_7.88.0.bb
rename to meta/recipes-support/curl/curl_7.88.1.bb
index 749bda815c..0930d229d2 100644
--- a/meta/recipes-support/curl/curl_7.88.0.bb
+++ b/meta/recipes-support/curl/curl_7.88.1.bb
@@ -14,7 +14,7 @@ SRC_URI = " \
 file://run-ptest \
 file://disable-tests \
 "
-SRC_URI[sha256sum] = 
"fd17432cf28714a4cf39d89e26b8ace0d8901199fe5d01d75eb0ae3bbfcc731f"
+SRC_URI[sha256sum] = 
"1dae31b2a7c1fe269de99c0c31bb488346aab3459b5ffca909d6938249ae415f"
 
 # Curl has used many names over the years...
 CVE_PRODUCT = "haxx:curl haxx:libcurl curl:curl curl:libcurl libcurl:libcurl 
daniel_stenberg:curl"
-- 
2.34.1


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