From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pikepdf: update to 8.13.0.
Date: Fri, 08 Mar 2024 09:30:58 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49184@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1250 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/49184
python3-pikepdf: update to 8.13.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/49184.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pikepdf-49184.patch --]
[-- Type: text/x-diff, Size: 1175 bytes --]
From 72ad7eeb948c51eef1537ff5b0f8db954db1514f Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Fri, 8 Mar 2024 09:28:40 +0100
Subject: [PATCH] python3-pikepdf: update to 8.13.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 7490d278c05b70..86501ca505ffae 100644
--- a/srcpkgs/python3-pikepdf/template
+++ b/srcpkgs/python3-pikepdf/template
@@ -1,6 +1,6 @@
# Template file for 'python3-pikepdf'
pkgname=python3-pikepdf
-version=8.10.0
+version=8.13.0
revision=1
build_style=python3-module
hostmakedepends="python3-pybind11 python3-wheel"
@@ -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=4b9d6fc972b93bc3ef7c7f7b1c79268d8ab53239e7ff8a1cfc288ec1ddd1cb41
+checksum=3bbd79c7cd6630361d83e75132aeaf3a64ceb837f82870bafdc210a31e3d917a
pre_check() {
cp -r src/pikepdf.egg-info "$(cd build/lib* && pwd)"
next reply other threads:[~2024-03-08 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 8:30 oynqr [this message]
2024-05-02 9:33 ` [PR REVIEW] " Eloitor
2024-06-16 23:09 ` [PR PATCH] [Closed]: " 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-49184@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).