<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dpkg on Linux Security</title><link>https://linuxtransfer.com/tags/dpkg/</link><description>Recent content in Dpkg on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Jul 2026 10:36:58 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/dpkg/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering from a Botched Package Update with Dpkg and APT History</title><link>https://linuxtransfer.com/post/2026-07-17-recovering-from-a-botched-package-update-with/</link><pubDate>Fri, 17 Jul 2026 10:36:58 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-07-17-recovering-from-a-botched-package-update-with/</guid><description>&lt;h2 id="introduction-to-package-recovery">Introduction to Package Recovery&lt;/h2>
&lt;p>When a package update goes wrong, it can leave your system in a mess. I&amp;rsquo;ve seen this go wrong when a dependency is broken or a package is not properly configured. This is where &lt;code>dpkg&lt;/code> and &lt;code>apt&lt;/code> 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&amp;rsquo;ll explore how to recover from a botched package update using &lt;code>dpkg&lt;/code> and &lt;code>apt&lt;/code> history.&lt;/p></description></item></channel></rss>