From: cpixl <cpixl@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pex: update to 2.1.8.
Date: Sat, 04 Apr 2020 17:11:14 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20648@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 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/20648
pex: update to 2.1.8.
A patch file from https://github.com/void-linux/void-packages/pull/20648.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pex-20648.patch --]
[-- Type: text/x-diff, Size: 957 bytes --]
From d8a39288617da4182b805228a1bce9d4a7bf7ddb Mon Sep 17 00:00:00 2001
From: Daniel Santana <daniel@santana.tech>
Date: Sat, 4 Apr 2020 12:09:33 -0300
Subject: [PATCH] pex: update to 2.1.8.
---
srcpkgs/pex/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pex/template b/srcpkgs/pex/template
index 74d93f940c4..7843044a980 100644
--- a/srcpkgs/pex/template
+++ b/srcpkgs/pex/template
@@ -1,6 +1,6 @@
# Template file for 'pex'
pkgname=pex
-version=2.1.7
+version=2.1.8
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=c8db74e9e6842e36b8ca598cf831f91ee1410bc1a1a4bcb3f2310b87783877c7
+checksum=64e2f8146e0c00fd50213ac01933014aadd7b00c7709e961067c4c47f37fe31f
post_build() {
PYTHONPATH="$PWD" make -C docs man
next reply other threads:[~2020-04-04 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 15:11 cpixl [this message]
2020-04-05 8:01 ` [PR PATCH] [Merged]: " xtraeme
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-20648@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).