From: aurieh <aurieh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-blinker: update to 1.5
Date: Sun, 23 Oct 2022 06:25:33 +0200 [thread overview]
Message-ID: <20221023042533.mfBWX9rBQ60_53JVDDGYJ7x2z9Tr1-w8XL7MzTGKxV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40070@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
There is an updated pull request by aurieh against master on the void-packages repository
https://github.com/aurieh/void-packages python3-blinker-1.5
https://github.com/void-linux/void-packages/pull/40070
python3-blinker: update to 1.5
[Changelog](https://blinker.readthedocs.io/en/stable/#version-1-5), [diff](https://github.com/pallets-eco/blinker/compare/rel-1.4...1.5): no breaking changes.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/40070.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-blinker-1.5-40070.patch --]
[-- Type: text/x-diff, Size: 1396 bytes --]
From fb14f642597c928eb9546e0cd7e27c44a2d4e32a Mon Sep 17 00:00:00 2001
From: Auri <me@aurieh.me>
Date: Thu, 20 Oct 2022 23:54:08 +0000
Subject: [PATCH] python3-blinker: update to 1.5
---
srcpkgs/python3-blinker/template | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-blinker/template b/srcpkgs/python3-blinker/template
index 609af96d16d8..df629b7e55c2 100644
--- a/srcpkgs/python3-blinker/template
+++ b/srcpkgs/python3-blinker/template
@@ -1,19 +1,21 @@
# Template file for 'python3-blinker'
pkgname=python3-blinker
-version=1.4
-revision=7
+version=1.5
+revision=1
wrksrc="blinker-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
makedepends="python3-devel"
depends="python3"
+checkdepends="python3-pytest"
short_desc="Fast, simple object-to-object and broadcast signaling for Python3"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
-homepage="http://pythonhosted.org/blinker/"
+homepage="https://blinker.readthedocs.io/en/stable/"
+changelog="https://raw.githubusercontent.com/pallets-eco/blinker/main/CHANGES.rst"
distfiles="${PYPI_SITE}/b/blinker/blinker-${version}.tar.gz"
-checksum=471aee25f3992bd325afa3772f1063dbdbbca947a041b8b89466dc00d606f8b6
+checksum=923e5e2f69c155f2cc42dafbbd70e16e3fde24d2d4aa2ab72fbe386238892462
post_install() {
- vlicense LICENSE
+ vlicense LICENSE.rst
}
next prev parent reply other threads:[~2022-10-23 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 23:58 [PR PATCH] " aurieh
2022-10-23 1:14 ` [PR REVIEW] " classabbyamp
2022-10-23 3:42 ` aurieh
2022-10-23 3:51 ` classabbyamp
2022-10-23 4:23 ` aurieh
2022-10-23 4:25 ` aurieh [this message]
2022-10-23 7:19 ` [PR PATCH] [Merged]: " classabbyamp
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=20221023042533.mfBWX9rBQ60_53JVDDGYJ7x2z9Tr1-w8XL7MzTGKxV4@z \
--to=aurieh@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).