Github messages for voidlinux
 help / color / mirror / Atom feed
From: nbelikov <nbelikov@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: python3-pathvalidate-2.5.0
Date: Mon, 13 Jun 2022 19:33:06 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37549@inbox.vuxu.org> (raw)

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

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

https://github.com/nbelikov/void-packages python3-pathvalidate
https://github.com/void-linux/void-packages/pull/37549

New package: python3-pathvalidate-2.5.0
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES** (this package is a new requirement for `Electron-Cash`).

#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)



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

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

From de04b02ae863b62f5cd8cfe72e4de2fc19ed4cb0 Mon Sep 17 00:00:00 2001
From: Nikolay Belikov <nb@nbelikov.com>
Date: Mon, 13 Jun 2022 20:26:06 +0300
Subject: [PATCH] New package: python3-pathvalidate-2.5.0

---
 srcpkgs/python3-pathvalidate/template | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 srcpkgs/python3-pathvalidate/template

diff --git a/srcpkgs/python3-pathvalidate/template b/srcpkgs/python3-pathvalidate/template
new file mode 100644
index 000000000000..2eb4ecf90878
--- /dev/null
+++ b/srcpkgs/python3-pathvalidate/template
@@ -0,0 +1,24 @@
+# Template file for 'python3-pathvalidate'
+pkgname=python3-pathvalidate
+version=2.5.0
+revision=1
+short_desc="Python library to sanitize/validate strings such as filenames/paths"
+maintainer="Nikolay Belikov <nb@nbelikov.com>"
+license="MIT"
+homepage="https://github.com/thombashi/pathvalidate"
+changelog="https://github.com/thombashi/pathvalidate/releases"
+
+build_style=python3-module
+wrksrc="pathvalidate-${version}"
+hostmakedepends="python3-setuptools"
+depends="python3>=3.6"
+# Tests depend on unpackaged allpairspy, faker, pytest-discord,
+# pytest-md-report.
+make_check=no
+
+distfiles="${PYPI_SITE}/p/pathvalidate/pathvalidate-${version}.tar.gz"
+checksum="119ba36be7e9a405d704c7b7aea4b871c757c53c9adc0ed64f40be1ed8da2781"
+
+post_install() {
+	vlicense LICENSE
+}

             reply	other threads:[~2022-06-13 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 17:33 nbelikov [this message]
2022-06-13 17:44 ` [PR REVIEW] " classabbyamp
2022-06-13 17:45 ` classabbyamp
2022-06-13 17:45 ` classabbyamp
2022-06-13 17:45 ` classabbyamp
2022-06-13 18:08 ` [PR PATCH] [Updated] " nbelikov
2022-06-13 18:09 ` nbelikov
2022-06-13 18:17 ` [PR PATCH] [Updated] " nbelikov
2022-06-16 16:57 ` [PR PATCH] [Closed]: " nbelikov
2022-06-16 16:57 ` nbelikov

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-37549@inbox.vuxu.org \
    --to=nbelikov@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).