<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recovery on Linux Security</title><link>https://linuxtransfer.com/tags/recovery/</link><description>Recent content in Recovery on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 10 Jul 2026 11:49:45 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering from a Botched Package Upgrade with apt and snapshotting</title><link>https://linuxtransfer.com/post/2026-07-10-recovering-from-a-botched-package-upgrade-wit/</link><pubDate>Fri, 10 Jul 2026 11:49:45 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-07-10-recovering-from-a-botched-package-upgrade-wit/</guid><description>&lt;h2 id="introduction-to-recovery">Introduction to Recovery&lt;/h2>
&lt;p>I&amp;rsquo;ve seen this go wrong when a package upgrade fails - it can be frustrating and even lead to system instability. When this happens, it&amp;rsquo;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&amp;rsquo;ll explore how to use &lt;code>apt&lt;/code> and snapshotting to recover from a failed package upgrade on a Linux system.&lt;/p></description></item></channel></rss>