From: ankur.tyagi85@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Ankur Tyagi <ankur.tyagi85@gmail.com>
Subject: [oe][meta-oe][PATCH 12/13] libp11: upgrade 0.4.18 -> 0.4.19
Date: Fri, 24 Jul 2026 14:14:06 +1200 [thread overview]
Message-ID: <20260724021407.2840261-12-ankur.tyagi85@gmail.com> (raw)
In-Reply-To: <20260724021407.2840261-1-ankur.tyagi85@gmail.com>
From: Ankur Tyagi <ankur.tyagi85@gmail.com>
Release Notes:
https://github.com/OpenSC/libp11/releases/tag/libp11-0.4.19
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
.../libp11/{libp11_0.4.18.bb => libp11_0.4.19.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-support/libp11/{libp11_0.4.18.bb => libp11_0.4.19.bb} (95%)
diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.18.bb b/meta-oe/recipes-support/libp11/libp11_0.4.19.bb
similarity index 95%
rename from meta-oe/recipes-support/libp11/libp11_0.4.18.bb
rename to meta-oe/recipes-support/libp11/libp11_0.4.19.bb
index 950880c1f2..237256e551 100644
--- a/meta-oe/recipes-support/libp11/libp11_0.4.18.bb
+++ b/meta-oe/recipes-support/libp11/libp11_0.4.19.bb
@@ -11,7 +11,7 @@ DEPENDS = "libtool openssl"
SRC_URI = "git://github.com/OpenSC/libp11.git;branch=master;protocol=https;tag=${BPN}-${PV}"
-SRCREV = "52a437cd51fcfbaaa8b27d2c6f562e88fd015c0d"
+SRCREV = "ae5756ccf5cb7929bb8edc986a9e6a65584406bd"
UPSTREAM_CHECK_GITTAGREGEX = "libp11-(?P<pver>\d+(\.\d+)+)"
next prev parent reply other threads:[~2026-07-24 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 2:13 [oe][meta-oe][PATCH 1/13] colord: upgrade 1.4.7 -> 1.4.8 ankur.tyagi85
2026-07-24 2:13 ` [oe][meta-oe][PATCH 2/13] iozone3: upgrade 508 -> 510 ankur.tyagi85
2026-07-24 2:13 ` [oe][meta-oe][PATCH 3/13] gensio: upgrade 3.0.2 -> 3.0.3 ankur.tyagi85
2026-07-24 2:13 ` [oe][meta-oe][PATCH 4/13] cryptsetup: upgrade 2.8.6 -> 2.8.7 ankur.tyagi85
2026-07-24 2:13 ` [oe][meta-oe][PATCH 5/13] simpleiot: upgrade 0.18.4 -> 0.18.5 ankur.tyagi85
2026-07-24 2:14 ` [oe][meta-oe][PATCH 6/13] valkey: upgrade 9.1.0 -> 9.1.1 ankur.tyagi85
2026-07-24 2:14 ` [oe][meta-oe][PATCH 7/13] htop: upgrade 3.5.1 -> 3.5.2 ankur.tyagi85
2026-07-24 2:14 ` [oe][meta-oe][PATCH 8/13] libusb-compat: upgrade 0.1.8 -> 0.1.9 ankur.tyagi85
2026-07-24 2:14 ` [oe][meta-oe][PATCH 9/13] jq: upgrade 1.8.1 -> 1.8.2 ankur.tyagi85
2026-07-24 2:14 ` [oe][meta-oe][PATCH 10/13] freerdp3: upgrade 3.28.0 -> 3.30.0 ankur.tyagi85
2026-07-24 2:14 ` [oe][meta-oe][PATCH 11/13] libraw: upgrade 0.22.1 -> 0.22.2 ankur.tyagi85
2026-07-24 2:14 ` ankur.tyagi85 [this message]
2026-07-24 2:14 ` [oe][meta-oe][PATCH 13/13] liboauth2: upgarde 2.2.0 -> 2.3.0 ankur.tyagi85
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=20260724021407.2840261-12-ankur.tyagi85@gmail.com \
--to=ankur.tyagi85@gmail.com \
--cc=openembedded-devel@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;
as well as URLs for NNTP newsgroup(s).