From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: openexr3.0 update
Date: Mon, 09 Jan 2023 15:31:12 +0100 [thread overview]
Message-ID: <20230109143112.LFhRdZkQmNqIML3Rhvn4OAkKeLGekVcHinQSYcMW_js@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39852@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
There's a merged pull request on the void-packages repository
openexr3.0 update
https://github.com/void-linux/void-packages/pull/39852
Description:
[ci-skip] [ci skip]
# TODO:
- **Review**. (If someone could do a rebuild of everything changed here would be highly appreciated, I am currently
leaving my laptop overnight compiling everything with xxbuild for a specific arch, see below what I have already tested, getting some crossbuilding testing would be nice)
## New Templates
- robin-map 1.0.1
- pystring 1.1.3
## Changed Templates:
- alembic 1.7.16 --> 1.8.3 (adopt)
- ilmbase --> imath 3.1.5
- openexr 2.4.1 --> 3.1.5 (adopt)
- gmic 2.9.9 --> 3.1.6
- opencolorio 1.1.1 --> 2.1.2
- openimageio 2.2.15.1 --> 2.3.18.0.
## Revbumped (xrevshlib)
- Field3D
- ImageMagick
- PrusaSlicer
- blender
- calligra
- darktable
- gimp
- hugin
- kimageformats
- kio-extras
- krita
- libgdal
- opencv
- openvdb
- osg
- synfig
- synfigstudio
- vigra
- vips
## Local build testing
- x86_64 (native)
- x86_64-musl (native)
- i686 (native)
- armv6l (cross)
<!--
- armv7l-musl (crossbuilding)
- armv7l (crossbuilding)
- armv6l-musl (crossbuilding)
- armv6l (crossbuilding)
-->
next prev parent reply other threads:[~2023-01-09 14:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 21:45 [PR PATCH] New package: imath-3.1.5 motorto
2022-10-09 22:03 ` [PR PATCH] [Updated] " motorto
2022-10-15 11:46 ` motorto
2022-10-15 17:31 ` motorto
2022-10-15 17:39 ` [PR PATCH] [Updated] openexr3.0 update motorto
2022-10-16 13:38 ` motorto
2022-10-16 13:43 ` lemmi
2022-10-16 15:37 ` Johnnynator
2022-10-16 15:37 ` Johnnynator
2022-10-16 19:51 ` [PR PATCH] [Updated] " motorto
2022-10-16 20:19 ` motorto
2022-10-16 20:38 ` motorto
2022-10-16 21:05 ` motorto
2022-10-16 21:06 ` motorto
2022-10-16 21:15 ` motorto
2022-10-16 22:16 ` motorto
2022-10-17 8:42 ` motorto
2022-10-17 12:40 ` motorto
2022-10-17 21:49 ` motorto
2022-10-17 21:58 ` motorto
2022-10-17 22:01 ` motorto
2022-10-18 14:40 ` motorto
2022-10-18 14:44 ` motorto
2022-10-23 11:45 ` [PR PATCH] [Updated] " motorto
2022-10-24 13:34 ` motorto
2022-10-26 8:45 ` motorto
2022-11-02 11:21 ` motorto
2022-11-02 11:26 ` motorto
2022-11-03 8:47 ` motorto
2022-11-04 12:20 ` motorto
2022-11-05 21:54 ` motorto
2022-11-18 8:30 ` motorto
2022-11-18 9:35 ` motorto
2022-11-19 15:29 ` motorto
2022-11-20 10:50 ` motorto
2022-11-20 10:53 ` motorto
2022-11-20 10:54 ` motorto
2022-11-23 8:39 ` motorto
2022-12-23 0:43 ` motorto
2022-12-24 13:22 ` motorto
2022-12-24 13:25 ` motorto
2022-12-25 18:40 ` [PR PATCH] [Updated] " motorto
2022-12-25 18:46 ` motorto
2022-12-25 18:49 ` motorto
2023-01-02 14:05 ` motorto
2023-01-07 14:22 ` motorto
2023-01-07 14:27 ` motorto
2023-01-09 12:07 ` Johnnynator
2023-01-09 12:07 ` Johnnynator
2023-01-09 12:45 ` [PR PATCH] [Updated] " Johnnynator
2023-01-09 14:31 ` Johnnynator [this message]
2023-01-09 15:39 ` 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=20230109143112.LFhRdZkQmNqIML3Rhvn4OAkKeLGekVcHinQSYcMW_js@z \
--to=johnnynator@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).