Openembedded Core Discussions
 help / color / mirror / Atom feed
From: tim.orling@konsulko.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] Upgrades (AUH) for 2025-06-24
Date: Tue, 24 Jun 2025 16:13:50 -0700	[thread overview]
Message-ID: <cover.1750806216.git.tim.orling@konsulko.com> (raw)

From: Tim Orling <tim.orling@konsulko.com>

Upgrades mostly from AUH, with the exception of python3-maturin
which were done manually (they should work with AUH again after 1.8.7 fixed
the SRC_URI issue due to patch).

The following changes since commit ea4b963d9a59210bb9eeaee55dcb6378ef65baba:

  buildhistory: Drop BUILDHISTORY_RESET due to reliability issues (2025-06-24 13:53:23 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib timo/upgrades-2025-06-24
  https://git.yoctoproject.org/poky-contrib/log/?h=timo/upgrades-2025-06-24

Tim Orling (6):
  python3-wheel: upgrade 0.45.1 -> 0.46.1
  python3-maturin: upgrade 1.8.6 -> 1.8.7
  python3-maturin: upgrade 1.8.7 -> 1.9.0
  python3-cryptography{-vectors}: upgrade 45.0.3 -> 45.0.4
  python3-certifi: upgrade 2025.4.26 -> 2025.6.15
  python3-pytest-subtests: upgrade 0.14.1 -> 0.14.2

 ...5.4.26.bb => python3-certifi_2025.6.15.bb} |  4 +-
 .../python/python3-cryptography-common.inc    |  2 +-
 .../python/python3-cryptography-vectors.bb    |  2 +-
 .../python/python3-cryptography.bb            |  2 +-
 ...toml-remove-benchmark-disable-option.patch |  4 +-
 .../python/python3-maturin-crates.inc         | 54 ++++++++++++-------
 ...urin_1.8.6.bb => python3-maturin_1.9.0.bb} |  4 +-
 ...1.bb => python3-pytest-subtests_0.14.2.bb} |  2 +-
 ...heel_0.45.1.bb => python3-wheel_0.46.1.bb} |  2 +-
 9 files changed, 46 insertions(+), 30 deletions(-)
 rename meta/recipes-devtools/python/{python3-certifi_2025.4.26.bb => python3-certifi_2025.6.15.bb} (80%)
 rename meta/recipes-devtools/python/{python3-maturin_1.8.6.bb => python3-maturin_1.9.0.bb} (78%)
 rename meta/recipes-devtools/python/{python3-pytest-subtests_0.14.1.bb => python3-pytest-subtests_0.14.2.bb} (88%)
 rename meta/recipes-devtools/python/{python3-wheel_0.45.1.bb => python3-wheel_0.46.1.bb} (85%)

-- 
2.43.0



             reply	other threads:[~2025-06-24 23:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 23:13 tim.orling [this message]
2025-06-24 23:13 ` [PATCH 1/6] python3-wheel: upgrade 0.45.1 -> 0.46.1 tim.orling
2025-06-26 10:19   ` [OE-core] " Ross Burton
2025-06-26 14:55     ` Tim Orling
2025-06-26 15:25   ` [PATCH 1/6 v2] python3-wheel: upgrade 0.45.1 -> 0.46.1; add ptest tim.orling
2025-06-24 23:13 ` [PATCH 2/6] python3-maturin: upgrade 1.8.6 -> 1.8.7 tim.orling
2025-06-24 23:33   ` Patchtest results for " patchtest
2025-06-25  4:24   ` [PATCH 2/6 v2] " tim.orling
2025-06-25  4:46     ` Patchtest results for " patchtest
2025-06-24 23:13 ` [PATCH 3/6] python3-maturin: upgrade 1.8.7 -> 1.9.0 tim.orling
2025-06-24 23:13 ` [PATCH 4/6] python3-cryptography{-vectors}: upgrade 45.0.3 -> 45.0.4 tim.orling
2025-06-24 23:13 ` [PATCH 5/6] python3-certifi: upgrade 2025.4.26 -> 2025.6.15 tim.orling
2025-06-24 23:13 ` [PATCH 6/6] python3-pytest-subtests: upgrade 0.14.1 -> 0.14.2 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.1750806216.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