yum

SOW 0.5.0 focuses on adopting SOW for existing flat YUM repositories. The main addition is sow create --metadata-timestamp SECONDS: publishers can retain a valid publication time when replacing another metadata generator, including repositories used …

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 …

pgsty/infra-pkg is the upstream build source for Pigsty Infra packages. This tutorial assumes the dual-architecture RPMs and DEBs already exist and covers the second half of the job: turning that pile of packages into a real, consumable, maintainable …

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 …

The tutorials cover new Managed workspaces and migration of existing Plain repositories. 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 …

This guide covers a flat directory of RPMs and repodata/, such as a repository previously built with createrepo_c. It uses Plain sow create, without creating a Managed workspace. The publication-time option requires SOW 0.5.0 or later. 1. Establish …

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