From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pikepdf: update to 6.2.0.
Date: Sun, 09 Oct 2022 15:27:33 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39835@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
There is a new 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/39835
python3-pikepdf: update to 6.2.0.
<!-- 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/39835.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pikepdf-39835.patch --]
[-- Type: text/x-diff, Size: 1153 bytes --]
From 155b6ee20162543235aa599baecd6a8f2ba4c276 Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Sun, 9 Oct 2022 15:20:56 +0200
Subject: [PATCH] python3-pikepdf: update to 6.2.0.
---
srcpkgs/python3-pikepdf/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-pikepdf/template b/srcpkgs/python3-pikepdf/template
index 631065b0beb4..8e4190d62b35 100644
--- a/srcpkgs/python3-pikepdf/template
+++ b/srcpkgs/python3-pikepdf/template
@@ -1,6 +1,6 @@
# Template file for 'python3-pikepdf'
pkgname=python3-pikepdf
-version=6.0.0.post2
+version=6.2.0
revision=1
wrksrc="pikepdf-${version}"
build_style=python3-module
@@ -16,7 +16,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=dae409c6434151498afc78e5fa636396b48e8a49dc46456012fc4917a0870078
+checksum=7a6731d19c338ecf98159fa9989eaffbb15b9c25c6eef366a0c5b2a68c299849
pre_check() {
cp -r src/pikepdf.egg-info "$(cd build/lib* && pwd)"
next reply other threads:[~2022-10-09 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:27 oynqr [this message]
2022-10-09 16:10 ` [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-39835@inbox.vuxu.org \
--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).