Description of problem: zlib-ng ships a CMake package configuration file, but it is not usable due to having the wrong name (`zlib-ng.cmake` should be `zlib-ng-config.cmake`). Version-Release number of selected component (if applicable): zlib-ng-devel-2.1.6-5.fc40.x86_64 How reproducible: Always Steps to Reproduce: 1. Call find_package(zlib-ng) from a CMake project Actual results: CMake can't find zlib-ng because no zlib-ng-config.cmake exists. Expected results: CMake finds zlib-ng with zlib-ng_DIR=/usr/lib64/cmake/zlib-ng. Additional info: Not sure if this is upstream or a packaging issue, but it can be easily fixed by either renaming `zlib-ng.cmake` or providing a symlink `zlib-ng-config.cmake -> zlib-ng.cmake`.
This as already been fixed upstream in zlib-ng 2.1.7: https://github.com/zlib-ng/zlib-ng/pull/1647 There is a PR created for Rawhide here: https://src.fedoraproject.org/rpms/zlib-ng/pull-request/20 My goal is to distribute this version in F40 after some testing in Rawhide.
FEDORA-2024-c11bae3c39 (zlib-ng-2.1.7-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c11bae3c39
FEDORA-2024-c11bae3c39 (zlib-ng-2.1.7-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-865a0061ad (zlib-ng-2.1.7-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-865a0061ad
FEDORA-2024-865a0061ad has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-865a0061ad` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-865a0061ad See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-865a0061ad (zlib-ng-2.1.7-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.