From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] perl-JSON: update to 4.10.
Date: Wed, 05 Jul 2023 13:20:49 +0200 [thread overview]
Message-ID: <20230705112049.93jWz09ZwRrnWI8NXsT3jPcD_ieDIIq3pnkLgkUBxcc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44858@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
There is an updated pull request by Bnyro against master on the void-packages repository
https://github.com/Bnyro/void-packages perl-JSON
https://github.com/void-linux/void-packages/pull/44858
perl-JSON: update to 4.10.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/44858.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-perl-JSON-44858.patch --]
[-- Type: text/x-diff, Size: 1079 bytes --]
From 8efa3779b1a1b79c08107f3b68967cd30bac8cbd Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Wed, 5 Jul 2023 13:21:25 +0200
Subject: [PATCH] perl-JSON: update to 4.10.
---
srcpkgs/perl-JSON/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/perl-JSON/template b/srcpkgs/perl-JSON/template
index f51d655448bb..a979c4fd529b 100644
--- a/srcpkgs/perl-JSON/template
+++ b/srcpkgs/perl-JSON/template
@@ -1,6 +1,6 @@
# Template file for 'perl-JSON'
pkgname=perl-JSON
-version=4.03
+version=4.10
revision=1
build_style=perl-module
hostmakedepends="perl"
@@ -11,5 +11,6 @@ short_desc="JSON (JavaScript Object Notation) encoder/decoder"
maintainer="Steven R <dev@styez.com>"
license="Artistic-1.0-Perl, GPL-1.0-or-later"
homepage="https://metacpan.org/release/JSON"
+changelog="https://metacpan.org/dist/JSON/changes"
distfiles="${CPAN_SITE}/JSON/JSON-${version}.tar.gz"
-checksum=e41f8761a5e7b9b27af26fe5780d44550d7a6a66bf3078e337d676d07a699941
+checksum=df8b5143d9a7de99c47b55f1a170bd1f69f711935c186a6dc0ab56dd05758e35
next prev parent reply other threads:[~2023-07-05 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 11:19 [PR PATCH] " Bnyro
2023-07-05 11:20 ` Bnyro [this message]
2023-07-08 18:22 ` [PR PATCH] [Merged]: " Duncaen
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=20230705112049.93jWz09ZwRrnWI8NXsT3jPcD_ieDIIq3pnkLgkUBxcc@z \
--to=bnyro@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).