• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Plesk PHP packages built with older libavif which breaks yum updates

danami

Silver Pleskian
Username:

TITLE


Plesk PHP packages built with older libavif which breaks yum updates

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Product version: Plesk Obsidian 18.0.81.2
OS version: AlmaLinux 9.8 x86_64
Build date: 2026/09/25 20:00
Revision: 92d6fda48253f48a21224724a05a5b5820d72773

PROBLEM DESCRIPTION

There is a dependency version mismatch between EPEL (Extra Packages for Enterprise Linux) and Plesk's PHP repositories for AlmaLinux 9.

Why It Happens
libavif Major Version Bump: EPEL recently updated libavif from version 0.11.x to 1.1.x (which increments the shared library SONAME from libavif.so.15 or older to new versions/incompatible ABI boundaries).

Conflicting Dependencies:

The new Plesk PHP GD extension (plesk-php83-gd) requires libavif.so.15()(64bit) and needs the updated libavif / svt-av1-libs from EPEL.

However, your OS currently has older versions installed (libavif-0.11.1 and svt-av1-libs-0.9.0).

DNF/YUM defaults to refusing upgrades that remove or replace existing libraries unless explicitly permitted.

Here is the error


Code:
# yum update

Last metadata expiration check: 0:18:55 ago on Tue 29 Sep 2026 04:41:02 AM.

Error:

 Problem 1: package plesk-php82-gd-8.2.34-0redhat.9.260925.1442.x86_64 from @System requires libavif.so.15()(64bit), but none of the providers can be installed

  - cannot install both libavif-1.1.1-3.el9.x86_64 from epel and libavif-0.11.1-5.el9.x86_64 from @System

  - cannot install the best update candidate for package plesk-php82-gd-8.2.34-0redhat.9.260925.1442.x86_64

  - cannot install the best update candidate for package libavif-0.11.1-5.el9.x86_64

 Problem 2: package libavif-0.11.1-5.el9.x86_64 from @System requires libSvtAv1Enc.so.0()(64bit), but none of the providers can be installed

  - cannot install both svt-av1-libs-2.3.0-3.el9.x86_64 from epel and svt-av1-libs-0.9.0-1.el9.x86_64 from @System

  - package plesk-php83-gd-8.3.35-0redhat.9.260925.1442.x86_64 from @System requires libavif.so.15()(64bit), but none of the providers can be installed

  - cannot install the best update candidate for package svt-av1-libs-0.9.0-1.el9.x86_64

  - cannot install the best update candidate for package plesk-php83-gd-8.3.35-0redhat.9.260925.1442.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)

STEPS TO REPRODUCE

Run the command: yum update

ACTUAL RESULT

yum should continue to work

EXPECTED RESULT

yum should work without any human interaction.

ANY ADDITIONAL INFORMATION

The only workaround I've been apple to see is to run yum update --allowerasing but it will remove any of the plesk-php82-gd, plesk-php83-gd packages.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Last edited:
As of Plesk Obsidian 18.0.82, he issue with updating any installed packages was resolved:

Fixed an issue where, on Plesk servers running on AlmaLinux 9, if the EPEL repository was enabled and one or more Plesk PHP GD packages were installed, updating any installed packages via the dnf update or yum update commands would fail. (PPPM-15544)

Thank you for reporting the behavior and brining our team's attention to it.
 
Back
Top