From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] perl-Regexp-Grammars: update to 1.058.
Date: Fri, 10 Feb 2023 19:44:41 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42197@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
There is a new pull request by zdykstra against master on the void-packages repository
https://github.com/zdykstra/void-packages perl-Regexp-Grammars-1.058
https://github.com/void-linux/void-packages/pull/42197
perl-Regexp-Grammars: update to 1.058.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Another mostly no-op upstream change. Is ... is Perl dying?
A patch file from https://github.com/void-linux/void-packages/pull/42197.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-perl-Regexp-Grammars-1.058-42197.patch --]
[-- Type: text/x-diff, Size: 1144 bytes --]
From daafa0bb9594c81089366bd2ac8005b4a65484f1 Mon Sep 17 00:00:00 2001
From: Zach Dykstra <dykstra.zachary@gmail.com>
Date: Fri, 10 Feb 2023 12:42:04 -0600
Subject: [PATCH] perl-Regexp-Grammars: update to 1.058.
---
srcpkgs/perl-Regexp-Grammars/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/perl-Regexp-Grammars/template b/srcpkgs/perl-Regexp-Grammars/template
index 02466657dada..d3af3f32ba05 100644
--- a/srcpkgs/perl-Regexp-Grammars/template
+++ b/srcpkgs/perl-Regexp-Grammars/template
@@ -1,7 +1,7 @@
# Template file for 'perl-Regexp-Grammars'
pkgname=perl-Regexp-Grammars
-version=1.057
-revision=2
+version=1.058
+revision=1
build_style=perl-module
hostmakedepends="perl"
makedepends="perl"
@@ -11,4 +11,4 @@ maintainer="Zach Dykstra <dykstra.zachary@gmail.com>"
license="Artistic-1.0-Perl, GPL-1.0-or-later"
homepage="https://metacpan.org/release/Regexp-Grammars"
distfiles="${CPAN_SITE}/Regexp/${pkgname/perl-/}-${version}.tar.gz"
-checksum=af53c19818461cd701aeb57c49dffdb463edc4bf8f658d9ea4e6d534ac177041
+checksum=ea88d58e251674fae39b49f4d3b5342eaccb8fcb55856cd304aa1a5ff3d41c92
next reply other threads:[~2023-02-10 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:44 zdykstra [this message]
2023-02-13 18:21 ` [PR PATCH] [Merged]: " leahneukirchen
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-42197@inbox.vuxu.org \
--to=zdykstra@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).