From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: python3-parver-0.3.1
Date: Fri, 31 Dec 2021 19:03:26 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34791@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
There is a new pull request by unspecd against master on the void-packages repository
https://github.com/unspecd/void-packages pkg/python3-parver
https://github.com/void-linux/void-packages/pull/34791
New package: python3-parver-0.3.1
[ci skip]
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
Depends on #34774.
A patch file from https://github.com/void-linux/void-packages/pull/34791.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pkg/python3-parver-34791.patch --]
[-- Type: text/x-diff, Size: 1235 bytes --]
From a7be7c909e427942b298c196740b907b577644b2 Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Fri, 31 Dec 2021 11:01:30 +1100
Subject: [PATCH] New package: python3-parver-0.3.1
---
srcpkgs/python3-parver/template | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644 srcpkgs/python3-parver/template
diff --git a/srcpkgs/python3-parver/template b/srcpkgs/python3-parver/template
new file mode 100644
index 000000000000..68800130d269
--- /dev/null
+++ b/srcpkgs/python3-parver/template
@@ -0,0 +1,19 @@
+# Template file for 'python3-parver'
+pkgname=python3-parver
+version=0.3.1
+revision=1
+wrksrc="parver-${version}"
+build_style=python3-module
+hostmakedepends="python3-setuptools"
+depends="python3-Arpeggio python3-attrs python3-six"
+checkdepends="${depends} python3-hypothesis python3-pretend python3-pytest"
+short_desc="Allows parsing and manipulation of PEP 440 version numbers"
+maintainer="Evgeny Ermakov <evgeny.v.ermakov@gmail.com>"
+license="MIT"
+homepage="https://github.com/RazerM/parver"
+distfiles="${homepage}/archive/${version}.tar.gz"
+checksum=db9cb60d6fa8fa5fe88af7016c26846a297dec8ce30f4966f29edf1351e4a544
+
+post_install() {
+ vlicense LICENSE
+}
next reply other threads:[~2021-12-31 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 18:03 unspecd [this message]
2022-01-01 21:17 ` [PR PATCH] [Closed]: " unspecd
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-34791@inbox.vuxu.org \
--to=unspecd@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).