When a package update goes wrong, it can leave your system in a mess. I’ve seen this go wrong when a dependency is broken or a package is not properly configured. This is where dpkg and apt come to the rescue. As of 2026, these tools remain essential for managing packages on Debian-based systems, including Ubuntu and its derivatives. In this article, we’ll explore how to recover from a botched package update using dpkg and apt history.
I’ve seen this go wrong when a package upgrade fails - it can be frustrating and even lead to system instability. When this happens, it’s essential to have a plan in place to recover your system. Fortunately, with the right tools and techniques, recovering from a botched package upgrade is relatively straightforward. In this article, we’ll explore how to use apt and snapshotting to recover from a failed package upgrade on a Linux system.
When managing packages on a Linux system, you’ve likely encountered version conflicts, especially when dealing with dependencies. I’ve seen this go wrong when trying to update a package, only to find that it breaks another package that depends on it. In my experience, apt remains a crucial tool for managing packages, and understanding how to use apt-mark and pinning can help avoid these kinds of dependency conflicts.