From: anjandev <anjandev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-qrcode: update to 7.3.1
Date: Thu, 13 Oct 2022 08:06:01 +0200 [thread overview]
Message-ID: <20221013060601.3I2OsofyqnGKNlqDaAdK5qIVJyb8ehaE3Yv1rdY3VK0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39928@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
There is an updated pull request by anjandev against master on the void-packages repository
https://github.com/anjandev/void-packages qr
https://github.com/void-linux/void-packages/pull/39928
python3-qrcode: update to 7.3.1
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/39928.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-qr-39928.patch --]
[-- Type: text/x-diff, Size: 1315 bytes --]
From 0c8164bdc40d802444bd787ea850611b723f89f3 Mon Sep 17 00:00:00 2001
From: Anjandev Momi <anjan@momi.ca>
Date: Wed, 12 Oct 2022 22:38:09 -0700
Subject: [PATCH] python3-qrcode: update to 7.3.1
---
srcpkgs/python3-qrcode/template | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-qrcode/template b/srcpkgs/python3-qrcode/template
index 50a1966adb5b..b907c50e0b06 100644
--- a/srcpkgs/python3-qrcode/template
+++ b/srcpkgs/python3-qrcode/template
@@ -1,18 +1,20 @@
# Template file for 'python3-qrcode'
pkgname=python3-qrcode
-version=6.1
-revision=5
+version=7.3.1
+revision=1
wrksrc="qrcode-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3-six"
-checkdepends="python3-six"
+checkdepends="python3-six python3-Pillow"
short_desc="QR Code image generator (Python3)"
maintainer="Charles E. Lehner <cel@celehner.com>"
license="BSD-3-Clause"
homepage="https://github.com/lincolnloop/python-qrcode"
distfiles="${PYPI_SITE}/q/qrcode/qrcode-${version}.tar.gz"
-checksum=505253854f607f2abf4d16092c61d4e9d511a3b4392e60bff957a68592b04369
+checksum=375a6ff240ca9bd41adc070428b5dfc1dcfbb0f2507f1ac848f6cded38956578
+# packages needed to run tests are not packaged in void
+make_check=no
do_check() {
python3 setup.py test
next prev parent reply other threads:[~2022-10-13 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 5:39 [PR PATCH] " anjandev
2022-10-13 5:43 ` anjandev
2022-10-13 5:58 ` [PR PATCH] [Updated] " anjandev
2022-10-13 6:06 ` anjandev [this message]
2022-10-13 6:09 ` anjandev
2022-10-13 8:54 ` [PR REVIEW] " paper42
2022-10-13 21:14 ` [PR PATCH] [Updated] " anjandev
2023-01-12 2:29 ` github-actions
2023-01-27 1:59 ` [PR PATCH] [Closed]: " github-actions
-- strict thread matches above, loose matches on Subject: below --
2022-02-13 13:57 [PR PATCH] " MouadCharradi
2022-02-15 16:05 ` [PR PATCH] [Updated] " MouadCharradi
2022-02-13 3:43 [PR PATCH] " MouadCharradi
2022-02-13 12:27 ` [PR PATCH] [Updated] " MouadCharradi
2022-02-13 13:15 ` MouadCharradi
2022-02-13 1:06 [PR PATCH] " MouadCharradi
2022-02-13 2:07 ` [PR PATCH] [Updated] " MouadCharradi
2022-02-13 2:28 ` MouadCharradi
2022-02-13 2:47 ` MouadCharradi
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=20221013060601.3I2OsofyqnGKNlqDaAdK5qIVJyb8ehaE3Yv1rdY3VK0@z \
--to=anjandev@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).