From: tim.orling@konsulko.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Upgrades for 2026-08-03
Date: Mon, 3 Aug 2026 16:26:37 -0700 [thread overview]
Message-ID: <cover.1785799308.git.tim.orling@konsulko.com> (raw)
From: Tim Orling <tim.orling@konsulko.com>
* Upgrade python3-cryptography,-vectors to 50.0.0
- all ptests pass in local core-image-ptest-python3-crytpography run
on qemux86-64
* Upgrade python3-uv-build to 0.12.1
- No issues seen in building for qemux86-64
* Upgrade python3-webosckets to 17.0.1
* Revert enabling ptest for python3-websockets, the tests/ are no longer
packaged in the sdist and this is intentional. The upstream docs
directly warn against packagers running the tests.
The following changes since commit fca8500024b7d3470fb046aaa5c7fef311ea018d:
libssh2: fix CVE-2026-66035 (2026-08-03 18:04:08 +0100)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib timo/upgrades-20260803
https://git.openembedded.org/openembedded-core-contrib/log/?h=timo/upgrades-20260803
for you to fetch changes up to 67b03cb15e4d75bced1c4837a0cf391105a2a379:
Revert "python3-websockets: enable ptest" (2026-08-03 16:18:14 -0700)
----------------------------------------------------------------
Tim Orling (4):
python3-cryptography{-vectors}: upgrade 49.0.0 -> 50.0.0
python3-uv-build: upgrade 0.11.32 -> 0.12.1
python3-websockets: upgrade 16.1.1 -> 17.0.1
Revert "python3-websockets: enable ptest"
.../distro/include/ptest-packagelists.inc | 1 -
.../python/python3-cryptography-common.inc | 2 +-
.../python/python3-cryptography-crates.inc | 40 ++---
.../python/python3-cryptography-vectors.bb | 2 +-
.../python/python3-cryptography.bb | 2 +-
...toml-remove-benchmark-disable-option.patch | 12 +-
.../python/python3-uv-build-crates.inc | 170 ++++++++++--------
..._0.11.32.bb => python3-uv-build_0.12.1.bb} | 2 +-
.../python/python3-websockets/run-ptest | 7 -
.../python/python3-websockets_16.1.1.bb | 29 ---
.../python/python3-websockets_17.0.1.bb | 15 ++
11 files changed, 140 insertions(+), 142 deletions(-)
rename meta/recipes-devtools/python/{python3-uv-build_0.11.32.bb => python3-uv-build_0.12.1.bb} (92%)
delete mode 100644 meta/recipes-devtools/python/python3-websockets/run-ptest
delete mode 100644 meta/recipes-devtools/python/python3-websockets_16.1.1.bb
create mode 100644 meta/recipes-devtools/python/python3-websockets_17.0.1.bb
--
2.47.3
next reply other threads:[~2026-08-03 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 23:26 tim.orling [this message]
2026-08-03 23:26 ` [PATCH 1/4] python3-cryptography{-vectors}: upgrade 49.0.0 -> 50.0.0 tim.orling
2026-08-03 23:26 ` [PATCH 2/4] python3-uv-build: upgrade 0.11.32 -> 0.12.1 tim.orling
2026-08-03 23:26 ` [PATCH 3/4] python3-websockets: upgrade 16.1.1 -> 17.0.1 tim.orling
2026-08-03 23:26 ` [PATCH 4/4] Revert "python3-websockets: enable ptest" tim.orling
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=cover.1785799308.git.tim.orling@konsulko.com \
--to=tim.orling@konsulko.com \
--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