From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] perl-YAML-Tiny: update to 1.76
Date: Sat, 11 Jan 2025 18:02:23 +0100 [thread overview]
Message-ID: <20250111170223.E954E2433B@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53659@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
There is an updated pull request by newbluemoon against master on the void-packages repository
https://github.com/newbluemoon/void-packages perl-YAML-Tiny
https://github.com/void-linux/void-packages/pull/53659
perl-YAML-Tiny: update to 1.76
<!-- 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, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv7l-musl (cross)
A patch file from https://github.com/void-linux/void-packages/pull/53659.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-perl-YAML-Tiny-53659.patch --]
[-- Type: text/x-diff, Size: 1046 bytes --]
From 7fbc3078ebd491a7b46cb15cfc112a61bab35a08 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Tue, 24 Dec 2024 06:32:49 +0100
Subject: [PATCH] perl-YAML-Tiny: update to 1.76
---
srcpkgs/perl-YAML-Tiny/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/perl-YAML-Tiny/template b/srcpkgs/perl-YAML-Tiny/template
index 79e3ec5d32a30f..12b29ffd24a98c 100644
--- a/srcpkgs/perl-YAML-Tiny/template
+++ b/srcpkgs/perl-YAML-Tiny/template
@@ -1,6 +1,6 @@
# Template file for 'perl-YAML-Tiny'
pkgname=perl-YAML-Tiny
-version=1.74
+version=1.76
revision=1
build_style=perl-module
hostmakedepends="perl"
@@ -11,4 +11,4 @@ maintainer="newbluemoon <blaumolch@mailbox.org>"
license="Artistic-1.0-Perl, GPL-1.0-or-later"
homepage="https://github.com/Perl-Toolchain-Gang/YAML-Tiny"
distfiles="${CPAN_SITE}/YAML/YAML-Tiny-${version}.tar.gz"
-checksum=7b38ca9f5d3ce24230a6b8bdc1f47f5b2db348e7f7f9666c26f5955636e33d6c
+checksum=a8d584394cf069bf8f17cba3dd5099003b097fce316c31fb094f1b1c171c08a3
next prev parent reply other threads:[~2025-01-11 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 7:45 [PR PATCH] " newbluemoon
2025-01-11 17:02 ` newbluemoon [this message]
2025-01-28 17:46 ` [PR PATCH] [Updated] " newbluemoon
2025-02-09 8:10 ` newbluemoon
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=20250111170223.E954E2433B@inbox.vuxu.org \
--to=newbluemoon@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).