From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-greenlet: update to 1.1.0.
Date: Tue, 15 Jun 2021 15:36:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31514@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
There is a new pull request by Piraty against master on the void-packages repository
https://github.com/Piraty/void-packages python3-greenlet-1.1.0
https://github.com/void-linux/void-packages/pull/31514
python3-greenlet: update to 1.1.0.
<!-- 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.)
- [ ] 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/31514.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-greenlet-1.1.0-31514.patch --]
[-- Type: text/x-diff, Size: 1217 bytes --]
From 9c45773d6eb0ecd3e6b574643fdfb965e1f8a732 Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Tue, 15 Jun 2021 15:34:54 +0200
Subject: [PATCH] python3-greenlet: update to 1.1.0.
---
srcpkgs/python3-greenlet/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-greenlet/template b/srcpkgs/python3-greenlet/template
index 182cada6bedd..700f8771301f 100644
--- a/srcpkgs/python3-greenlet/template
+++ b/srcpkgs/python3-greenlet/template
@@ -1,6 +1,6 @@
# Template file for 'python3-greenlet'
pkgname=python3-greenlet
-version=0.4.17
+version=1.1.0
revision=1
wrksrc="greenlet-${version}"
build_style=python3-module
@@ -12,10 +12,10 @@ license="MIT"
homepage="https://github.com/python-greenlet/greenlet"
changelog="https://raw.githubusercontent.com/python-greenlet/greenlet/master/NEWS"
distfiles="${PYPI_SITE}/g/greenlet/greenlet-${version}.tar.gz"
-checksum=41d8835c69a78de718e466dd0e6bfd4b46125f21a67c3ff6d76d8d8059868d6b
+checksum=c87df8ae3f01ffb4483c796fe1b15232ce2b219f0b18126948616224d3f658ee
do_check() {
- python3 setup.py test
+ PYTHONPATH="$(cd build/lib* && pwd)" python3 -m unittest discover -v greenlet.tests
}
post_install() {
next reply other threads:[~2021-06-15 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 13:36 Piraty [this message]
2021-06-15 13:39 ` ericonr
2021-06-15 18:03 ` [PR PATCH] [Updated] " Piraty
2021-06-15 18:04 ` Piraty
2021-06-15 18:15 ` Piraty
2021-06-17 2:35 ` ericonr
2021-06-17 11:27 ` [PR PATCH] [Merged]: " Piraty
-- strict thread matches above, loose matches on Subject: below --
2021-05-10 19:09 [PR PATCH] " pfpulux
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-31514@inbox.vuxu.org \
--to=piraty@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).