The utility for building of AlmaLinux distributions (repos, ISO images).
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Lubomír Sedlář 111af836ea Include all test fixtures in source tarball
Listing all possible file extensions is error-prone.

Signed-off-by: Lubomír Sedlář <>
5 years ago
bin ostree: Fix handler crash without commit ID 5 years ago
contrib/yum-dnf-compare gather: Only parse pungi log once 6 years ago
doc 4.1.29 release 5 years ago
pungi Drop the memory saving code 5 years ago
pungi_utils unified_isos: Add extra variants to metadata 5 years ago
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 6 years ago
tests extra-iso: Use correct efiboot.img file 5 years ago
.gitignore Log PDC communications and info for modular composes 6 years ago
AUTHORS extra-files: Write a metadata file enumerating extra files 7 years ago
COPYING Remove FSF address from comments 7 years ago
GPL Update GPL to latest version from 8 years ago Include all test fixtures in source tarball 5 years ago
Makefile Extract only first version from specfile 7 years ago Add README 8 years ago
TODO Initial code merge for Pungi 4.0. 9 years ago
git-changelog Use Python 3 print function 6 years ago
pungi.spec 4.1.29 release 5 years ago 4.1.29 release 5 years ago
tox.ini Ignore more pycodestyle warnings 6 years ago


Pungi is a distribution compose tool.

Composes are release snapshots that contain release deliverables such as:

  • installation trees
    • RPMs
    • repodata
    • comps
  • (bootable) ISOs
  • kickstart trees
    • anaconda images
    • images for PXE boot

Tool overview

Pungi consists of multiple separate executables backed by a common library.

The main entry-point is the pungi-koji script. It loads the compose configuration and kicks off the process. Composing itself is done in phases. Each phase is responsible for generating some artifacts on disk and updating the compose object that is threaded through all the phases.

Pungi itself does not actually do that much. Most of the actual work is delegated to separate executables. Pungi just makes sure that all the commands are invoked in the appropriate order and with correct arguments. It also moves the artifacts to correct locations.