4.4 YUM, DNF & Zypper Package Management (102.5)

4.4 YUM, DNF & Zypper Package Management (102.5)

Quick Summary: While low-level rpm manages individual archive files locally, modern enterprise RPM distributions rely on high-level package management frameworks to automatically resolve dependencies, query remote software mirrors, download packages, and apply transaction updates. YUM (Yellowdog Updater, Modified) and its modern successor DNF (Dandified YUM) serve Red Hat Enterprise Linux, CentOS, Rocky Linux, and Fedora. In the SUSE Linux ecosystem, Zypper provides high-speed package management utilizing the libsolv SAT solver engine.

---

1. Evolution of High-Level RPM Management: YUM vs. DNF Architecture

Historically, YUM managed RPM packages across RHEL/CentOS 5, 6, and 7. However, as software repositories scaled, YUM suffered from high memory consumption, slow dependency calculation, and an undocumented Python API. DNF replaced YUM in Fedora and RHEL 8/9, introducing major architectural improvements:

• SAT-Based Dependency Resolver (libsolv): DNF employs the state-of-the-art Boolean Satisfiability (SAT) algorithm developed by SUSE for instant, deterministic dependency resolution.
• Performance & Memory Efficiency: Core metadata parsing is implemented in optimized C/C++ libraries (libdnf, librepo).
• Backward Compatibility: DNF preserves virtually identical command syntax to YUM. On modern RHEL/Fedora systems, /usr/bin/yum is a symbolic link pointing directly to /usr/bin/dnf.

┌─────────────────────────────────────────────────────────────┐
│                     DNF / YUM Front-End                     │
├─────────────────────────────────────────────────────────────┤
│  libsolv (SAT Solver)  │  librepo (HTTP/FTP Metadata)       │
├────────────────────────┴────────────────────────────────────┤
│                 RPM Engine (/var/lib/rpm/)                  │
└─────────────────────────────────────────────────────────────┘

---

2. YUM / DNF Command Operations

Both yum and dnf share a unified set of subcommands for package operations.

# Find which package provides the 'netstat' or 'ifconfig' command
$ dnf provides "*/netstat"
net-tools-2.0-0.62.20160912git.el9.x86_64 : Basic networking tools
Repo        : @System
Matched from:
Filename    : /usr/bin/netstat

# Check for available security and software updates
$ dnf check-update

💡 LPIC-1 Exam Fill-in-the-Blank Alert: The command to find which package owns or provides a specific file or command across all repositories (even uninstalled packages) is dnf provides <path> or yum provides <path> (or whatprovides).

---

3. Transaction History & Rollback Operations

DNF and YUM record every package transaction in a persistent SQLite history database. This allows administrators to audit historical package installations, view who performed an action, and roll back broken updates.

# View chronological list of recent package management transactions
$ sudo dnf history
ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
     4 | install nginx            | 2026-08-28 14:10 | Install        |    4
     3 | upgrade -y               | 2026-08-25 09:30 | Upgrade        |   28 EE
     2 | install gcc make         | 2026-08-20 11:15 | Install        |   12
     1 | Initial installation     | 2026-08-01 08:00 | Install        |  485

# Display granular details of transaction ID 4
$ sudo dnf history info 4

# Undo ONLY the specific actions taken in transaction ID 4
$ sudo dnf history undo 4

# Roll back ALL transactions that occurred after transaction ID 2
$ sudo dnf history rollback 2

⚠️ LPIC-1 Trap: Note the fundamental distinction between undo and rollback:

• dnf history undo <id>: Reverses only the single transaction specified by <id>.
• dnf history rollback <id>: Reverses all transactions that occurred after <id>, reverting the operating system back to its exact state at the conclusion of transaction <id>.

---

4. Package Groups Management

DNF/YUM packages related software suites into Package Groups (e.g., "Development Tools", "Web Server", "Virtualization Host"), enabling single-command provisioning of entire software environments.

# List all installed and available package groups
$ dnf grouplist
Available Environment Groups:
   Server with GUI
   Development and Creative Workstation
Available Groups:
   Development Tools
   RPM Development Tools
   Security Tools

# Display mandatory, default, and optional packages in a group
$ dnf groupinfo "Development Tools"

# Install all mandatory and default packages in the group
$ sudo dnf groupinstall "Development Tools"
# OR using modern DNF syntax:
$ sudo dnf group install "Development Tools"

# Remove all packages associated with the group
$ sudo dnf groupremove "Development Tools"

---

5. Configuration Directives in dnf.conf and yum.conf

The master configuration file is located at /etc/dnf/dnf.conf (or /etc/yum.conf). It contains a mandatory [main] section that governs global package manager behavior.

[main]
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=True
best=True
skip_if_unavailable=False
cachedir=/var/cache/dnf
keepcache=0
exactarch=1
obsoletes=1

Key Configuration Directives

• gpgcheck=1: Enforces GPG signature checking on all downloaded packages.
• installonly_limit=3: Limits the number of simultaneous kernel versions retained on disk. When a new kernel is installed, the oldest kernel is automatically purged to prevent /boot exhaustion.
• keepcache=0: Set to 0 to automatically delete downloaded RPM packages after successful installation; set to 1 to retain downloaded RPM archives in cachedir.
• clean_requirements_on_remove=True: Automatically erases unneeded dependencies when a package is removed (equivalent to autoremove).

---

6. OpenSUSE Package Management with zypper

In openSUSE and SUSE Linux Enterprise Server (SLES), the high-level package management tool is zypper. It interfaces with the ZYpp engine and supports intuitive, highly compact short subcommands.

Essential zypper Global Flags

• -n, --non-interactive: Automatically answers prompts with their default values for non-interactive scripting.
• --dry-run: Tests transaction without making filesystem modifications.
• --no-gpg-checks: Skips GPG signature verification (testing only).

# Perform non-interactive distribution upgrade
$ sudo zypper -n dup

# Search for which package provides /usr/bin/git
$ zypper wp /usr/bin/git