Skip to content

Tags: apt

  • Why SOW Uses One Payload Tree per Repository

    By Vonng In Design 738 words 4 min

    VonngDesignrepositorypoolrpmaptcompatibilitydecision

    Why SOW Uses One Payload Tree per Repository

    This decision was drafted on 2026-08-05 during the pre-v0.2 release design consolidation and shipped in SOW v0.2.0 on 2026-08-08. It remains the layout contract in v0.3 and v0.4. It records an architecture choice, not a blanket compatibility claim: …

    This decision was drafted on 2026-08-05 during the pre-v0.2 release design consolidation and shipped in SOW v0.2.0 on 2026-08-08. It remains the layout contract in v0.3 and v0.4. It records an architecture choice, not a blanket compatibility claim: …

  • Platforms & Integrations

    In Reference

    Referencerpmdebyumaptobject-storage

    This page defines the environments SOW ships for, the storage semantics it requires, and the exact scope of its automated integrations. Repository generation happens inside the SOW binary; a real package manager remains the final check for a deployed …

    This page defines the environments SOW ships for, the storage semantics it requires, and the exact scope of its automated integrations. Repository generation happens inside the SOW binary; a real package manager remains the final check for a deployed …

  • Signing Model

    In Features

    Featuresigningrpmapt

    There are two different questions a client can ask about a repository, and SOW answers them with two separate mechanisms. Confusing them is the most common source of “I signed it but dnf still complains”, so this page starts by pulling them apart. …

    There are two different questions a client can ask about a repository, and SOW answers them with two separate mechanisms. Confusing them is the most common source of “I signed it but dnf still complains”, so this page starts by pulling them apart. …

  • Sign Your Repository

    In Tutorials

    Tutorialsigningaptyum

    SOW has two independent signing paths: Path Output Client control RPM metadata repodata/repomd.xml.asc repo_gpgcheck=1 APT metadata InRelease and Release.gpg Signed-By RPM package body embedded RPM signature gpgcheck=1 APT trusts package hashes …

    SOW has two independent signing paths: Path Output Client control RPM metadata repodata/repomd.xml.asc repo_gpgcheck=1 APT metadata InRelease and Release.gpg Signed-By RPM package body embedded RPM signature gpgcheck=1 APT trusts package hashes …

  • Tutorials

    In Tutorials

    Tutorialyumaptsigningpublish

    Each tutorial starts from a new workspace. Commands are intended to be run in order; replace uppercase placeholders and package paths for your environment. If you have not installed SOW yet, start with Installation and Quick Start. The tutorials …

    Each tutorial starts from a new workspace. Commands are intended to be run in order; replace uppercase placeholders and package paths for your environment. If you have not installed SOW yet, start with Installation and Quick Start. The tutorials …

  • Build an APT Repository

    In Tutorials

    Tutorialaptdebmanageddist

    This tutorial creates a new Managed DEB repository. You need a writable directory, and one or more DEB files. 1. Create the workspace mkdir -p /srv/sow cd /srv/sow sow init . sow repo new pigsty sow dist new trixie --format deb -r pigsty The Dist …

    This tutorial creates a new Managed DEB repository. You need a writable directory, and one or more DEB files. 1. Create the workspace mkdir -p /srv/sow cd /srv/sow sow init . sow repo new pigsty sow dist new trixie --format deb -r pigsty The Dist …