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
Stepan Oksanichenko 60a347a4a2 Merge pull request 'ALBS-1030: Generate Devel section in packages.json' (#14) from ALBS-1030 into al_master
Reviewed-on: #14
7 months ago
contrib/yum-dnf-compare gather: Only parse pungi log once 6 years ago
doc - Changelog is updated 7 months ago
pungi ALBS-1030: Generate Devel section in packages.json 7 months ago
pungi_utils Format code 3 years ago
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 6 years ago
tests osbuild: test passing of rich repos from configuration 7 months ago
.gitignore nomacboot option for livemedia koji tasks 2 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 Use pytest instead of nosetests 3 years ago Correct irc network name & add matrix room 2 years ago
TODO Initial code merge for Pungi 4.0. 9 years ago
git-changelog git-changelog: Fix running on Python 3 4 years ago
pungi.spec - Changelog is updated 7 months ago
requirements.txt - fedmsg is removed as not needed 11 months ago - Changelog is updated 7 months ago
test-requirements.txt Use requirements.txt 3 years ago
tox.ini Involve bandit 2 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.