Github messages for voidlinux
 help / color / mirror / Atom feed
From: unspecd <>
Subject: [PR PATCH] ImageMagick: update to
Date: Wed, 12 Jan 2022 01:40:38 +0100	[thread overview]
Message-ID: <> (raw)

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

There is a new pull request by unspecd against master on the void-packages repository pkg/ImageMagick

ImageMagick: update to
<!-- 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 [quality requirements]( **YES**|**NO**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](
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-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - ppc64le-musl

A patch file from is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pkg/ImageMagick-35008.patch --]
[-- Type: text/x-diff, Size: 1087 bytes --]

From 3aa89ee52e4a3154b0b9c8dc3ed437a919ccf3ca Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <>
Date: Wed, 29 Dec 2021 08:53:22 +1100
Subject: [PATCH] ImageMagick: update to

 srcpkgs/ImageMagick/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/ImageMagick/template b/srcpkgs/ImageMagick/template
index 356015153e80..1810efcaea22 100644
--- a/srcpkgs/ImageMagick/template
+++ b/srcpkgs/ImageMagick/template
@@ -1,6 +1,6 @@
 # Template file for 'ImageMagick'
@@ -20,7 +20,7 @@ license="ImageMagick"
 subpackages="libmagick libmagick-devel"

             reply	other threads:[~2022-01-12  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  0:40 unspecd [this message]
2022-01-20  1:03 ` [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).