From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/6] enchant2: upgrade 2.6.9 -> 2.7.2
Date: Tue, 7 May 2024 10:23:03 +0800 [thread overview]
Message-ID: <20240507022308.13637-1-anuj.mittal@intel.com> (raw)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
.../enchant/{enchant2_2.6.9.bb => enchant2_2.7.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/enchant/{enchant2_2.6.9.bb => enchant2_2.7.2.bb} (91%)
diff --git a/meta/recipes-support/enchant/enchant2_2.6.9.bb b/meta/recipes-support/enchant/enchant2_2.7.2.bb
similarity index 91%
rename from meta/recipes-support/enchant/enchant2_2.6.9.bb
rename to meta/recipes-support/enchant/enchant2_2.7.2.bb
index aaf3525ad8c..08998dd48fe 100644
--- a/meta/recipes-support/enchant/enchant2_2.6.9.bb
+++ b/meta/recipes-support/enchant/enchant2_2.7.2.bb
@@ -12,7 +12,7 @@ DEPENDS = "glib-2.0 groff-native"
inherit autotools pkgconfig github-releases
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/enchant-${PV}.tar.gz"
-SRC_URI[sha256sum] = "d9a5a10dc9b38a43b3a0fa22c76ed6ebb7e09eb535aff62954afcdbd40efff6b"
+SRC_URI[sha256sum] = "7cc3400a6657974a740b6e3c2568e2935c70e5302f07fadb2095366b75ecad6f"
GITHUB_BASE_URI = "https://github.com/AbiWord/enchant/releases"
--
2.45.0
next reply other threads:[~2024-05-07 2:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 2:23 Anuj Mittal [this message]
2024-05-07 2:23 ` [PATCH 2/6] harfbuzz: upgrade 8.3.1 -> 8.4.0 Anuj Mittal
2024-05-07 2:23 ` [PATCH 3/6] libproxy: upgrade 0.5.4 -> 0.5.6 Anuj Mittal
2024-05-07 2:23 ` [PATCH 4/6] libsolv: upgrade 0.7.28 -> 0.7.29 Anuj Mittal
2024-05-07 2:23 ` [PATCH 5/6] mmc-utils: upgrade to latest revision Anuj Mittal
2024-05-07 2:23 ` [PATCH 6/6] sqlite3: upgrade 3.45.1 -> 3.45.3 Anuj Mittal
2024-05-09 12:49 ` [OE-core] [PATCH 1/6] enchant2: upgrade 2.6.9 -> 2.7.2 Ross Burton
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=20240507022308.13637-1-anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).