From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] perl-Type-Tiny: update to 2.000001.
Date: Mon, 03 Oct 2022 11:52:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39659@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
There is a new pull request by jcgruenhage against master on the void-packages repository
https://github.com/jcgruenhage/void-packages perl-Type-Tiny-2.000001_1
https://github.com/void-linux/void-packages/pull/39659
perl-Type-Tiny: update to 2.000001.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/39659.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-perl-Type-Tiny-2.000001_1-39659.patch --]
[-- Type: text/x-diff, Size: 1156 bytes --]
From a84a10d33573eb8d867b22f37ccbf90bdde09973 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Mon, 3 Oct 2022 11:52:26 +0200
Subject: [PATCH] perl-Type-Tiny: update to 2.000001.
---
srcpkgs/perl-Type-Tiny/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/perl-Type-Tiny/template b/srcpkgs/perl-Type-Tiny/template
index 6289677b2653..5c92851f53ff 100644
--- a/srcpkgs/perl-Type-Tiny/template
+++ b/srcpkgs/perl-Type-Tiny/template
@@ -1,6 +1,6 @@
# Template file for 'perl-Type-Tiny'
pkgname=perl-Type-Tiny
-version=1.016010
+version=2.000001
revision=1
wrksrc="${pkgname/perl-/}-${version}"
build_style=perl-module
@@ -12,4 +12,4 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="Artistic-1.0-Perl, GPL-1.0-or-later"
homepage="https://metacpan.org/release/Type-Tiny"
distfiles="https://cpan.metacpan.org/authors/id/T/TO/TOBYINK/${pkgname/perl-/}-${version}.tar.gz"
-checksum=e3fee77753a0abc636c5a57595cfb1c8e1ac11d7c8ff3b216e599091abe3e368
+checksum=63f942e1d6f5104fa90acbfc435e69e570d8b3374fe0c733f8419e31a6331920
next reply other threads:[~2022-10-03 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 9:52 jcgruenhage [this message]
2022-10-03 13:08 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39659@inbox.vuxu.org \
--to=jcgruenhage@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).