<?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 Café</title>
    <link>https://mrtomlinux.org/tags/apt/</link>
    <description>Recent content in Apt on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 15 May 2026 10:03:43 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/apt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Dependency Chaos with Apt Pinning on a Small Debian Server</title>
      <link>https://mrtomlinux.org/post/2026-05-15-taming-dependency-chaos-with-apt-pinning-on-a/</link>
      <pubDate>Fri, 15 May 2026 10:03:43 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-15-taming-dependency-chaos-with-apt-pinning-on-a/</guid>
      <description>&lt;h2 id=&#34;introduction-to-apt-pinning&#34;&gt;Introduction to Apt Pinning&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when you&amp;rsquo;re managing a small Debian server and dependencies become a challenge. That&amp;rsquo;s where apt pinning comes in – a feature that lets you control the version of packages installed on your system. On Debian-based systems, &lt;code&gt;apt&lt;/code&gt; is the package manager of choice, providing a robust way to manage dependencies and install software. However, when you need to ensure a specific package version is used, apt pinning is your friend.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
