From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-confuse: update to 2.0.0.
Date: Tue, 04 Oct 2022 15:07:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39705@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
There is a new pull request by TinfoilSubmarine against master on the void-packages repository
https://github.com/TinfoilSubmarine/void-packages maint/python3-confuse
https://github.com/void-linux/void-packages/pull/39705
python3-confuse: update to 2.0.0.
<!-- 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, (ARCH-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/39705.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-maint/python3-confuse-39705.patch --]
[-- Type: text/x-diff, Size: 1322 bytes --]
From c37736bc817929827d55846a6f9f11a6bd083feb Mon Sep 17 00:00:00 2001
From: Joel Beckmeyer <joel@beckmeyer.us>
Date: Tue, 4 Oct 2022 09:05:13 -0400
Subject: [PATCH] python3-confuse: update to 2.0.0.
---
srcpkgs/python3-confuse/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-confuse/template b/srcpkgs/python3-confuse/template
index 05a9764fa7e5..f922b75e0da5 100644
--- a/srcpkgs/python3-confuse/template
+++ b/srcpkgs/python3-confuse/template
@@ -1,10 +1,10 @@
# Template file for 'python3-confuse'
pkgname=python3-confuse
-version=1.7.0
+version=2.0.0
revision=1
wrksrc="confuse-${version}"
-build_style=python3-module
-hostmakedepends="python3-setuptools"
+build_style=python3-pep517
+hostmakedepends="python3-flit_core"
depends="python3-yaml"
checkdepends="${depends} python3-pytest"
short_desc="Painless YAML config files for Python"
@@ -13,7 +13,7 @@ license="MIT"
homepage="https://github.com/beetbox/confuse"
changelog="https://raw.githubusercontent.com/beetbox/confuse/master/docs/changelog.rst"
distfiles="${PYPI_SITE}/c/confuse/confuse-${version}.tar.gz"
-checksum=c9fe8474516a62397f8e52fcf89547bb2f2737b1a4a6f6dec11a286f0b3a7401
+checksum=acc57c45ec2a9850a90fe7c29812bbdd8405e48a49c1a22899df915d0aca941f
post_install() {
vlicense LICENSE
next reply other threads:[~2022-10-04 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 13:07 TinfoilSubmarine [this message]
2022-10-04 14:30 ` [PR PATCH] [Merged]: " ahesford
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-39705@inbox.vuxu.org \
--to=tinfoilsubmarine@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).