From: cptpcrd <cptpcrd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] watchexec: update to 1.15.0.
Date: Mon, 12 Apr 2021 14:05:12 +0200 [thread overview]
Message-ID: <20210412120512.bVXlSNcCwXykufXUqX1eGgSr9LooPpGjhm5iMDtBMWU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30182@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
There is an updated pull request by cptpcrd against master on the void-packages repository
https://github.com/cptpcrd/void-packages watchexec
https://github.com/void-linux/void-packages/pull/30182
watchexec: update to 1.15.0.
I no longer actively use Void (though I might come back in the future :-), so **I have not tested this**. I just noticed that there was an update and thought I should PR it since I'm still listed as the maintainer.
I can keep submitting untested updates for `watchexec` and `birdtray` (the 2 packages I'm listed as the maintainer of), or, if you want, I can remove myself as the maintainer and stop doing that. I'm fine either way; I just wanted to make it clear what the situation is here.
A patch file from https://github.com/void-linux/void-packages/pull/30182.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-watchexec-30182.patch --]
[-- Type: text/x-diff, Size: 1076 bytes --]
From f919c19596b4e919c7fc174edd1476ed125257e0 Mon Sep 17 00:00:00 2001
From: cptpcrd <31829097+cptpcrd@users.noreply.github.com>
Date: Mon, 12 Apr 2021 07:54:04 -0400
Subject: [PATCH] watchexec: update to 1.15.0.
---
srcpkgs/watchexec/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/watchexec/template b/srcpkgs/watchexec/template
index 8b62e5ee01d1..d044956eeb14 100644
--- a/srcpkgs/watchexec/template
+++ b/srcpkgs/watchexec/template
@@ -1,6 +1,6 @@
# Template file for 'watchexec'
pkgname=watchexec
-version=1.14.1
+version=1.15.0
revision=1
build_style=cargo
short_desc="Executes commands in response to file modifications"
@@ -8,7 +8,7 @@ maintainer="cptpcrd <cptpcrd.git@gmail.com>"
license="Apache-2.0"
homepage="https://github.com/watchexec/watchexec"
distfiles="https://github.com/watchexec/watchexec/archive/${version}.tar.gz"
-checksum=23ca90f1f070b0d30e821667c8b9deaf174d020373ea032e9e22f1a78adcfa1c
+checksum=536366e294047480ebfd440edc473690c226f23d07ea166023d1a7e8953c4f34
post_install() {
vdoc README.md
next prev parent reply other threads:[~2021-04-12 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 12:02 [PR PATCH] " cptpcrd
2021-04-12 12:05 ` cptpcrd [this message]
2021-04-12 13:34 ` ericonr
2021-04-12 13:38 ` [PR PATCH] [Updated] " cptpcrd
2021-04-12 13:40 ` watchexec: update to 1.15.0, orphan (along with birdtray) cptpcrd
2021-04-14 12:29 ` [PR PATCH] [Closed]: " ericonr
2021-04-14 12:29 ` ericonr
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=20210412120512.bVXlSNcCwXykufXUqX1eGgSr9LooPpGjhm5iMDtBMWU@z \
--to=cptpcrd@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).