Hi, I got an alert from Yum-Cron this morning: Failed to check for updates with the following error message: Failed to build transaction: sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 requires libMagickCore.so.5()(64bit) sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 requires libMagickWand.so.5()(64bit) The CR repository is activated on this server, so I guess that's why. Which leads me to the more general question of: enable CR on a production server, yes or no? Pros : get security updates sooner Cons : expect breakage like the one above Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 Mob. : 06 51 80 12 12
On Thu, Apr 09, 2020 at 11:06:45AM +0200, Nicolas Kovacs wrote:> Which leads me to the more general question of: enable CR on a production > server, yes or no?Not on production. Only for testing. -- Jonathan Billings <billings at negate.org>
> On Thu, Apr 09, 2020 at 11:06:45AM +0200, Nicolas Kovacs wrote: >> Which leads me to the more general question of: enable CR on a >> production >> server, yes or no? > > Not on production. Only for testing.I'm not sure. Running production environments without CR enabled means you're running without current security updates for quite some time. Seems a bad and risky idea to me. Regards, Simon
> Hi, > > I got an alert from Yum-Cron this morning: > > Failed to check for updates with the following error message: > Failed to build transaction: > sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 > requires libMagickCore.so.5()(64bit) > sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 requires > libMagickWand.so.5()(64bit) > > The CR repository is activated on this server, so I guess that's why. > > Which leads me to the more general question of: enable CR on a production > server, yes or no? > > Pros : get security updates sooner > > Cons : expect breakage like the one above > > Any suggestions?Hi, The breakage you see is not directly within CentOS 7 and CR. The problem is that your SCLO package sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 is for 7.7.1908 and needs to be updated for CentOS 7.8. All the same you'll not be able to update to CentOS 7.8 until a fixed sclo-php72-php-pecl-imagick package is available. Applying CR updates to clean installations of a basic CentOS system usually works very fine. Regards, Simon