From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] openexr: update to 3.1.7.
Date: Tue, 18 Apr 2023 13:06:11 +0200 [thread overview]
Message-ID: <20230418110611.HOn6DR8_DSPGuWLvQLWvN2P6kQ20UNQUQLo7b5f3U8k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43508@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages openexr-3.1.7
https://github.com/void-linux/void-packages/pull/43508
openexr: update to 3.1.7.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/43508.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-openexr-3.1.7-43508.patch --]
[-- Type: text/x-diff, Size: 1167 bytes --]
From c4a9d86cfb95ed34c3d16e94e9ae6e9f55074eba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Tue, 18 Apr 2023 12:04:00 +0100
Subject: [PATCH] openexr: update to 3.1.7.
---
srcpkgs/openexr/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/openexr/template b/srcpkgs/openexr/template
index 2c2b21b043b5..b15bfb736f72 100644
--- a/srcpkgs/openexr/template
+++ b/srcpkgs/openexr/template
@@ -1,7 +1,7 @@
# Template file for 'openexr'
pkgname=openexr
-version=3.1.5
-revision=2
+version=3.1.7
+revision=1
build_style=cmake
build_helper="qemu"
hostmakedepends="pkg-config"
@@ -12,7 +12,7 @@ license="BSD-3-Clause"
homepage="https://www.openexr.com/"
changelog="https://raw.githubusercontent.com/AcademySoftwareFoundation/openexr/main/CHANGES.md"
distfiles="https://github.com/openexr/openexr/archive/v${version}.tar.gz>openexr-${version}.tar.gz"
-checksum=93925805c1fc4f8162b35f0ae109c4a75344e6decae5a240afdfce25f8a433ec
+checksum=78dbca39115a1c526e6728588753955ee75fa7f5bb1a6e238bed5b6d66f91fd7
if [ "$XBPS_CHECK_PKGS" ]; then
configure_args+=" -DBUILD_TESTING=ON"
next prev parent reply other threads:[~2023-04-18 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 11:05 [PR PATCH] " motorto
2023-04-18 11:06 ` motorto [this message]
2023-04-30 2:22 ` [PR PATCH] [Merged]: " abenson
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=20230418110611.HOn6DR8_DSPGuWLvQLWvN2P6kQ20UNQUQLo7b5f3U8k@z \
--to=motorto@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).