Package Management (Apt/Dnf/Pacman Internals)

Find out exactly which repo gave you that broken package version

🧩 The Challenge

Dealing with a vendor repo that pushed a broken update and now everything is failing dependencies is a special kind of hell. You spend hours hunting through logs when the answer is sitting right there in the metadata.

💡 The Fix

Check the internal apt-cache output to map specific versions to their source URLs so you know exactly which maintainer caused the mess. This saves you from nuking your whole sources list just to find the culprit.

apt-cache policy <package_name>

⚙️ Why It Works

By dumping the policy output, the package manager reveals the exact priority and origin URI for every version of the binary it has tracked. It takes the guesswork out of mirror versioning.

🚀 Pro-Tip: Always check the priority number—if it is higher than 500, your system will favor that repo’s update over everything else.

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