From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] ImageMagick: update to 7.1.0.23.
Date: Sat, 12 Feb 2022 18:19:31 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35557@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
There is a new pull request by tibequadorian against master on the void-packages repository
https://github.com/tibequadorian/void-packages imagemagick
https://github.com/void-linux/void-packages/pull/35557
ImageMagick: update to 7.1.0.23.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/35557.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-imagemagick-35557.patch --]
[-- Type: text/x-diff, Size: 1083 bytes --]
From f0a74042311f21ac4f0ba10e5b0284b2547cf364 Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Sat, 12 Feb 2022 17:28:35 +0100
Subject: [PATCH] ImageMagick: update to 7.1.0.23.
---
srcpkgs/ImageMagick/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/ImageMagick/template b/srcpkgs/ImageMagick/template
index 1810efcaea22..7c0ea928209c 100644
--- a/srcpkgs/ImageMagick/template
+++ b/srcpkgs/ImageMagick/template
@@ -1,6 +1,6 @@
# Template file for 'ImageMagick'
pkgname=ImageMagick
-version=7.1.0.19
+version=7.1.0.23
revision=1
_majorver=${version%.*}
_patchver=${version##*.}
@@ -20,7 +20,7 @@ license="ImageMagick"
homepage="https://www.imagemagick.org"
changelog="https://imagemagick.org/script/changelog.php"
distfiles="https://github.com/ImageMagick/ImageMagick/archive/${_majorver}-${_patchver}.tar.gz"
-checksum=385ca5bd8ce9b37e685779c46868171af949265c9db40067c1c4d7442dbc723e
+checksum=62c24362891d0af2be9a81d01117195ba0ec8e6982c7568195a33019bfc82188
subpackages="libmagick libmagick-devel"
next reply other threads:[~2022-02-12 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 17:19 tibequadorian [this message]
2022-02-12 18:04 ` [PR PATCH] [Updated] " tibequadorian
2022-02-12 19:37 ` [PR PATCH] [Merged]: " paper42
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-35557@inbox.vuxu.org \
--to=tibequadorian@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).