From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] upgrades: expat, libpcre2, gnupg, librepo
Date: Tue, 1 Sep 2026 08:21:21 +0200 [thread overview]
Message-ID: <20260901062125.37994-1-jaipaul.cheernam@est.tech> (raw)
A batch of routine version upgrades for four recipes:
expat: 2.8.3 -> 2.8.4
libpcre2: 10.47 -> 10.48
gnupg: 2.5.21 -> 2.5.22
librepo: 1.20.0 -> 1.21.0
Jaipaul Cheernam (4):
expat: upgrade 2.8.3 -> 2.8.4
libpcre2: upgrade 10.47 -> 10.48
gnupg: upgrade 2.5.21 -> 2.5.22
librepo: upgrade 1.20.0 -> 1.21.0
.../expat/{expat_2.8.3.bb => expat_2.8.4.bb} | 2 +-
...btain-PYTHON_INSTALL_DIR-by-running-p.patch | 4 ++--
.../{librepo_1.20.0.bb => librepo_1.21.0.bb} | 2 +-
...verride-init-is-not-needed-with-gcc-9.patch | 2 +-
...e-a-custom-value-for-the-location-of-.patch | 4 ++--
...-use-pkgconfig-instead-of-npth-config.patch | 2 +-
.../recipes-support/gnupg/gnupg/relocate.patch | 18 +++++++++---------
.../gnupg/{gnupg_2.5.21.bb => gnupg_2.5.22.bb} | 2 +-
.../{libpcre2_10.47.bb => libpcre2_10.48.bb} | 2 +-
9 files changed, 19 insertions(+), 19 deletions(-)
rename meta/recipes-core/expat/{expat_2.8.3.bb => expat_2.8.4.bb} (92%)
rename meta/recipes-devtools/librepo/{librepo_1.20.0.bb => librepo_1.21.0.bb} (94%)
rename meta/recipes-support/gnupg/{gnupg_2.5.21.bb => gnupg_2.5.22.bb} (97%)
rename meta/recipes-support/libpcre/{libpcre2_10.47.bb => libpcre2_10.48.bb} (96%)
next reply other threads:[~2026-09-01 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 6:21 Jaipaul Cheernam [this message]
2026-09-01 6:21 ` [PATCH 1/4] expat: upgrade 2.8.3 -> 2.8.4 Jaipaul Cheernam
2026-09-01 6:21 ` [PATCH 2/4] libpcre2: upgrade 10.47 -> 10.48 Jaipaul Cheernam
2026-09-01 6:21 ` [PATCH 3/4] gnupg: upgrade 2.5.21 -> 2.5.22 Jaipaul Cheernam
2026-09-01 6:21 ` [PATCH 4/4] librepo: upgrade 1.20.0 -> 1.21.0 Jaipaul Cheernam
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=20260901062125.37994-1-jaipaul.cheernam@est.tech \
--to=jaipaul.cheernam@est.tech \
--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