Note that prusa-slicer-2.3.1 update received some negative karma and I did not intend to push it stable until this is fixed. Not sure what to do here, but backward-incompatible updates that need rebuilds are generally not permitted on stable Fedora releases. I'll try to rebuild the 2.2.0 release with this and replace it here.
Adding negative karma, for now, to avoid accidental autopush.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
For some reason this popped up today, even though I checked updates-testing in last few days:
Problem 1: package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- cannot install the best update candidate for package usd-libs-21.05-3.fc34.x86_64
- cannot install the best update candidate for package openvdb-libs-8.0.1-2.fc34.x86_64
Problem 2: problem with installed package usd-libs-21.05-3.fc34.x86_64
- package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- package openvdb-8.2.0-1.fc34.x86_64 requires libopenvdb.so.8.2()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package openvdb-8.0.1-2.fc34.x86_64
Problems without updates-testing:
Problem 1: package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- cannot install the best update candidate for package usd-libs-21.05-3.fc34.x86_64
- cannot install the best update candidate for package openvdb-libs-8.0.1-2.fc34.x86_64
Problem 2: problem with installed package usd-libs-21.05-3.fc34.x86_64
- package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- package OpenImageIO-2.2.19.0-2.fc34.x86_64 requires libopenvdb.so.8.2()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package OpenImageIO-2.2.19.0-1.fc34.x86_64
It’s too late now, but this update included an ABI/soversion break in OpenVDB—which happens with every minor version. See https://bugzilla.redhat.com/show_bug.cgi?id=2031326. A rebuild of USD is probably the only path forward.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted prusa-slicer-2.3.1-1.fc34, and has inherited its bugs and notes.
This update has been submitted for testing by bodhi.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Note that prusa-slicer-2.3.1 update received some negative karma and I did not intend to push it stable until this is fixed. Not sure what to do here, but backward-incompatible updates that need rebuilds are generally not permitted on stable Fedora releases. I'll try to rebuild the 2.2.0 release with this and replace it here.
Adding negative karma, for now, to avoid accidental autopush.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
churchyard edited this update.
churchyard edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by churchyard.
churchyard edited this update.
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
For some reason this popped up today, even though I checked updates-testing in last few days:
Problems without updates-testing:
I removed
usd-libsby updating with--allowerasingsince it's been installed in September with a blender update.It’s too late now, but this update included an ABI/soversion break in OpenVDB—which happens with every minor version. See https://bugzilla.redhat.com/show_bug.cgi?id=2031326. A rebuild of USD is probably the only path forward.