Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-PyPDF2: update to 2.11.1.
Date: Mon, 24 Oct 2022 18:05:48 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40141@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

There is a new pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages python3-PyPDF2
https://github.com/void-linux/void-packages/pull/40141

python3-PyPDF2: update to 2.11.1.
#### 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

A patch file from https://github.com/void-linux/void-packages/pull/40141.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-PyPDF2-40141.patch --]
[-- Type: text/x-diff, Size: 1708 bytes --]

From 06acca99bb37bf6fbed92791a978cccc4936908b Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Mon, 24 Oct 2022 21:33:23 +0530
Subject: [PATCH] python3-PyPDF2: update to 2.11.1.

---
 srcpkgs/python3-PyPDF2/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/python3-PyPDF2/template b/srcpkgs/python3-PyPDF2/template
index be976304ea93..06cecaaa35c5 100644
--- a/srcpkgs/python3-PyPDF2/template
+++ b/srcpkgs/python3-PyPDF2/template
@@ -1,8 +1,8 @@
 # Template file for 'python3-PyPDF2'
 pkgname=python3-PyPDF2
-version=2.4.1
+version=2.11.1
 revision=1
-_sample_files_gitrev=4d24ff93dcddf21d55d028d9675d5b5bf9d7a350
+_sample_files_gitrev=fee1d72f36bfb73fec831a1cc6de273510a306a6
 create_wrksrc=yes
 build_wrksrc="PyPDF2-${version}"
 build_style=python3-module
@@ -13,11 +13,11 @@ short_desc="PDF library for splitting, merging, cropping, and transforming pages
 maintainer="Piotr Wójcik <chocimier@tlen.pl>"
 license="BSD-3-Clause"
 homepage="https://pypdf2.readthedocs.io/en/latest/"
-changelog="https://raw.githubusercontent.com/py-pdf/PyPDF2/main/CHANGELOG"
+changelog="https://raw.githubusercontent.com/py-pdf/PyPDF2/main/CHANGELOG.md"
 distfiles="https://github.com/py-pdf/PyPDF2/archive/refs/tags/${version}.tar.gz
  https://github.com/py-pdf/sample-files/archive/${_sample_files_gitrev}.tar.gz"
-checksum="ec3b2792744c2bac3a51e1e3646b491e3b9374575e0e9361fcb4ec6756fb2061
- 04257ac9185da140a3463e1efd049ffe1ad2a9a8224375c13f2b5aec02f4f672"
+checksum="a4e323120adc5103d53c370782bfc86381143ea7b69e9213eb1263c7aaf39df8
+ 24e5b1edaf78628f5267d4aed241795f3f1143e7fa0934f80be02a6c802296d7"
 
 post_extract() {
 	rmdir ${build_wrksrc}/sample-files

             reply	other threads:[~2022-10-24 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 16:05 icp1994 [this message]
2022-10-27 23:06 ` [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-40141@inbox.vuxu.org \
    --to=icp1994@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).