LibRaw was recently rebased to 0.21.1 in CentOS Stream 9 aimed at RHEL 9.4: https://issues.redhat.com/browse/RHEL-768 This alters the sonames exported by LibRaw, and therefore OpenImageIO needs to be rebuilt against the new sonames. To fix this for CentOS Stream 9 users, before RHEL 9.4 is released, we need an epel9-next branch for OpenImageIO: https://docs.fedoraproject.org/en-US/epel/epel-about-next/
Friendly ping, this blocks CentOS Stream 9 users with this package installed from fully updating their systems, or installing other packages that link against the latest LibRaw. If a maintainer can request the epel9-next branch, I can complete the necessary rebuild. A scratch build based on the epel9 branch completed successfully. https://koji.fedoraproject.org/koji/taskinfo?taskID=109379868
FEDORA-EPEL-2023-639e141f60 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-639e141f60
Thanks for the reminder. Update submitted.
FEDORA-EPEL-2023-639e141f60 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-639e141f60 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This update installs fine on RHEL, but doesn't resolve the issue in this bug. It is simple to reproduce on CentOS Stream 9. dnf install OpenImageIO dnf update Error: Problem: package OpenImageIO-2.4.17.0-1.el9.x86_64 from @System requires libraw_r.so.20()(64bit), but none of the providers can be installed - cannot install both LibRaw-0.21.1-1.el9.x86_64 from appstream and LibRaw-0.20.2-6.el9.x86_64 from @System - cannot install both LibRaw-0.21.1-1.el9.x86_64 from appstream and LibRaw-0.20.2-4.el9.x86_64 from appstream - cannot install both LibRaw-0.21.1-1.el9.x86_64 from appstream and LibRaw-0.20.2-5.el9.x86_64 from appstream - cannot install both LibRaw-0.21.1-1.el9.x86_64 from appstream and LibRaw-0.20.2-6.el9.x86_64 from appstream - cannot install the best update candidate for package OpenImageIO-2.4.17.0-1.el9.x86_64 - cannot install the best update candidate for package LibRaw-0.20.2-6.el9.x86_64 An epel9-next branch must be requested so that an EPEL 9 Next build can be created that properly links against libraw_r.so.23. Please run the following commands from within the cloned dist-git repo: fedpkg request-branch epel9-next (wait a few minutes for the branch to be created) git fetch git switch epel9-next git merge epel9 git push fedpkg build fedpkg update --type bugfix --notes "Rebuilt for LibRaw soname change" --bugs 2245057 This will give us separate OpenImageIO-2.4.17.0-1.el9 and OpenImageIO-2.4.17.0-1.el9.next builds, for RHEL and CentOS respectively. When that LibRaw change lands in RHEL 9.4, the epel9 branch can have the release bumped to 2, which will be a proper upgrade path for both RHEL and CentOS users.
(In reply to Carl George 🤠 from comment #5) > This update installs fine on RHEL, but doesn't resolve the issue in this > bug. It is simple to reproduce on CentOS Stream 9. Thanks for the testing, Carl! Reopening.
FEDORA-EPEL-2023-639e141f60 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
Posting the new error would help as I don't know why a rebuild wouldn't fix it.
(In reply to Richard Shaw from comment #8) > Posting the new error would help as I don't know why a rebuild wouldn't fix > it. Please, see comment 5. Carl already explained it. OpenImageIO needs a epel9-next, and that's where it should be rebuilt against the LibRaw that's in CentOS Stream 9.
> Posting the new error would help as I don't know why a rebuild wouldn't fix it. The new build was built against RHEL 9 and libraw_r.so.20 (LibRaw-0.20.2-6.el9). CentOS Stream 9 now has libraw_r.so.23 (LibRaw-0.21.1-1.el9). It is planned for RHEL 9 to get libraw_r.so.23 next year. Normally packages built against RHEL work on both RHEL and CentOS, however in situations like this where a library soname is different for a period of time, maintainers need to do an additional build in EPEL Next. This is explained in further detail in the EPEL Next documentation. https://docs.fedoraproject.org/en-US/epel/epel-about-next/ As a proven packager, I can resolve this for you, I just can't request the epel9-next branch because I'm not a maintainer of the package. If you run `fedpkg request-branch epel9-next`, I'll take care of the rest. Alternatively, if you give the epel-packagers-sig group commit or collaborator access to the package, that will allow me to request the branch myself.
I've added epel-packagers-sig as a collaborator to epel* and requested the branch, see: https://pagure.io/releng/fedora-scm-requests/issue/58580
FEDORA-EPEL-NEXT-2023-9fb0826d21 has been submitted as an update to Fedora EPEL 9 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2023-9fb0826d21
FEDORA-EPEL-NEXT-2023-9fb0826d21 has been pushed to the Fedora EPEL 9 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2023-9fb0826d21 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2023-9fb0826d21 has been pushed to the Fedora EPEL 9 Next stable repository. If problem still persists, please make note of it in this bug report.