From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-importlib_metadata: update to 6.1.0.
Date: Sun, 19 Mar 2023 20:13:24 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42867@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-importlib_metadata
https://github.com/void-linux/void-packages/pull/42867
python3-importlib_metadata: update to 6.1.0.
#### 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/42867.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-importlib_metadata-42867.patch --]
[-- Type: text/x-diff, Size: 1204 bytes --]
From 29abebfddc21ce35e40850e6f305179bdd6e7b48 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Mon, 20 Mar 2023 00:42:26 +0530
Subject: [PATCH] python3-importlib_metadata: update to 6.1.0.
---
srcpkgs/python3-importlib_metadata/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-importlib_metadata/template b/srcpkgs/python3-importlib_metadata/template
index 128ff01187f0..e9b68c7dee4f 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.0.0
+version=6.1.0
revision=1
build_style=python3-pep517
hostmakedepends="python3-setuptools_scm python3-wheel"
@@ -11,4 +11,4 @@ license="Apache-2.0"
homepage="https://pypi.org/project/importlib-metadata/"
changelog="https://raw.githubusercontent.com/python/importlib_metadata/main/CHANGES.rst"
distfiles="${PYPI_SITE}/i/importlib_metadata/importlib_metadata-${version}.tar.gz"
-checksum=e354bedeb60efa6affdcc8ae121b73544a7aa74156d047311948f6d711cd378d
+checksum=43ce9281e097583d758c2c708c4376371261a02c34682491a8e98352365aad20
next reply other threads:[~2023-03-19 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 19:13 icp1994 [this message]
2023-03-20 4:13 ` [PR PATCH] [Merged]: " classabbyamp
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-42867@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).