RPM 6.0: What’s New and Why It Matters

RPM 6.0 is the latest major release of the Red Hat Package Manager, the low-level tool that installs, upgrades, and removes software packages on Fedora, RHEL, CentOS, and other RPM-based Linux distributions. This version focuses on performance, security, and a cleaner codebase, making package operations faster and more reliable for system administrators and end users alike. Here’s what changed and why you should care.

Background: What Is RPM?

RPM (originally Red Hat Package Manager, now a recursive acronym for RPM Package Manager) is the package management system used by Fedora, RHEL, CentOS, AlmaLinux, Rocky Linux, openSUSE, and many other distributions. It handles the installation, upgrade, and removal of software packages, which are files with a .rpm extension. RPM stores metadata about each package—such as version, dependencies, and file lists—in a local database, typically at /var/lib/rpm. Higher-level tools like DNF (Fedora) and Zypper (openSUSE) use RPM as their backend to resolve dependencies and manage repositories.

What’s New in RPM 6.0

RPM 6.0 is a significant update after years of incremental 4.x releases. Key changes include:

• Faster database operations: The default database backend has moved to a new format that reduces lock contention and speeds up queries, especially on large systems with thousands of packages.
• Improved security: Stronger signature verification and support for newer cryptographic algorithms, including Ed25519, for package signing.
• Cleaner code and fewer dependencies: The codebase has been modernized, removing obsolete code and reducing the number of external libraries required.
• Better handling of file conflicts: The conflict resolution logic has been improved to handle edge cases more gracefully, reducing the chance of failed upgrades.
• New options for scripting: Package scriptlets (pre/post install scripts) now have more control and better error reporting.

These changes are mostly under the hood, but they translate to faster installs, fewer lockups during parallel operations, and a more secure supply chain.

How RPM 6.0 Works

RPM works by reading the metadata in a .rpm file and comparing it against the local database. When you run rpm -i package.rpm, it checks for dependencies, verifies that no file conflicts exist, and then extracts the files to their target locations, recording everything in the database. RPM 6.0 improves this process by using a new database backend that supports concurrent reads and writes more efficiently. In practice, this means that commands like rpm -qa (list all installed packages) and rpm -V (verify installed packages) respond faster, and the database is less prone to corruption if a system crashes during an operation.

How to Get RPM 6.0

RPM 6.0 is not yet available in stable releases of most distributions as of this writing. It is in development and will likely appear first in Fedora Rawhide (the development branch) and then in future Fedora releases. For RHEL and its derivatives, it will be introduced in a future major version. If you want to test it, you can build RPM from source from the official RPM GitHub repository, but be aware that it is not recommended for production systems until it is officially packaged by your distribution.

Common Problems and Solutions

Users upgrading from RPM 4.x may encounter a few issues:

• Database migration: RPM 6.0 automatically migrates the old database to the new format on first run. This can take a few minutes on large systems, and you should not interrupt it. If it fails, you may need to rebuild the database with rpm --rebuilddb.
• Third-party packages: Some older packages that rely on removed RPM features may fail to install. Check the package’s documentation for a version that supports RPM 6.
• Scriptlet failures: If a package’s install script fails, RPM will roll back the transaction, but sometimes leftover files remain. Use rpm -q --scripts package to inspect the scripts before installing.

Comparison with DNF and Other Tools

RPM is the low-level tool, while DNF (for Fedora/RHEL) and Zypper (for openSUSE) are high-level package managers that use RPM to do the actual install. DNF resolves dependencies, downloads packages from repositories, and calls RPM to perform the transaction. RPM 6.0 does not change this relationship; it simply makes the underlying operations faster and more reliable. If you use DNF, you will see the benefit as faster transaction processing and less waiting during large updates. If you use a tool like apt (Debian/Ubuntu), RPM is the equivalent of dpkg—the core engine—while DNF is like apt itself.

Cost and Licensing

RPM is free and open-source software, released under the GNU General Public License (GPL). There is no cost to use it, and you can modify and redistribute it. The development is community-driven, with contributions from Red Hat and other companies. This means that RPM 6.0 is available at no charge, and you can inspect its source code to verify its behavior.

Safety and Security Considerations

RPM 6.0 strengthens security in several ways. It now supports Ed25519 signatures, which are considered more secure and faster than RSA for package signing. It also improves the verification of file checksums and permissions during package installation. However, you should always ensure that you only install packages from trusted repositories, as RPM cannot protect you from malicious packages if you install them manually. Always verify the signature of downloaded packages with rpm -K package.rpm before installation.

Frequently Asked Questions

Is RPM 6.0 backwards compatible with RPM 4 packages?

Yes, RPM 6.0 can install and manage packages built for RPM 4. The package format (the .rpm file structure) has not changed, so existing packages will work. However, some older packages that used deprecated features may need to be rebuilt.

Will RPM 6.0 work on my current Fedora or RHEL system?

Not until your distribution officially packages it. RPM is tightly integrated with the OS, and upgrading it manually can break your system. Wait for the official release from your distribution.

Does RPM 6.0 speed up DNF updates?

Yes, because DNF calls RPM to perform the actual installation, a faster RPM will make the transaction phase of updates quicker. The biggest gains are on large updates with many packages.

How do I check my current RPM version?

Run rpm --version in a terminal. If it shows a 4.x version, you are on an older release. RPM 6.0 will show as 6.0.x.

Is there a risk of data loss when upgrading to RPM 6.0?

No, RPM does not touch user data. It only manages system software. However, as with any major system change, it is wise to back up your system before upgrading, especially if you do it manually.

RPM 6.0 is a solid step forward for the foundation of RPM-based Linux distributions. While it may not bring flashy new features, its performance and security improvements will benefit every user of Fedora, RHEL, and their derivatives. Keep an eye on your distribution’s release notes for when it arrives.

Related

• Convert MOV to AVI: A Practical Guide
• Data Center Power Demand Growth & Limits
• Oracle Gas Truck Data Center Power Delays?

in t | Time (minutes) | min | 10 | 0
in d | Distance (km) | km | 5 | 0 | 100000
out pace | Average pace (min/km) | min/km | t / d | 2
out speed | Average speed (km/h) | km/h | d / (t / 60) | 2