From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-keyring: update to 24.0.1.
Date: Thu, 22 Jun 2023 21:04:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44571@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-keyring
https://github.com/void-linux/void-packages/pull/44571
python3-keyring: update to 24.0.1.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
A patch file from https://github.com/void-linux/void-packages/pull/44571.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-keyring-44571.patch --]
[-- Type: text/x-diff, Size: 2792 bytes --]
From 59cc939f0897023925d72db377fd3c0fa8ef7a73 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Wed, 21 Jun 2023 00:57:13 +0530
Subject: [PATCH 1/2] python3-importlib_metadata: update to 6.7.0.
---
srcpkgs/python3-importlib_metadata/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-importlib_metadata/template b/srcpkgs/python3-importlib_metadata/template
index 82f5db1b125b..29c19546984e 100644
--- a/srcpkgs/python3-importlib_metadata/template
+++ b/srcpkgs/python3-importlib_metadata/template
@@ -1,6 +1,6 @@
# Template file for 'python3-importlib_metadata'
pkgname=python3-importlib_metadata
-version=6.6.0
+version=6.7.0
revision=1
build_style=python3-pep517
hostmakedepends="python3-setuptools_scm python3-wheel"
@@ -9,6 +9,6 @@ short_desc="Read metadata from python3 packages"
maintainer="icp <pangolin@vivaldi.net>"
license="Apache-2.0"
homepage="https://pypi.org/project/importlib-metadata/"
-changelog="https://raw.githubusercontent.com/python/importlib_metadata/main/CHANGES.rst"
+changelog="https://raw.githubusercontent.com/python/importlib_metadata/main/NEWS.rst"
distfiles="${PYPI_SITE}/i/importlib_metadata/importlib_metadata-${version}.tar.gz"
-checksum=92501cdf9cc66ebd3e612f1b4f0c0765dfa42f0fa38ffb319b6bd84dd675d705
+checksum=1aaf550d4f73e5d6783e7acb77aec43d49da8017410afae93822cc9cca98c4d4
From 9eba4a621f1fc5716a47062f68d8bb823e7a67c2 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Wed, 21 Jun 2023 00:58:05 +0530
Subject: [PATCH 2/2] python3-keyring: update to 24.0.1.
---
srcpkgs/python3-keyring/template | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-keyring/template b/srcpkgs/python3-keyring/template
index 306cab402c8c..24eb8790ee38 100644
--- a/srcpkgs/python3-keyring/template
+++ b/srcpkgs/python3-keyring/template
@@ -1,6 +1,6 @@
# Template file for 'python3-keyring'
pkgname=python3-keyring
-version=23.13.1
+version=24.0.1
revision=1
build_style=python3-pep517
hostmakedepends="python3-wheel python3-setuptools_scm"
@@ -11,9 +11,14 @@ short_desc="Python interface to the system keyring service"
maintainer="icp <pangolin@vivaldi.net>"
license="MIT"
homepage="https://pypi.org/project/keyring/"
-changelog="https://raw.githubusercontent.com/jaraco/keyring/main/CHANGES.rst"
+changelog="https://raw.githubusercontent.com/jaraco/keyring/main/NEWS.rst"
distfiles="${PYPI_SITE}/k/keyring/keyring-${version}.tar.gz"
-checksum=ba2e15a9b35e21908d0aaf4e0a47acc52d6ae33444df0da2b49d41a46ef6d678
+checksum=f77da625a448baa77906b099be9feaa29aa90979547506ac1ec422926085cee0
+make_check_pre="env PY_IGNORE_IMPORTMISMATCH=1"
+
+pre_check() {
+ vsed -e '/addopts/d' -i pytest.ini
+}
post_install() {
vlicense LICENSE
next reply other threads:[~2023-06-22 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 19:04 icp1994 [this message]
2023-06-23 12:23 ` [PR PATCH] [Merged]: " Duncaen
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-44571@inbox.vuxu.org \
--to=icp1994@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).