From: misuchiru03 <misuchiru03@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-zope.hookable: update to 5.2
Date: Fri, 07 Oct 2022 16:57:02 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39793@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
There is a new pull request by misuchiru03 against master on the void-packages repository
https://github.com/misuchiru03/void-packages up_python3-zope.hookable_5.2
https://github.com/void-linux/void-packages/pull/39793
python3-zope.hookable: update to 5.2
#### 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)
- 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/39793.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-up_python3-zope.hookable_5.2-39793.patch --]
[-- Type: text/x-diff, Size: 1518 bytes --]
From 3fa5f9995b0710b19fabbf8cf4af653066c05674 Mon Sep 17 00:00:00 2001
From: Alex Childs <misuchiru03+github@gmail.com>
Date: Fri, 7 Oct 2022 09:54:29 -0500
Subject: [PATCH] python3-zope.hookable: update to 5.2
---
srcpkgs/python3-zope.hookable/template | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-zope.hookable/template b/srcpkgs/python3-zope.hookable/template
index 10ea2e31545e..6925d58a7103 100644
--- a/srcpkgs/python3-zope.hookable/template
+++ b/srcpkgs/python3-zope.hookable/template
@@ -1,16 +1,22 @@
# Template file for 'python3-zope.hookable'
pkgname=python3-zope.hookable
-version=5.1.0
-revision=3
+version=5.2
+revision=1
wrksrc="zope.hookable-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
makedepends="python3-devel"
depends="python3"
+checkdepends="${depends} python3-zope.testing python3-zope.testrunner"
short_desc="Zope hookable architecture for Python3"
maintainer="Alex Childs <misuchiru03+void@gmail.com>"
license="ZPL-2.1"
homepage="https://github.com/zopefoundation/zope.hookable"
changelog="https://raw.githubusercontent.com/zopefoundation/zope.hookable/master/CHANGES.rst"
distfiles="${PYPI_SITE}/z/zope.hookable/zope.hookable-${version}.tar.gz"
-checksum=8fc3e6cd0486c6af48e3317c299def719b57538332a194e0b3bc6a772f4faa0e
+checksum=4c3018bcf2b39cf5cccf40826f799b4b8c140056db780f96cb0ca332a243bd29
+
+do_check() {
+ # Manual check function running the test per the docs
+ python setup.py test
+}
next reply other threads:[~2022-10-07 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:57 misuchiru03 [this message]
2022-10-08 17:28 ` [PR REVIEW] " classabbyamp
2022-10-09 0:23 ` misuchiru03
2022-10-09 0:32 ` misuchiru03
2022-10-09 0:33 ` [PR PATCH] [Updated] " misuchiru03
2022-10-09 1:16 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39793@inbox.vuxu.org \
--to=misuchiru03@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).