From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-watchdog: update to 2.2.1.
Date: Sun, 22 Jan 2023 14:25:15 +0100 [thread overview]
Message-ID: <20230122132515.IJCigiZRJxXVlIjpAdTH-q9STXTFwmPFbp-BE_ubpow@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41386@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
There is an updated pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-watchdog
https://github.com/void-linux/void-packages/pull/41386
python3-watchdog: update to 2.2.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/41386.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-watchdog-41386.patch --]
[-- Type: text/x-diff, Size: 1546 bytes --]
From 3b26c738e5026ccba4c4083e6ebeff2d048401b6 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 31 Dec 2022 20:30:07 +0530
Subject: [PATCH] python3-watchdog: update to 2.2.1.
---
srcpkgs/python3-watchdog/template | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-watchdog/template b/srcpkgs/python3-watchdog/template
index bea7fbb2289f..66eb30387ae3 100644
--- a/srcpkgs/python3-watchdog/template
+++ b/srcpkgs/python3-watchdog/template
@@ -1,17 +1,19 @@
# Template file for 'python3-watchdog'
pkgname=python3-watchdog
-version=2.1.6
-revision=2
+version=2.2.1
+revision=1
build_style=python3-module
+make_check_args="--deselect tests/test_inotify_buffer.py::test_unmount_watched_directory_filesystem"
hostmakedepends="python3-setuptools"
-depends="python3-yaml python3-argh python3-pathtools"
+depends="python3-yaml"
checkdepends="python3-pytest $depends"
short_desc="Python3 API and shell utilities to monitor file system events"
maintainer="Maurizio Porrato <maurizio.porrato@gmail.com>"
license="Apache-2.0"
-homepage="http://github.com/gorakhargosh/watchdog"
+homepage="https://github.com/gorakhargosh/watchdog"
+changelog="https://raw.githubusercontent.com/gorakhargosh/watchdog/master/changelog.rst"
distfiles="${PYPI_SITE}/w/watchdog/watchdog-${version}.tar.gz"
-checksum=a36e75df6c767cbf46f61a91c70b3ba71811dfa0aca4a324d9407a06a8b7a2e7
+checksum=cdcc23c9528601a8a293eb4369cbd14f6b4f34f07ae8769421252e9c22718b6f
conflicts="python-watchdog>=0"
pre_check() {
next prev parent reply other threads:[~2023-01-22 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 19:44 [PR PATCH] python3-watchdog: update to 2.2.0 icp1994
2023-01-02 8:47 ` kruceter
2023-01-02 8:56 ` [PR PATCH] [Updated] " icp1994
2023-01-02 9:07 ` [PR REVIEW] python3-watchdog: update to 2.2.1 paper42
2023-01-02 9:10 ` icp1994
2023-01-02 11:06 ` paper42
2023-01-22 13:25 ` icp1994 [this message]
2023-01-22 19:23 ` [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=20230122132515.IJCigiZRJxXVlIjpAdTH-q9STXTFwmPFbp-BE_ubpow@z \
--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).