Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pex: update to 2.1.103.
Date: Tue, 16 Aug 2022 17:23:49 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38709@inbox.vuxu.org> (raw)

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

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

https://github.com/icp1994/void-packages pex
https://github.com/void-linux/void-packages/pull/38709

pex: update to 2.1.103.
#### 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

This template effectively enforces `make_check=no` since this has `build_style=python3-pep517` with no explicit `checkdepends`. Running the tests as is requires [bootstrapping different python interpreters](https://github.com/pantsbuild/pex/blob/v2.1.103/pex/testing.py#L453-L459) by building them from source via `pyenv`. I couldn't figure out if there's a way to run the tests only with system installed python. Instead I installed it and run the commands mentioned in their quick start guide which seem to work as intended.

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

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

From 1e7c123dc7e34fab4b60276b2b51991404b1e58b Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sun, 14 Aug 2022 21:20:20 +0530
Subject: [PATCH] pex: update to 2.1.103.

---
 srcpkgs/pex/template | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/srcpkgs/pex/template b/srcpkgs/pex/template
index 340ecb6260e0..c01ae4bd8b12 100644
--- a/srcpkgs/pex/template
+++ b/srcpkgs/pex/template
@@ -1,18 +1,18 @@
 # Template file for 'pex'
 pkgname=pex
-version=2.1.15
-revision=3
+version=2.1.103
+revision=1
 wrksrc="pex-${version}"
-build_style=python3-module
-hostmakedepends="python3-setuptools python3-Sphinx"
-depends="python3-setuptools"
+build_style=python3-pep517
+hostmakedepends="python3-flit_core python3-Sphinx"
+depends="python3"
 short_desc="Library & tool for generating .pex (Python EXecutable) files"
 maintainer="Daniel Santana <daniel@santana.tech>"
 license="Apache-2.0"
 homepage="https://github.com/pantsbuild/pex"
-changelog="https://raw.githubusercontent.com/pantsbuild/pex/master/CHANGES.rst"
+changelog="https://raw.githubusercontent.com/pantsbuild/pex/main/CHANGES.rst"
 distfiles="${PYPI_SITE}/p/pex/pex-${version}.tar.gz"
-checksum=e1092ae52cfdef41c22d98fa98f9225ac21936a7d096131777ca3a7940fe1b2d
+checksum=07bcd633626b7fd6d18eb0d6303acfd0a4fbcb31692e737b15794626da896bf0
 
 post_build() {
 	PYTHONPATH="$PWD" make -C docs man

             reply	other threads:[~2022-08-16 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 15:23 icp1994 [this message]
2022-08-16 15:30 ` icp1994
2022-08-17  0:40 ` classabbyamp
2022-08-17 12:35 ` [PR PATCH] [Updated] " icp1994
2022-08-17 21:59 ` [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-38709@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).