<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debian on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/debian/</link>
    <description>Recent content in Debian on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 09 Jun 2026 09:04:29 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/debian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Dependency Chaos with Package Pinning in Debian-Based Systems</title>
      <link>https://linuxeries.org/post/2026-06-09-taming-dependency-chaos-with-package-pinning-/</link>
      <pubDate>Tue, 09 Jun 2026 09:04:29 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-06-09-taming-dependency-chaos-with-package-pinning-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-package-pinning&#34;&gt;Introduction to Package Pinning&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve found package pinning to be a lifesaver on Debian-based systems, allowing you to specify the exact version of a package to install or keep. This is particularly useful when managing dependencies and avoiding potential conflicts or compatibility issues. I&amp;rsquo;ve seen this go wrong when a package update breaks a critical application, so it&amp;rsquo;s essential to have control over package versions.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-package-pinning&#34;&gt;Understanding Package Pinning&lt;/h2&gt;&#xA;&lt;p&gt;To pin a package, you&amp;rsquo;ll need to create a file in the &lt;code&gt;/etc/apt/preferences.d/&lt;/code&gt; directory with a &lt;code&gt;.pref&lt;/code&gt; extension. This file should contain the package name and the desired version. For example, to pin the &lt;code&gt;nginx&lt;/code&gt; package to version &lt;code&gt;1.23.4&lt;/code&gt;, you would create a file called &lt;code&gt;nginx.pref&lt;/code&gt; with the following contents:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
