From: fivestang <fivestang@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-neovim: update to version 0.4.1
Date: Mon, 27 Apr 2020 02:47:46 +0200 [thread overview]
Message-ID: <20200427004746.Pdesaq-7hy2BQUG6RZWfhmbd6IIEPu2CSj4gdwq7xoA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21309@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
There is an updated pull request by fivestang against master on the void-packages repository
https://github.com/fivestang/void-packages master
https://github.com/void-linux/void-packages/pull/21309
python3-neovim: update to version 0.4.1
A patch file from https://github.com/void-linux/void-packages/pull/21309.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-21309.patch --]
[-- Type: text/x-diff, Size: 1315 bytes --]
From 02dbed42222182d62ca5fa844253581ce44e0c8a Mon Sep 17 00:00:00 2001
From: fivestang <fivestang@protonmail.com>
Date: Fri, 24 Apr 2020 15:39:32 -0400
Subject: [PATCH] python3-neovim: update to version 0.4.1
removed 'pycompile_module="pynvim"' as per xlint
---
srcpkgs/python3-neovim/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-neovim/template b/srcpkgs/python3-neovim/template
index 2730cd1b92b..b5c705bbafd 100644
--- a/srcpkgs/python3-neovim/template
+++ b/srcpkgs/python3-neovim/template
@@ -1,11 +1,10 @@
# Template file for 'python3-neovim'
pkgname=python3-neovim
-version=0.3.2
-revision=4
+version=0.4.1
+revision=1
archs=noarch
wrksrc="pynvim-${version}"
build_style="python3-module"
-pycompile_module="pynvim"
hostmakedepends="python3-setuptools"
depends="neovim python3-greenlet python3-msgpack"
short_desc="Python3 client for Neovim"
@@ -13,4 +12,4 @@ maintainer="Steve Prybylski <sa.prybylx@gmail.com>"
license="Apache-2.0"
homepage="https://github.com/neovim/python-client"
distfiles="https://github.com/neovim/python-client/archive/${version}.tar.gz>${pkgname}-${version}.tar.gz"
-checksum=0a44c540dd5790acfbc7e411b0ed4fb6c44914d866226ebebf370c24c2723dc2
+checksum=132ea5c226399aed45a959f1d8efe8cdd89a769a672534722760a9a67b06dfa0
next prev parent reply other threads:[~2020-04-27 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 19:43 [PR PATCH] " fivestang
2020-04-26 1:42 ` [PR PATCH] [Updated] " fivestang
2020-04-26 7:52 ` Piraty
2020-04-26 13:17 ` fivestang
2020-04-26 23:21 ` Piraty
2020-04-27 0:47 ` fivestang [this message]
2020-05-03 22:23 ` Piraty
2020-05-03 23:31 ` [PR PATCH] [Closed]: " fivestang
2020-05-04 15:45 ` Piraty
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=20200427004746.Pdesaq-7hy2BQUG6RZWfhmbd6IIEPu2CSj4gdwq7xoA@z \
--to=fivestang@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).