it has been recently proposed to switch openSUSE to run ldconfig via a
%transfiletriggerin/-un scriptlet instead of manually in %post & %postun
the same way as Fedora does it at the moment.
However, an interesting issue has been raised: what happens if package A
gets upgraded in the same transaction as package B, but B needs A during
the upgrade. A will install a new shared library, but ldconfig will run
after B has already tried to upgrade.
Do we have some mechanism to prevent this? Or does this essentially
never happen in practice?
The only "workaround" that came up was to use ordinary file triggers,
but that is not a great idea either these would fire way too frequently
(as mentioned by Florian Weimer on this list in 2018: ).
OIIO 2.3 has been released with a soname bump. My plan is to build for
rawhide/f35. f33/34 will only receive bugfix releases of the 2.2 series.
The list of affected packages is pretty short:
I will also include OCIO 2.1 for f35 (already built for rawhide).