From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: epy-2022.4.18
Date: Mon, 03 Oct 2022 15:42:17 +0200 [thread overview]
Message-ID: <20221003134217.7mg-53EK4o4ELMD8I6C4aoJay-Nz_w8yseoV4lDgHG8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39316@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
There is an updated pull request by benalb against master on the void-packages repository
https://github.com/benalb/void-packages epy
https://github.com/void-linux/void-packages/pull/39316
New package: epy-2022.4.18
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (X86_64-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
A patch file from https://github.com/void-linux/void-packages/pull/39316.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-epy-39316.patch --]
[-- Type: text/x-diff, Size: 998 bytes --]
From 0ff290fb5f0e7c8c011af66686bf39fd43c9645c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Fri, 16 Sep 2022 15:41:14 +0200
Subject: [PATCH] New package: epy-2022.4.18
---
srcpkgs/epy/template | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 srcpkgs/epy/template
diff --git a/srcpkgs/epy/template b/srcpkgs/epy/template
new file mode 100644
index 000000000000..ba05ffd465d2
--- /dev/null
+++ b/srcpkgs/epy/template
@@ -0,0 +1,14 @@
+# Template file for 'epy'
+pkgname=epy
+version=2022.4.18
+revision=1
+build_style=python3-module
+hostmakedepends="python3 python3-setuptools"
+depends="python3"
+checkdepends="python3-pytest"
+short_desc="CLI ebook reader"
+maintainer="Benjamín Albiñana <benalb@gmail.com>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/wustho/epy"
+distfiles="${homepage}/archive/refs/tags/v${version}.tar.gz"
+checksum=140225acf0216ce3a7f502adb752c0ee7c189297051d0cb84e65e4fe767add23
next prev parent reply other threads:[~2022-10-03 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:42 [PR PATCH] " benalb
2022-09-16 13:46 ` benalb
2022-10-02 21:14 ` [PR REVIEW] " Piraty
2022-10-03 13:42 ` benalb [this message]
2022-10-03 13:45 ` benalb
2022-10-03 15:38 ` [PR PATCH] [Merged]: " Piraty
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=20221003134217.7mg-53EK4o4ELMD8I6C4aoJay-Nz_w8yseoV4lDgHG8@z \
--to=benalb@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).