Symptoms
Running dnf update (or yum update) fails with dependency resolution errors similar to:
CONFIG_TEXT: Problem 1: package ea-phpXX-php-gd-*.x86_64 from @System requires libavif.so.15()(64bit), but none of the providers can be installed
- cannot install both libavif-*.el9.next.x86_64 from epel-next and libavif-*.el9.x86_64 from @System
- cannot install both libavif-*.el9.next.x86_64 from epel-next and libavif-*.el9.x86_64 from epel
- cannot install the best update candidate for package libavif-*.x86_64
- cannot install the best update candidate for package ea-phpXX-php-gd-*.x86_64
Problem 2: package ffmpeg-libs-*.x86_64 from @System requires libSvtAv1Enc.so.0()(64bit), but none of the providers can be installed
- cannot install both svt-av1-libs-*.el9.next.x86_64 from epel-next and svt-av1-libs-*.el9.x86_64 from @System
...
Cause
The epel-next repository is enabled on the server alongside epel. epel-next carries newer builds of libavif and svt-av1-libs than the versions already installed from epel/@System. Those newer epel-next builds no longer provide the specific libraries (libavif.so.15, libSvtAv1Enc.so.0) that the installed EasyApache PHP-GD package and ffmpeg-libs require. During dependency resolution, the package manager tries to select the newest available build as the "best" candidate, finds it from epel-next, and that build conflicts with the already-installed version that is required.
epel-next is not required by cPanel or EasyApache. It is not enabled by default on these operating systems, so its presence usually traces back to a manual repo installation or a third-party script.
Resolution
Confirm
epel-nextis enabled:# dnf repolist enabled | grep -i epel
If nothing else on the server depends on
epel-next, disable it:# yum-config-manager --disable epel-next
Note: If
yum-config-manageris not installed, edit/etc/yum.repos.d/epel-next.repoand setenabled=0under each section in the file instead.Clear and rebuild the cache:
# dnf clean all && dnf makecache
Perform the update:
# dnf update
Comments
0 comments
Article is closed for comments.