ImageMagick soname bump was approved [0] in EPEL Steering Committee meeting. and I'm continuing with the process for incompatible upgrades from step 4 forward [1]. and 81 security bugs will be fixed
Just a note that this ImageMagick update broke yum on all a tonne of servers that have EPEL enabled :
Problem:
[root@busy-gates ~]# yum update
Last metadata expiration check: 0:07:35 ago on Fri 20 May 2022 06:49:26 AM MDT.
Error:
Problem: package plesk-php73-imagick-3.6.0-1centos.8.211118.1928.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed
- package plesk-php73-imagick-3.6.0-1centos.8.211118.1928.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-php73-imagick-3.6.0-1centos.8.211118.1928.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)
Does EPEL normally do major package updates like this mid cycle? I thought that EPEL packages only got major upgrades when switching from doing a dist OS upgrade?
--
Best regards,
Marcel Evenson
Danami - Software for the Cloud
www.danami.com