From: ankur.tyagi85@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Ankur Tyagi <ankur.tyagi85@gmail.com>
Subject: [oe][meta-networking][PATCH 1/11] open62541: upgrade 1.5.6 -> 1.5.7
Date: Sun, 30 Aug 2026 12:50:05 +1200 [thread overview]
Message-ID: <20260830005015.2555347-1-ankur.tyagi85@gmail.com> (raw)
From: Ankur Tyagi <ankur.tyagi85@gmail.com>
Changelog:
https://github.com/open62541/open62541/releases/tag/v1.5.7
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
.../opcua/{open62541_1.5.6.bb => open62541_1.5.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-networking/recipes-protocols/opcua/{open62541_1.5.6.bb => open62541_1.5.7.bb} (98%)
diff --git a/meta-networking/recipes-protocols/opcua/open62541_1.5.6.bb b/meta-networking/recipes-protocols/opcua/open62541_1.5.7.bb
similarity index 98%
rename from meta-networking/recipes-protocols/opcua/open62541_1.5.6.bb
rename to meta-networking/recipes-protocols/opcua/open62541_1.5.7.bb
index 8126132773..10e2e36675 100644
--- a/meta-networking/recipes-protocols/opcua/open62541_1.5.6.bb
+++ b/meta-networking/recipes-protocols/opcua/open62541_1.5.7.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = "\
"
SRCREV_FORMAT = "opcua_mdnsd_ua-nodeset_mqtt-c"
-SRCREV_opcua = "cd69ed6f6a4d46966f67794e23a7b7b331f7d402"
+SRCREV_opcua = "d1173ccc31560ffc60c29e24ce8adb19f8c3c686"
SRCREV_mdnsd = "c1be962b37e4b952625d9b0a873e5ca619b1a35a"
SRCREV_ua-nodeset = "257db9ad98ee7ba4b67d3500b54bfc9d744a36af"
SRCREV_mqtt-c = "0f4c34c8cc00b16cfee094745d68b8cdbaecd8e0"
next reply other threads:[~2026-08-30 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 0:50 ankur.tyagi85 [this message]
2026-08-30 0:50 ` [oe][meta-multimedia][PATCH 2/11] mpd: upgrade 0.24.14 -> 0.24.15 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-networking][PATCH 3/11] dovecot: upgrade 2.4.4 -> 2.4.5 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-oe][PATCH 4/11] grpc: upgrade 1.83.0 -> 1.83.1 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 5/11] python3-virtualenv: upgrade 21.7.4 -> 21.7.7 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 6/11] python3-tox: upgrade 4.60.0 -> 4.61.1 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 7/11] python3-sdbus: upgrade 0.14.2 -> 0.14.3 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 8/11] python3-simplejson: upgrade 4.1.1 -> 4.1.2 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 9/11] python3-discovery: upgrade 1.5.2 -> 1.6.0 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 10/11] python3-cmd2: upgrade 4.2.1 -> 4.2.2 ankur.tyagi85
2026-08-30 0:50 ` [oe][meta-python][PATCH 11/11] python3-colorlog: upgrade 6.11.0 -> 6.12.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=20260830005015.2555347-1-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