• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Forwarded to devs [PPPM-11847] Heads-up: RHEL7.8 is out, plesk-php-imagick should be rebuilt against libMagickCore-6.Q16.so.6

burnley

Regular Pleskian
User name: burnley

TITLE

Heads-up: RHEL7.8 is out, plesk-php-imagick should be rebuilt against libMagickCore-6.Q16.so.6

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 7.7 64bit, Plesk Obsidian, all plesk-php*-imagick packages

PROBLEM DESCRIPTION

With CentOS 7.8 around the corner we need to prepare for the big 7.7 -> 7.8 yum update. One of the roadblocks at the moment is the ImageMagick soname change, which is affecting the existing plesk-php*-imagick packages. RedHat have rebased ImageMagick to 6.9.10.68 which provides libMagickCore-6.Q16.so.6 and libMagickWand-6.Q16.so.6, while Plesk's imagick.so extensions are still linked against libMagickWand.so.5 and libMagickCore.so.5.
ImageMagick-6.9.10.68-3.el7 is already provided in CentOS CR and Remi's RPM repo is already providing .so.6 packages via ImageMagick6-libs.
References:
Latest ImageMagick-6.9.11.6-2.el7.remi changes soname (Page 1) — User support — Remi's RPM repository - Forum

STEPS TO REPRODUCE

Option 1. Install / upgrade to RHEL 7.8 on a Plesk server with plesk-php*-imagick packages installed.
Option 2. On RHEL / CentOS 7.7 install ImageMagick6-libs from Remi repo

ACTUAL RESULT

yum update fails due to the soname change.
[...]
--> Finished Dependency Resolution
Error: Package: plesk-php53-imagick-3.1.2-centos7.15100614.x86_64 (@PHP_5_3_29-dist)
Requires: libMagickCore.so.5()(64bit)
Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@base)
libMagickCore.so.5()(64bit)
Updated By: ImageMagick-6.9.11.6-2.el7.remi.x86_64 (remi)
Not found
Error: Package: plesk-php53-imagick-3.1.2-centos7.15100614.x86_64 (@PHP_5_3_29-dist)
Requires: libMagickWand.so.5()(64bit)
Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@base)
libMagickWand.so.5()(64bit)
Updated By: ImageMagick-6.9.11.6-2.el7.remi.x86_64 (remi)
Not found
Error: Package: plesk-php52-imagick-3.1.2-centos7.15100614.x86_64 (@PHP_5_2_17-dist)
Requires: libMagickCore.so.5()(64bit)
Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@base)
libMagickCore.so.5()(64bit)
Updated By: ImageMagick-6.9.11.6-2.el7.remi.x86_64 (remi)
Not found
[...]

EXPECTED RESULT

yum update succeeds

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
@burnley,
Thanks for the heads up. We are working on a proper solution for it, planning to fix soon (before 18.0.27 lands, if possible).
I've issued a bug ID PPPM-11847 to track it.
 
@abashurov thanks for looking into it, it's important for us to have it fixed quickly, since we're trying to keep our servers up to date to the best of our abilities. One option would be for you to ship your own ImageMagick5 compat package that installs somewhere in /opt/plesk and rebuild the plesk-php-imagick packages against the compat .so.5 libraries. This will allow for a clean CentOS 7.7->7.8 upgrade and later on down the track you'll be able to rebuild and test plesk-php-imagick against the latest ImageMagick library.
 
A help center article on this would be useful. I've marked ImageMagick to be ignored by yum for now until a clean fast solution is offered.
 
After upgrading to the latest version of Plesk and today's updated Plesk-PHP*-imagemagick updates I don't have this issue anymore.
 
with the latest change plesk automatic updates are failing if ImageMagick has not yet been upgraded and is set to ignore
 
Last edited:
Back
Top