Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: andrej.v@skyrain.eu, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] busybox: 1.36.1 -> 1.37.0
Date: Fri, 11 Oct 2024 13:33:00 +0100	[thread overview]
Message-ID: <a9c4777b9bf0987e3a01138e664fdfbe45907035.camel@linuxfoundation.org> (raw)
In-Reply-To: <20241011094830.1009557-1-andrej.v@skyrain.eu>

On Fri, 2024-10-11 at 11:48 +0200, Andrej Valek via lists.openembedded.org wrote:
> - update to next stable version 1.37.0
>  - refresh defconfig
>    - disable new applets (ip_link_can)
>    - enable new applets (time64, find_exec_ok, getfattr, udhcpd_bootp)
>  - remove and refresh already merged patches
> 
> Signed-off-by: Andrej Valek <andrej.v@skyrain.eu>
> ---
>  ...ab_1.36.1.bb => busybox-inittab_1.37.0.bb} |   0
>  ...01-awk-fix-precedence-of-relative-to.patch | 197 ------------------
>  ...-fix-segfault-when-compiled-by-clang.patch |  41 ----
>  ...1-awk.c-fix-CVE-2023-42366-bug-15874.patch |  37 ----
>  ...x-ternary-operator-and-precedence-of.patch |  96 ---------
>  .../busybox/busybox/CVE-2021-42380.patch      | 151 --------------
>  .../busybox/busybox/CVE-2023-42363.patch      |  67 ------
>  meta/recipes-core/busybox/busybox/defconfig   |   8 +-
>  .../{busybox_1.36.1.bb => busybox_1.37.0.bb}  |   8 +-
>  9 files changed, 7 insertions(+), 598 deletions(-)
>  rename meta/recipes-core/busybox/{busybox-inittab_1.36.1.bb => busybox-inittab_1.37.0.bb} (100%)
>  delete mode 100644 meta/recipes-core/busybox/busybox/0001-awk-fix-precedence-of-relative-to.patch
>  delete mode 100644 meta/recipes-core/busybox/busybox/0001-awk-fix-segfault-when-compiled-by-clang.patch
>  delete mode 100644 meta/recipes-core/busybox/busybox/0001-awk.c-fix-CVE-2023-42366-bug-15874.patch
>  delete mode 100644 meta/recipes-core/busybox/busybox/0002-awk-fix-ternary-operator-and-precedence-of.patch
>  delete mode 100644 meta/recipes-core/busybox/busybox/CVE-2021-42380.patch
>  delete mode 100644 meta/recipes-core/busybox/busybox/CVE-2023-42363.patch
>  rename meta/recipes-core/busybox/{busybox_1.36.1.bb => busybox_1.37.0.bb} (84%)

This would seem to be causing:

https://valkyrie.yoctoproject.org/#/builders/65/builds/225/steps/11/logs/stdio

and many other failures in that build:

https://valkyrie.yoctoproject.org/#/builders/29/builds/251

Cheers,

Richard


  reply	other threads:[~2024-10-11 12:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  9:48 [OE-core][PATCH] busybox: 1.36.1 -> 1.37.0 Andrej Valek
2024-10-11 12:33 ` Richard Purdie [this message]
2024-10-15 12:20   ` Andrej Valek
2024-10-18 13:48     ` Andrej Valek
2024-10-18 16:25       ` Ross Burton
2024-10-16  8:30 ` [OE-core][PATCH v2] " Andrej Valek
2024-10-19 16:02 ` [OE-core][PATCH v3] " Andrej Valek
2024-10-19 16:19   ` Patchtest results for " patchtest
2024-10-20  6:31     ` Andrej Valek
2024-10-23  9:14   ` Andrej Valek
2024-10-23 14:52     ` Richard Purdie
2024-10-23 15:09       ` Andrej Valek
2024-10-23 15:38         ` Richard Purdie
2024-10-23 17:24       ` Andrej Valek
2024-10-23 17:22 ` [OE-core][PATCH v4] " Andrej Valek
2024-10-23 17:33   ` Patchtest results for " patchtest

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9c4777b9bf0987e3a01138e664fdfbe45907035.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=andrej.v@skyrain.eu \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox