All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] libpcre2: upgrade 10.47 -> 10.48
Date: Tue,  1 Sep 2026 08:21:23 +0200	[thread overview]
Message-ID: <20260901062125.37994-3-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20260901062125.37994-1-jaipaul.cheernam@est.tech>

Release: https://github.com/PCRE2Project/pcre2/releases/tag/pcre2-10.48

Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
---
 .../libpcre/{libpcre2_10.47.bb => libpcre2_10.48.bb}            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/libpcre/{libpcre2_10.47.bb => libpcre2_10.48.bb} (96%)

diff --git a/meta/recipes-support/libpcre/libpcre2_10.47.bb b/meta/recipes-support/libpcre/libpcre2_10.48.bb
similarity index 96%
rename from meta/recipes-support/libpcre/libpcre2_10.47.bb
rename to meta/recipes-support/libpcre/libpcre2_10.48.bb
index 35330845d1..d5daff03c0 100644
--- a/meta/recipes-support/libpcre/libpcre2_10.47.bb
+++ b/meta/recipes-support/libpcre/libpcre2_10.48.bb
@@ -19,7 +19,7 @@ SRC_URI = "${GITHUB_BASE_URI}/download/pcre2-${PV}/pcre2-${PV}.tar.bz2 \
 GITHUB_BASE_URI = "https://github.com/PCRE2Project/pcre2/releases"
 UPSTREAM_CHECK_REGEX = "releases/tag/pcre2-(?P<pver>\d+(\.\d+)+)$"
 
-SRC_URI[sha256sum] = "47fe8c99461250d42f89e6e8fdaeba9da057855d06eb7fc08d9ca03fd08d7bc7"
+SRC_URI[sha256sum] = "b6c68fdf6f3ac31388b50aa89ff0fc49c00c987c16e7b5146491d12003f2c8ed"
 
 CVE_PRODUCT = "pcre2"
 


  parent 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 [PATCH 0/4] upgrades: expat, libpcre2, gnupg, librepo Jaipaul Cheernam
2026-09-01  6:21 ` [PATCH 1/4] expat: upgrade 2.8.3 -> 2.8.4 Jaipaul Cheernam
2026-09-01  6:21 ` Jaipaul Cheernam [this message]
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-3-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 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.