The rpm.versions system manages many of the packages on your cPanel & WHM server.
cPanel & WHM includes PHP and its modules as a set of packages, including the associated PEAR and PECL packages and PHP loaders.
Hosting providers and system administrators can use this document to determine whether their systems have been compromised.
This document describes how to build custom RPMs for your Red-Hat® systems.
System administrators and third-party developers can modify cPanel-provided package management.
This document provides steps on how to set packages to both the managed and unmanaged states.
Third-party customers who want to create their own package repositories must create digest files and GnuPG (GPG) signatures as well as the necessary package files.
RPM® (RPM Package Manager) refers to a software format, the software that the RPM package contains, and the package management system.
This interface allows you to install software packages via the package-management system.
Package managers allow you to easily update, install, and remove packages on your system.
This interface allows you to rebuild the RPM database.
This document provides examples of common RPM installation failures.
An RPM target represents the group of RPMs that must exist on the server for a specific service to function properly.
This interface allows you to update your server's RPM packages.
Target settings represent the group of packages that must exist on the server for a specific service to function properly.
The cpupdate.conf file on your server determines how cPanel & WHM updates your system.
This package includes scripts that allow you to work with EasyApache 4 (EA4) from the command line rather than in WHM's EasyApache 4 interface.
This file contains all of the cPanel-provided settings for the rpm.versions system.
This file stores the server's system information settings.
Use this script to update the /var/cpanel/rpm.versions.d/local.versions file.