<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rollback on Linux Security</title><link>https://linuxtransfer.com/tags/rollback/</link><description>Recent content in Rollback on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Nov 2026 09:57:37 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/rollback/index.xml" rel="self" type="application/rss+xml"/><item><title>Rolling Back a Broken Flatpak Update</title><link>https://linuxtransfer.com/post/2026-11-15-rolling-back-a-broken-flatpak-update-on-a-pro/</link><pubDate>Sun, 15 Nov 2026 09:57:37 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-11-15-rolling-back-a-broken-flatpak-update-on-a-pro/</guid><description>&lt;h2 id="rolling-back-a-broken-flatpak-update-on-a-production-server">Rolling Back a Broken Flatpak Update on a Production Server&lt;/h2>
&lt;p>Flatpak is great for sandboxed desktop apps, but on a production box you’re still dealing with real‑world workloads. A bad runtime bump can bring an entire workflow to a halt or expose a vulnerability if the new runtime regresses. The silver lining? Flatpak keeps a full history of every branch you’ve ever installed, so you can undo a bad update without touching other apps.&lt;/p></description></item></channel></rss>