<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apt on Linux Security</title><link>https://linuxtransfer.com/tags/apt/</link><description>Recent content in Apt on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 Jun 2026 10:36:07 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/apt/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Package Versions with apt-mark and pinning to Avoid Dependency Conflicts</title><link>https://linuxtransfer.com/post/2026-06-07-taming-package-versions-with-apt-mark-and-pin/</link><pubDate>Sun, 07 Jun 2026 10:36:07 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-06-07-taming-package-versions-with-apt-mark-and-pin/</guid><description>&lt;h2 id="introduction-to-package-versioning">Introduction to Package Versioning&lt;/h2>
&lt;p>When managing packages on a Linux system, you&amp;rsquo;ve likely encountered version conflicts, especially when dealing with dependencies. I&amp;rsquo;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, &lt;code>apt&lt;/code> remains a crucial tool for managing packages, and understanding how to use &lt;code>apt-mark&lt;/code> and pinning can help avoid these kinds of dependency conflicts.&lt;/p></description></item></channel></rss>