Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] perl-Package-DeprecationManager: update to 0.18
Date: Sat, 04 Mar 2023 09:08:11 +0100	[thread overview]
Message-ID: <20230304080811.a4KDFwccMCilVkXD395NH14RIyRne2d-k32Rms2BZis@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42396@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

There is an updated pull request by newbluemoon against master on the void-packages repository

https://github.com/newbluemoon/void-packages perl-Package-DeprecationManager
https://github.com/void-linux/void-packages/pull/42396

perl-Package-DeprecationManager: update to 0.18
<!-- 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):
  - x86_64-musl
  - armv7l-musl


A patch file from https://github.com/void-linux/void-packages/pull/42396.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-perl-Package-DeprecationManager-42396.patch --]
[-- Type: text/x-diff, Size: 1585 bytes --]

From 9ff18f93154209efba43307fcdb9f4d6fab2da81 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Wed, 22 Feb 2023 19:38:35 +0100
Subject: [PATCH] perl-Package-DeprecationManager: update to 0.18

---
 srcpkgs/perl-Package-DeprecationManager/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/perl-Package-DeprecationManager/template b/srcpkgs/perl-Package-DeprecationManager/template
index aecb8d7a860a..45b154fb3fce 100644
--- a/srcpkgs/perl-Package-DeprecationManager/template
+++ b/srcpkgs/perl-Package-DeprecationManager/template
@@ -1,15 +1,15 @@
 # Template file for 'perl-Package-DeprecationManager'
 pkgname=perl-Package-DeprecationManager
-version=0.17
-revision=4
+version=0.18
+revision=1
 build_style=perl-module
 hostmakedepends="perl"
-makedepends="${hostmakedepends} perl-Package-Stash perl-Params-Util perl-Sub-Install perl-Sub-Name"
+makedepends="${hostmakedepends} perl-Package-Stash perl-Params-Util perl-Sub-Install"
 depends="${makedepends}"
 checkdepends="perl-Test-Warnings perl-Test-Fatal"
 short_desc="Manage deprecation warnings for your distribution"
 maintainer="newbluemoon <blaumolch@mailbox.org>"
 license="Artistic-2.0"
 homepage="https://metacpan.org/release/Package-DeprecationManager"
-distfiles="${CPAN_SITE}/Package/${pkgname/perl-/}-$version.tar.gz"
-checksum="1d743ada482b5c9871d894966e87d4c20edc96931bb949fb2638b000ddd6684b"
+distfiles="${CPAN_SITE}/Package/Package-DeprecationManager-${version}.tar.gz"
+checksum=b68d3f0ced55b7615fddbb6029b89f92a34fe0dd8c6fd6bceffc157d56834fe8

  parent reply	other threads:[~2023-03-04  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 18:41 [PR PATCH] " newbluemoon
2023-02-22 23:01 ` [PR REVIEW] " mhmdanas
2023-02-23  6:15 ` [PR PATCH] [Updated] " newbluemoon
2023-03-04  8:08 ` newbluemoon [this message]
2023-03-05 22:10 ` [PR PATCH] [Merged]: " Piraty

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=20230304080811.a4KDFwccMCilVkXD395NH14RIyRne2d-k32Rms2BZis@z \
    --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).