Build a YUM Repository

Mon, 01 Jan 0001 00:00:00 +0000

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 is an identifier chosen by you. SOW does not infer an operating-system release from el9.

Build an APT Repository

Mon, 01 Jan 0001 00:00:00 +0000

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 name becomes the APT suite. It is an identifier chosen by you; SOW does not infer distribution semantics from trixie.

Tutorials

Mon, 01 Jan 0001 00:00:00 +0000

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 below cover the managed repository path.

Build a YUM Repository

A managed RPM repository with per-architecture views, noarch projection, debuginfo filtering, version limits, and a working dnf client configuration.

Build an APT Repository

A managed DEB repository with a Debian-style pool, by-hash indexes, and a deb822 client configuration.

Sign Your Repository

Mon, 01 Jan 0001 00:00:00 +0000

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 through the signed Release; SOW does not re-sign DEB package bodies. Start with metadata signing. Add RPM package signing only when you own the signing policy for those package bytes.

1. Create a dedicated key

The commands below create an unencrypted example key. Use a protected key and a passphrase reference for production; see the configuration reference.

Serve and Publish Repositories

Mon, 01 Jan 0001 00:00:00 +0000

SOW writes static files; it is not an HTTP server. This guide keeps the writable Workspace separate from the path Nginx serves.

Public and private paths

Mode	Public unit	Never serve
Plain	the directory passed to `sow create`	transient `.sow-plain-stage-*` output; no durable journal
Managed	one Repository’s complete `pool/ + dists/` tree	Workspace `sow.yml`, `.sow/`, SQLite, locks, journals, staging

For the workspace in First Workspace, the source Repository is /srv/sow/local. Do not make /srv/sow the document root.

Build the pigsty-infra Repository

Mon, 01 Jan 0001 00:00:00 +0000

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 repository named infra.

1. Put the packages under ~/repo

This tutorial uses the fixed path ~/repo throughout. Copy the existing packages into two input directories:

mkdir -p ~/repo/packages/rpm ~/repo/packages/deb
cp ~/pgsty/infra-pkg/dist/rpm/*.rpm ~/repo/packages/rpm/
cp ~/pgsty/infra-pkg/dist/deb/*.deb ~/repo/packages/deb/

Confirm that all four format-by-architecture cells contain real payloads:

Tutorial on SOW

Build a YUM Repository

1. Create the workspace

Build an APT Repository

1. Create the workspace

Tutorials

Sign Your Repository

1. Create a dedicated key

Serve and Publish Repositories

Public and private paths

Build the pigsty-infra Repository

1. Put the packages under ~/repo