HEADS UP: OpenEXR 3.X coming soon!

[Richard Shaw]

So I've spent about 40 hours pushing through build problems in the COPR[1]
I've set up beating what packages I could into submission and moving the
ones I couldn't (or shouldn't) port to the openexr2 compat package.

Some of the ones I didn't even try porting were packages that looked to be
legacy like the kde3/kde4 ones or packages on their 40th release with no
activity upstream. I don't want to update any package when it's unlikely or
impossible (dead upstream) that OpenEXR 3 will ever be supported officially.

Some packages only needed some build system updates because of the
restructuring of the libraries. Others needed just a little bit of porting
in the code.

With all that said, I'm down to one package/problem... Blender

The problem is not with Blender itself, but rather that it depends on
OpenVDB and I've already confirmed with upstream that OpenEXR 3 will not be
supported until the next major release. Ironically they are both under the
stewardship of the Academy Software Foundation (AWSF) so great coordination
there... :/

That being said, OpenSceneGraph wasn't ready either but it was relatively
easy to port after I figured out that the EXR plugin it builds doesn't
create a fatal error during the build when it fails (frustrating!)

Ok, and as usual, writing all of this has helped me work through porting
OpenVDB... I'll see about sending the patch upstream.

I'll probably create the side-tag tomorrow and start working on the builds.

Thanks,
Richard

[Zbigniew Jędrzejewski-Szmek]

On Mon, Jul 19, 2021 at 10:01:50PM -0500, Richard Shaw wrote:
>  So I've spent about 40 hours pushing through build problems in
> the COPR[1]
>  I've set up beating what packages I could into submission and moving the
>  ones I couldn't (or shouldn't) port to the openexr2 compat package.
>  
>  Some of the ones I didn't even try porting were packages that looked to be
>  legacy like the kde3/kde4 ones or packages on their 40th release with no
>  activity upstream. I don't want to update any package when it's unlikely or
>  impossible (dead upstream) that OpenEXR 3 will ever be supported officially.
>  
>  Some packages only needed some build system updates because of the
>  restructuring of the libraries. Others needed just a little bit of porting
>  in the code.
>  
>  With all that said, I'm down to one package/problem... Blender
>  
>  The problem is not with Blender itself, but rather that it depends on
>  OpenVDB and I've already confirmed with upstream that OpenEXR 3 will not be
>  supported until the next major release. Ironically they are both under the
>  stewardship of the Academy Software Foundation (AWSF) so great coordination
>  there... :/
>  
>  That being said, OpenSceneGraph wasn't ready either but it was relatively
>  easy to port after I figured out that the EXR plugin it builds doesn't
>  create a fatal error during the build when it fails (frustrating!)
>  
>  Ok, and as usual, writing all of this has helped me work through porting
>  OpenVDB... I'll see about sending the patch upstream.
>  
>  I'll probably create the side-tag tomorrow and start working on the builds. 
Thanks for working on this!

Zbyszek

[Fabio Valentini]

On Tue, Jul 20, 2021 at 5:02 AM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:
>  So I've spent about 40 hours pushing through build problems in the COPR[1] I've
> set up beating what packages I could into submission and moving the ones I couldn't
> (or shouldn't) port to the openexr2 compat package.
>
>  Some of the ones I didn't even try porting were packages that looked to be legacy
> like the kde3/kde4 ones or packages on their 40th release with no activity upstream. I
> don't want to update any package when it's unlikely or impossible (dead upstream)
> that OpenEXR 3 will ever be supported officially.
>
>  Some packages only needed some build system updates because of the restructuring of the
> libraries. Others needed just a little bit of porting in the code.
>
>  With all that said, I'm down to one package/problem... Blender
>
>  The problem is not with Blender itself, but rather that it depends on OpenVDB and
> I've already confirmed with upstream that OpenEXR 3 will not be supported until the
> next major release. Ironically they are both under the stewardship of the Academy Software
> Foundation (AWSF) so great coordination there... :/
>
>  That being said, OpenSceneGraph wasn't ready either but it was relatively easy to
> port after I figured out that the EXR plugin it builds doesn't create a fatal error
> during the build when it fails (frustrating!)
>
>  Ok, and as usual, writing all of this has helped me work through porting OpenVDB...
> I'll see about sending the patch upstream.
>
>  I'll probably create the side-tag tomorrow and start working on the builds. 
So ... just so you know, tomorrow might not be the best time to do
this, since that will collide with the mass rebuild for F35:
https://pagure.io/releng/issue/10219

If you have that option, I would wait with building all your things in
a side tag until the mass rebuild is done and the f35-rebuild side tag
has been merged to rawhide. Otherwise you'll have to account for
possible in-flight builds of your stuff ...

Fabio

[Richard Shaw]

On Tue, Jul 20, 2021 at 4:44 PM Fabio Valentini <decathorpe(a)gmail.com&gt;
wrote:

>  > I'll probably create the side-tag tomorrow and start working on the
>  builds.
>
>  So ... just so you know, tomorrow might not be the best time to do
>  this, since that will collide with the mass rebuild for F35:
>  https://pagure.io/releng/issue/10219
>
>  If you have that option, I would wait with building all your things in
>  a side tag until the mass rebuild is done and the f35-rebuild side tag
>  has been merged to rawhide. Otherwise you'll have to account for
>  possible in-flight builds of your stuff ...
>  
I've only done like two builds, so I could probably just throw them away..

I could also just push all the commits and hope the mass rebuild takes care
of them? :)

