From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: peter.marko@siemens.com,
openembedded-core@lists.openembedded.org,
Steve Sakoman <steve@sakoman.com>
Subject: Re: [OE-core][PATCH] openssl: upgrade 3.3.1 -> 3.4.0
Date: Thu, 24 Oct 2024 09:19:21 +0100 [thread overview]
Message-ID: <d51cd8af63e7187d735d8ad7a6d72ded7fcf81a8.camel@linuxfoundation.org> (raw)
In-Reply-To: <20241023184829.2216595-1-peter.marko@siemens.com>
On Wed, 2024-10-23 at 20:48 +0200, Peter Marko via lists.openembedded.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> Release information:
> https://github.com/openssl/openssl/blob/openssl-3.4/NEWS.md#major-changes-between-openssl-33-and-openssl-340-22-oct-2024
>
> Handles CVE-2024-9143
>
> Refreshed patches.
>
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
> ...ke-history-reporting-when-test-fails.patch | 53 ++++++++-----------
> ...1-Configure-do-not-tweak-mips-cflags.patch | 4 +-
> ...sysroot-and-debug-prefix-map-from-co.patch | 4 +-
> .../{openssl_3.3.1.bb => openssl_3.4.0.bb} | 2 +-
> 4 files changed, 28 insertions(+), 35 deletions(-)
> rename meta/recipes-connectivity/openssl/{openssl_3.3.1.bb => openssl_3.4.0.bb} (99%)
Unfortunately this causes a regression in python3's ptest:
https://valkyrie.yoctoproject.org/#/builders/73/builds/270
I did revert this patch and tested a build and that passes so it is definitely from here.
I'm trying this in conjunction with the python 3.13 upgrade which might
let us fix this for master but if so, the problem for styhead and
earlier will probably remain.
There was a related python bug:
https://github.com/python/cpython/issues/87743
Copying Steve so he knows that gremlins lurk here...
Cheers,
Richard
next prev parent reply other threads:[~2024-10-24 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 18:48 [OE-core][PATCH] openssl: upgrade 3.3.1 -> 3.4.0 Peter Marko
2024-10-24 8:19 ` Richard Purdie [this message]
[not found] ` <180155B44E341F73.23694@lists.openembedded.org>
2024-10-24 10:14 ` Richard Purdie
2024-10-24 18:56 ` Marko, Peter
2024-11-08 21:46 ` Randy MacLeod
2024-11-29 18:33 ` Marko, Peter
2024-11-30 8:10 ` Alexander Kanavin
2024-11-30 8:11 ` Richard Purdie
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=d51cd8af63e7187d735d8ad7a6d72ded7fcf81a8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=steve@sakoman.com \
/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