Decision Guide: Enabling the Rocky Linux Plus Repository for Newer Packages

Decision and Constraints

The decision is whether to enable the Rocky Linux Plus repository to obtain newer versions of selected packages (e.g., kernel, systemd, Python) when the default BaseOS and AppStream repositories do not meet a workload’s feature or performance requirements. The operation must stay within Rocky Linux’s support lifecycle, avoid breaking third‑party RPM dependencies, and preserve the ability to receive security updates from the base channels.

Options Comparison

Option	Description	Typical Use Case
BaseOS+AppStream only	Default repositories with stable, older versions	General production servers needing maximum stability
BaseOS+AppStream+Plus	Adds the Rocky Linux Plus repo with newer selected packages	Workloads benefiting from a newer kernel or libraries while still wanting vendor support
BaseOS+AppStream+ELS	Extended Life Support for older Rocky releases	Systems needing extended security patches beyond standard EOL

Trade‑offs

Enabling Plus provides newer features, improved hardware support, and potentially better performance for applications that require recent library versions. However, Plus packages may not have been vetted by all third‑party vendors, which can introduce dependency conflicts. The ELS option offers extended security updates but no new features, while staying on BaseOS+AppStream only yields the highest stability but may lack recent improvements.

Enabling Rocky Linux Plus Repository

1. Install the release package that defines the Plus repository (run as root or with sudo):

   dnf install -y rocky-release-plus

2. Enable the newly available repository:

   dnf config-manager --set-enabled rockyplus

3. Verify that the repository is enabled and visible:

   dnf repolist enabled | grep rockyplus

   You should see a line indicating rockyplus with a status of enabled.

4. Optionally, inspect a package known to be newer in Plus (for example, the kernel) to confirm the version source:

   rpm -q kernel --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n'

   The output will include a release marker such as .plus if the package comes from the Plus repository.

Validation After Enabling

Perform a refresh and update to ensure packages are pulled from the correct source:

dnf update --refresh

During the update process, observe the output lines that indicate the repository origin; packages sourced from Plus will show rockyplus in the repository column. After the update completes, reboot the system (if a kernel update was applied) and verify that it boots successfully.

Limitations and Practical Checks

• Mixing Plus with third‑party repositories that expect base versions can cause dependency conflicts. Always test the change in a staging environment before applying to production.

• Plus packages receive updates only while the underlying Rocky Linux release is within its support lifecycle. After the release reaches End‑of‑Life (EOL), the Plus repository is no longer maintained, so plan a migration path to a newer Rocky release or to the ELS channel if extended security is needed.

• To confirm that the system can still receive updates from BaseOS and AppStream, run:

  dnf check-update --disablerepo=rockyplus

  This command checks for updates while temporarily disabling the Plus repo; if it returns expected updates from BaseOS/AppStream, the base channels remain functional.

• If you need to revert the change, disable the Plus repository:

  dnf config-manager --set-disabled rockyplus

  Then run dnf distro-sync to return installed packages to the versions available in the base repositories.