Matio-1.5.17-3.el7 and vips-8.5.6-3.el7.cloudlinux packages have been scheduled for gradual rollout

 

update

Matio-1.5.17-3.el7 and vips-8.5.6-3.el7.cloudlinux packages have been scheduled for gradual rollout from our production repository.

Rollout slot: 4

Rolled out to: 0.2%

ETA for 100% rollout: August, 20

During the last few days, some of our clients experienced issues with updating packages from the EPEL repository. This happened because one of our dependency requires a package that is published in both repositories CloudLinux and EPEL.

It produces an error message like this:


Error: Package: vips-8.5.6-1.el7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libmatio.so.2()(64bit)
Removing: matio-1.5.3-1.el7.x86_64 (@cloudlinux-x86_64-server-7)
libmatio.so.2()(64bit)
Updated By: matio-1.5.17-3.el7.x86_64 (epel)
~libmatio.so.9()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

This update fixes the updating issue.

Update command
yum update vips matio

Immediate update (via bypass)

yum update vips matio --enablerepo=cloudlinux-rollout-4-bypass

Matio-1.5.17-3.el7 and vips-8.5.6-3.el7.cloudlinux packages have been scheduled for gradual rollout

 

update

Matio-1.5.17-3.el7 and vips-8.5.6-3.el7.cloudlinux packages have been scheduled for gradual rollout from our production repository.

Rollout slot: 4

Rolled out to: 0.2%

ETA for 100% rollout: August, 20

During the last few days, some of our clients experienced issues with updating packages from the EPEL repository. This happened because one of our dependency requires a package that is published in both repositories CloudLinux and EPEL.

It produces an error message like this:


Error: Package: vips-8.5.6-1.el7.cloudlinux.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libmatio.so.2()(64bit)
Removing: matio-1.5.3-1.el7.x86_64 (@cloudlinux-x86_64-server-7)
libmatio.so.2()(64bit)
Updated By: matio-1.5.17-3.el7.x86_64 (epel)
~libmatio.so.9()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

This update fixes the updating issue.

Update command
yum update vips matio

Immediate update (via bypass)

yum update vips matio --enablerepo=cloudlinux-rollout-4-bypass
imunify-logo

WEB SERVER SECURITY BLOG

Subscribe to CloudLinux Newsletter