Due to the upcoming unslotted OpenEXR stabilisation, this will lead to conflicts for most luminance-hdr users. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1968167
I was considering trying this but seeing the Fedora maintainer declare it was too difficult has put me off. I don't think I have any real motivation to do it and ideally someone who uses this software can look into it.
Archlinux patch makes it seem easy: https://github.com/archlinux/svntogit-community/blob/packages/luminancehdr/trunk/luminancehdr-openexr3.patch Maybe we can get that working together with a spanking fresh version bump?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f183705a78237d697d57279c392fe4afb27b9ae3 commit f183705a78237d697d57279c392fe4afb27b9ae3 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2022-02-25 20:52:56 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2022-02-25 20:53:15 +0000 media-gfx/luminance-hdr: Version bump, for un-slotted OpenEXR 3 Bug: https://bugs.gentoo.org/833486 Bug: https://bugs.gentoo.org/833487 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> media-gfx/luminance-hdr/Manifest | 1 + .../files/luminance-hdr-2.6.1.1-fixheaders.patch | 15 ++++ .../files/luminance-hdr-2.6.1.1-openexr3.patch | 28 ++++++ .../luminance-hdr/luminance-hdr-2.6.1.1.ebuild | 100 +++++++++++++++++++++ 4 files changed, 144 insertions(+)
I guess we can consider this fixed then.
