Github messages for voidlinux
 help / color / mirror / Atom feed
From: sternenseemann <sternenseemann@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mcabber: use aspell instead of enchant
Date: Mon, 08 Feb 2021 14:28:33 +0100	[thread overview]
Message-ID: <20210208132833.rhhbxoAjeRsbqltfoGbEOrthuXz3u-IDSIZqAH30uWQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28583@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

There is an updated pull request by sternenseemann against master on the void-packages repository

https://github.com/sternenseemann/void-packages mcabber-aspell
https://github.com/void-linux/void-packages/pull/28583

mcabber: use aspell instead of enchant
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/28583.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mcabber-aspell-28583.patch --]
[-- Type: text/x-diff, Size: 2785 bytes --]

From 090aaaf903fe03e824a961872c454531c81d60cc Mon Sep 17 00:00:00 2001
From: sternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>
Date: Mon, 8 Feb 2021 13:49:48 +0100
Subject: [PATCH 1/2] mcabber: use aspell instead of enchant

Reference #27710
---
 srcpkgs/mcabber/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/mcabber/template b/srcpkgs/mcabber/template
index 3c30cfae508f..674ea4f43c3d 100644
--- a/srcpkgs/mcabber/template
+++ b/srcpkgs/mcabber/template
@@ -1,11 +1,11 @@
 # Template file for 'mcabber'
 pkgname=mcabber
 version=1.1.2
-revision=1
+revision=2
 build_style=gnu-configure
-configure_args="--enable-hgcset --enable-enchant --enable-otr"
+configure_args="--enable-hgcset --enable-aspell --enable-otr"
 hostmakedepends="pkg-config"
-makedepends="enchant-devel gpgme-devel libgcrypt-devel libotr-devel
+makedepends="aspell-devel gpgme-devel libgcrypt-devel libotr-devel
  loudmouth-devel"
 short_desc="Small XMPP (Jabber) console client"
 maintainer="Lukas Epple <sternenseemann@lukasepple.de>"

From 771f1a9148bf2debe86764eba5819d1d3418f4a3 Mon Sep 17 00:00:00 2001
From: sternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>
Date: Mon, 8 Feb 2021 13:52:51 +0100
Subject: [PATCH 2/2] loudmouth, mcabber: orphan

I haven't been using void linux for a few years and forgot to orphan
these packages at my departure.
---
 srcpkgs/loudmouth/template | 2 +-
 srcpkgs/mcabber/template   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/loudmouth/template b/srcpkgs/loudmouth/template
index 50d205fdcb19..37212d47d81f 100644
--- a/srcpkgs/loudmouth/template
+++ b/srcpkgs/loudmouth/template
@@ -7,7 +7,7 @@ configure_args="--with-ssl=openssl --with-asyncns --with-compile-warnings=no"
 hostmakedepends="pkg-config automake libtool glib-devel gtk-doc"
 makedepends="libglib-devel libidn-devel libressl-devel"
 short_desc="Lightweight Jabber client library written in C/Glib"
-maintainer="Lukas Epple <sternenseemann@lukasepple.de>"
+maintainer="Orphaned <orphan@voidlinux.org>"
 license="LGPL-2.1-or-later"
 homepage="https://github.com/mcabber/loudmouth"
 distfiles="https://github.com/mcabber/${pkgname}/archive/${version}.tar.gz"
diff --git a/srcpkgs/mcabber/template b/srcpkgs/mcabber/template
index 674ea4f43c3d..0403e9c27825 100644
--- a/srcpkgs/mcabber/template
+++ b/srcpkgs/mcabber/template
@@ -8,7 +8,7 @@ hostmakedepends="pkg-config"
 makedepends="aspell-devel gpgme-devel libgcrypt-devel libotr-devel
  loudmouth-devel"
 short_desc="Small XMPP (Jabber) console client"
-maintainer="Lukas Epple <sternenseemann@lukasepple.de>"
+maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
 homepage="http://mcabber.com"
 distfiles="${homepage}/files/mcabber-${version}.tar.bz2"

  reply	other threads:[~2021-02-08 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 13:11 [PR PATCH] Mcabber aspell sternenseemann
2021-02-08 13:28 ` sternenseemann [this message]
2021-02-09 15:56 ` [PR PATCH] [Merged]: mcabber: use aspell instead of enchant leahneukirchen

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=20210208132833.rhhbxoAjeRsbqltfoGbEOrthuXz3u-IDSIZqAH30uWQ@z \
    --to=sternenseemann@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).