<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Package-Management on Linux Security</title><link>https://linuxtransfer.com/tags/package-management/</link><description>Recent content in Package-Management on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 10:01:55 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/package-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Dependency Hell: Using apt-mark to Pin Packages in Debian-Based Systems</title><link>https://linuxtransfer.com/post/2026-05-15-taming-dependency-hell-using-apt-mark-to-pin-/</link><pubDate>Fri, 15 May 2026 10:01:55 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-05-15-taming-dependency-hell-using-apt-mark-to-pin-/</guid><description>&lt;h2 id="introduction-to-dependency-hell">Introduction to Dependency Hell&lt;/h2>
&lt;p>I&amp;rsquo;ve seen this go wrong when you&amp;rsquo;re in the middle of a critical project and a package update breaks a dependency, causing system instability. In Debian-based systems, &lt;code>apt-mark&lt;/code> is a useful tool for pinning packages and avoiding this kind of chaos. It&amp;rsquo;s not a silver bullet, but it can help prevent packages from being automatically removed or upgraded, which can cause conflicts.&lt;/p>
&lt;h2 id="what-is-apt-mark">What is apt-mark?&lt;/h2>
&lt;p>&lt;code>apt-mark&lt;/code> is a command-line tool that allows you to mark packages as automatically installed or manually installed. This can be a lifesaver when you need to prevent a package from being automatically upgraded to a newer version that may cause conflicts. Don&amp;rsquo;t bother with trying to manually manage dependencies - &lt;code>apt-mark&lt;/code> makes it easy to pin packages to a specific version.&lt;/p></description></item></channel></rss>