First try it in COPR and make sure that everything will *actually*
rebuild successfully with the updated OpenColorIO.
Then follow the process in
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide for
ABI or API breaking updates: “When a proposed update contains an ABI or
API change: notify a week in advance both the devel list and maintainers
directly (using the [email protected] alias)
whose packages depend on yours to rebuild or offer to do these rebuilds
for them.”
Everything needs to be rebuilt in a side tag,
https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/, which
you can accomplish either by coordinating with the maintainers of
dependent packages or by enlisting the help of a provenpackager. (I
might be willing, but only for an update that’s been properly tested and
coordinated.) The following order should work with "fedpkg chain-build",
or in COPR: OpenColorIO : OpenImageIO OpenImageIO2.5 krita : olive usd :
blender : luxcorerender.
In any case, an ABI-breaking update will only be a candidate for Rawhide
and (after branching, before Final Freeze) Fedora 44.
Finally, please do keep listening to and engaging with Richard Shaw, who
is the maintainer of the OpenColorIO package in Fedora. Most of the work
of an update like this is not just uploading the sources, it’s
impact-checking and coordination.
On 04/02/2026 7:40 pm, Bartosz Kosiorek via devel wrote:
Thanks,
How I could rebuild all dependencies?
Should I build OpenColorIO first, and then create PRs for dependencies?
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
