Bug 2323307

I took a quick look at this, 12.0.0 introduces a new dependency (https://github.com/wjakob/nanobind) that will need to be packaged to keep the Python bindings building. If the bindings are disabled it builds and installs out of the box: https://koji.fedoraproject.org/koji/taskinfo?taskID=127025952

Put up https://src.fedoraproject.org/rpms/openvdb/pull-request/7 in the meantime to clean up the spec a bit in preparation for a potential update down the road

Releases retrieved: 12.0.1
Upstream release that is considered latest: 12.0.1
Current version/release in rawhide: 11.0.0-19.fc42
URL: https://www.openvdb.org

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/21124/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/openvdb

@luya_tfz

It looks like you built this in Rawhide, with an unannounced SONAME version bump. This is contrary to the Updates Policy[1], and it’s disruptive because all of the dependent packages now suddenly fail to install.

- When a proposed update contains an ABI or API change: notify a week in advance both the devel list and maintainers directly (using the packagename-maintainers alias) whose packages depend on yours to rebuild or offer to do these rebuilds for them.

- Use a side-tag when dealing with mass builds of many packages, so they can land at the same time.

If you haven’t had a chance to rebuild dependent packages in Rawhide by tomorrow, I’ll try to find time to take care of it.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide

openvdb -> OpenImageIO
openvdb -> blender
openvdb -> luxcorerender
openvdb -> openvkl
openvdb -> usd

OpenImageIO -> blender
OpenImageIO -> luxcorerender
OpenImageIO -> usd

blender -> luxcorerender

usd -> blender

Therefore, it looks like a workable chain-build order would be:

OpenImageIO openvkl : usd : blender : luxcorerender

…assuming there are no incompatibilities with the new openvdb.

My bad. I have completely overlooked the use of side tag for Rawhide. I was able to setup a side tag "f43-build-side-109550" and moved version 12.0.1 to that target. It is matter of "fedpkg build --target=f43-build-side-109550" as checking "koji wait-repo f43-build-side-109550". I ran out of time to do the remaining task so feel free to do so.

I’ll start the rebuilds. As the creator of the side tag, you’ll need to be the one to create the Bodhi update when they finish.

Rebuilds are in progress (using "fedpkg chain-build") in task 131230550, https://koji.fedoraproject.org/koji/taskinfo?taskID=131230550. I tried the first few locally to look for glaring API incompatibilities, but didn’t go past usd. Assuming all goes well, the builds will probably take a few hours to finish since the packages are large and the builds need to be mostly sequential.

@luya_tfz

The rebuilds are done. Please make a Bodhi update from the side tag, and associate the following bugs: 2323307,2357833,2357829,2357831,2357828,2357830,2357799. Thanks!

FEDORA-2025-9433cb2de7 (blender-4.4.0-5.fc43, luxcorerender-2.7-0.30.beta1.fc43, and 5 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-9433cb2de7

All done.

Thank you!

FEDORA-2025-9433cb2de7 (blender-4.4.0-5.fc43, luxcorerender-2.7-0.30.beta1.fc43, and 5 more) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.