From: ankur.tyagi85@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>,
Khem Raj <khem.raj@oss.qualcomm.com>,
Ankur Tyagi <ankur.tyagi85@gmail.com>
Subject: [oe][meta-oe][whinlatter][PATCH 4/19] openldap: upgrade 2.6.12 -> 2.6.13
Date: Mon, 30 Mar 2026 23:38:31 +1300 [thread overview]
Message-ID: <20260330103846.3381644-4-ankur.tyagi85@gmail.com> (raw)
In-Reply-To: <20260330103846.3381644-1-ankur.tyagi85@gmail.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
(cherry picked from commit b089df410f7877b4a45e79047e091ea8d3875bc5)
Changelog:
https://git.openldap.org/openldap/openldap/-/blob/OPENLDAP_REL_ENG_2_6_13/CHANGES?ref_type=tags
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
.../openldap/{openldap_2.6.12.bb => openldap_2.6.13.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-support/openldap/{openldap_2.6.12.bb => openldap_2.6.13.bb} (99%)
diff --git a/meta-oe/recipes-support/openldap/openldap_2.6.12.bb b/meta-oe/recipes-support/openldap/openldap_2.6.13.bb
similarity index 99%
rename from meta-oe/recipes-support/openldap/openldap_2.6.12.bb
rename to meta-oe/recipes-support/openldap/openldap_2.6.13.bb
index beee1b2738..59f20d0f08 100644
--- a/meta-oe/recipes-support/openldap/openldap_2.6.12.bb
+++ b/meta-oe/recipes-support/openldap/openldap_2.6.13.bb
@@ -21,7 +21,7 @@ SRC_URI = "http://www.openldap.org/software/download/OpenLDAP/openldap-release/$
file://0001-build-top.mk-unset-STRIP_OPTS.patch \
"
-SRC_URI[sha256sum] = "1716ad779e85d743694c3e3b05277fb71b6a5eadca43c7a958aa62683b22208e"
+SRC_URI[sha256sum] = "d693b49517a42efb85a1a364a310aed16a53d428d1b46c0d31ef3fba78fcb656"
DEPENDS = "util-linux groff-native"
next prev parent reply other threads:[~2026-03-30 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:38 [oe][meta-oe][whinlatter][PATCH 1/19] iwd: update 3.10 -> 3.11 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-oe][whinlatter][PATCH 2/19] iwd: upgrade 3.11 -> 3.12 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-oe][whinlatter][PATCH 3/19] openldap: upgrade 2.6.10 -> 2.6.12 ankur.tyagi85
2026-03-30 10:38 ` ankur.tyagi85 [this message]
2026-03-30 10:38 ` [oe][meta-webserver][whinlatter][PATCH 5/19] hiawatha: upgrade 11.7 -> 11.8 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-webserver][whinlatter][PATCH 6/19] hiawatha: fix SRC_URI ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-webserver][whinlatter][PATCH 7/19] nginx: upgrade 1.29.1 -> 1.29.2 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-webserver][whinlatter][PATCH 8/19] nginx: upgrade 1.28.2 -> 1.28.3 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-python][whinlatter][PATCH 9/19] python3-astroid: upgrade 4.0.2 -> 4.0.4 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-python][whinlatter][PATCH 10/19] python3-aiofiles: fix HOMEPAGE ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-python][whinlatter][PATCH 11/19] python3-alembic: add HOMEPAGE ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-python][whinlatter][PATCH 12/19] python3-apiflash: upgrade 3.0.0 -> 3.0.2 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 13/19] nautilus: upgrade 49.2 -> 49.3 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 14/19] nautilus: upgrade 49.3 -> 49.4 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 15/19] nautilus: update 49.4 -> 49.5 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 16/19] gvfs: upgrade 1.58.0 -> 1.58.1 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 17/19] gvfs: upgrade 1.58.1 -> 1.58.2 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 18/19] gvfs: upgrade 1.58.2 -> 1.58.4 ankur.tyagi85
2026-03-30 10:38 ` [oe][meta-gnome][whinlatter][PATCH 19/19] libwnck3: upgrade 43.2 -> 43.3 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=20260330103846.3381644-4-ankur.tyagi85@gmail.com \
--to=ankur.tyagi85@gmail.com \
--cc=khem.raj@oss.qualcomm.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=wangmy@fujitsu.com \
/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