Thanks,
Richard

[Richard Shaw]

Current status:

aqsis - Move to openexr2
bcd - Moved to openexr2
blender - seems to be failing for Python related issue
calligra - Moved to openexr2, FTBFS for FontConfig reasons
CTL - Moved to openexr2
darktable -done
Field3D - done
freeimage - done
gegl04 - done
gimp
gmic - done
gstreamer1-plugins-bad-free
hugin - Trying to port to OpenEXR 3
ImageMagick
kdebase3 - Moved to openexr2
kdelibs - Moved to openexr2
kde-runtime - Moved to openexr2
kf5-kimageformats - Moved to openexr2
kio-extras - Done
krita
luminance-hdr - done
luxcorerender - done
opencv - done
OpenImageIO - done
OpenSceneGraph - Working on porting to OpenEXR 3
openshadinglanguage - Working on porting to OpenEXR 3
openvdb - done
pfstools - Move to openexr2
povray - FTBFS on ppc64le only for RPATH issue
prusa-slicer - Expects openvdb to use IlmBase::Half
synfig - done
vigra
vips - done
YafaRay - done

Thanks,
Richard

[Miro Hrončok]

On 05. 08. 21 19:01, Richard Shaw wrote:
>  prusa-slicer - Expects openvdb to use IlmBase::Half 
That one should be fixed.

-- 
Miro Hrončok
-- 
Phone: [phone]
IRC: mhroncok

[Richard Shaw]

On Thu, Aug 5, 2021 at 12:32 PM Miro Hrončok <mhroncok(a)redhat.com&gt; wrote:

>  On 05. 08. 21 19:01, Richard Shaw wrote:
>  > prusa-slicer - Expects openvdb to use IlmBase::Half
>
>  That one should be fixed.
>  
Could very well be that my notes are stale. Lots of moving parts to this
update :)

Thanks,
Richard

[Richard Shaw]

On Thu, Aug 5, 2021 at 12:37 PM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:

>  On Thu, Aug 5, 2021 at 12:32 PM Miro Hrončok
> <mhroncok(a)redhat.com&gt; wrote:
>
> > On 05. 08. 21 19:01, Richard Shaw wrote:
> > > prusa-slicer - Expects openvdb to use IlmBase::Half
> >
> > That one should be fixed.
> >
>
>  Could very well be that my notes are stale. Lots of moving parts to this
>  update :)
>  
Well kinda... The patch fixes building for rawhide but it fails on f34.
Doesn't look like the "fix" is backwards compatible...

Thanks,
Richard

[Miro Hrončok]

On 06. 08. 21 4:17, Richard Shaw wrote:
>  On Thu, Aug 5, 2021 at 12:37 PM Richard Shaw <hobbes1069(a)gmail.com
>
>  <mailto:[e-mail]>> wrote:
>  
>      On Thu, Aug 5, 2021 at 12:32 PM Miro Hrončok <mhroncok(a)redhat.com
>      <mailto:[e-mail]>> wrote:
>  
>          On 05. 08. 21 19:01, Richard Shaw wrote:
>           > prusa-slicer - Expects openvdb to use IlmBase::Half
>  
>          That one should be fixed.
>  
>  
>      Could very well be that my notes are stale. Lots of moving parts to this
>      update :)
>  
>  
>  Well kinda... The patch fixes building for rawhide but it fails on f34. Doesn't 
>  look like the "fix" is backwards compatible... 
The patch is only applied on F35+. It is not the best solution, but it is 
pragmatic.

