From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pikepdf: update to 6.2.9.
Date: Tue, 14 Feb 2023 08:43:32 +0100 [thread overview]
Message-ID: <20230214074332._yqByd0_bN9Susih3z_TczknrjtegvjJEW7lvMYdfq4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41900@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1254 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/41900
python3-pikepdf: update to 6.2.9.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/41900.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pikepdf-41900.patch --]
[-- Type: text/x-diff, Size: 1252 bytes --]
From 37ddaa4f8990d5285b5485e2b51fea2ca520ff31 Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Tue, 22 Nov 2022 17:02:44 +0100
Subject: [PATCH] python3-pikepdf: update to 7.0.0.
---
srcpkgs/python3-pikepdf/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-pikepdf/template b/srcpkgs/python3-pikepdf/template
index f1265584d735..b960df1c63f0 100644
--- a/srcpkgs/python3-pikepdf/template
+++ b/srcpkgs/python3-pikepdf/template
@@ -1,7 +1,7 @@
# Template file for 'python3-pikepdf'
pkgname=python3-pikepdf
-version=6.2.0
-revision=2
+version=7.0.0
+revision=1
build_style=python3-module
hostmakedepends="python3-pybind11 python3-setuptools_scm python3-wheel"
makedepends="libqpdf-devel python3-pybind11"
@@ -15,7 +15,7 @@ license="MPL-2.0"
homepage="https://github.com/pikepdf/pikepdf"
changelog="https://raw.githubusercontent.com/pikepdf/pikepdf/master/docs/releasenotes/version${version%%.*}.rst"
distfiles="${PYPI_SITE}/p/pikepdf/pikepdf-${version}.tar.gz"
-checksum=7a6731d19c338ecf98159fa9989eaffbb15b9c25c6eef366a0c5b2a68c299849
+checksum=5d812d4777a9eb86f19db3484adb34620e31880838dcbe1ce8d60305f9d46710
pre_check() {
cp -r src/pikepdf.egg-info "$(cd build/lib* && pwd)"
next prev parent reply other threads:[~2023-02-14 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 11:18 [PR PATCH] " oynqr
2023-02-14 7:43 ` oynqr [this message]
2023-02-16 3:05 ` [PR PATCH] [Merged]: python3-pikepdf: update to 7.0.0 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=20230214074332._yqByd0_bN9Susih3z_TczknrjtegvjJEW7lvMYdfq4@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).