From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] enchant2: update to 2.3.3.
Date: Sat, 07 Jan 2023 23:22:36 +0100 [thread overview]
Message-ID: <20230107222236._d8VSGsUnkan33rMKJeIw1BTe6JtYqcCQGo_nELVgk4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41512@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages enchant-2.3.3
https://github.com/void-linux/void-packages/pull/41512
enchant2: update to 2.3.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
```
SUMMARY
pkg host target cross result
enchant2 x86_64 x86_64 n OK
enchant2 x86_64-musl x86_64-musl n OK
enchant2 i686 i686 n OK
enchant2 x86_64-musl aarch64-musl y OK
enchant2 x86_64-musl aarch64 y OK
enchant2 x86_64-musl armv7l-musl y OK
enchant2 x86_64-musl armv7l y OK
enchant2 x86_64-musl armv6l-musl y OK
enchant2 x86_64-musl armv6l y OK
```
A patch file from https://github.com/void-linux/void-packages/pull/41512.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-enchant-2.3.3-41512.patch --]
[-- Type: text/x-diff, Size: 1371 bytes --]
From 5f68621cd896faf9979258a5f37509cfd75d811a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 7 Jan 2023 22:18:51 +0000
Subject: [PATCH] enchant2: update to 2.3.3.
---
srcpkgs/enchant2/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/enchant2/template b/srcpkgs/enchant2/template
index 51a6c64eff35..572af001c442 100644
--- a/srcpkgs/enchant2/template
+++ b/srcpkgs/enchant2/template
@@ -1,7 +1,7 @@
# Template file for 'enchant2'
pkgname=enchant2
-version=2.3.2
-revision=2
+version=2.3.3
+revision=1
build_style=gnu-configure
# so package doesn't conflict with enchant's /usr/share/enchant/enchant.ordering;
# might be a bug in their build system that only this directory and/or file aren't
@@ -20,8 +20,9 @@ short_desc="Generic spell checking library"
maintainer="Orphaned <orphan@voidlinux.org>"
license="LGPL-2.1-or-later"
homepage="https://abiword.github.io/enchant/"
+changelog="https://raw.githubusercontent.com/AbiWord/enchant/master/NEWS"
distfiles="https://github.com/AbiWord/enchant/releases/download/v${version}/enchant-${version}.tar.gz"
-checksum=ce9ba47fd4d34031bd69445598a698a6611602b2b0e91d705e91a6f5099ead6e
+checksum=3da12103f11cf49c3cf2fd2ce3017575c5321a489e5b9bfa81dd91ec413f3891
make_check=no # tests broken
enchant2-devel_package() {
next prev parent reply other threads:[~2023-01-07 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 22:19 [PR PATCH] " motorto
2023-01-07 22:22 ` motorto [this message]
2023-01-13 17:32 ` [PR PATCH] [Merged]: " Vaelatern
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=20230107222236._d8VSGsUnkan33rMKJeIw1BTe6JtYqcCQGo_nELVgk4@z \
--to=motorto@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).