From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Imath 3.1.9 + Openexr 3.1.9.
Date: Sun, 02 Jul 2023 22:56:00 +0200 [thread overview]
Message-ID: <20230702205600.RFrmOt0yTthtxWYvPIq4FI7CXRcEgpOQUWAiU054vEs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44300@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
There's a merged pull request on the void-packages repository
Imath 3.1.9 + Openexr 3.1.9.
https://github.com/void-linux/void-packages/pull/44300
Description:
[ci-skip] [ci skip]
<!-- Uncomment relevant sections and delete options which are not applicable -->
# 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)
## Local build testing
- x86_64 (native)
<!--
- x86_64-musl (native)
- i686 (native)
- armv6l (crossbuilding)
- armv7l-musl (crossbuilding)
- armv7l (crossbuilding)
- armv6l-musl (crossbuilding)
- armv6l (crossbuilding)
-->
#### Testing the changes
- I tested the changes in this PR: **briefly**, as in didn't test some package that were revbumped.
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
Previously closed the imath 3.1.8 update because of the changed shlib and the high number of packages that would need to be revbumped. Waited for openexr to release a new version and re-opened this.
prev parent reply other threads:[~2023-07-02 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 16:58 [PR PATCH] Imath 3.1.9 + Openexr 3.1.8 motorto
2023-06-28 14:45 ` [PR PATCH] [Updated] " motorto
2023-06-28 14:48 ` Imath 3.1.9 + Openexr 3.1.9 motorto
2023-06-28 14:49 ` motorto
2023-06-29 22:41 ` Johnnynator
2023-06-30 7:43 ` motorto
2023-07-02 20:56 ` Johnnynator [this message]
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=20230702205600.RFrmOt0yTthtxWYvPIq4FI7CXRcEgpOQUWAiU054vEs@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).