Package Management (Apt/Dnf/Pacman Internals)

Stop your package manager from stalling on interactive config prompts

🧩 The Challenge

Every time I run a massive unattended upgrade, some random package decides it’s the right time to ask me a question about a config file change, leaving my automation hanging for hours. It drives me absolutely nuts when a server deployment just sits there doing nothing because a maintainer didn’t set their package defaults to non-interactive.

💡 The Fix

You have to force the environment variables that tell the package manager to stop asking for human input and just keep the existing config file. This ensures your scripts actually finish while keeping your production settings untouched.

DEBIAN_FRONTEND=noninteractive apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install <package_name>

⚙️ Why It Works

Setting the frontend variable shuts off the ncurses prompts, while the Dpkg options tell the backend to prioritize the existing version of any modified configuration files over the package maintainer’s version. It stops the silent hanging dead in its tracks.

🚀 Pro-Tip: Alias this command if you’re doing this more than twice a week.

Linux Tips & Tricks | © ngelinux.com | 7/17/2026