This bug is used to track the readiness of ipmiutil with OpenSSL 3.0.0. Currently the build fails to build with OpenSSL 3.0.0 with the following logs Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=78020195 Kindly fix them to ensure this package builds with OpenSSL 3.0.0 You can treat the deprecated warnings not as errors if you want to continue to use deprecated functions, but it is encouraged to use the new APIs, and this migration could be done sooner than later. To not treat deprecated warnings as errors, you may use -Wno-error=deprecated-declarations To port to new APIs, kindly refer to the OpenSSL upstream migration guide: https://www.openssl.org/docs/manmaster/man7/migration_guide.html Thank you
Added detection of OpenSSL 3.x in ipmiutil-3.1.8, and it builds now. See https://sourceforge.net/projects/ipmiutil/files/ipmiutil-3.1.8.tar.gz/download
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
ipmiutil 3.1.8 advertises some OpenSSL 3 fixes in its changelog (I have not tried it).
This is fixed in ipmiutil versions 3.1.8 and greater. The ipmiutil-3.1.9 release has been applied to Fedora rawhide and built in f37. https://koji.fedoraproject.org/koji/buildinfo?buildID=2178545
FEDORA-2023-339590718b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-339590718b
FEDORA-2023-339590718b has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-339590718b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-339590718b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-339590718b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.