Description of problem: Wine depends on wine-capi which depends on isdn4k-utils that is no longer distributed with RHEL8 (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/considerations_in_adopting_rhel_8/changes-to-packages_considerations-in-adopting-rhel-8#removed-packages_changes-to-packages) Version-Release number of selected component (if applicable): wine-capi-4.0.2-1.el8.x86_64 wine-4.0.2-1.el8.x86_64 How reproducible: Enable RHEL 8 repos (appstream & baseos) and codeready-builder one also for SDL2. Steps to Reproduce: 1. dnf install wine Actual results: Problème: package wine-4.0.2-1.el8.x86_64 requires wine-capi(x86-64) = 4.0.2-1.el8, but none of the providers can be installed - conflicting requests - nothing provides isdn4k-utils(x86-64) needed by wine-capi-4.0.2-1.el8.x86_64 Expected results: Having wine installed. Additional info: I tried to install isdn4k-utils RPM packages from https://dl.fedoraproject.org/pub/fedora/linux/releases/30/Everything/x86_64/os/Packages/i/ But it needs additional deps (libgcrypt.so.2, libm.so.6) then I aborted. Regards,
FEDORA-EPEL-2019-b45c7e9299 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b45c7e9299
wine-4.0.2-2.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b45c7e9299
wine-4.0.3-1.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b45c7e9299
wine-4.0.3-1.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.