Skip to content
zoryn/ maintainer-assistant

Quick start

From a brand-new ALT Linux install to a sisyphus subtask in two zoryn commands at the core (plus a few helpers the first time around).

1. Initial setup

Run once per developer machine. zoryn gen environment creates ~/.zoryn, the SSH aliases for gitery/gyle, ~/.hasher/config, ~/.rpmmacros, and — if you don't already have them — an ed25519 SSH key and a 4096-bit RSA GPG key.

# Generate configuration files (~/.zoryn, ~/.ssh/config, ~/.hasher/config, ~/.rpmmacros, ~/.gitconfig)
zoryn gen environment

# Add a remote builder (optional — only needed for builds off your local machine)
zoryn builder add

gen environment is interactive by default; for scripted provisioning see the zoryn gen environment reference.

2. Working with packages

The per-package cycle — the actual day-to-day loop — usually looks like this:

# Clone a package from sisyphus
zoryn clone mypackage
cd mypackage

# Update package to new upstream version (fetch → merge → spec → changelog → build)
zoryn up

# Submit to sisyphus (commit, tag, push, task new/add — one command)
zoryn submit

# Submit to a stable branch with auto-dependencies on sisyphus tasks
zoryn submit -B p11

# Check if a newer upstream version is available
zoryn check version

# Find the spec file in a gear repo
zoryn spec find

Two core commands — zoryn up and zoryn submit — plus helpers get you a ready sisyphus subtask. Everything else (clone, check, spec find) is auxiliary for the edges.

  • zoryn up — the 14-stage pipeline with --continue / --abort / --stage
  • zoryn submit — subtask positioning with --with, replacement with --replace
  • zoryn task manage — interactive TUI for approving and running tasks
  • Configuration — tune ~/.zoryn once, override per-package in .gear/version-up