From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-perf: update to 1.6.1.
Date: Fri, 18 Oct 2019 21:53:59 +0200 [thread overview]
Message-ID: <20191018195359.AuGydxJnzeflSv31jgXrEFhndZw_piyQrqhx6Ew-KFs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15418@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
There is an updated pull request by mobinmob against master on the void-packages repository
https://github.com/mobinmob/void-packages python3-perf
https://github.com/void-linux/void-packages/pull/15418
python3-perf: update to 1.6.1.
A patch file from https://github.com/void-linux/void-packages/pull/15418.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-perf-15418.patch --]
[-- Type: text/x-diff, Size: 1537 bytes --]
From 26ca74837576e90b23568d32b8264e151d3daf21 Mon Sep 17 00:00:00 2001
From: mobinmob <mobinmob@disroot.org>
Date: Sat, 12 Oct 2019 22:25:48 +0300
Subject: [PATCH] python3-perf: update to 1.6.1.
---
srcpkgs/python3-perf/template | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/python3-perf/template b/srcpkgs/python3-perf/template
index 4f3a09237eb..a03251f97e8 100644
--- a/srcpkgs/python3-perf/template
+++ b/srcpkgs/python3-perf/template
@@ -1,20 +1,20 @@
# Template file for 'python3-perf'
pkgname=python3-perf
-version=1.6.0
+version=1.6.1
revision=1
archs=noarch
-wrksrc="perf-${version}"
+wrksrc="pyperf-${version}"
build_style=python3-module
-pycompile_module="perf"
+pycompile_module="pyperf"
hostmakedepends="python3-setuptools"
depends="python3-setuptools python3-six"
short_desc="Toolkit to run Python benchmarks"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
-homepage="https://github.com/vstinner/perf"
-#changelog="https://raw.githubusercontent.com/vstinner/perf/master/doc/changelog.rst"
-distfiles="https://github.com/vstinner/perf/archive/${version}.tar.gz"
-checksum=c1f6f0262be85e7e14daa0875c7d226d6a87b2cf9eebbfb91f6e7c34ef223df0
+homepage="https://pyperf.readthedocs.io"
+changelog="https://raw.githubusercontent.com/vstinner/pyperf/master/doc/changelog.rst"
+distfiles="https://github.com/vstinner/pyperf/archive/${version}.tar.gz"
+checksum=fbe793f6f2e036ab4dcca105b5c5aa34fd331dd881e7a3e158e5e218c63cfc32
post_install() {
vlicense COPYING
next prev parent reply other threads:[~2019-10-18 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 19:59 [PR PATCH] " voidlinux-github
2019-10-15 19:26 ` voidlinux-github
2019-10-15 19:33 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-15 19:33 ` voidlinux-github
2019-10-15 19:34 ` voidlinux-github
2019-10-15 20:03 ` voidlinux-github
2019-10-15 20:07 ` voidlinux-github
2019-10-16 11:03 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-16 11:03 ` voidlinux-github
2019-10-16 11:04 ` voidlinux-github
2019-10-16 16:41 ` voidlinux-github
2019-10-16 18:25 ` voidlinux-github
2019-10-18 19:53 ` voidlinux-github [this message]
2019-10-18 19:53 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-18 19:55 ` voidlinux-github
2019-10-19 7:19 ` [PR PATCH] [Merged]: " voidlinux-github
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=20191018195359.AuGydxJnzeflSv31jgXrEFhndZw_piyQrqhx6Ew-KFs@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).