From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] openexr: update to 3.2.126.
Date: Sun, 25 Feb 2024 19:17:08 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48937@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages openexr-3.2.126
https://github.com/void-linux/void-packages/pull/48937
openexr: update to 3.2.126.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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/48937.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-openexr-3.2.126-48937.patch --]
[-- Type: text/x-diff, Size: 1129 bytes --]
From 466f47d75878e6266ca9d39da688fc80496dff64 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sun, 25 Feb 2024 17:16:56 +0000
Subject: [PATCH] openexr: update to 3.2.126.
---
srcpkgs/openexr/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/openexr/template b/srcpkgs/openexr/template
index b0a816d838bbb..ccdd30fbd1ad3 100644
--- a/srcpkgs/openexr/template
+++ b/srcpkgs/openexr/template
@@ -1,6 +1,6 @@
# Template file for 'openexr'
pkgname=openexr
-version=3.2.1
+version=3.2.126
revision=1
build_style=cmake
build_helper="qemu"
@@ -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=61e175aa2203399fb3c8c2288752fbea3c2637680d50b6e306ea5f8ffdd46a9b
+checksum=51e2bc9d27f53280d3e57cf89a28b8ec4dbc81b124f869a0ca9b9b9dd0316f22
if [ "$XBPS_CHECK_PKGS" ]; then
configure_args+=" -DBUILD_TESTING=ON"
next reply other threads:[~2024-02-25 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 18:17 motorto [this message]
2024-02-25 18:43 ` [PR PATCH] [Updated] " motorto
2024-02-25 19:03 ` [PR PATCH] [Closed]: " motorto
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-48937@inbox.vuxu.org \
--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).