• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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

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)
Click to expand...

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)
Click to expand...

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
 
IgorG said:
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
Click to expand...

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]
 
sergiomb said:
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 .
Click to expand...
@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
 
danami said:
@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
Click to expand...

Wouldn't that create a permanent exclude, and potentially conflict with a future update?
 
motowebmaster said:
Wouldn't that create a permanent exclude, and potentially conflict with a future update?
Click to expand...
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.
 
danami said:
@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.
Click to expand...

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

jasar-ahmedovski.gif
 
IgorG said:
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
Click to expand...
Any update on this?
 
You must log in or register to reply here.

Similar threads

S
Issue MariaDB 10.5 to 10.11 upgrade failure on AlmaLinux 9.5
Replies
3
Views
2K
sder
S
tkalfaoglu
Issue ImageMagick dependancy problem
Replies
2
Views
4K
Azurel
Azurel
P
Issue Problem with dnf update - Imagick update
Replies
2
Views
2K
Peter99
P
burnley
Forwarded to devs [PPPM-11847] Heads-up: RHEL7.8 is out, plesk-php-imagick should be rebuilt against libMagickCore-6.Q16.so.6
Replies
5
Views
3K
evcz
E
P
Issue Plesk Onyx for Linux Fails to Resolve Dependencies for libMagickCore-6
Replies
3
Views
2K
pleskpanel
P
Back
Top