From: cpixl <cpixl@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pex: update to 2.1.12.
Date: Sun, 05 Jul 2020 21:23:53 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23397@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
There is a new pull request by cpixl against master on the void-packages repository
https://github.com/cpixl/void-packages pex
https://github.com/void-linux/void-packages/pull/23397
pex: update to 2.1.12.
A patch file from https://github.com/void-linux/void-packages/pull/23397.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pex-23397.patch --]
[-- Type: text/x-diff, Size: 960 bytes --]
From 82f5f17c3616d213a890e5ff317ed6859e8e1ff7 Mon Sep 17 00:00:00 2001
From: Daniel Santana <daniel@santana.tech>
Date: Sun, 5 Jul 2020 16:23:34 -0300
Subject: [PATCH] pex: update to 2.1.12.
---
srcpkgs/pex/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pex/template b/srcpkgs/pex/template
index 53988e31088..1b1b6e41359 100644
--- a/srcpkgs/pex/template
+++ b/srcpkgs/pex/template
@@ -1,6 +1,6 @@
# Template file for 'pex'
pkgname=pex
-version=2.1.11
+version=2.1.12
revision=1
archs=noarch
wrksrc="pex-${version}"
@@ -12,7 +12,7 @@ maintainer="Daniel Santana <daniel@santana.tech>"
license="Apache-2.0"
homepage="https://github.com/pantsbuild/pex"
distfiles="${PYPI_SITE}/p/pex/pex-${version}.tar.gz"
-checksum=9fc8f1562676c537b4c7fe4a62ecaaa2803fa43b56aba2f2435d833eb6b6036a
+checksum=b84014ab576f2819830881b292854b98225f6063e8d93410086261e2d693d644
post_build() {
PYTHONPATH="$PWD" make -C docs man
next reply other threads:[~2020-07-05 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 19:23 cpixl [this message]
2020-07-05 20:32 ` [PR PATCH] [Merged]: " jnbr
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-23397@inbox.vuxu.org \
--to=cpixl@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).