Bug 1826860

Summary: php-pecl-imagick failed Dependency Resolution
Product: [Fedora] Fedora EPEL Reporter: Aldo Necci <necci>
Component: php-pecl-imagickAssignee: Pavel Alexeev <pahan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: fedora, pahan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-23 05:14:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aldo Necci 2020-04-22 16:26:46 UTC
Description of problem: 
upgrading from Scientific linux 7.7 to Scientific linux 7.8

Actual results:
Resolving Dependencies
--> Running transaction check
---> Package ImageMagick.x86_64 0:6.7.8.9-18.el7 will be updated
--> Processing Dependency: libMagickCore.so.5()(64bit) for package: php-pecl-imagick-3.1.0-0.6.RC2.el7.x86_64
--> Processing Dependency: libMagickWand.so.5()(64bit) for package: php-pecl-imagick-3.1.0-0.6.RC2.el7.x86_64
---> Package ImageMagick.x86_64 0:6.9.10.68-3.el7 will be an update
--> Finished Dependency Resolution
Error: Package: php-pecl-imagick-3.1.0-0.6.RC2.el7.x86_64 (@epel)
           Requires: libMagickCore.so.5()(64bit)
           Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@sl)
               libMagickCore.so.5()(64bit)
           Updated By: ImageMagick-6.9.10.68-3.el7.x86_64 (sl)
               Not found
Error: Package: php-pecl-imagick-3.1.0-0.6.RC2.el7.x86_64 (@epel)
           Requires: libMagickWand.so.5()(64bit)
           Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@sl)
               libMagickWand.so.5()(64bit)
           Updated By: ImageMagick-6.9.10.68-3.el7.x86_64 (sl)
               Not found

Comment 1 Remi Collet 2020-04-23 05:14:54 UTC

*** This bug has been marked as a duplicate of bug 1821917 ***