It seems packages in Fedora 40 changed and prusa-slicer-2.7.4-1.fc40 no longer builds in Fedora 40. Reproducible: Always Steps to Reproduce: 1. git clone -b f40 https://src.fedoraproject.org/rpms/prusa-slicer/ 2. cd prusa-slicer/ 3. fedpkg scratch-build Actual Results: Building prusa-slicer-2.7.4-1.fc40 for f40-candidate Created task: 120198141 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=120198141 Watching tasks (this may be safely interrupted)... 120198141 build (f40-candidate, /rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796): free 120198141 build (f40-candidate, /rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796): free -> open (buildvm-a64-34.iad2.fedoraproject.org) 120198167 buildSRPMFromSCM (/rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796): free 120198167 buildSRPMFromSCM (/rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796): free -> open (buildvm-x86-05.iad2.fedoraproject.org) 120198235 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, ppc64le): open (buildvm-ppc64le-25.iad2.fedoraproject.org) 120198234 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, aarch64): open (buildhw-a64-06.iad2.fedoraproject.org) 120198236 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, s390x): open (buildvm-s390x-04.s390.fedoraproject.org) 120198233 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, x86_64): open (buildhw-x86-11.iad2.fedoraproject.org) 120198167 buildSRPMFromSCM (/rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796): open (buildvm-x86-05.iad2.fedoraproject.org) -> closed 0 free 5 open 1 done 0 failed 120198234 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, aarch64): open (buildhw-a64-06.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch aarch64), mock exited with status 30; see root.log for more information 0 free 4 open 1 done 1 failed 120198236 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, s390x): open (buildvm-s390x-04.s390.fedoraproject.org) -> FAILED: BuildError: error building package (arch s390x), mock exited with status 30; see root.log for more information 0 free 3 open 1 done 2 failed 120198233 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, x86_64): open (buildhw-x86-11.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch x86_64), mock exited with status 30; see root.log for more information 0 free 2 open 1 done 3 failed 120198141 build (f40-candidate, /rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796): open (buildvm-a64-34.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch x86_64), mock exited with status 30; see root.log for more information 0 free 1 open 1 done 4 failed 120198235 buildArch (prusa-slicer-2.7.4-1.fc40.src.rpm, ppc64le): open (buildvm-ppc64le-25.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch ppc64le), mock exited with status 30; see root.log for more information 0 free 0 open 1 done 5 failed 120198141 build (f40-candidate, /rpms/prusa-slicer.git:f4c6c15266ee6e33a8a1c20719bf2ce2a0784796) failed Expected Results: No failure. https://kojipkgs.fedoraproject.org//work/tasks/8233/120198233/root.log from https://koji.fedoraproject.org/koji/taskinfo?taskID=120198233 says DEBUG util.py:463: Repositories loaded. DEBUG util.py:461: Failed to resolve the transaction: DEBUG util.py:461: Problem: package tbb2020.3-devel-2020.3-4.fc40.x86_64 conflicts with tbb-devel provided by tbb-devel-2021.11.0-5.fc40.x86_64 DEBUG util.py:461: - package openvdb-devel-11.0.0-11.fc40.x86_64 requires cmake(tbb) = 2020.3, but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:610: Child return code was: 1
Looking at logs in https://koji.fedoraproject.org/koji/buildinfo?buildID=2439979, the last passing build in Fedora 40, it installed in build time tbb-devel-2021.11.0-5.fc40 tbb-2021.11.0-5.fc40 tbb2020.3-2020.3-4.fc40 Now it seems tbb2020.3-devel is (also) being pulled into the transaction.
It seems the regression was caused by https://src.fedoraproject.org/rpms/openvdb/c/32378e69f3ed145614173ea224aeec9e578eee51?branch=f40 change in openvdb. Luya, would you have a recommendation how to deal with the situation when some packages (in this case opencascade-devel) require tbb-devel, and openvdb-devel not requires a conflicting tbb2020.3-devel?
Fedora rawhide has the same problem: https://koji.fedoraproject.org/koji/taskinfo?taskID=120200716 -> https://kojipkgs.fedoraproject.org//work/tasks/716/120200716/root.log: DEBUG util.py:461: Failed to resolve the transaction: DEBUG util.py:461: Problem: package tbb2020.3-devel-2020.3-4.fc40.x86_64 from build conflicts with tbb-devel provided by tbb-devel-2021.11.0-6.fc41.x86_64 from build DEBUG util.py:461: - package openvdb-devel-11.0.0-12.fc41.x86_64 from build requires cmake(tbb) = 2020.3, but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:610: Child return code was: 1
(In reply to Jan Pazdziora from comment #2) > and openvdb-devel not requires a conflicting tbb2020.3-devel? and openvdb-devel *now* requires a conflicting tbb2020.3-devel? Sorry for the typo.
(In reply to Jan Pazdziora from comment #2) > It seems the regression was caused by > https://src.fedoraproject.org/rpms/openvdb/c/ > 32378e69f3ed145614173ea224aeec9e578eee51?branch=f40 change in openvdb. > > Luya, would you have a recommendation how to deal with the situation when > some packages (in this case opencascade-devel) require tbb-devel, and > openvdb-devel not requires a conflicting tbb2020.3-devel? In this case, affected package will need to rebuild for tbb2020.3 for the time being as some applications i.e. Blender have yet to get ported to the newer version of tbb. See https://vfxplatform.com/
So I wonder -- how important is it to be strict about that 2020.3? Could the https://src.fedoraproject.org/rpms/openvdb/c/32378e69f3ed145614173ea224aeec9e578eee51?branch=f40 be changed to some "or" boolean dependency, to allow either version to be used by the end user? Note that tbb and tbb2020.3 can be installed in parallel (and already do, for prusa-slicer), it's "just" the -devel packages that now have the conflict, due to the cmake(tbb) = 2020.3 build dependency ...
(In reply to Jan Pazdziora from comment #6) > So I wonder -- how important is it to be strict about that 2020.3? Could the > https://src.fedoraproject.org/rpms/openvdb/c/ > 32378e69f3ed145614173ea224aeec9e578eee51?branch=f40 be changed to some "or" > boolean dependency, to allow either version to be used by the end user? Something like "BuildRequires: cmake(tbb) >= 2020.3"?
No, we need Requires changed -- the problem is when openvdb-devel is used to build other packages, not when it itself is built.
Here is the commit and see if it is correct: https://src.fedoraproject.org/rpms/openvdb/c/58fe5e75a34b9af173d4a0380601f9fcbfae9af2?branch=rawhide
Looks good to me, thanks.
FEDORA-2024-1369eb0389 (openvdb-11.0.0-13.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-1369eb0389
FEDORA-2024-1369eb0389 (openvdb-11.0.0-13.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
Update is pending Fedoar 40: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c6deaf0ef0
For the record, this change makes the build dependencies of prusa-slicer work again but the tests then segfault, tracked in bug 2301103.