The utility for building of AlmaLinux distributions (repos, ISO images).
bcc440491e
The initial version of the filtered the latest builds at the start. That doesn't matter in many cases: * When there are no lookaside repos, there is generally a single version of each package. * When lookaside repos do not overlap with compose repos, or contain only older versions. It is however a problem when the lookaside repos contain higher version of a package than what is in a compose repo, and some package explicitly requires the older version. Consider this scenario: * lookaside contains bar-1.1 * compose repo contains bar-1.0 and foo-1.0 * foo-1.0 `Requires: bar < 1.1` The original code would filter out the bar-1.0 package, and then fail on unresolved dependencies. This patch moves the computation of latest packages much later, to part of code where all options to satisfy a dependency are selected and the best match is chosen. At that point if there are multiple versions available, we do want the latest one. JIRA: SPMM-13483 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