Undoing Package Changes with DNF History Rollback on Fedora

Problem and Takeaway

A system update or package installation introduces regressions—broken dependencies, missing libraries, or behavioral changes in applications. Fedora's DNF package manager records every transaction in /var/lib/dnf/history/, letting you revert a specific operation without a full system restore. The rollback uninstalls packages added in that transaction, reinstalls packages removed, and preserves user-modified configuration files where possible.

Prerequisites

• Fedora 38 or later (DNF 5.x behavior is consistent; commands shown work on DNF 4 and 5).
• Root or sudo access to run dnf history and dnf history rollback.
• Transaction history must not have been cleared (dnf clean all does not remove history, but manual deletion of /var/lib/dnf/history/* does).
• Target transaction should not involve kernel packages, SELinux policy updates, or third-party repository metadata changes—these are not reverted by rollback.

View Transaction History

Run the following as root or with sudo to list recent transactions with IDs, dates, and actions:

dnf history list

Output example (truncated):

ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
  42   | install podman           | 2026-10-08 14:22 | Install        |   12
  41   | upgrade                  | 2026-10-07 09:15 | Upgrade        |   47
  40   | remove firefox           | 2026-10-06 16:40 | Remove         |    1

Note the ID of the transaction you want to undo. You can also filter: dnf history list podman shows only transactions mentioning "podman".

Inspect a Transaction Before Rollback

Review the exact package changes for a given ID:

dnf history info 42

This prints each package with its version, repository, and whether it was installed, upgraded, or removed. Confirm the list matches the change you intend to reverse.

Perform the Rollback

Execute the rollback for the chosen transaction ID. DNF will show a summary of packages to be removed, installed, or downgraded and prompt for confirmation:

dnf history rollback 42

Type y to proceed. The operation uninstalls packages added by transaction 42 and reinstalls packages that transaction removed. Configuration files you modified under /etc are preserved (marked .rpmnew or .rpmsave as appropriate).

Verify System State After Rollback

Check that the expected packages are now at their pre-transaction versions:

dnf repoquery --last=1

This shows the most recent transaction's effect. Alternatively, query specific packages:

rpm -q podman

Compare the version against what dnf history info 42 reported before rollback.

Limitations and Recovery Options

• Kernel and SELinux changes are not rolled back. If the transaction updated the kernel or SELinux policy, those remain at the newer version. Boot into a previous kernel from the GRUB menu if needed.
• Third-party repository metadata changes persist. If the transaction added or modified a repo file, rollback does not revert it. Manually edit or remove /etc/yum.repos.d/ entries.
• Dependency conflicts can block rollback. If later transactions installed packages that depend on the ones you're trying to remove, DNF will refuse. You may need to roll back the later transactions first (higher IDs) in reverse chronological order.
• History cleared? No rollback possible. If /var/lib/dnf/history/ is empty, you must manually downgrade or remove packages using dnf downgrade or dnf remove with specific versions.

Roll Back a Range of Transactions

To undo multiple consecutive transactions, specify the earliest ID in the range with --last:

dnf history rollback --last=40

This rolls back transactions 42, 41, and 40 (assuming 42 is the latest). Review the combined package list carefully before confirming.

Quick Reference