From: mustaqimM <mustaqimM@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pillow-simd: update to 7.0.0.post3
Date: Tue, 14 Apr 2020 15:49:34 +0200 [thread overview]
Message-ID: <20200414134934.BMPw_6tyb4zlQ47iT8M9aO6gkfxXvvJsog5J2nhZoSE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20974@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
There is an updated pull request by mustaqimM against master on the void-packages repository
https://github.com/mustaqimM/void-packages update_pillow_simd
https://github.com/void-linux/void-packages/pull/20974
python3-pillow-simd: update to 7.0.0.post3
It's happened again :/
I switched to the `update_pillow_simd` branch, added its template and git committed the changes from the other branch (`update_ueberzug`) that I added but didn't commit. Is this default git behaviour?
A patch file from https://github.com/void-linux/void-packages/pull/20974.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update_pillow_simd-20974.patch --]
[-- Type: text/x-diff, Size: 1398 bytes --]
From a09529144a0757853eaaa968f9c12d36f7b8c943 Mon Sep 17 00:00:00 2001
From: mustaqim <mustaqim@pm.me>
Date: Tue, 14 Apr 2020 15:48:49 +0200
Subject: [PATCH] python3-pillow-simd: update to 7.0.0.post3
---
srcpkgs/python3-pillow-simd/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-pillow-simd/template b/srcpkgs/python3-pillow-simd/template
index 4c756b07c79..f9271ff261c 100644
--- a/srcpkgs/python3-pillow-simd/template
+++ b/srcpkgs/python3-pillow-simd/template
@@ -1,7 +1,7 @@
# Template file for 'python3-pillow-simd'
pkgname=python3-pillow-simd
-version=5.3.0.post1
-revision=2
+version=7.0.0.post3
+revision=1
archs="x86_64*"
wrksrc="pillow-simd-${version}"
build_style=python3-module
@@ -14,9 +14,9 @@ short_desc="Python3 Imaging Library (PIL) fork (SIMD)"
maintainer="mustaqim <mustaqim@pm.me>"
license="custom: PIL"
homepage="https://python-pillow.org/pillow-perf/"
-changelog="https://github.com/uploadcare/pillow-simd/compare/v5.2.0.post1...v5.3.0.post1"
+changelog="https://github.com/uploadcare/pillow-simd/blob/simd/master/CHANGES.SIMD.rst"
distfiles="https://github.com/uploadcare/pillow-simd/archive/v${version}.tar.gz"
-checksum=ac135e962d1b335c393e2a31991cae41302cf248f42925a8defba284d2289cec
+checksum=9844b83312804a155fbdb5d4239578f4f1861f8a196ab8310992524484053b06
conflicts="python-Pillow"
post_install() {
next prev parent reply other threads:[~2020-04-14 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:39 [PR PATCH] " mustaqimM
2020-04-14 13:49 ` mustaqimM [this message]
2020-04-14 14:00 ` mustaqimM
2020-04-14 14:08 ` [PR PATCH] [Updated] " mustaqimM
2020-04-14 18:14 ` mustaqimM
2020-04-14 19:26 ` mustaqimM
2020-04-15 21:37 ` Chocimier
2020-04-16 4:53 ` [PR PATCH] [Updated] " mustaqimM
2020-04-20 19:47 ` [PR PATCH] [Merged]: " Chocimier
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=20200414134934.BMPw_6tyb4zlQ47iT8M9aO6gkfxXvvJsog5J2nhZoSE@z \
--to=mustaqimm@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).