The utility for building of AlmaLinux distributions (repos, ISO images).
b32c8f3e5e
Generally we want all packages to come from particular event. There are two exceptions: packages configured via `pkgset_koji_builds` are pulled in by exact NVR and skip event; and modules in `pkgset_koji_modules` are pulled in by NSVC and also ignore events. However, the modular content tag did honor event, and could lead to a crashed compose if the content tag did not exist at the configured event. This patch is a slightly too big hammer. It ignores events for all modules, not just ones configured by explicit NSVC. It's not a huge deal as the content tags are created before the corresponding module build is created, and once all rpm builds are tagged into the content tag, MBS will never change it again. JIRA: RHELCMP-12765 Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com> |
||
---|---|---|
contrib | ||
doc | ||
pungi | ||
pungi_utils | ||
share | ||
tests | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
git-changelog | ||
GPL | ||
Makefile | ||
MANIFEST.in | ||
pungi.spec | ||
README.md | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
TODO | ||
tox.ini |
Pungi
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.
Links
- Documentation: https://docs.pagure.org/pungi/
- Upstream GIT: https://pagure.io/pungi/
- Issue tracker: https://pagure.io/pungi/issues
- Questions can be asked in the #fedora-releng IRC channel on irc.libera.chat
or in the matrix room
#releng:fedoraproject.org