From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pikepdf: update to 4.0.0.
Date: Sat, 06 Nov 2021 09:48:13 +0100 [thread overview]
Message-ID: <20211106084813.lZTrR2C4cMEXzcbOIdb5w6Im4aQ02D2P_dgwZH6HG4A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33901@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
There is an updated pull request by oynqr against master on the void-packages repository
https://github.com/oynqr/void-packages python3-pikepdf
https://github.com/void-linux/void-packages/pull/33901
python3-pikepdf: update to 4.0.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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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
-->
This is a major release since c++17 support is now a requirement and this is the first release to "officially" support python 3.10.
A patch file from https://github.com/void-linux/void-packages/pull/33901.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pikepdf-33901.patch --]
[-- Type: text/x-diff, Size: 1524 bytes --]
From 31548653c5ad1094833d0e7d881ca4a45670f862 Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Thu, 4 Nov 2021 16:35:15 +0100
Subject: [PATCH] python3-pikepdf: update to 4.0.0.
---
srcpkgs/python3-pikepdf/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-pikepdf/template b/srcpkgs/python3-pikepdf/template
index 8a7e57ed946d..2ff62d25ecf0 100644
--- a/srcpkgs/python3-pikepdf/template
+++ b/srcpkgs/python3-pikepdf/template
@@ -1,19 +1,20 @@
# Template file for 'python3-pikepdf'
pkgname=python3-pikepdf
-version=3.2.0
+version=4.0.0
revision=1
wrksrc="pikepdf-${version}"
build_style=python3-module
hostmakedepends="python3-pybind11 python3-setuptools_scm python3-wheel"
makedepends="libqpdf-devel python3-pybind11"
-depends="python3-lxml python3-Pillow"
-checkdepends="python3-dateutil python3-hypothesis python3-psutil python3-pytest $depends"
+depends="python3-lxml python3-Pillow python3-setuptools"
+checkdepends="python3-dateutil python3-hypothesis python3-psutil python3-pytest
+ $depends"
short_desc="Python library for reading and writing PDF files"
maintainer="Philipp David <pd@3b.pm>"
license="MPL-2.0"
homepage="https://github.com/pikepdf/pikepdf"
distfiles="${PYPI_SITE}/p/pikepdf/pikepdf-${version}.tar.gz"
-checksum=a0582f00440668c07edb8403e82724961c7812c8e6c30655e34825b2645f15cd
+checksum=487be40a2ec463a272b4490396787c9fba2b0bbe6c44e7254e1867b1d3c02df9
pre_build() {
vsed -e '/setuptools_scm_git_archive/d' -i setup.py
next prev parent reply other threads:[~2021-11-06 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 15:40 [PR PATCH] " oynqr
2021-11-05 20:26 ` paper42
2021-11-06 8:47 ` oynqr
2021-11-06 8:48 ` oynqr [this message]
2021-11-06 10:35 ` [PR PATCH] [Merged]: " paper42
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=20211106084813.lZTrR2C4cMEXzcbOIdb5w6Im4aQ02D2P_dgwZH6HG4A@z \
--to=oynqr@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).