Description of problem: It appears that ceres-solver-devel embeds the Eigen3 version at build time, and complains if a different version is present when downstream packages attempt to compile against ceres-solver. Version-Release number of selected component (if applicable): 1.12.0-4.el7 How reproducible: 100% Steps to Reproduce: 1. In cmake, find_package(Ceres REQUIRED) Actual results: CMake Error at /usr/lib64/cmake/Ceres/CeresConfig.cmake:88 (message): Failed to find Ceres - Found Eigen dependency, but the version of Eigen found (3.3.7) does not exactly match the version of Eigen Ceres was compiled with (3.3.4). This can cause subtle bugs by triggering violations of the One Definition Rule. See the Wikipedia article http://en.wikipedia.org/wiki/One_Definition_Rule for more details Expected results: Ceres is found and is usable.
My bad. I set up a buildroot override for eigen-3.3.7 and built 1.12.0-3, but the -4 build with the suitesparse updates happened before eigen3 and -3 landed in stable. Rebuilding now.
FEDORA-EPEL-2020-8acc2111eb has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-8acc2111eb
FEDORA-EPEL-2020-8acc2111eb has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-8acc2111eb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-8acc2111eb has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.