Description of problem: Unable to install hwinfo through the EPEL8 repository at the moment. Looking at the build root log, it was build against the previous version of libx86emu (1.11-10), instead of the latest version 3.5-1. Libx86emu 3.5-1 has libx86emu.so.3()(64-bit), instead of libx86emu.so.1()(64bit), so package install will fail with a 'conflicting requests' error. Version-Release number of selected component (if applicable): hwinfo-21.80-2.el8 How reproducible: each time Steps to Reproduce: dnf install hwinfo Updating Subscription Management repositories. Last metadata expiration check: 0:57:07 ago on Mon 04 Apr 2022 01:36:41 PM CEST. Error: Problem: conflicting requests - nothing provides libx86emu.so.1()(64bit) needed by hwinfo-21.80-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Actual results: unable to install hwinfo package Expected results: hwinfo package install without error Additional info:
FEDORA-EPEL-2022-9abf798346 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9abf798346
This was caused by an unannounced soname increase in libx86emu-3.5-1.el8 [0]. That kind of update is not normally allowed by EPEL policy [1]. The maintainer should have followed the incompatible upgrades policy [2]. It looks like hwinfo is the only affected package, and the damage is already done, so rather than reverting this update I've forced a rebuild of hwinfo to link against the new soname. Note that I'm not the hwinfo maintainer, I'm just jumping in to assist for this one thing. That update [3] is on its way to epel-testing. [0] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c1b36337e0 [1] https://docs.fedoraproject.org/en-US/epel/epel-policy/ [2] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ [3] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9abf798346
FEDORA-EPEL-2022-9abf798346 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.