From: <daniel.turull@ericsson.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <richard.purdie@linuxfoundation.org>, <paul@pbarker.dev>,
<Randy.MacLeod@windriver.com>, <alex.kanavin@gmail.com>,
Daniel Turull <daniel.turull@ericsson.com>
Subject: [PATCH 5/7] xz: inherit upstream-stable-release-point
Date: Fri, 31 Jul 2026 14:25:20 +0200 [thread overview]
Message-ID: <20260731122522.1647968-6-daniel.turull@ericsson.com> (raw)
In-Reply-To: <20260731122522.1647968-1-daniel.turull@ericsson.com>
From: Daniel Turull <daniel.turull@ericsson.com>
XZ Utils's README documents that an even minor (Y) is a stable series
where the revision (Z) "is incremented when bugs get fixed without adding
any new features". So upgrades within a major.minor are stable point
upgrades per the OE-Core stable release policy (ref-manual, "Stable Point
Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades
https://github.com/tukaani-project/xz/blob/v5.8.3/README#L138
Checked the last two point releases for feature creep:
5.8.3 (Mar 31 2026): one CVE (CVE-2026-34743, a buffer overflow in
lzma_index_append), one invalid-memory-access fix, build portability
fixes for Windows ARM64EC and Hurd, and man page translations. No new
options or API.
5.8.2 (Dec 17 2025): build portability fixes for four toolchains, a
RHEL 9 kernel-bug workaround, and a resource-aware memory-limit default
tweak that is a bugfix rather than a new feature. No new options or
API.
Already tracked this way on the OE stable branches, counting only bumps
made since each branch forked from master: kirkstone picked up 5.2.6 and
scarthgap 5.4.7, one bump each.
AI-Generated: Kiro with Claude Opus 5
Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
---
meta/recipes-extended/xz/xz_5.8.3.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-extended/xz/xz_5.8.3.bb b/meta/recipes-extended/xz/xz_5.8.3.bb
index b76b1726e4..0735696011 100644
--- a/meta/recipes-extended/xz/xz_5.8.3.bb
+++ b/meta/recipes-extended/xz/xz_5.8.3.bb
@@ -34,6 +34,10 @@ SRC_URI[sha256sum] = "3d3a1b973af218114f4f889bbaa2f4c037deaae0c8e815eec381c3d546
UPSTREAM_CHECK_REGEX = "releases/tag/v(?P<pver>\d+(\.\d+)+)"
UPSTREAM_CHECK_URI = "https://github.com/tukaani-project/xz/releases/"
+# XZ Utils publishes bugfix/security-only micro releases on its stable
+# (even-minor) branches.
+inherit upstream-stable-release-point
+
CACHED_CONFIGUREVARS += "gl_cv_posix_shell=/bin/sh"
inherit autotools gettext ptest
next prev parent reply other threads:[~2026-07-31 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 12:25 [PATCH 0/7] Mark recipes whose point releases are fixes-only (1/3) daniel.turull
2026-07-31 12:25 ` [PATCH 1/7] util-linux: inherit upstream-stable-release-point daniel.turull
2026-07-31 12:25 ` [PATCH 2/7] systemd: " daniel.turull
2026-07-31 12:25 ` [PATCH 3/7] glib-2.0: " daniel.turull
2026-07-31 12:25 ` [PATCH 4/7] dbus: " daniel.turull
2026-07-31 12:25 ` daniel.turull [this message]
2026-07-31 12:25 ` [PATCH 6/7] git: " daniel.turull
2026-07-31 12:25 ` [PATCH 7/7] perl: " 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=20260731122522.1647968-6-daniel.turull@ericsson.com \
--to=daniel.turull@ericsson.com \
--cc=Randy.MacLeod@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=richard.purdie@linuxfoundation.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