From: tkiatd <tkiatd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pem: update to 20.1.0
Date: Sat, 10 Oct 2020 13:27:35 +0200 [thread overview]
Message-ID: <20201010112735.zuGXEEJJFK3NI9jVb8md0FSFEXOlp_nHwvvECRFSL38@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25365@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
There is an updated pull request by tkiatd against master on the void-packages repository
https://github.com/tkiatd/void-packages python3-pem
https://github.com/void-linux/void-packages/pull/25365
python3-pem: update to 20.1.0
A patch file from https://github.com/void-linux/void-packages/pull/25365.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pem-25365.patch --]
[-- Type: text/x-diff, Size: 1229 bytes --]
From 35f8ff53a17f75c415c305af4961d5366e92becb Mon Sep 17 00:00:00 2001
From: tkiatd <tkiatd@outlook.com>
Date: Mon, 5 Oct 2020 23:26:59 +0700
Subject: [PATCH] python3-pem: update to 20.1.0
travis CI failed: so I remove deprecated noarch and do not set pycompile_module
---
srcpkgs/python3-pem/template | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-pem/template b/srcpkgs/python3-pem/template
index ad51601c006..9622282b836 100644
--- a/srcpkgs/python3-pem/template
+++ b/srcpkgs/python3-pem/template
@@ -1,11 +1,9 @@
# Template file for 'python3-pem'
pkgname=python3-pem
-version=19.3.0
+version=20.1.0
revision=1
-archs=noarch
wrksrc="pem-${version}"
build_style=python3-module
-pycompile_module="pem"
hostmakedepends="python3-setuptools"
depends="python3"
short_desc="Easy PEM file parsing in Python3"
@@ -13,7 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://pem.readthedocs.io/en/stable/"
distfiles="${PYPI_SITE}/p/pem/pem-${version}.tar.gz"
-checksum=d10058932ec7b9bbc81c40862275395b9faa287353a9152b642393e7efcdb526
+checksum=2763631a5ffe55f1f21fa34abafdba174a8eeb670d84f66dcfd7a523b44608f6
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2020-10-10 11:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 16:32 [PR PATCH] " tkiatd
2020-10-06 9:05 ` [PR PATCH] [Updated] " tkiatd
2020-10-09 12:19 ` Duncaen
2020-10-10 11:27 ` tkiatd [this message]
2020-10-10 12:04 ` tkiatd
2020-10-15 5:58 ` ericonr
2020-10-15 5:59 ` ericonr
2020-10-15 12:15 ` [PR PATCH] [Updated] " tkiatd
2020-10-15 12:24 ` tkiatd
2020-10-15 13:52 ` tkiatd
2020-10-15 13:58 ` tkiatd
2020-10-15 16:39 ` [PR PATCH] [Merged]: " ericonr
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=20201010112735.zuGXEEJJFK3NI9jVb8md0FSFEXOlp_nHwvvECRFSL38@z \
--to=tkiatd@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).