Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: ImageMagick and ImageMagick-perl on RH8 (EPEL 8 repository) Version-Release number of selected component (if applicable): Newest: 6.9.12.50-1.el8 How reproducible: Cannot install ImageMagick and ImageMagick-perl from EPEL repository - package conflict occurs. Steps to Reproduce: 1. Update EPEL8 cache repository 2. Probe install ImageMagick and ImageMagick-perl together Actual results: # dnf install ImageMagick ImageMagick-perl Ostatnio sprawdzono ważność metadanych: 1:49:26 temu w dniu Fri Jun 10 06:33:50 2022. Błąd: Problem: package ImageMagick-perl-6.9.12.50-1.el8.x86_64 requires perl(:MODULE_COMPAT_5.32.1), but none of the providers can be installed - package ImageMagick-perl-6.9.12.50-1.el8.x86_64 requires libperl.so.5.32()(64bit), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.32.1-471.module_el8.6.0+2766+8bf0b7ce.x86_64 is filtered out by modular filtering Expected results: Installing both packages is correct Additional info: The error appears to have appeared after the latest ImageMagick update
We have the same issue with LemonLDAP::NG, as ImageMagick-perl is a dependency
For some reason previous build use perl from modules I don't know why but please give positive karma urgently https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0c9f27acb3 to be pushed to updates (stable)
BTW the correct Product is "Fedora EPEL" , if you could fix it I appreciate , I haven't permissions Than you
fixed now , you can close this bug , I don't have permissions because you change it to not a Fedora product
why you don't close this bug ? I don't have permissions because you change it to a not Fedora product Thank you
(In reply to Sergio Basto from comment #4) > fixed now , you can close this bug , I don't have permissions because you > change it to not a Fedora product Hello I also don't have permissions for change this wrong "Product" type. I see info "You are not permitted to change products for this bug.". The problem itself has been resolved and the implemented fix is working. Looks like I can't change the status either :(