Package Management (Apt/Dnf/Pacman Internals)
Stop guessing what files your package manager actually left behind
🧩 The Challenge
Dealing with a botched package installation is annoying enough, but trying to figure out which specific config files an update touched before it died is a total nightmare. I’ve spent way too long manually diffing directories because I didn’t realize the package manager database already held the answer.
đź’ˇ The Fix
You can use the package manager’s internal verification tool to list every file currently installed on your system that has a mismatched checksum. It’s the fastest way to see what got corrupted or modified during a half-finished install.
dpkg --verify⚙️ Why It Works
This command triggers the integrity check of the MD5 sums stored in /var/lib/dpkg/info against the actual files on your disk. Any output you see tells you exactly which files have been tampered with or truncated since they were laid down.
🚀 Pro-Tip: Pipe the output to grep if you only care about specific configuration directories like /etc.
Linux Tips & Tricks | © ngelinux.com | 9/17/2026