From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python-enum34: update to 1.1.10
Date: Sun, 09 May 2021 02:28:46 +0200 [thread overview]
Message-ID: <20210509002846.g_Y_fcBmPXrtdLTBgHlX0At63N2ZauDUYXY6yJaIfig@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30755@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
There is an updated pull request by heliocat against master on the void-packages repository
https://github.com/heliocat/void-packages python-enum34
https://github.com/void-linux/void-packages/pull/30755
python-enum34: update to 1.1.10
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
@asergi
A patch file from https://github.com/void-linux/void-packages/pull/30755.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python-enum34-30755.patch --]
[-- Type: text/x-diff, Size: 1313 bytes --]
From fb743c83e1790e3612546fb9f590b9b13e8289ab Mon Sep 17 00:00:00 2001
From: Colin Booth <colin@heliocat.net>
Date: Sat, 8 May 2021 17:25:33 -0700
Subject: [PATCH] python-enum34: update to 1.1.10
---
srcpkgs/python-enum34/template | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/python-enum34/template b/srcpkgs/python-enum34/template
index 99ca2ade67a1..64f503c29ddc 100644
--- a/srcpkgs/python-enum34/template
+++ b/srcpkgs/python-enum34/template
@@ -1,22 +1,21 @@
# Template file for 'python-enum34'
pkgname=python-enum34
-version=1.1.6
-revision=2
+version=1.1.10
+revision=1
wrksrc="enum34-${version}"
build_style=python2-module
hostmakedepends="python-setuptools"
depends="python"
-pycompile_module="enum"
short_desc="Backport of Python 3.4 enum module"
maintainer="Alessio Sergi <al3hex@gmail.com>"
+license="BSD-3-Clause"
homepage="https://bitbucket.org/stoneleaf/enum34"
-license="3-clause-BSD"
distfiles="${PYPI_SITE}/e/enum34/enum34-${version}.tar.gz"
-checksum=8ad8c4783bf61ded74527bffb48ed9b54166685e4230386a9ed9b1279e2df5b1
+checksum=cce6a7477ed816bd2542d03d53db9f0db935dd013b70f336a95c73979289f248
pre_build() {
# remove doc
- sed -i "/'enum' :/,+6d" setup.py
+ vsed -i "/'enum' :/,+6d" setup.py
}
post_install() {
vlicense enum/LICENSE
next prev parent reply other threads:[~2021-05-09 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 0:26 [PR PATCH] " heliocat
2021-05-09 0:28 ` heliocat [this message]
2021-05-09 3:59 ` ericonr
2021-05-09 6:19 ` [PR PATCH] [Updated] " heliocat
2021-05-09 6:19 ` heliocat
2021-05-09 20:25 ` [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=20210509002846.g_Y_fcBmPXrtdLTBgHlX0At63N2ZauDUYXY6yJaIfig@z \
--to=heliocat@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).