Github messages for voidlinux
 help / color / mirror / Atom feed
From: gspe <gspe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python-enchant: remove package
Date: Sat, 23 Jan 2021 14:23:07 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28117@inbox.vuxu.org> (raw)

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

There is a new pull request by gspe against master on the void-packages repository

https://github.com/gspe/void-packages python-enchant
https://github.com/void-linux/void-packages/pull/28117

python-enchant: remove package
pyenchant now requires: Python >=3.5


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python-enchant-28117.patch --]
[-- Type: text/x-diff, Size: 1840 bytes --]

From 2efa012576d4521c488845394162d674f7517e8a Mon Sep 17 00:00:00 2001
From: Giuseppe Fierro <gspe@ae-design.ws>
Date: Sat, 23 Jan 2021 14:20:12 +0100
Subject: [PATCH] python-enchant: remove package

pyenchant now requires: Python >=3.5
---
 srcpkgs/python-enchant/template   | 14 --------------
 srcpkgs/removed-packages/template |  3 ++-
 2 files changed, 2 insertions(+), 15 deletions(-)
 delete mode 100644 srcpkgs/python-enchant/template

diff --git a/srcpkgs/python-enchant/template b/srcpkgs/python-enchant/template
deleted file mode 100644
index d29c1ad7ac6..00000000000
--- a/srcpkgs/python-enchant/template
+++ /dev/null
@@ -1,14 +0,0 @@
-# Template file for 'python-enchant'
-pkgname=python-enchant
-version=2.0.0
-revision=4
-wrksrc="pyenchant-${version}"
-build_style=python2-module
-hostmakedepends="python-setuptools enchant-devel"
-depends="enchant"
-short_desc="Spellchecking library for Python 3"
-maintainer="Orphaned <orphan@voidlinux.org>"
-license="LGPL-2.1"
-homepage="https://github.com/rfk/pyenchant"
-distfiles="${PYPI_SITE}/p/pyenchant/pyenchant-${version}.tar.gz"
-checksum=fc31cda72ace001da8fe5d42f11c26e514a91fa8c70468739216ddd8de64e2a0
diff --git a/srcpkgs/removed-packages/template b/srcpkgs/removed-packages/template
index e5e08f74170..954d5bb0c3e 100644
--- a/srcpkgs/removed-packages/template
+++ b/srcpkgs/removed-packages/template
@@ -1,7 +1,7 @@
 # Template file for 'removed-packages'
 pkgname=removed-packages
 version=0.1
-revision=13
+revision=14
 build_style=meta
 short_desc="Uninstalls packages removed from repository"
 maintainer="Piotr Wójcik <chocimier@tlen.pl>"
@@ -60,6 +60,7 @@ replaces="
  python-PyQt4<=4.12.1_4
  python-SecretStorage<=2.3.1_4
  python-audit<=2.8.5_2
+ python-enchant<=2.0.0_4
  python-jellyfish<=0.6.1_2
  python-matplotlib<=2.2.4_2
  python-matplotlib-data<=2.2.4_2

             reply	other threads:[~2021-01-23 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23 13:23 gspe [this message]
2021-01-23 19:37 ` [PR REVIEW] " ericonr
2021-01-24 20:08 ` [PR PATCH] [Closed]: " ericonr

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28117@inbox.vuxu.org \
    --to=gspe@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).