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-platformdirs: update to 2.5.2.
Date: Sat, 23 Jul 2022 15:49:29 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38208@inbox.vuxu.org> (raw)

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

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

https://github.com/icp1994/void-packages python3-platformdirs
https://github.com/void-linux/void-packages/pull/38208

python3-platformdirs: update to 2.5.2.
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### 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/38208.patch is attached

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

From f1f76a8748eb4ca7f1239a2963ce14e4c519d011 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 23 Jul 2022 19:17:31 +0530
Subject: [PATCH] python3-platformdirs: update to 2.5.2.

---
 srcpkgs/python3-platformdirs/template | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/python3-platformdirs/template b/srcpkgs/python3-platformdirs/template
index e5b09121ded8..288ab676ac4b 100644
--- a/srcpkgs/python3-platformdirs/template
+++ b/srcpkgs/python3-platformdirs/template
@@ -1,10 +1,10 @@
 # Template file for 'python3-platformdirs'
 pkgname=python3-platformdirs
-version=2.3.0
-revision=2
+version=2.5.2
+revision=1
 wrksrc="platformdirs-${version}"
-build_style=python3-module
-hostmakedepends="python3-setuptools python3-setuptools_scm"
+build_style=python3-pep517
+hostmakedepends="hatchling hatch-vcs"
 depends="python3"
 checkdepends="python3-appdirs python3-pytest python3-pytest-mock"
 short_desc="Library to determine platform-specific system directories"
@@ -13,8 +13,10 @@ license="MIT"
 homepage="https://github.com/platformdirs/platformdirs"
 changelog="https://raw.githubusercontent.com/platformdirs/platformdirs/main/CHANGES.rst"
 distfiles="${PYPI_SITE}/p/platformdirs/platformdirs-${version}.tar.gz"
-checksum=15b056538719b1c94bdaccb29e5f81879c7f7f0f4a153f46086d155dffcd4f0f
+checksum=58c8abb07dcb441e6ee4b11d8df0ac856038f944ab98b7be6b27b2a3c7feef19
+make_check_pre="env PYTHONPATH=src"
 
 post_install() {
+	# TODO: reanme to LICENSE for later versions
 	vlicense LICENSE.txt
 }

             reply	other threads:[~2022-07-23 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 13:49 icp1994 [this message]
2022-07-23 16:32 ` [PR REVIEW] " classabbyamp
2022-07-23 16:40 ` icp1994
2022-07-23 16:56 ` classabbyamp
2022-07-23 17:03 ` [PR PATCH] [Updated] " icp1994
2022-07-23 17:07 ` [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-38208@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).