<?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 Pi Stack</title>
    <link>https://www.pistack.xyz/tags/debian/</link>
    <description>Recent content in Debian on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 11:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/debian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Aptly vs Reprepro vs Apt-mirror: Self-Hosted Debian Package Repository Management 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-02-aptly-vs-reprepro-vs-apt-mirror-self-hosted-debian-package-repository-guide/</link>
      <pubDate>Sat, 02 May 2026 11:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-02-aptly-vs-reprepro-vs-apt-mirror-self-hosted-debian-package-repository-guide/</guid>
      <description>&lt;p&gt;Managing Debian and Ubuntu packages across multiple servers requires a reliable, self-hosted package repository. Whether you need to distribute custom-built &lt;code&gt;.deb&lt;/code&gt; files, mirror upstream repositories for offline access, or maintain a stable snapshot of package versions for reproducible deployments, a self-hosted apt repository gives you full control over your software supply chain.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
