From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] perl-CryptX: update to 0.074
Date: Sun, 26 Dec 2021 14:49:27 +0100 [thread overview]
Message-ID: <20211226134927.kL2hY21CzrVcgdXHMMD9PaMTbDImwdRvahGWPQU7giU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32106@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
There is an updated pull request by newbluemoon against master on the void-packages repository
https://github.com/newbluemoon/void-packages perl-CryptX
https://github.com/void-linux/void-packages/pull/32106
perl-CryptX: update to 0.074
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/32106.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-perl-CryptX-32106.patch --]
[-- Type: text/x-diff, Size: 1210 bytes --]
From f57b07d6da76de30411acff722f2546fe71a99f5 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Wed, 21 Jul 2021 21:04:29 +0200
Subject: [PATCH] perl-CryptX: update to 0.075
---
srcpkgs/perl-CryptX/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/perl-CryptX/template b/srcpkgs/perl-CryptX/template
index f5db006cf426..f43289900a41 100644
--- a/srcpkgs/perl-CryptX/template
+++ b/srcpkgs/perl-CryptX/template
@@ -1,15 +1,16 @@
# Template file for 'perl-CryptX'
pkgname=perl-CryptX
-version=0.072
-revision=2
+version=0.075
+revision=1
wrksrc="${pkgname#perl-}-${version}"
build_style=perl-module
hostmakedepends="perl"
makedepends="perl"
depends="perl"
+checkdepends="perl-JSON"
short_desc="Cryptographic toolkit (self-contained, no external libraries needed)"
maintainer="newbluemoon <blaumolch@mailbox.org>"
license="Artistic-1.0-Perl, GPL-1.0-or-later, Unlicense"
homepage="https://metacpan.org/release/CryptX"
distfiles="${CPAN_SITE}/Crypt/${pkgname#perl-}-${version}.tar.gz"
-checksum=162ffb9306e90dab4743a5b22ede21a53e09de2200d0ea35bd4f13744a161706
+checksum=f4f742d1c165ed337abadaab3ec18d9a05c577a6d635e777b9a4b8809e2cc0f4
next prev parent reply other threads:[~2021-12-26 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 19:24 [PR PATCH] perl-CryptX: update to 0.073 newbluemoon
2021-09-10 7:22 ` [PR PATCH] [Updated] " newbluemoon
2021-11-07 8:46 ` newbluemoon
2021-12-26 13:49 ` newbluemoon [this message]
2021-12-30 16:08 ` [PR PATCH] [Merged]: perl-CryptX: update to 0.075 Chocimier
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=20211226134927.kL2hY21CzrVcgdXHMMD9PaMTbDImwdRvahGWPQU7giU@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).