Package Management (Apt/Dnf/Pacman Internals)

Stop dnf from making you guess which repo brought in the trash

🧩 The Challenge

Dealing with a dependency hell scenario where a package pulls in a version you didn’t want is a special kind of nightmare. I once spent an entire afternoon trying to figure out why an internal tool suddenly decided to install a development library from a third-party repo instead of the stable one.

💡 The Fix

You need to lean on the dnf history command combined with the list command to see exactly which repository a specific package version was fetched from. It saves you from staring at long debug logs while questioning your life choices.

dnf history list <package_name>
dnf history info <transaction_id>

⚙️ Why It Works

Dnf keeps a local database of every transaction it ever performs, so you can backtrack through the exact metadata associated with that specific install event. It essentially forces the package manager to reveal the provenance of the files sitting on your disk.

🚀 Pro-Tip: Use dnf info <package_name> and look for the ‘From repo’ line before you run your next install to save yourself the detective work.

Linux Tips & Tricks | © ngelinux.com | 10/20/2026