• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Problem: package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be i

Azurel

Silver Pleskian
Username:

TITLE

Problem: package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.6 (Sky Tiger)
Plesk Obsidian Version 18.0.43 Update #1,

PROBLEM DESCRIPTION

# yum update

STEPS TO REPRODUCE

on AlmaLinux call command "yum update"

ACTUAL RESULT

Output
Error:
Problem: package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed
- package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64 requires libMagickWand-6.Q16.so.6()(64bit), but none of the providers can be installed
- cannot install both ImageMagick-libs-6.9.12.48-2.el8.x86_64 and ImageMagick-libs-6.9.10.86-1.el8.x86_64
- cannot install both ImageMagick-libs-6.9.10.86-1.el8.x86_64 and ImageMagick-libs-6.9.12.48-2.el8.x86_64
- cannot install the best update candidate for package plesk-php74-imagick-3.7.0-0redhat.8.220415.1034.x86_64
- cannot install the best update candidate for package ImageMagick-libs-6.9.10.86-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

EXPECTED RESULT

No errors

ANY ADDITIONAL INFORMATION

Actual I don't use PHP 7.4 /admin/php-handler/list shows 0 Domains. So I removed extension php 7.4 with Plesk uninstaller.

After this. Now I get this for PHP 8.1

Error:
Problem: package plesk-php81-imagick-3.7.0.1-0redhat.8.220513.0910.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed
- package plesk-php81-imagick-3.7.0.1-0redhat.8.220513.0910.x86_64 requires libMagickWand-6.Q16.so.6()(64bit), but none of the providers can be installed
- cannot install both ImageMagick-libs-6.9.12.48-2.el8.x86_64 and ImageMagick-libs-6.9.10.86-1.el8.x86_64
- cannot install both ImageMagick-libs-6.9.10.86-1.el8.x86_64 and ImageMagick-libs-6.9.12.48-2.el8.x86_64
- cannot install the best update candidate for package plesk-php81-imagick-3.7.0.1-0redhat.8.220513.0910.x86_64
- cannot install the best update candidate for package ImageMagick-libs-6.9.10.86-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
From the developer:

The root cause is in epel repository: ImageMagick-libs from epel don't satisfy plesk-php74-imagick:

Code:
# repoquery --requires plesk-php74-imagick | grep libMagickCore
libMagickCore-6.Q16.so.6()(64bit)
# repoquery --provides ImageMagick-libs-6.9.10.86 | grep libMagickCore
libMagickCore-6.Q16.so.6()(64bit)
# repoquery --provides ImageMagick-libs-6.9.12.48 | grep libMagickCore
libMagickCore-6.Q16.so.7()(64bit)

Filled bugreport PPPM-13570
 
My solution which worked is to edit /etc/yum.repos.d/epel.repo and add this line

exclude=ImageMagick-libs
 
From the developer:

The root cause is in epel repository: ImageMagick-libs from epel don't satisfy plesk-php74-imagick:

Code:
# repoquery --requires plesk-php74-imagick | grep libMagickCore
libMagickCore-6.Q16.so.6()(64bit)
# repoquery --provides ImageMagick-libs-6.9.10.86 | grep libMagickCore
libMagickCore-6.Q16.so.6()(64bit)
# repoquery --provides ImageMagick-libs-6.9.12.48 | grep libMagickCore
libMagickCore-6.Q16.so.7()(64bit)

Filled bugreport PPPM-13570

I'm having this same issue, but using php 8.1. I'm not doing anything, my site is workin as-is. Wasn't sure if I should add --alowerasing to my dnf command.
 
@deltatech Thanks, that helps me.

@IgorG so far all previous updates with plesk imagick working fine. I haven't changed anything in the settings for months and there were several new Imagegick versions.
 
Hi , sorry
ImageMagick soname bump was approved in EPEL Steering Committee meeting
after more than 15 days in testing [1] it was passed to stable. because we thought it worth and bring more security to RHEL / Centos 8 .
When you run an update and you have a broken dep , is not the end of the world , just add --skip-broken , i.e. `dnf update --skip-broken` , and wait for the update of plesk with the rebuilt against the new ImageMagick .


[1]
 
When you run an update and you have a broken dep , is not the end of the world , just add --skip-broken , i.e. `dnf update --skip-broken` , and wait for the update of plesk with the rebuilt against the new ImageMagick .
@sergiomb Unfortunately --skip-broken will not work in this case. The only work around is to add the line exclude=ImageMagick-libs in the /etc/yum.repos.d/epel.repo file or via the command line using:
Code:
dnf update --exclude=ImageMagick-libs
 
@sergiomb Unfortunately --skip-broken will not work in this case. The only work around is to add the line exclude=ImageMagick-libs in the /etc/yum.repos.d/epel.repo file or via the command line using:
Code:
dnf update --exclude=ImageMagick-libs

Wouldn't that create a permanent exclude, and potentially conflict with a future update?
 
Wouldn't that create a permanent exclude, and potentially conflict with a future update?
Yes you only want to use an exclude like exclude=ImageMagick* temporarily (the exclude applies to epel packages only). Apparently the reason the EPEL upgraded ImageMagick mid cycle like this was to fix a bunch of security vulnerabilities. Ultimately the permanent fix is for Plesk to build their packages against the new version.
 
yes, you just need hold on the upgrade of ImageMagick , dnf update --exclude="ImageMagick*"

use ImageMagick* quoted is better
 
@Amadex disabling the entire EPEL repo isn't a solution. I recommend just adding the line exclude=ImageMagick* to the [EPEL] section in the file /etc/yum.repos.d/epel.repo for now. I'm sure that the Plesk devs will likely update the ImageMagick from their repo as the EPEL repo updated their packages to fix security issues.
 
@Amadex disabling the entire EPEL repo isn't a solution. I recommend just adding the line exclude=ImageMagick* to the [EPEL] section in the file /etc/yum.repos.d/epel.repo for now. I'm sure that the Plesk devs will likely update the ImageMagick from their repo as the EPEL repo updated their packages to fix security issues.

That is what I've done for now. Copied my original epel.repo file elsewhere.
 
That is what I've done for now. Copied my original epel.repo file elsewhere.
I've did the same, so let's wait.

jasar-ahmedovski.gif
 
From the developer:

The root cause is in epel repository: ImageMagick-libs from epel don't satisfy plesk-php74-imagick:

Code:
# repoquery --requires plesk-php74-imagick | grep libMagickCore
libMagickCore-6.Q16.so.6()(64bit)
# repoquery --provides ImageMagick-libs-6.9.10.86 | grep libMagickCore
libMagickCore-6.Q16.so.6()(64bit)
# repoquery --provides ImageMagick-libs-6.9.12.48 | grep libMagickCore
libMagickCore-6.Q16.so.7()(64bit)

Filled bugreport PPPM-13570
Any update on this?
 
Back
Top