Skip to content

apt

6 pages
  • Why SOW Uses One Payload Tree per Repository

    By Vonng In Design 686 words 4 min

    VonngDesignrepositorypoolrpmaptcompatibilitydecision

    Why SOW Uses One Payload Tree per Repository

    This decision was drafted on 2026-08-05 and shipped in SOW v0.2.0 on 2026-08-08. SOW 0.5.0 still uses this layout. Each Repository stores one package tree and lets its distribution views reference that tree. Decision Each SOW Repository owns one …

    This decision was drafted on 2026-08-05 and shipped in SOW v0.2.0 on 2026-08-08. SOW 0.5.0 still uses this layout. Each Repository stores one package tree and lets its distribution views reference that tree. Decision Each SOW Repository owns one …

  • Platforms & Integrations

    In Reference

    Referencerpmdebyumaptobject-storage

    SOW builds RPM and DEB repository files on Linux and macOS. Choose a supported local filesystem for the workspace, then configure HTTP or storage access for clients. Platforms Operating system amd64 arm64 Release formats Linux Yes Yes Archive, RPM, …

    SOW builds RPM and DEB repository files on Linux and macOS. Choose a supported local filesystem for the workspace, then configure HTTP or storage access for clients. Platforms Operating system amd64 arm64 Release formats Linux Yes Yes Archive, RPM, …

  • Signing Model

    In Features

    Featuresigningrpmapt

    Configure metadata signing to let clients verify repository indexes. Configure RPM package signing separately when clients also need to verify signatures embedded in RPM files. What gets signed Setting Signed content Output Client setting …

    Configure metadata signing to let clients verify repository indexes. Configure RPM package signing separately when clients also need to verify signatures embedded in RPM files. What gets signed Setting Signed content Output Client setting …

  • Sign Your Repository

    In Tutorials

    Tutorialsigningaptyum

    Repository signing has two layers: metadata signatures and RPM package signatures. Configure each layer separately: Path Output Client control RPM metadata repodata/repomd.xml.asc repo_gpgcheck=1 APT metadata InRelease and Release.gpg Signed-By RPM …

    Repository signing has two layers: metadata signatures and RPM package signatures. Configure each layer separately: Path Output Client control RPM metadata repodata/repomd.xml.asc repo_gpgcheck=1 APT metadata InRelease and Release.gpg Signed-By RPM …

  • Tutorials

    In Tutorials

    Tutorialyumaptsigningpublish

    These tutorials cover repository creation, signing, publication, and updates. Start with Installation if you have not installed SOW. Migrate an Existing YUM Repository Replace the metadata generator for a flat RPM repository while preserving …

    These tutorials cover repository creation, signing, publication, and updates. Start with Installation if you have not installed SOW. Migrate an Existing YUM Repository Replace the metadata generator for a flat RPM repository while preserving …

  • Build an APT Repository

    In Tutorials

    Tutorialaptdebmanageddist

    This tutorial creates a new Managed DEB repository. Install SOW and Python 3, and prepare DEB files built for your clients. Use an empty /srv/sow directory that your user can create and write to, or substitute another writable path. 1. Create the …

    This tutorial creates a new Managed DEB repository. Install SOW and Python 3, and prepare DEB files built for your clients. Use an empty /srv/sow directory that your user can create and write to, or substitute another writable path. 1. Create the …