From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-jaraco.logging: update to 3.3.0.
Date: Fri, 16 Feb 2024 21:42:07 +0100 [thread overview]
Message-ID: <20240216204207.C254D231A7@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48777@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
There is an updated pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-jaraco.logging
https://github.com/void-linux/void-packages/pull/48777
python3-jaraco.logging: update to 3.3.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/48777.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-jaraco.logging-48777.patch --]
[-- Type: text/x-diff, Size: 1405 bytes --]
From 6e04bd446262651ceb99ea16e631ec0d4cd28a5d Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Fri, 26 Jan 2024 02:08:18 +0530
Subject: [PATCH] python3-jaraco.logging: update to 3.3.0.
---
srcpkgs/python3-jaraco.logging/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-jaraco.logging/template b/srcpkgs/python3-jaraco.logging/template
index ec514e0eaf226..29fe5144f3450 100644
--- a/srcpkgs/python3-jaraco.logging/template
+++ b/srcpkgs/python3-jaraco.logging/template
@@ -1,7 +1,7 @@
# Template file for 'python3-jaraco.logging'
pkgname=python3-jaraco.logging
-version=3.1.2
-revision=3
+version=3.3.0
+revision=1
build_style=python3-pep517
hostmakedepends="python3-wheel python3-setuptools_scm"
depends="python3-tempora"
@@ -9,9 +9,9 @@ short_desc="Support for Python logging facility"
maintainer="icp <pangolin@vivaldi.net>"
license="MIT"
homepage="https://github.com/jaraco/jaraco.logging"
-changelog="https://raw.githubusercontent.com/jaraco/jaraco.logging/main/CHANGES.rst"
+changelog="https://raw.githubusercontent.com/jaraco/jaraco.logging/main/NEWS.rst"
distfiles="${PYPI_SITE}/j/jaraco.logging/jaraco.logging-${version}.tar.gz"
-checksum=93a70b8b3767779ad6c7b56ee98579ced77b69f16abbcae749f62c2c59e67931
+checksum=f4a7cfbacb86a834c2886c01a3b52bc4cde2728c1d9717c49d4dce1d6248f07b
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2024-02-16 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 20:39 [PR PATCH] " icp1994
2024-02-16 20:42 ` icp1994 [this message]
2024-02-16 21:27 ` [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=20240216204207.C254D231A7@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).