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ář c9f34b6684 gather: Only parse pungi log once
No need to read the file three times, we can just get all the data in
one go.

Signed-off-by: Lubomír Sedlář <>
6 years ago
bin ostree: Add notification handler to wait for signature 6 years ago
contrib/yum-dnf-compare gather: Only parse pungi log once 6 years ago
doc gather: Report missing comps packages 6 years ago
pungi gather: Only parse pungi log once 6 years ago
pungi_utils unified-iso: Only link to non-empty variants 6 years ago
share Add support for modular composes 7 years ago
tests gather: Only parse pungi log once 6 years ago
.gitignore Update makefile targets for testing 8 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 setup: Update manifest to include doc images 6 years ago
Makefile Extract only first version from specfile 7 years ago Add README 8 years ago
RELEASE-NOTES Rename product_* to release_*. 8 years ago
TODO Initial code merge for Pungi 4.0. 9 years ago
git-changelog Fix changelog generator script 6 years ago
pungi.spec 4.1.17 release 6 years ago 4.1.17 release 6 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.