Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-userpath: update to 1.9.1.
Date: Wed, 18 Oct 2023 21:39:24 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46764@inbox.vuxu.org> (raw)

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

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

https://github.com/icp1994/void-packages python3-userpath
https://github.com/void-linux/void-packages/pull/46764

python3-userpath: update to 1.9.1.
#### 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/46764.patch is attached

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

From 8fa9df08a63b144f79ad7e941da2ac27a25a79cb Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Mon, 16 Oct 2023 11:49:41 +0530
Subject: [PATCH] python3-userpath: update to 1.9.1.

---
 srcpkgs/python3-userpath/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-userpath/template b/srcpkgs/python3-userpath/template
index 14a72c8dbb8dc..04a6c0ffd9828 100644
--- a/srcpkgs/python3-userpath/template
+++ b/srcpkgs/python3-userpath/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-userpath'
 pkgname=python3-userpath
-version=1.9.0
-revision=2
+version=1.9.1
+revision=1
 build_style=python3-pep517
 hostmakedepends="hatchling python3-wheel"
 depends="python3-click"
@@ -12,7 +12,7 @@ license="MIT, Apache-2.0"
 homepage="https://github.com/ofek/userpath"
 changelog="https://raw.githubusercontent.com/ofek/userpath/master/HISTORY.rst"
 distfiles="${PYPI_SITE}/u/userpath/userpath-${version}.tar.gz"
-checksum=85e3274543174477c62d5701ed43a3ef1051824a9dd776968adc411e58640dd1
+checksum=ce8176728d98c914b6401781bf3b23fccd968d1647539c8788c7010375e02796
 
 post_install() {
 	vlicense LICENSE.txt LICENSE

             reply	other threads:[~2023-10-18 19:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 19:39 icp1994 [this message]
2023-10-19 10:14 ` [PR PATCH] [Merged]: " ahesford

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-46764@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).