All of lore.kernel.org
 help / color / mirror / Atom feed
From: <daniel.turull@ericsson.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Daniel Turull <daniel.turull@ericsson.com>
Subject: [wrynose][PATCH 00/20] backport inherit upstream-stable-release-point
Date: Wed, 2 Sep 2026 11:59:00 +0200	[thread overview]
Message-ID: <20260902095920.2840293-1-daniel.turull@ericsson.com> (raw)

From: Daniel Turull <daniel.turull@ericsson.com>

This series backports 'upstream-stable-release-point' support from
OE-Core master to wrynose. The first three commits are the
infrastructure, cherry-picked from the OE-Core originals:

  - recipeutils: add optional stable_upgrade parameter to
    get_recipe_upgrade_status, which passes UPSTREAM_STABLE_RELEASE_REGEX
    to the fetch method as filter_regex
  - upstream-stable-release-point.bbclass, which derives
    UPSTREAM_STABLE_RELEASE_REGEX from the recipe version so that stable
    point-release upgrades can be recognised
  - devtool/upgrade.py: add --stable option, the user-facing entry point
    that enables stable-only upgrade checking

The remaining 17 commits make the corresponding recipes inherit this
bbclass.

A companion bitbake series (filter_regex support for
latest_versionstring, also by Chen Qi) is sent separately against
bitbake 2.18. Without it the --stable option requests a
filter_regex parameter that older fetch2 implementations do not accept.

Each commit is cherry-picked with -x from the OE-Core original. Wrynose
carries older versions of several recipes, so those commits were applied
to the corresponding wrynose recipe file (e.g. git_2.53.0.bb rather than
git_2.55.0.bb); the adapted commits carry an 'Adapted for wrynose' note
in the commit message.

Pending TSC approval. Request sent.

Chen Qi (3):
  recipeutils: add optional stable_upgrade parameter to
    get_recipe_upgrade_status
  upstream-stable-release-point.bbclass: add bbclass for stable point
    upgrade
  devtool/upgrade.py: add --stable option

Daniel Turull (17):
  systemd: inherit upstream-stable-release-point
  glib-2.0: inherit upstream-stable-release-point
  dbus: inherit upstream-stable-release-point
  xz: inherit upstream-stable-release-point
  git: inherit upstream-stable-release-point
  perl: inherit upstream-stable-release-point
  libxml2: inherit upstream-stable-release-point
  python3: inherit upstream-stable-release-point
  openssl: inherit upstream-stable-release-point
  binutils: inherit upstream-stable-release-point
  libgcrypt: inherit upstream-stable-release-point
  sqlite3: inherit upstream-stable-release-point
  lttng-tools: inherit upstream-stable-release-point
  util-linux: inherit upstream-stable-release-point
  lttng-ust: inherit upstream-stable-release-point
  babeltrace2: inherit upstream-stable-release-point
  lttng-modules: inherit upstream-stable-release-point

 .../upstream-stable-release-point.bbclass     | 21 +++++++++++++++++
 meta/lib/oe/recipeutils.py                    | 23 ++++++++++++++-----
 .../openssl/openssl_3.5.7.bb                  |  5 ++++
 meta/recipes-core/dbus/dbus_1.16.2.bb         |  6 +++++
 meta/recipes-core/glib-2.0/glib.inc           |  4 +++-
 meta/recipes-core/libxml/libxml2_2.15.2.bb    |  4 ++++
 meta/recipes-core/systemd/systemd.inc         |  5 ++++
 meta/recipes-core/util-linux/util-linux.inc   |  4 ++++
 meta/recipes-devtools/binutils/binutils.inc   |  5 ++++
 meta/recipes-devtools/git/git_2.53.0.bb       |  4 ++++
 meta/recipes-devtools/perl/perl_5.42.0.bb     |  2 +-
 .../recipes-devtools/python/python3_3.14.6.bb |  4 ++++
 meta/recipes-extended/xz/xz_5.8.2.bb          |  4 ++++
 .../recipes-kernel/lttng/babeltrace2_2.1.2.bb |  4 +++-
 .../lttng/lttng-modules_2.14.4.bb             |  6 +++++
 .../lttng/lttng-tools_2.14.1.bb               |  2 +-
 meta/recipes-kernel/lttng/lttng-ust_2.14.0.bb |  4 +++-
 .../libgcrypt/libgcrypt_1.12.1.bb             |  2 +-
 meta/recipes-support/sqlite/sqlite3.inc       |  2 +-
 scripts/lib/devtool/upgrade.py                |  9 +++++---
 20 files changed, 104 insertions(+), 16 deletions(-)
 create mode 100644 meta/classes-recipe/upstream-stable-release-point.bbclass



             reply	other threads:[~2026-09-02  9:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  9:59 daniel.turull [this message]
2026-09-02  9:59 ` [wrynose][PATCH 01/20] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 02/20] upstream-stable-release-point.bbclass: add bbclass for stable point upgrade daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 03/20] devtool/upgrade.py: add --stable option daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 04/20] systemd: inherit upstream-stable-release-point daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 05/20] glib-2.0: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 06/20] dbus: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 07/20] xz: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 08/20] git: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 09/20] perl: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 10/20] libxml2: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 11/20] python3: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 12/20] openssl: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 13/20] binutils: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 14/20] libgcrypt: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 15/20] sqlite3: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 16/20] lttng-tools: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 17/20] util-linux: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 18/20] lttng-ust: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 19/20] babeltrace2: " daniel.turull
2026-09-02  9:59 ` [wrynose][PATCH 20/20] lttng-modules: " daniel.turull

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=20260902095920.2840293-1-daniel.turull@ericsson.com \
    --to=daniel.turull@ericsson.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 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.