2.8.21 (September 3, 2026)
--------------------------

This release fixes two bugs in composite dictionaries: first, if any
dictionary creation failed during creation of a composite dictionary,
dictionaries already created would be leaked; and secondly, the broker error
status could end up indicating an error incorrectly when one provider or
language failed and a fallback later succeeded. Thanks to @lpyuu for the
report and fixes.

2.8.20 (August 25, 2026)
------------------------

This release improves the man page for enchant(1), mostly by documenting
Ispell command-line options and pipe-mode commands that it ignores.

Signed-off-by: Richard Purdie <[email protected]>
---
 .../enchant/{enchant2_2.8.19.bb => enchant2_2.8.21.bb}          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/enchant/{enchant2_2.8.19.bb => enchant2_2.8.21.bb} 
(91%)

diff --git a/meta/recipes-support/enchant/enchant2_2.8.19.bb 
b/meta/recipes-support/enchant/enchant2_2.8.21.bb
similarity index 91%
rename from meta/recipes-support/enchant/enchant2_2.8.19.bb
rename to meta/recipes-support/enchant/enchant2_2.8.21.bb
index f5d5897fd06..49d953a6c87 100644
--- a/meta/recipes-support/enchant/enchant2_2.8.19.bb
+++ b/meta/recipes-support/enchant/enchant2_2.8.21.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] = 
"c8d70991d544ee39274b96bd01d2858a009fe732ff43f2aaf605fd61ecd06f60"
+SRC_URI[sha256sum] = 
"dd2a762697c463148a8f59867089a5ebf2dd1449d869f93764b76c12bcf8acc0"
 
 GITHUB_BASE_URI = "https://github.com/rrthomas/enchant/releases";
 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245117): 
https://lists.openembedded.org/g/openembedded-core/message/245117
Mute This Topic: https://lists.openembedded.org/mt/121086832/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to