Stop your package manager from blind-siding you with configuration changes
Package Management (Apt/Dnf/Pacman Internals)
Stop your package manager from blind-siding you with configuration changes
🧩 The Challenge
You finally run a long-overdue upgrade on a production web server, and suddenly your Nginx config is nuked because the package maintainer decided a new default was better than your carefully tuned one. Waking up to a down site because of a hidden configuration overwrite is a special kind of hell I wouldn’t wish on anyone.
💡 The Fix
Start using the built-in diff capabilities of your package manager before you hit the yes key. It saves you from guessing whether a package update is about to overwrite your custom local settings.
apt-get dist-upgrade --dry-run
or for dnf: dnf upgrade --setopt=tsflags=test
⚙️ Why It Works
These flags simulate the entire transaction process without actually touching your filesystem, letting you see exactly which configuration files are flagged for replacement. It pulls the curtain back so you can inspect potential conflicts before they become real-world problems.
🚀 Pro-Tip: If you use Debian or Ubuntu, check /etc/apt/apt.conf.d/ to set Dpkg::Options {“–force-confold”}; so the system never overwrites your config files without asking.
Linux Tips & Tricks | © ngelinux.com | 7/26/2026