-- 
Miro Hrončok
-- 
Phone: [phone]
IRC: mhroncok

[Richard Shaw]

On Fri, Aug 6, 2021 at 3:57 AM Miro Hrončok <mhroncok(a)redhat.com&gt; wrote:

>  On 06. 08. 21 4:17, Richard Shaw wrote:
>  > On Thu, Aug 5, 2021 at 12:37 PM Richard Shaw <hobbes1069(a)gmail.com
>  > <mailto:[e-mail]>> wrote:
>  >
>  >     On Thu, Aug 5, 2021 at 12:32 PM Miro Hrončok <mhroncok(a)redhat.com
>  >     <mailto:[e-mail]>> wrote:
>  >
>  >         On 05. 08. 21 19:01, Richard Shaw wrote:
>  >          > prusa-slicer - Expects openvdb to use IlmBase::Half
>  >
>  >         That one should be fixed.
>  >
>  >
>  >     Could very well be that my notes are stale. Lots of moving parts to
>  this
>  >     update :)
>  >
>  >
>  > Well kinda... The patch fixes building for rawhide but it fails on f34.
>  Doesn't
>  > look like the "fix" is backwards compatible...
>
>  The patch is only applied on F35+. It is not the best solution, but it is
>  pragmatic.
>  
Well an %if 0%{?fedora} > 34 fixed that, but there's a stranger issue I
still need to investigate as I've seen this in more than one package, but
specifically on prusa-slicer...

CMake detects Imath, has include and link commands during compilation (only
links with target sla_print_tests), but Imath isn't in the Requires of the
RPMs. It doesn't need OpenEXR anymore because OpenVDB doesn't need it, so
that part of the mystery is solved.

Here's a scratch build which hasn't finished but but I assume will show the
above:
https://kojipkgs.fedoraproject.org//work/tasks/5228/73385228/build.log

Similarly in openshadinglanguage (but slightly different) it detects both
OpenEXR 3 and Imath 3, it only links with Imath[1], but then Imath doesn't
end up in the Requires[2] of the RPMs.

Thanks,
Richard

[1]
https://kojipkgs.fedoraproject.org//packages/openshadinglanguage/1.11.14....
[2] https://koji.fedoraproject.org/koji/rpminfo?rpmID=27306586

[Ben Beasley]

This is just a note that luminance-hdr did move to openexr2, and will 
remain there for the foreseeable future—unless somebody writes a 
nontrivial patch for 3.x support, or the recently-absent upstream picks 
up development again. The curious may consult 
https://bugzilla.redhat.com/show_bug.cgi?id=1968167 for details.

– Ben Beasley

On 8/5/21 1:01 PM, Richard Shaw wrote:
> Current status:
> 
> aqsis - Move to openexr2
> bcd - Moved to openexr2
> blender - seems to be failing for Python related issue
> calligra - Moved to openexr2, FTBFS for FontConfig reasons
> CTL - Moved to openexr2
> darktable -done
> Field3D - done
> freeimage - done
> gegl04 - done
> gimp
> gmic - done
> gstreamer1-plugins-bad-free
> hugin - Trying to port to OpenEXR 3
> ImageMagick
> kdebase3 - Moved to openexr2
> kdelibs - Moved to openexr2
> kde-runtime - Moved to openexr2
> kf5-kimageformats - Moved to openexr2
> kio-extras - Done
> krita
> luminance-hdr - done
> luxcorerender - done
> opencv - done
> OpenImageIO - done
> OpenSceneGraph - Working on porting to OpenEXR 3
> openshadinglanguage - Working on porting to OpenEXR 3
> openvdb - done
> pfstools - Move to openexr2
> povray - FTBFS on ppc64le only for RPATH issue
> prusa-slicer - Expects openvdb to use IlmBase::Half
> synfig - done
> vigra
> vips - done
> YafaRay - done
> 
> Thanks,
> Richard
> 
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>

[Mamoru TASAKA]

Richard Shaw wrote on 2021/08/06 2:01:
>  Current status: 
>  blender - seems to be failing for Python related issue 
Already reported upstream:
https://developer.blender.org/T89931

Currently no active response so far.

Regards,
Mamoru