From: "Yoann Congal" <yoann.congal@smile.fr>
To: <dkelaiya@cisco.com>, <openembedded-core@lists.openembedded.org>
Cc: "Vijay Anusuri" <vanusuri@mvista.com>
Subject: Re: [OE-core][wrynose][PATCH 1/3] python3: upgrade 3.14.7 -> 3.14.8
Date: Mon, 19 Oct 2026 16:18:43 +0200 [thread overview]
Message-ID: <DM8VOXLTFEIS.6MCCPMLQ3EI@smile.fr> (raw)
In-Reply-To: <20261016053944.3835603-2-dkelaiya@cisco.com>
On Fri Oct 16, 2026 at 7:39 AM CEST, Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Vijay Anusuri <vanusuri@mvista.com>
>
> Release information:
> * https://www.python.org/downloads/release/python-3148/
> * Python 3.14.8 is an expedited security release and the eighth
> maintenance release of 3.14, containing around 354 bugfixes,
> build improvements and documentation changes from 142 contributors
> since 3.14.7.
>
> Handles CVE-2026-19445 CVE-2026-19553 CVE-2026-19672 CVE-2026-15310
> CVE-2026-15806 CVE-2026-17084
>
> Changelog: https://docs.python.org/3/whatsnew/changelog.html#python-3-14-8-final
>
> Backport Changes:
> - The new test_append_limited_history ptest fails on musl with the
> default libedit backend. libedit opens the history file for
> appending, then emits a header if ftell() reports offset zero.
> musl leaves the initial append stream at that offset, so a second
> _HiStOrY_V2_ header is appended and CPython's truncation keeps it
> in place of the expected history entry. Skip only that test on musl
> until the libedit interaction is fixed.
>
> OE-Core failure report:
> https://patchwork.yoctoproject.org/project/oe-core/patch/010101a0f6296539-d5cd290b-b68d-4632-a774-5263fa10249e-000000@us-west-2.amazonses.com/
>
> Upstream issue:
> https://github.com/python/cpython/issues/123018
>
> Signed-off-by: Vijay Anusuri <vanusuri@mvista.com>
> Signed-off-by: Darsh Kelaiya <dkelaiya@cisco.com>
> ---
> .../python/{python3_3.14.7.bb => python3_3.14.8.bb} | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
> rename meta/recipes-devtools/python/{python3_3.14.7.bb => python3_3.14.8.bb} (98%)
This series can only be reviewed for wrynose once python3 upgraded on
master and blacksail (both 3.14.7 right now)
I think I saw 2 attempts to upgrade on master and none yet for blacksail:
* python3: upgrade 3.14.7 -> 3.14.8 - Patchwork
https://patchwork.yoctoproject.org/project/oe-core/patch/20261008090135.1485765-1-vanusuri@mvista.com/
* [v2,2/2] python3: upgrade 3.14.7 -> 3.15.0 - Patchwork
https://patchwork.yoctoproject.org/project/oe-core/patch/20261012103426.3090-2-jaipaul.cheernam@est.tech/
Maybe you can help by reviewing master's patch and, then, sending
blacksail backports?
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-10-19 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 5:39 [Internal Review][OE-core][wrynose][PATCH 0/3] python3: upgrade to 3.14.8 and backport security fixes Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16 5:39 ` [OE-core][wrynose][PATCH 1/3] python3: upgrade 3.14.7 -> 3.14.8 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-19 14:18 ` Yoann Congal [this message]
2026-10-16 5:39 ` [OE-core][wrynose][PATCH 2/3] python3: fix CVE-2025-15367 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16 5:39 ` [OE-core][wrynose][PATCH 3/3] python3: fix CVE-2026-87910 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-14 9:42 ` Yoann Congal
2026-11-17 12:51 ` [wrynose][PATCH " Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16 5:54 ` [OE-core][wrynose][PATCH 0/3] python3: upgrade to 3.14.8 and backport security fixes Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
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=DM8VOXLTFEIS.6MCCPMLQ3EI@smile.fr \
--to=yoann.congal@smile.fr \
--cc=dkelaiya@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=vanusuri@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.