From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pipx: update to 1.2.0.
Date: Wed, 15 Mar 2023 21:08:42 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42795@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-pipx
https://github.com/void-linux/void-packages/pull/42795
python3-pipx: update to 1.2.0.
#### 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**
A patch file from https://github.com/void-linux/void-packages/pull/42795.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pipx-42795.patch --]
[-- Type: text/x-diff, Size: 1290 bytes --]
From aca875372d98a61e2f138ec6050a0ba4fa062479 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Wed, 15 Mar 2023 21:56:47 +0530
Subject: [PATCH] python3-pipx: update to 1.2.0.
---
srcpkgs/python3-pipx/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-pipx/template b/srcpkgs/python3-pipx/template
index f2e3b673a12e..c0cbecd87371 100644
--- a/srcpkgs/python3-pipx/template
+++ b/srcpkgs/python3-pipx/template
@@ -1,17 +1,17 @@
# Template file for 'python3-pipx'
pkgname=python3-pipx
-version=1.1.0
-revision=2
+version=1.2.0
+revision=1
build_style=python3-pep517
hostmakedepends="hatchling"
-depends="python3-argcomplete python3-packaging python3-userpath"
+depends="python3-argcomplete python3-packaging python3-platformdirs python3-userpath"
short_desc="Install and Run Python Applications in Isolated Environments"
maintainer="Leah Neukirchen <leah@vuxu.org>"
license="MIT"
homepage="https://pypa.github.io/pipx/"
changelog="https://pypa.github.io/pipx/changelog/"
distfiles="${PYPI_SITE}/p/pipx/pipx-${version}.tar.gz"
-checksum=4d2f70daf15f121e90b7394b0730ee82fc39d7da514e50a7bbf8066be88883bb
+checksum=d1908041d24d525cafebeb177efb686133d719499cb55c54f596c95add579286
post_install() {
vlicense LICENSE
next reply other threads:[~2023-03-15 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 20:08 icp1994 [this message]
2023-03-16 12:26 ` [PR PATCH] [Merged]: " abenson
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-42795@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).